Editing Legacy Maemo 5 Documentation/Human Interface Guidelines/View Menu
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 19: | Line 19: | ||
Avoid any use of submenus beyond what fits in the 10 menu item slots in the View menu. Even just removing those menu commands that do not fit, should be considered. | Avoid any use of submenus beyond what fits in the 10 menu item slots in the View menu. Even just removing those menu commands that do not fit, should be considered. | ||
- | The fallback way to support additional menu items (in corner cases) is to have an menu item in the view menu | + | The fallback way to support additional menu items (in corner cases) is to have an menu item in the view menu open a dialog, which has the action area removed, and contains a dialog wide grid of command buttons in two columns. Visually this is quite similar to the view menu itself. |
The less menu items, the better. This is important not only because there are a limited number of items allowed within Hildon, but also because it is good practice to limit the amount of menu items a user is forced to navigate through to achieve a particular action. Again, if some other widget can perform an action within the application's interface, do not include a menu item for it. | The less menu items, the better. This is important not only because there are a limited number of items allowed within Hildon, but also because it is good practice to limit the amount of menu items a user is forced to navigate through to achieve a particular action. Again, if some other widget can perform an action within the application's interface, do not include a menu item for it. |
Learn more about Contributing to the wiki.