Hello Bob!

I think we should keep both. The mental processes around working with an
application are different depending on the person and on the task. For
this reason we should keep as many options to do things as possible as
long as they cannot be misunderstood and are not in the way of other
functions.

About the unidirectionality of Create Generalization. I don't know why
we can't have both directions. Select one or more classes and then
        rightclick on a class->CreateModelElement->CreateGeneralization
(make Generalized)
        rightclick on a class->CreateModelElement->CreateGeneralization
(make Specialized)
(better names are needed).

        /Linus


> -----Original Message-----
> From: Bob Tarling [mailto:[EMAIL PROTECTED]
> Sent: den 8 januari 2007 02:57
> To: [email protected]
> Subject: [argouml-dev] Re: Creating model elements without using
diagram
> 
> Just thinking about this a little further there is an advantage to the
> drag and drop to prop panel vs right click in explorer. Maybe it's
> worth my persevering.
> 
> For example if I wanted to create a generalization with class A as the
> specialization of class B I can select class B in the explorer and
> then drag class A from the explorer to the specializations box of
> class B. So I know in which direction the generalization will be
> formed.
> 
> With the explorer only I can select class A and class B then
> rightclick->CreateModelElement->CreateGeneralization. With this the
> generalization is created but which will be the specialized class and
> which will be the generalized class. It depends on the order of
> selection in the tree but that's not clear to the user.
> 
> For associations and dependencys I prefer to right click on the tree.
> For things like generalization I think the drag is more useful.
> 
> What do others think about the usability of these features? Should we
keep
> both?
> 
> Bob.
> 
> 
> On 08/01/07, Bob Tarling <[EMAIL PROTECTED]> wrote:
> > I spent quite some time trying to get the drag mechanism working
from
> > the explorer to the JList in the prop panel but I'm now thinking of
> > backing this out before the next release.
> >
> > I've found a few nasty side effects due to the changes I made in
> > ExplorerTree and DnDExplorerTree and I'm concerned there may be more
> > lurking.
> >
> > I'll revert these back to there original state before I started at
> > some time tomorrow.
> >
> > The alternative I've come up with of simply allowing the users to
> > select 1 or more items in the explorer and providing popup menu
> > options seems a lot simpler.
> >
> > Bob.
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to