-
Followers
Aurorablade (Assigned To) , Pilus
AttachmentsNo attachmentsAssociationsNo associationsActivityThe mock up sketch for the layout are now done and available here. It is ready for review.
A few things to note:
- You can navigate the 3 different windows with the 'Previous' and 'Next' buttons. No other buttons are functional
- The action area are blank, but that will be designed as part of ticket #91
Feel free to comment with feedback on the mock-up
Two things:
1) The left justify/right justify thing we talked about. Rather than trying to split the string with a delimiter, it seems like it would be more logical to simply have two extra fields (I.E. White1Left, White1Right, and White2Left and White2Right). That simplifies things for the end user by avoiding reserving a character for use in the description strings, makes it so the user doesn't have to remember said string.
2) Window/Page 1 and 2 seem to be the same as the simple item's menu. Rather than having a separate menu for the advanced menu, what about making the base item menu windows be the first and second windows you have with the Advanced menu, but on the second page, have a "Finish" button and an "Advanced Item Settings" button? The design would be closer to the current one (Basic info on first page, action info on the second page), and it would keep the advanced item information separated on the third, similar to what you have.
Tooltip Menu
Action Menu
Advanced Menu (This one is obviously rough, since it lacks a lot of the UI elements needed - The layout would be pretty much the same as your original design)
The idea being that the "advanced" button on the second page would be the "Convert to Advanced Item" button that is currently on the simple menu page. Alternatively, leave the menu as it is, with the tooltip and action information on a single window, then make a second tab for the Advanced attributes (Just moving the Advanced button)
Simple Item Menu with buttons moved
Advanced Item Menu "extension" from the Simple Item Menu
I also noticed that the entire Requirement concept seems to be removed. I know you'd talked about that, but is there anything planned to replace said system?Regarding 1)
It is my intention to have that covered with the Tooltip menu. There the user can add any tooltip to the item. Including some that contains information from the attributes for the item.
Regarding 2)
It is important to notice that the action list in the simple item menu and the action area in the advanced item menu are very different in both looks and content. The simple item menu was designed to fit on one page to make it more simple for the user. While the advanced menu does have some fields in common with the simple one, I do not believe that there is much won in implementing them together.
I like that way that the buttons have been moved around in your mock ups. I think it could be an idea to do that in the simple item menu.
Regarding the lacking requirements, then those can be created in the new action area. In the mock-up an example is given with an Event handler. That could just as well have been some sort of requirement that then got one port if the requirement is true and another port that will be activate when it is false.After some further consideration I can see that it will be a good idea to have the right and left text option as different input fields, even though it is possible to reach the same in the additional tool tip menu. In that way it will be easier for new users to use.on Jan 02, 2012 @ 11:16pm UTC * By Pilus
Assigned to set to AurorabladeStatus changed from Ready for review to AcceptedThe menu can now be implemented based on the description and feedback.
A few implementation requirements
R1 - The menu to be created inside one class, which should be named GHI_AdvancedItemMenu and placed inside the folder "AdvancedItemMenu"
R2 - The implementation will be a non-singleton class
R3 - An extra class named GHI_AdvancedItemMenuList should also be made to hold these classes
R4 - When created the AdvancedItemMenu (*AIM*) should initialize a new GHM menu. This menu should follow the layout discussed in this task. The Action area and buttons for it can be replaced by a dummy object. All scripts on buttons etc can be ignored for now.
R5 - The AIM should have a public function named "New". This function should call AnimatedShow on the menu frame and initialize it with empty information.
Hints:
- To avoid double work etc, aim to only create code that fulfills these requirements.
- The structure are almost completely identical to the simple item menu. Some inspiration can be gathered there, but be careful with copy pasting.
on Jan 08, 2012 @ 08:59pm UTC * By Aurorablade
Sorry been busy and haven't gotten up with you (and slept late today but not busy), i did upload what i did for it i was gonna ask you to look it over see what i may have done wrong.Np. Thanks for notifying me. For next time, please remember to change the status of the ticket to "In Progress" when you start working and then to "ready for review" or stuck if you strike problems or need feedback :)(In revision:579) Changes for re #90(In revision:581) re #90.
- Placed the action area in the advanced item menu.
- Fixed an issue with the item preview tooltip being shown on all pages.
- Adjusted some positioning of menu elements
- Removed redundant dummy objects
on Jan 11, 2012 @ 02:00am UTC * By Aurorablade
Status changed from Ready for review to In ProgressDoing adjustments to frame.
on Jan 11, 2012 @ 02:49am UTC * By Aurorablade
Need help with: blankwizard theme buttons do not color to theme.
Page 3 issue with aligning delete buttons.
There was a hieght issues but i fixed that as i was changeing width and not height, will commit later.(In revision:584) re #90. Fixed the problem with lacking color on wizard menu frames. It was an OnLoad script that got overwritten.
re #92. More progress on the action area.
on Jan 12, 2012 @ 12:34am UTC * By Aurorablade
Status changed from In Progress to Ready for reviewSome issues having trouble with: The delete buttons on page 3 can't push them over, the next/back buttons and cancel should be centered.(In revision:599) Re #90. Made some changes to the structure of the advanced item menuI have moved stuff a bit around to make better space for descriptions and take away empty space. On 3rd page I removed all "Edit" and "Delete" buttons. I intend that they should be replaced by a small edit and delete button in the end of each line in the list. In my opinion this makes the whole page less crowded and easier to use.
I am doing to work on a general GHM problem regarding the left side alignment. So far it seems to always be needed to put a dummy object in before buttons, texts and lists to make them stay aligned. I have found out what causes this and I will clean it up.
On this ticket in general then I believe that it is done.(In revision:600) Re #90. Fixed the design fault in GHM that made it necessary to use dummy objects in the beginning of the line to each correct alignment for some objects. More simple action menus needs to be cleared of dummy objects. Dummy objects might still be needed to give text objects a height
on Jan 16, 2012 @ 01:41am UTC * By Aurorablade
the Menu looks good now, Thanks.should we Mark it as fixed?Time ExpenditureLoading
The menu got 3 pages:
1. A page with standard information. All the stuff from the normal menu, excluding the action list and use text
2. Page reserved for dynamic actions
3. Page reserved for attributes and tooltip changes
When making a new item, this menu is reached by creating a normal item and then pressing the 'convert to advanced item' button. This moves all the information to the advanced menu.
When editing an item which got advanced info attached, it opens up the advanced menu directly.
A problem in the design could be that creating a dynamic action fully could require the use of attributes, but they are not set up before the 3rd page. A solution for that is to allow the creation of attributes from e.g. the action menu and then just only have them all displayed on the 3rd page.