This commit is contained in:
@@ -31,6 +31,7 @@ All platforms and browsers
|
||||
- IMPLEMENTED / NOT TESTED: Login, doesn't have any ui if failed login, maybe a red frowny face icon? :)
|
||||
- IMPLEMENTED / NOT TESTED: need clear buttons on pw and login
|
||||
- IMPLEMENTED / NOT TESTED: Numeric input fields don't give numeric keyboard
|
||||
- Navigation guard: navigate away with unsaved changes should warn and prevent but have option to continue anyway
|
||||
- Save on broken rules in Widget edit form it's not clear that save does nothing if there are broken rules. Button should be deactivated or there should be a message if you click on it or something.
|
||||
- Red outline and inactive seems ideal
|
||||
- Save button placement, not sure I like having to scroll down the page to save on small format screens where there is potentially going to be a *lot* of scrolling needed which hides the info box etc
|
||||
@@ -70,6 +71,22 @@ All platforms and browsers
|
||||
- Move help menu item in shell into menu as bottom item instead
|
||||
- TODO: CODE THIS FOR THIS MENU ISSUE
|
||||
- Just added ability to send info to store that is picked up by nav menu
|
||||
- REQUIREMENTS
|
||||
- Global Help link on *every* page
|
||||
- will change on each page
|
||||
- Global Logout link on every page
|
||||
- Unchanging
|
||||
- Probably more global page items
|
||||
- Menu supports dividers
|
||||
- Menu has a context section and a global section
|
||||
- One set of menu items only not two separate ones internally
|
||||
- Context items are at the top, then a divider, then the global ones at the bottom
|
||||
- Caller sets if it's contextual or not to adapt colour of app bar, but otherwise it's the same exact menu all the time
|
||||
- Caller should be able to set items colour so (for example) Save can be redded out when not savable
|
||||
- Caller should be able to set the ENABLED property so it can handle different states
|
||||
- Maybe a change item event that takes a key and updates it rather than refreshing the whole menu basis on state change?
|
||||
- I.E. so that can change save button enabled and colour when state of form broken rules changes?
|
||||
|
||||
|
||||
|
||||
iPad
|
||||
|
||||
Reference in New Issue
Block a user