Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ve-dev] Create Visual Class Wizard - new design for review


Makes sense.  If that's the case (if all "Other" equate to the same java), having its own root entry in the tree would be more efficient.
Here are the two options...
   One problem with (b) is that it may not make clear to users that not using a style (turning off the checkmark) will populate the superclass with a specific class (java.lang.Object).... because they may thing that it will disable everything (right and left controls)... i.e., they may not realize what it means (i.e., will happen if they turn it off.)

A)


B)


  Thanks,

       Lucinio Santos
       Manager, WebSphere Tools User Experience
       Phone: (919) 543-4813  (tie: 3-4813) -  Fax: (919) 254-8169
       santosg@xxxxxxxxxx



Joe Winchester <WINCHEST@xxxxxxxxxx>
Sent by: ve-dev-admin@xxxxxxxxxxx

03/18/2004 12:35 PM
Please respond to ve-dev

       
        To:        ve-dev@xxxxxxxxxxx
        cc:        
        Subject:        Re: [ve-dev] Create Visual Class Wizard - new design for review




Folks,


One thing that might be nice is to see a short description of what each tree entry does.  For some entries (such as SWT -> Application) these are subclasses of java.lang.Object which doesn't let the user know what really happens (which is that we create a class with a main doing a display loop and a Shell within it).  Maybe when each entry is selected the status message is updated to show a longer descrpiption of what kind of class is going to be generated.


Another point (maybe this was discussed yesterday and I missed - in which case apologies) is why is Other beneath each category.  e.g. we have SWT > Other and Swing > Other.  These all do the same (which is to put java.lang.Object) in the list, so instead of taking up 3 items of vertical height why not somehow make it one item (perhaps Other is a top level item), or maybe other is a checkbox above the tree like (Use template) which when selected enables the tree and when not selected disables the tree and is just java.lang.Object superclass.  Perhaps the label "Style" to the left of the tree would be a checkbox "Use Style".


Best regards,


Joe


Back to the top