Re: [ve-dev] Wizard to create a new Java Class using the Visual Editor

[Lucinio Santos <santosg@xxxxxxxxxx>]

Srimanth,

   The problem with dropping
the radio buttons and place it all in the dropdown would be that...
        a)
You'd lose that first easy-scan scan of the high level categories
        b)
If you meant that the dropdown would contain all classes... this would
result in a deeper dropdown... harder to find the class you're looking
for
        c)
If you meant that the dropdown would contain just the high level classes...
you wouldn't be able to subclass any other (more obscure) class.

Your right, though, that you would save
real sate.

Thanks,

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

Srimanth Gunturi/Raleigh/IBM@IBMUS Sent by: ve-dev-admin@xxxxxxxxxxx 02/06/2004 01:32 PM Please respond to ve-dev

To:        ve-dev@xxxxxxxxxxx         cc:        ve-dev@xxxxxxxxxxx, ve-dev-admin@xxxxxxxxxxx         Subject:        Re: [ve-dev] Wizard to create a new Java Class using the Visual Editor

I was wondering if this would work - In the case of using a combo-box for
superclass, would the Radio buttons be necessary ?

When Other is selected from the Drop-down, the Browse button gets enabled.
Regards, 
Sri.

Lucinio Santos/Raleigh/IBM@IBMUS
Sent by: ve-dev-admin@xxxxxxxxxxx

02/06/2004 11:55 AM

Please respond to
ve-dev

To	ve-dev@xxxxxxxxxxx
cc
Subject	Re: [ve-dev] Wizard to create a new Java Class using the Visual Editor

Thank you all for your comments. 

- Peter... You're right.  My error. I neglected to match the "Superclass"
field with the selected "Style" dropdown.

- Illya... I think this was your point (1).  That was the intention...
The Superclass field would be updated dynamically depending on the "Style"
and radio button selections. 
   About the choice of name for "Style" (you and Eugene
suggested "Widget set" and "Toolkit".  These are
good ideas.  What do you both think about the argument the following
counter argument: since developers could add their own contributions to
this dropdown, they could become their own organization/personal "style"
(although technically they are "toolkits").

- Eugene... The radio buttons are intended to be generic.  Looks like
you propose (legitimately) adding one more: Dialog
...as well as a corresponding dropdown (to accompany this "Dialog"
radio button) that would include the various dialog classes that could
be extended.  Problem is, don't you think that would require too much
realstate? 
   
What we could do is to make the "Superclass" field a dropdown
that includes any classes that match the Style dropdown and Radio buttons
selection. 

Resulting in something like this...

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