I've shuffled them around and injected a couple of my own.

There are some points for discussion but lets continue vote first and
come back to comments later.

Bob.


>  6. A quick "Build class wizard" allowing to create a class from scratch and
Nice concept that could grow for other types. Please lets use modal wizards ;-)


>  7. Integration of classes between diagrams – A class created on a Class
I think users would like to see this feature as they're used to it in
other apps.


>  1. Drag a field from a class as a new entity
I assume this is to be able to drag things like an attribute from one
class to another in order to move or copy to that second class.
How does the user indicate that he wants to drag the attribute or just
move the class itself?


>  3c) drag/drop reorder of attributes and operations (Bob)
I keep this with the above only because I see reuse of work and
similar usability issues.


>  4. Laser mode - instead of drawing an association all the way from class X


8. See http://argouml.tigris.org/issues/show_bug.cgi?id=2924 and
dependencies, I think features such as convert class to interface
would be very useful.


>  2. Bird's eye view – a new panel showing a non editable, reduced size image
> of the current diagram (Bob)


9. Rotate through aggregation types by double clicking on association
end. Or some other neat shortcut that is more visible to the user, any
ideas?


>  3a) possibility to modify visibility of attribute/methods by clicking an
> icon in front of the name, or the current +, -, ~, # signs
A click might be difficult. How do we know that doesn't mean select to
edit as text. User interaction needs to be thought about.


>  3b) possibility to modify type of attribute or of the received/return type
> of an operation by using a drop down menu or the keyboard


>  5. An "Office 2007" like quick menu (the one that appears when a text is
This sounds similar to our toolbelt but designed for when editing a
text Fig. I like this but suspect this will mean work in enhancing
GEF. I'd rather this project was only ArgoUML based. However this
could be the way of handling 3a/3b

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

Reply via email to