Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "UI Checklist"
| Line 7: | Line 7: | ||
* Persist the state of each view between sessions (Guideline 7.20). | * Persist the state of each view between sessions (Guideline 7.20). | ||
| − | * Put only the most commonly used commands on the view toolbar. Any command on a toolbar must also appear in a menu, either the context menu or the view menu. (Guideline 7.12) | + | * Put only the most commonly used commands on the view toolbar. Any command on a toolbar must also appear in a menu, either the window menu, context menu or the view menu. (Guideline 7.12) |
| − | * Use the view pulldown menu for | + | * Use the view pulldown menu for commands not tied to selection (Guideline 7.10). Fill the context menu with selection oriented actions. (Guideline 7.13) |
| − | * Modifications made in an editor must follow an open-save-close lifecycle model (Guideline 6.2), whereas modifications made within a view must be saved immediately (Guideline 7.2). | + | * <font color=gray>Modifications of workspace resources made in an editor must follow an open-save-close lifecycle model (Guideline 6.2), whereas modifications made within a view must be saved immediately (Guideline 7.2).</font> |
| − | * If | + | * If a view or editor has support for Cut, Copy, Paste, or any of the global commands, these commands must be executable from the same commands in the window menu bar and toolbar. (Guideline 6.9, Guideline 7.19) |
'''Wizards and Dialogs''' | '''Wizards and Dialogs''' | ||
| Line 27: | Line 27: | ||
'''Workbench & Preferences''' | '''Workbench & Preferences''' | ||
| − | * | + | * Follow the visual style established for Eclipse UI graphics (new Guideline 2.0). Re-use the core visual concepts to maintain consistent representation and meaning across Eclipse plug-ins. (Guideline 2.1) |
| − | * If you create a preference group, use the root page for frequently used preferences, or those preferences which have wide spread effect. Specialize within the sub pages. The root preference page should not be blank. (Guideline 15.4) | + | * If you must create a new preference group, use the root page for frequently used preferences, or those preferences which have wide spread effect. Specialize within the sub pages. The root preference page should not be blank. (Guideline 15.4) |
* Use Headline style capitalization for menus, tooltip and all titles, including those used for windows, dialogs, tabs, column headings and push buttons (Guideline 1.5). Use Sentence style capitalization for all control labels in a dialog or window, including those for check boxes, radio buttons, group labels, and simple text fields (Guideline 1.6). | * Use Headline style capitalization for menus, tooltip and all titles, including those used for windows, dialogs, tabs, column headings and push buttons (Guideline 1.5). Use Sentence style capitalization for all control labels in a dialog or window, including those for check boxes, radio buttons, group labels, and simple text fields (Guideline 1.6). | ||
[[Category:UI_Guidelines]] | [[Category:UI_Guidelines]] | ||
Revision as of 00:58, 15 November 2007
NOTE: draft only, changes in progress
This is is a shortlist of the most relevant and easy to apply Eclipse User Interface Guidelines. Start by using this list, referring to the linked guideline items for details, then use the Full checklist for additional guidance.
Views & Editors
- Persist the state of each view between sessions (Guideline 7.20).
- Put only the most commonly used commands on the view toolbar. Any command on a toolbar must also appear in a menu, either the window menu, context menu or the view menu. (Guideline 7.12)
- Use the view pulldown menu for commands not tied to selection (Guideline 7.10). Fill the context menu with selection oriented actions. (Guideline 7.13)
- Modifications of workspace resources made in an editor must follow an open-save-close lifecycle model (Guideline 6.2), whereas modifications made within a view must be saved immediately (Guideline 7.2).
- If a view or editor has support for Cut, Copy, Paste, or any of the global commands, these commands must be executable from the same commands in the window menu bar and toolbar. (Guideline 6.9, Guideline 7.19)
Wizards and Dialogs
- Start a wizard with a prompt, not an error message. (Guideline 5.3)
- Seed the fields within a wizard using the current workbench state. (Guideline 5.4)
- Use a Browse Button whenever an existing object is referenced in a wizard. (Guideline 5.8)
- When a dialog opens, set the initial focus to the first input control in the container. If there are no input controls, the initial focus should be assigned to the default button (Guideline 4.1)
Workbench & Preferences
- Follow the visual style established for Eclipse UI graphics (new Guideline 2.0). Re-use the core visual concepts to maintain consistent representation and meaning across Eclipse plug-ins. (Guideline 2.1)
- If you must create a new preference group, use the root page for frequently used preferences, or those preferences which have wide spread effect. Specialize within the sub pages. The root preference page should not be blank. (Guideline 15.4)
- Use Headline style capitalization for menus, tooltip and all titles, including those used for windows, dialogs, tabs, column headings and push buttons (Guideline 1.5). Use Sentence style capitalization for all control labels in a dialog or window, including those for check boxes, radio buttons, group labels, and simple text fields (Guideline 1.6).