RE: [ui-best-practices-working-group] Question abouthow to handle best p

["Raev, Kaloyan" <kaloyan.raev@xxxxxxx>]

I would do it this way:

  1. when the "New XXX Connection Profile" dialog appears it should display an info message.

  2. if there is nothing available to select then automatically popup the "New Driver Definition" dialog, still keep an info message in the parent "New XXX Connection Profile" dialog. This saves some frustration for users. Beginners may not find by themselves the little button right to the drop-down list.

    2.a. if the user creates a valid driver, then after closing the "New Driver Definition" dialog, select the new driver in the Drivers drop-down list. The wizard can finish now - no error needed to display.

    2.b. if the user cancels the "New Driver Definition" dialog or creates an invalid driver, then show the error message.

 

However, I think that the text in the info message should differ the text in the error message. The info message should invite users to do something, while the error message should point what they have done wrong.

 

Greetings,

Kaloyan

---

From: ui-best-practices-working-group-bounces@xxxxxxxxxxx [mailto:ui-best-practices-working-group-bounces@xxxxxxxxxxx] On Behalf Of Boris Bokowski
Sent: 10 декември 2008 г. 22:54 ч.
To: User Interface Architecture Working Group
Subject: Re: [ui-best-practices-working-group] Question abouthow to handle best practice

Right - contrary to what I said, Eclipse Platform/JDT/PDE wizards don't show an icon when a wizard comes up (i.e. no INFO icon). Sorry if this caused confusion.

Boris

Eugene Kuleshov wrote on 12/10/2008 03:19:37 PM:

>
>   I would drop info icon from the message and maybe also use sensible
> defaults in the drop down (e.g. previously chosen value or drivers
> available by default).
>
>   By the way, if I am remembering correctly issue about not showing
> errors when wizard is shown is stated in the Eclipse UI guidelines.
> http://wiki.eclipse.org/User_Interface_Guidelines#Initialization_2
>
>   regards,
>   Eugene
>
>
> brian.fitzpatrick@xxxxxxxxxx wrote:
> > Thanks guys... So you'd recommend something along these lines:
> >
> >
> >
> > Brian Fitzpatrick
> > Eclipse Data Tools Platform PMC Chair
> > Eclipse Data Tools Platform Connectivity Team Lead
> > Staff Software Engineer, Sybase, Inc.
> >
> >
> >
> > *Boris Bokowski <Boris_Bokowski@xxxxxxxxxx>*
> > Sent by: ui-best-practices-working-group-bounces@xxxxxxxxxxx
> >
> > 12/10/2008 11:46 AM
> >
> >    
> > To
> >    User Interface Architecture Working Group
> > <ui-best-practices-working-group@xxxxxxxxxxx>
> > Subject
> >    Re: [ui-best-practices-working-group] Question about how to      
> >  handle        best practice
> >
> >
> >
> >
> > Francis Upton wrote on 12/10/2008 01:19:40 PM:
> > > What I have done in this case, is to have the message appear as it
> > > is, but just without the error icon (when the dialog is first
> > > presented), you can use an info icon I think.  I think the message
> > > at the top is useful.  Then if the user does something to cause the
> > > selection to be empty, it can have the error icon like it does now.
> >
> > Yes, this is what the Platform and JDT wizards are doing. We start out
> > with an INFO rather than ERROR status. Finish and Next would be
> > disabled of course. If the user enters something and then clears
> > again, you would show an ERROR status.
> >
> > > It's sometimes unpleasant to do all of the special handling for
> > > these cases, and I don't know of a standard easy pattern (other than
> > > the first time flag). :)
> >
> > If your wizard uses data binding,
> > org.eclipse.jface.databinding.wizard.WizardPageSupport does all that
> > special handling for you. See also
> > org.eclipse.jface.examples.databinding.snippets.Snippet014WizardDialog
> > in org.eclipse.jface.examples.databinding.
> >
> > Boris
>
> _______________________________________________
> ui-best-practices-working-group mailing list
> ui-best-practices-working-group@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group