[
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
|
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 ;)
Cheers,
---
Chris Aniszczyk | IBM Lotus | Eclipse Committer | http://mea-bloga.blogspot.com | +1 860 839 2465
Kimberley Peter ---03/21/2007 06:53:34 PM---Hi *
From: |
Kimberley Peter <kpeter@xxxxxxxxxx> |
To: |
ui-best-practices-working-group@xxxxxxxxxxx |
Date: |
03/21/2007 06:53 PM |
Subject: |
[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:
http://wiki.eclipse.org/index.php/Performance_Bloopers.
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.
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
Thanks!
Kim
_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group