ui-best-practices-working-group http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/maillist.html ui-best-practices-working-group en-us Tue, 17 Nov 2009 22:20:55 GMT Tue, 17 Nov 2009 22:20:55 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) ui-best-practices-working-group http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/maillist.html Re: [ui-best-practices-working-group] Contradiction in 'field decoratiors and validations' document http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00516.html Hi, Eitan, This document captured the proposed field decoration approach for Eclipse 3.2, but the design was never implemented. We had some implementation issues to solve (regarding dialog layout and leaving space for the indicators), followed by the inte... Hi, Eitan,

This document captured the proposed field decoration approach for Eclipse 3.2, but the design was never implemented. We had some implementation issues to solve (regarding dialog layout and leaving space for the indicators), followed by the interaction design issues to work out, including the issue you mention - what to do when a required field is in error when the wizard opens.

Other concerns were more basic. When is it necessary to use the required field indication at all? For example, we don't need it when there is only one field, or if it is a well-known pattern (user login dialog). If you use them in some dialogs, does the user expect to see them everywhere?

So I'd say the visuals were never fully battle tested and without trying to implement them, we never solved the interaction issues.
There are actually still open bugs on this topic [1], but no push for consensus.
If you are curious about the history and what we did try during 3.2, you can read [2] and [3].

I've updated the wiki page to point to the currently open bug and to clearly state that this was never implemented.

susan

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=120238
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=133529
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=237372

Inactive hide details for Daniel Megert ---11/16/2009 12:35:04 AM---I think the Field Decorators and Validation is just wrong/oDaniel Megert ---11/16/2009 12:35:04 AM---I think the Field Decorators and Validation is just wrong/outdated. The



          Daniel Megert <daniel_megert@xxxxxxxxxx>
          Sent by: ui-best-practices-working-group-bounces@xxxxxxxxxxx

          11/16/2009 12:34 AM
          Please respond to User Interface Architecture Working Group



To: User Interface Architecture Working Group <ui-best-practices-working-group@xxxxxxxxxxx>
cc:
Subject: Re: [ui-best-practices-working-group] Contradiction in 'field decoratiors and validations' document


I think the  Field Decorators and Validation is just wrong/outdated. The
Save As dialog in the Eclipse SDK is not like on the picture i.e. doesn't
decorate fields with errors or warnings.

Dani

|------------>
| From:      |
|------------>
 >--------------------------------------------------------------------------------------------------------------------------------------------------|
 |"Kurejwowski, Eitan" <eitan.kurejwowski@xxxxxxx>                                                                                                  |
 >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To:        |
|------------>
 >--------------------------------------------------------------------------------------------------------------------------------------------------|
 |"ui-best-practices-working-group@xxxxxxxxxxx" <ui-best-practices-working-group@xxxxxxxxxxx>                                                       |
 >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Cc:        |
|------------>
 >--------------------------------------------------------------------------------------------------------------------------------------------------|
 |"Spielmann, Nicola" <nicola.spielmann@xxxxxxx>, "Johnson,   Clare" <clare.johnson@xxxxxxx>, "Jansen,  Ulrike" <ulrike.jansen@xxxxxxx>,            |
 |"Krzonkalla,        Sonja" <sonja.krzonkalla@xxxxxxx>                                                                                             |
 >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date:      |
|------------>
 >--------------------------------------------------------------------------------------------------------------------------------------------------|
 |16.11.2009 08:54                                                                                                                                  |
 >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject:   |
|------------>
 >--------------------------------------------------------------------------------------------------------------------------------------------------|
 |[ui-best-practices-working-group] Contradiction in 'field   decoratiors and validations' document                                                 |
 >--------------------------------------------------------------------------------------------------------------------------------------------------|





Hi all,

The document Field Decorators and Validation describes the behavior of
errors by showing an error decorator next to the field:
http://wiki.eclipse.org/Image:SaveAsError.gif

This is contradictory to the guidelines for validation of data:


(â)If the first required field is empty, an informative prompt should be
shown in the text area, directing the user to fill in the field (â)
and also is not implemented in any wizard. So the question is what should
be the behavior for new wizards?
In my opinion we should ignore the decorators for errors in wizard to be
consistent with the current implementations and make a remark in the
document specifying that this behavior is not yet implemented to avoid
future confusion.

Best Regards,
Eitan


Eitan Kurejwowski
User Experience Designer
UX Tools and Technologies
SAP Labs Israel
T   +972 9 7779732
mailto:eitan.kurejwowski@xxxxxxx
http://www.sap.com



_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group

_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group

GIF image

GIF image

GIF image

]]> Tue, 17 Nov 2009 22:17:04 GMT http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00516.html susan_franklin@xxxxxxx (Susan Franklin McCourt) Re: [ui-best-practices-working-group] Contradiction in 'field decoratiors and validations' document http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00515.html I think the Field Decorators and Validation is just wrong/outdated. The Save As dialog in the Eclipse SDK is not like on the picture i.e. doesn't decorate fields with errors or warnings. Dani &gt;---------------------------------------------------------------... I think the Field Decorators and Validation is just wrong/outdated. The Save As dialog in the Eclipse SDK is not like on the picture i.e. doesn't decorate fields with errors or warnings. Dani |------------> | From: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"Kurejwowski, Eitan" <eitan.kurejwowski@xxxxxxx> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"ui-best-practices-working-group@xxxxxxxxxxx" <ui-best-practices-working-group@xxxxxxxxxxx> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Cc: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"Spielmann, Nicola" <nicola.spielmann@xxxxxxx>, "Johnson, Clare" <clare.johnson@xxxxxxx>, "Jansen, Ulrike" <ulrike.jansen@xxxxxxx>, | |"Krzonkalla, Sonja" <sonja.krzonkalla@xxxxxxx> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |16.11.2009 08:54 | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |[ui-best-practices-working-group] Contradiction in 'field decoratiors and validations' document | >--------------------------------------------------------------------------------------------------------------------------------------------------| Hi all, The document Field Decorators and Validation describes the behavior of errors by showing an error decorator next to the field: http://wiki.eclipse.org/Image:SaveAsError.gif This is contradictory to the guidelines for validation of data: (â)If the first required field is empty, an informative prompt should be shown in the text area, directing the user to fill in the field (â) and also is not implemented in any wizard. So the question is what should be the behavior for new wizards? In my opinion we should ignore the decorators for errors in wizard to be consistent with the current implementations and make a remark in the document specifying that this behavior is not yet implemented to avoid future confusion. Best Regards, Eitan Eitan Kurejwowski User Experience Designer UX Tools and Technologies SAP Labs Israel T +972 9 7779732 mailto:eitan.kurejwowski@xxxxxxx http://www.sap.com _______________________________________________ ui-best-practices-working-group mailing list ui-best-practices-working-group@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group ]]> Mon, 16 Nov 2009 08:34:56 GMT http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00515.html daniel_megert@xxxxxxx (Daniel Megert) [ui-best-practices-working-group] Contradiction in 'field decoratiors and validations' document http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00514.html Hi all, The document Field Decorators and Validation describes the behavior of errors by showing an error decorator next to the field: http://wiki.eclipse.org/Image:SaveAsError.gif This is contradictory to the guidelines for validation of data: (30;)...

Hi all,

 

The document Field Decorators and Validation describes the behavior of errors by showing an error decorator next to the field: http://wiki.eclipse.org/Image:SaveAsError.gif

 

This is contradictory to the guidelines for validation of data:

 (…)If the first required field is empty, an informative prompt should be shown in the text area, directing the user to fill in the field (…)

and also is not implemented in any wizard. So the question is what should be the behavior for new wizards?

In my opinion we should ignore the decorators for errors in wizard to be consistent with the current implementations and make a remark in the document specifying that this behavior is not yet implemented to avoid future confusion.

 

Best Regards,

Eitan

 

 

Eitan Kurejwowski
User Experience Designer
UX Tools and Technologies
SAP Labs Israel
T   +972 9 7779732
mailto:eitan.kurejwowski@xxxxxxx
http://www.sap.com

 

 

 

 

]]> Mon, 16 Nov 2009 07:54:10 GMT http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00514.html eitan.kurejwowski@xxxxxxx (Kurejwowski, Eitan) [ui-best-practices-working-group] Best practices for selecting editors http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00513.html Hi all, I have created a document called Best practices for selecting editors I will be happy to get your feedback. Best Regards, Eitan

Hi all,

I have created a document called Best practices for selecting editors

 

I will be happy to get your feedback.

 

Best Regards,

Eitan

]]> Wed, 04 Nov 2009 15:20:36 GMT http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00513.html eitan.kurejwowski@xxxxxxx (Kurejwowski, Eitan) [ui-best-practices-working-group] Anyone interested in a UI walkthrough or a meeting? http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00512.html Title: Anyone interested in a UI walkthrough or a meeting? Greetings all, We are now well into September and I hope everyone had a nice break over the summer. I am checking to see if there is any interest for a UI walkthrough or general meeting. This is a ... Title: Anyone interested in a UI walkthrough or a meeting? Greetings all,

We are now well into September and I hope everyone had a nice break over the summer. I am checking to see if there is any interest for a UI walkthrough or general meeting.

This is a time of planning and early development for many projects and is an excellent time to consider UI enhancements. The UIBPWG is a great forum to discuss UI issues and get feedback from colleagues. If anyone on this list is interested or knows someone who should be interested ;-) check out the link:

http://wiki.eclipse.org/UIBPWG_UI_Walkthrough

to see what a UI walkthrough is and how we do it.

Also, let me know if there is any interest in a general meeting and we can make that happen as well.

Best,

Bob Fraser
 ]]> Wed, 16 Sep 2009 17:13:18 GMT http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00512.html bob.fraser@xxxxxxx (Bob Fraser) Re: [ui-best-practices-working-group] Field labels in Eclipse Forms http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00511.html Hi Eitan, The image example doesn't show for me. I am guessing you are showing an OS theme where the labels in the forms are blue. The label colors change with the OS theme and have been assigned an adaptable set of RGB values that have good contrast with... Hi Eitan,

The image example doesn't show for me.

I am guessing you are showing an OS theme where the labels in the forms are blue. The label colors change with the OS theme and have been assigned an adaptable set of RGB values that have good contrast with any of the theme backgrounds. The reason for color labels, not black, is to distinguish the label from the content to make reading the form easier. This is a visual "trick" to help advance the content and enable quick visual parsing of the form.

Regards,
Kim
...................................................................
UI Design . Rational Software
IBM Toronto Media Design Studio



Inactive hide details for "Kurejwowski, Eitan" ---08/03/2009 06:31:54 AM---Hi all, I have a question. What is the reason for us"Kurejwowski, Eitan" ---08/03/2009 06:31:54 AM---Hi all, I have a question. What is the reason for using blue field labels in eclipse forms? Is this according with some UI gu


From:
"Kurejwowski, Eitan" <eitan.kurejwowski@xxxxxxx>

To:
<ui-best-practices-working-group@xxxxxxxxxxx>

Date:
08/03/2009 06:31 AM

Subject:
[ui-best-practices-working-group] Field labels in Eclipse Forms



Hi all,
I have a question. What is the reason for using blue field labels in eclipse forms? Is this according with some UI guideline?
Here is an example:



Thanks and Regards,
Eitan

Eitan Kurejwowski
User Experience Designer
UX Tools and Technologies
SAP Labs Israel
T +972 9 7779732
mailto:eitan.kurejwowski@xxxxxxx
http://www.sap.com
_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group


GIF image

GIF image

]]> Tue, 11 Aug 2009 16:30:52 GMT http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00511.html kpeter@xxxxxxx (Kimberley Peter) [ui-best-practices-working-group] UI pattern for navigation from cellTable http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00510.html Hi all, I&#8217;m looking for a UI pattern that allows editing and navigating from a cell in a table. The use case is similar to the link on a field label in form editors. The use case is as follows: 1. Type inplace the class name 2. p; p;Use content ...

Hi all,

I’m looking for a UI pattern that allows editing and navigating from a cell in a table. The use case is similar to the link on a field label in form editors.

The use case is as follows:

1.       Type inplace the class name

2.        Use content assist

3.        Create a new class

4.       Navigate to the java source

 

Does this pattern already exists?

 

Thanks,
Eitan

]]> Thu, 06 Aug 2009 09:32:17 GMT http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00510.html eitan.kurejwowski@xxxxxxx (Kurejwowski, Eitan) [ui-best-practices-working-group] AUTO: Raji Akella/Austin/IBM is out of the office.(returning 08/10/2009) http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00509.html I am out of the office until 08/10/2009.. Note: This is an automated response to your message [ui-best-practices-working-group] Field labels in Eclipse Forms sent on 8/3/09 4:31:24. This is the only notification you will receive while this person is away. I am out of the office until 08/10/2009..




Note: This is an automated response to your message [ui-best-practices-working-group] Field labels in Eclipse Forms sent on 8/3/09 4:31:24.
This is the only notification you will receive while this person is away.]]> Mon, 03 Aug 2009 16:07:23 GMT http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00509.html raji@xxxxxxx (Raji Akella) [ui-best-practices-working-group] AUTO: Eugene Chan/Toronto/IBM is out of the office. (returning 08/05/2009) http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00508.html I am out of the office until 08/05/2009. I will respond to your message when I return. If there is a business urgency, please contact my manager Ernest Mah (ernest@xxxxxxxxxx) Note: This is an automated response to your message &quot;[ui-best-practices-working... I am out of the office until 08/05/2009.

I will respond to your message when I return.

If there is a business urgency, please contact my manager Ernest Mah (ernest@xxxxxxxxxx)


Note: This is an automated response to your message "[ui-best-practices-working-group] Field labels in Eclipse Forms" sent on 8/3/09 6:31:24.

This is the only notification you will receive while this person is away.]]> Mon, 03 Aug 2009 14:02:00 GMT http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00508.html ewchan@xxxxxxx (Eugene Chan) [ui-best-practices-working-group] Bob Duchnicky/Toronto/IBM is on vacation until Wed Au 5th http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00507.html I will be out of the office starting 08/02/2009 and will not return until 08/05/2009. I will check e-mail occasionally. I will be out of the office starting 08/02/2009 and will not return until 08/05/2009.

I will check e-mail occasionally.]]> Mon, 03 Aug 2009 12:01:18 GMT http://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00507.html bobd@xxxxxxx (Bob Duchnicky)