Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ui-best-practices-working-group] RE: Improving Project UIs for Ganymede

Martin, agree, they are vague. They weren't intended on being a checklist to be policed, more like a "UI bloopers" or "things that you should keep in mind".

Cheers,
Kevin

Oberhuber, Martin wrote:
Thanks Mike and Kim.

While I find the "draft top 10" interesting and certainly good advice, they seem to be pretty vague right now.

"Use the Eclipse look and feel" - how to put
this into practice? How to verify during a review? What is "familiar"? What is "understandable"?

Number 7 ("Don't initiate dialogs or wizards
in an error state") is the most concrete advice
I can find.

I fully agree with Ed and cannot see how this
could become a "must do" for Ganymede. It's good,
though, to make these guidelines more prominent
and promote them to "should do".

Cheers,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
-----Original Message-----
From: ui-best-practices-working-group-bounces@xxxxxxxxxxx [mailto:ui-best-practices-working-group-bounces@xxxxxxxxxxx] On Behalf Of Mike Milinkovich
Sent: Wednesday, September 26, 2007 3:34 PM
To: eclipse.org-planning-council@xxxxxxxxxxx
Cc: ui-best-practices-working-group@xxxxxxxxxxx
Subject: FW: [ui-best-practices-working-group] RE: Improving Project UIs for Ganymede


Since I'm not sure if Kimberley is subscribed to this list, I am re-posting
_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group


Back to the top