Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ui-best-practices-working-group] Top 10 UI lists -- Please add your ideas

Great to see the contributions coming in.  Kim, do you think we should widen by sending your note to platform-ui-dev@xxxxxxxxxxx?


Kimberley Peter/Toronto/IBM@IBMCA
Sent by: ui-best-practices-working-group-bounces@xxxxxxxxxxx

03/21/2007 07:51 PM

Please respond to
User Interface Architecture Working Group        

[ui-best-practices-working-group] Top 10 UI lists -- Please add        your ideas

Hi *

As per the conversation at our workgroup meeting today, we are going to
come up with a top 10 list for good and bad UI practices for Eclipse to be
used as a base checklist.

I've taken a quick stab, but welcome your contributions to make this truly
solid and in keeping with what we believe can lead to a great Eclipse UI,
or a bad one. If you think any of these suck, don't hesitate to say so.
Let's expand the list initially as needed then pare back. Note Mik
suggested we reference the Performance Bloopers page:

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
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
7.   Don't initiate dialogs or wizards in an error state
8.   Use quick fix and quick assist mechanisms
10.  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


ui-best-practices-working-group mailing list

Back to the top