This project is abandoned and its default file will likely not work with the most recent version of Minecraft. Whether this project is out of date or its author has marked it as abandoned, this project is no longer maintained.
Development on this plugin has stopped, and all further development is on the much better GUI Creator
1.6.1 swaps the player panel with the screen panel. I added some more examples in the zip, and added support for bPermissions and PermissionsEx (they were already supported it seems but now they are 'officially' supported :) )
Do you mean having buttons that execute bPermissions commands (whitelisting players, etc.)? If so, that's already there.
If you mean controlling what buttons are visible when bPermissions is being used on the server, I'll have a look at adding it with PermissionsEx in a couple of days.
@RustyDagger
Why don't you just try it? It takes two minutes and I don't think it interferes with any other plugin.
What you say about the menu isn't right, the main menu only needs to have one button visible (a top level 'Main' one, for example). The Main screen button in the screenshot links to two sub screens, which link to another one, etc. None of the sbuscreens show up in the main navigation area.
Swapping the player area (when it's visible) and the navigation area might be worth doing though - I'll look into tit.
Another thing that's bugging me is the players being at the top of the page people tend to read top to bottom left to right so having the player data that is some what useless it tends to get looked at first. I think more important things like other pages should be at the top and less important things like the player list that may only be used for 1 or 2 buttons on the page should be at the bottom.
Any how the whole page to page thing is pretty confusing its like there are 2 ways to do it but no way to control 1 of them? personaly i find the menu with the buttons annoying as it lists every page and its not really needed more than capable of using linkbuttons to add links to where I think the user should be able to go to.
@RustyDagger
There's a lot more space than you think (considering it's only 427 x 240 to work with).
The way it works is that the player section will only appear if a button on the screen needs it. Without it, more than 40 command buttons can fit on one screen. The idea was never to add support for all commands for a plugin on one page, only the most useful ones that either need a lot of typing or ones that you use sometimes and have to look up the syntax every time. (Permissions, for example.)
As for the menu, the bottom row (WorldEdit/Chats/Kits/Permissions in the screenshot) is the main menu. Those buttons don't link to each other, they are completely separate. Six fit on the screen and once, but any number can be added and the arrows used to move between them.
Think of them as favourite screens, the ones that get used most often. Above that are the link buttons for the selected screen (Permissions in the screenshot). This row of buttons only shows up if it's included in the screen file. Each link button can be set to jump to any other screen file, so although there are only six visible at the bottom, with one click the 50th screen can easily be reached, and this screen can have a reciprocal link button. So a complex plugin like WorldEdit could have its main screen as one of the favourites, and any less-used commands that couldn't fit on the main screen can be put on a screen much further down the list.
Using your example, this would be Worldedit general | Commandbook | Logblock |WorldEdit selection management (possibly much further down the list)
However, the way you suggest is pretty close to the top of my list. If you haven't tried it yet (I recommend you do - it's so much easier to see it in action than to read about it) you might not have noticed, but so far it's almost completely automated. The user has to do little more than create a list with a label and a command and the plugin does the rest. Tomorrow's update adds parameter boxes (again, completely automatically) and possibly submenus if I can get them right quick enough but the version after that should offer much more control for the power users.
So the link buttons adds a button to the bottom menu?
I'm just not seeing a whole lot of space for some thing as complex as world edit to fit on one page. the reason that bottom bar bothers me is because it is showing buttons to places that are not needed for example i would lay it out like.
Main
Worldedit general > selection management
Commandbook
Logblock
In the above example there is no need at all for selection management to link to commandbook or logblock all it needs is a simple back button that links back to the main world edit page and the same for the world edit page back to the main page. granted thats not as quick to use if you wanted to go from selection to logblock but it saves space on the page. when you have 8 + pages.
@limitless904
Not sure to be honest. I started writing it when it was RB 1240, then moved to RB 1317 and now RB 1337.
It doesn't use many exotic functions, but it's best to have a newer version of Bukkit and especially Spout.
When the plugin starts it should log a few messages. "[Admin GUI] Version 1.5 is running!" (or similar) is the one you should check for, but also any warnings that were logged.
What is the minimum craftbukkit requirement? I'm using quite an older version, but its not showing up as an error in /plugins... But of course, it doesn't appear to even be working.
@LivingTosti
Yours was the most recent plugin in the submissions forum when I was uploading this the first time. Odd coincidence :)
Use jd-gui to have a look in the jar.
Basically, everything in the Container is created when the user presses the button. The Container to change (there are five in my GUI) is removed from the popup, created again, and re-attached. A method calculates the first and last button that will fit in the panel and gets those items from the main list.
It's possible to just hide it and re-show it if nothing has changed though.
You might have seen my YouControl plugin too.
Is it oke if i decompile youre code, and see how you did it with switching pages?
Since i can't get it fixed, thanks!
@RustyDagger
That has already been added to the next version. Now it has six buttons with back/forward buttons, and each screen can contain buttons which link to any other screen. Testing it now.
arrrr you see adding the page linking idea i mentioned below would remove the 6 page limit or you could just add some next buttons for the list down the bottom I would much prefer to just be able to link to another page from a page using a button and not be forced to have the pages down the bottom there.
@RustyDagger
Currently, very little is hard-coded into the plugin. Originally, it was a personal project for my screen and the server I play on but since it has grown I'm now trying to make it as general as possible.
The only things left to change are the button sizes and positions. At the moment it's locked to four to a row, (and six screen buttons) because that's what fits comfortably on my settings (Large GUI). There is no limit on how many screen files (or screen nodes) there can be, but any more than six are currently cut off. I'm planning to make it so that more rows are added if needed.
The name of the file doesn't matter as the name on the tab comes from the name="" attribute. Files can be .XML or .txt (as long as they have only one root node). It's done this way so one file can contain multiple screens and also be called 'My_screen_version_1.7' (or something) without having all that show up on the tab. I will add some code that takes the name from the file if the name attribute is empty though.
Linking to other screens and having sub-screens is not implemented yet (but it's coming :) ). Fully customizing the size and position of all the buttons is also coming soon.
Hopefully that makes things a bit clearer :)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
HELP
1.6.1 swaps the player panel with the screen panel. I added some more examples in the zip, and added support for bPermissions and PermissionsEx (they were already supported it seems but now they are 'officially' supported :) )
Do you mean having buttons that execute bPermissions commands (whitelisting players, etc.)? If so, that's already there.
If you mean controlling what buttons are visible when bPermissions is being used on the server, I'll have a look at adding it with PermissionsEx in a couple of days.
bPermissions support? Or would you at least be interested on working with me making a bPermissions GUI? :3
@RustyDagger Why don't you just try it? It takes two minutes and I don't think it interferes with any other plugin.
What you say about the menu isn't right, the main menu only needs to have one button visible (a top level 'Main' one, for example). The Main screen button in the screenshot links to two sub screens, which link to another one, etc. None of the sbuscreens show up in the main navigation area.
Swapping the player area (when it's visible) and the navigation area might be worth doing though - I'll look into tit.
Another thing that's bugging me is the players being at the top of the page people tend to read top to bottom left to right so having the player data that is some what useless it tends to get looked at first. I think more important things like other pages should be at the top and less important things like the player list that may only be used for 1 or 2 buttons on the page should be at the bottom.
Any how the whole page to page thing is pretty confusing its like there are 2 ways to do it but no way to control 1 of them? personaly i find the menu with the buttons annoying as it lists every page and its not really needed more than capable of using linkbuttons to add links to where I think the user should be able to go to.
@Hoot215 It took a few days but it's now possible to do exactly what you suggested :)
Just for fun I recreated the original GUI, only this time it involved no code at all \o/
@RustyDagger And it's done :) Check out the Hierarchy.txt file to see how to do exactly (I think) as you wanted.
@RustyDagger There's a lot more space than you think (considering it's only 427 x 240 to work with).
The way it works is that the player section will only appear if a button on the screen needs it. Without it, more than 40 command buttons can fit on one screen. The idea was never to add support for all commands for a plugin on one page, only the most useful ones that either need a lot of typing or ones that you use sometimes and have to look up the syntax every time. (Permissions, for example.)
As for the menu, the bottom row (WorldEdit/Chats/Kits/Permissions in the screenshot) is the main menu. Those buttons don't link to each other, they are completely separate. Six fit on the screen and once, but any number can be added and the arrows used to move between them.
Think of them as favourite screens, the ones that get used most often. Above that are the link buttons for the selected screen (Permissions in the screenshot). This row of buttons only shows up if it's included in the screen file. Each link button can be set to jump to any other screen file, so although there are only six visible at the bottom, with one click the 50th screen can easily be reached, and this screen can have a reciprocal link button. So a complex plugin like WorldEdit could have its main screen as one of the favourites, and any less-used commands that couldn't fit on the main screen can be put on a screen much further down the list.
Using your example, this would be Worldedit general | Commandbook | Logblock |WorldEdit selection management (possibly much further down the list)
However, the way you suggest is pretty close to the top of my list. If you haven't tried it yet (I recommend you do - it's so much easier to see it in action than to read about it) you might not have noticed, but so far it's almost completely automated. The user has to do little more than create a list with a label and a command and the plugin does the rest. Tomorrow's update adds parameter boxes (again, completely automatically) and possibly submenus if I can get them right quick enough but the version after that should offer much more control for the power users.
So the link buttons adds a button to the bottom menu?
I'm just not seeing a whole lot of space for some thing as complex as world edit to fit on one page. the reason that bottom bar bothers me is because it is showing buttons to places that are not needed for example i would lay it out like.
Main Worldedit general > selection management Commandbook Logblock
In the above example there is no need at all for selection management to link to commandbook or logblock all it needs is a simple back button that links back to the main world edit page and the same for the world edit page back to the main page. granted thats not as quick to use if you wanted to go from selection to logblock but it saves space on the page. when you have 8 + pages.
@limitless904 Not sure to be honest. I started writing it when it was RB 1240, then moved to RB 1317 and now RB 1337.
It doesn't use many exotic functions, but it's best to have a newer version of Bukkit and especially Spout.
When the plugin starts it should log a few messages. "[Admin GUI] Version 1.5 is running!" (or similar) is the one you should check for, but also any warnings that were logged.
What is the minimum craftbukkit requirement? I'm using quite an older version, but its not showing up as an error in /plugins... But of course, it doesn't appear to even be working.
@LivingTosti Yours was the most recent plugin in the submissions forum when I was uploading this the first time. Odd coincidence :)
Use jd-gui to have a look in the jar.
Basically, everything in the Container is created when the user presses the button. The Container to change (there are five in my GUI) is removed from the popup, created again, and re-attached. A method calculates the first and last button that will fit in the panel and gets those items from the main list.
It's possible to just hide it and re-show it if nothing has changed though.
You might have seen my YouControl plugin too.
Is it oke if i decompile youre code, and see how you did it with switching pages?
Since i can't get it fixed, thanks!
Okay, 1.5 is out.
Now with unlimited screen pages, and buttons to link to any other screen.
Please read the warning as the screen file format changed slightly and any existing files will need to be updated.
@RustyDagger That has already been added to the next version. Now it has six buttons with back/forward buttons, and each screen can contain buttons which link to any other screen. Testing it now.
@benji28fr Did you give yourself (and any player that wants to use it) the Admin_GUI.can_open_GUI permission?
What key are you using to open it?
I can't run the plug in when I touch on the letter that I chose it nothing happens .
Who can help me (mp)
log: 08:51:31 [INFO] [Admin GUI] screens folder is plugins\Admin GUI\Screens 08:51:31 [INFO] [Admin GUI] Found 1 screen files. 08:51:31 [INFO] [Admin GUI] Created new document 08:51:31 [INFO] [Admin GUI] Successfully read screen file 0 08:51:31 [INFO] [Admin GUI] Version 1.4.1 Running!
@coldandtiard
arrrr you see adding the page linking idea i mentioned below would remove the 6 page limit or you could just add some next buttons for the list down the bottom I would much prefer to just be able to link to another page from a page using a button and not be forced to have the pages down the bottom there.
@RustyDagger Currently, very little is hard-coded into the plugin. Originally, it was a personal project for my screen and the server I play on but since it has grown I'm now trying to make it as general as possible.
The only things left to change are the button sizes and positions. At the moment it's locked to four to a row, (and six screen buttons) because that's what fits comfortably on my settings (Large GUI). There is no limit on how many screen files (or screen nodes) there can be, but any more than six are currently cut off. I'm planning to make it so that more rows are added if needed.
The name of the file doesn't matter as the name on the tab comes from the name="" attribute. Files can be .XML or .txt (as long as they have only one root node). It's done this way so one file can contain multiple screens and also be called 'My_screen_version_1.7' (or something) without having all that show up on the tab. I will add some code that takes the name from the file if the name attribute is empty though.
Linking to other screens and having sub-screens is not implemented yet (but it's coming :) ). Fully customizing the size and position of all the buttons is also coming soon.
Hopefully that makes things a bit clearer :)