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 1: | Line 1: | ||
| - | + | =View Menu= | |
| - | + | The View Menu does not have a traditional menu bar like desktop application menus have. The user activates the View Menu by pressing the application's title area. | |
| - | The | + | |
The View Menu can hold up to ten menu items and can be divided into two columns -- or one column when in portrait orientation. The View Menu can also include filters. As with selectable items within window views, menu items are in fact buttons, and have no submenus. | The View Menu can hold up to ten menu items and can be divided into two columns -- or one column when in portrait orientation. The View Menu can also include filters. As with selectable items within window views, menu items are in fact buttons, and have no submenus. | ||
| - | [[Image:view_menu.png| | + | [[Image:view_menu.png|400px]] |
| + | |||
| + | ''Figure 8: A view menu'' | ||
| + | |||
Place menu items that perform similar actions ("Previous" and "Next", for example) side by side within a View Menu, and place the most important menu items on the top of the view. | Place menu items that perform similar actions ("Previous" and "Next", for example) side by side within a View Menu, and place the most important menu items on the top of the view. | ||
| Line 14: | Line 16: | ||
==What if more menus are needed?== | ==What if more menus are needed?== | ||
| - | |||
Follow the principles stated in section 1.8, "Hildonizing an Interface," to keep the interface simple yet functional. | Follow the principles stated in section 1.8, "Hildonizing an Interface," to keep the interface simple yet functional. | ||
| Line 24: | Line 25: | ||
==Filters== | ==Filters== | ||
| - | |||
Along with typical menu items, you can also use filters within a View Menu. Filters are toggle buttons that can be used for presentation/sorting purposes. For example, sorting a list of contacts alphabetically, or changing the size of icons in a list. | Along with typical menu items, you can also use filters within a View Menu. Filters are toggle buttons that can be used for presentation/sorting purposes. For example, sorting a list of contacts alphabetically, or changing the size of icons in a list. | ||
| Line 31: | Line 31: | ||
Always present filters in groups. There should always be at least two menu filters (for example, a menu filter that sorts a list of email messages alphabetically and one that sorts them by date -- not just one filter for alphabetical sorting). | Always present filters in groups. There should always be at least two menu filters (for example, a menu filter that sorts a list of email messages alphabetically and one that sorts them by date -- not just one filter for alphabetical sorting). | ||
| - | |||
| + | ==Menu Keyboard Shortcuts== | ||
Sometimes it makes sense to add keyboard shortcuts to some actions that can also be performed via the View Menu. | Sometimes it makes sense to add keyboard shortcuts to some actions that can also be performed via the View Menu. | ||
If the shortcut performs a common action like creating something new, formatting the text as bold, or undoing a previous action, take care in utilizing common shortcuts that are generally used in other applications. For example, the previous mentioned actions are Ctrl+n, Ctrl+b, and Ctrl+z, respectively. | If the shortcut performs a common action like creating something new, formatting the text as bold, or undoing a previous action, take care in utilizing common shortcuts that are generally used in other applications. For example, the previous mentioned actions are Ctrl+n, Ctrl+b, and Ctrl+z, respectively. | ||
| - | |||
| + | ==Unavailable Menu Items== | ||
Even though it is a common and useful practice in desktop applications to make certain menu items unavailable (for example, "dimmed"), when their actions are not available, Hildon takes a different approach: the menu items must not be visible at all. Although dimmed menu items suggest actions that are unavailable, they can cramp menu space on the small screen and make interaction with available menu items more confusing. | Even though it is a common and useful practice in desktop applications to make certain menu items unavailable (for example, "dimmed"), when their actions are not available, Hildon takes a different approach: the menu items must not be visible at all. Although dimmed menu items suggest actions that are unavailable, they can cramp menu space on the small screen and make interaction with available menu items more confusing. | ||
| - | [[Image:view_menu_wrong.png| | + | [[Image:view_menu_wrong.png|400px]] |
| + | |||
| + | ''Figure 9: An incorrect view menu'' | ||
Learn more about Contributing to the wiki.