Jump to: navigation, search

Difference between revisions of "Top Ten Lists Working Page"

m (Starter Set)
(Additions / Ideas)
Line 22: Line 22:
  
  
===== Additions / Ideas =====
+
==== Additions / Ideas ====
Top Ten Eclipse UI Violations
+
===== Top Ten Eclipse UI Best Practices =====
 +
 
 +
Should we mention something about Accessibility in the Good Practices list ?
 +
 
 +
Raji Akella
 +
 
 +
 
 +
===== Top Ten Eclipse UI Violations =====
  
 
5.  Bastardized property pages
 
5.  Bastardized property pages
Line 31: Line 38:
 
Just a pet-peeve ;)
 
Just a pet-peeve ;)
  
Cheers,
 
 
---
 
 
Chris Aniszczyk
 
Chris Aniszczyk

Revision as of 07:08, 22 March 2007

Starter Set

Top Ten Eclipse UI Guidelines

  1. Use the Eclipse look and feel if extending or plugging into Eclipse
  2. Use common SWT controls to get what SWT offers for cross-platform adaptability
  3. Be familiar with APIs for the UIs you are building
  4. Use icons and graphics consistent with the Eclipse style, decorations, states, and quality
  5. Understand the conventions of the OSs you are developing for
  6. Use understandable messages to help people recover from error conditions
  7. Don't initiate dialogs or wizards in an error state
  8. Use quick fix and quick assist mechanisms
  9. Reserve time for "polish"


Top Ten Eclipse UI Violations

  1. Low quality graphics or not consistent with the Eclipse style
  2. Poorly organized dialogs
  3. Oddly sized dialogs and wizards
  4. Cryptic error messages
  5. Property pages that don't adhere to platform uses (normal and tabbed)


Additions / Ideas

Top Ten Eclipse UI Best Practices

Should we mention something about Accessibility in the Good Practices list ?

Raji Akella


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