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 "Top Ten Lists Working Page"
(→Starter Set) |
(→Starter Set) |
||
| Line 3: | Line 3: | ||
==== Top Ten Eclipse UI Guidelines ==== | ==== Top Ten Eclipse UI Guidelines ==== | ||
#Use the Eclipse look and feel if extending or plugging into Eclipse | #Use the Eclipse look and feel if extending or plugging into Eclipse | ||
| − | #Use common SWT controls to get what SWT offers for cross-platform adaptability | + | #Use common SWT controls to get what SWT offers for cross-platform adaptability and accessibility |
#Be familiar with APIs for the UIs you are building | #Be familiar with APIs for the UIs you are building | ||
#Use icons and graphics consistent with the Eclipse style, decorations, states, and quality | #Use icons and graphics consistent with the Eclipse style, decorations, states, and quality | ||
| Line 10: | Line 10: | ||
#Don't initiate dialogs or wizards in an error state | #Don't initiate dialogs or wizards in an error state | ||
#Use quick fix and quick assist mechanisms | #Use quick fix and quick assist mechanisms | ||
| − | |||
#Reserve time for "polish" | #Reserve time for "polish" | ||
| Line 18: | Line 17: | ||
#Poorly organized dialogs | #Poorly organized dialogs | ||
#Oddly sized dialogs and wizards | #Oddly sized dialogs and wizards | ||
| + | #Useless dialogs | ||
#Cryptic error messages | #Cryptic error messages | ||
#Property pages that don't adhere to platform uses (normal and tabbed) | #Property pages that don't adhere to platform uses (normal and tabbed) | ||
| Line 28: | Line 28: | ||
Raji Akella | Raji Akella | ||
| + | |||
| + | Ref: http://wiki.eclipse.org/index.php/Platform_UI/Accessibility_Features | ||
Revision as of 08:46, 22 March 2007
Contents
Starter Set
Top Ten Eclipse UI Guidelines
- Use the Eclipse look and feel if extending or plugging into Eclipse
- Use common SWT controls to get what SWT offers for cross-platform adaptability and accessibility
- Be familiar with APIs for the UIs you are building
- Use icons and graphics consistent with the Eclipse style, decorations, states, and quality
- Understand the conventions of the OSs you are developing for
- Use understandable messages to help people recover from error conditions
- Don't initiate dialogs or wizards in an error state
- Use quick fix and quick assist mechanisms
- Reserve time for "polish"
Top Ten Eclipse UI Violations
- Low quality graphics or not consistent with the Eclipse style
- Poorly organized dialogs
- Oddly sized dialogs and wizards
- Useless dialogs
- Cryptic error messages
- Property pages that don't adhere to platform uses (normal and tabbed)
Additions / Ideas
Top Ten Eclipse UI Guidelines
Should we mention something about Accessibility in the Good Practices list ?
Raji Akella
Ref: http://wiki.eclipse.org/index.php/Platform_UI/Accessibility_Features
Top Ten Eclipse UI Violations
5. Bastardized property pages
You may choose to use friendlier language, but it pains me every time I come across a property pages that don't adhere to what the platform uses (normal or tabbed).
Just a pet-peeve ;)
Chris Aniszczyk
Useless dialogs
(Found on Steve Northover's blog: http://inside-swt.blogspot.com/2007/03/useless-dialog-of-day.html)
Kim Peter