Hello all,
At first my project proposal for GSoC was about the improvement of the
ArgoUML's GUI and was based on two views simple (for easy sketching) and
advanced (for complete settings).
It recently changed to something more important for the community:
usability issues of diagrams. Because the purpose of any SoC application
should be adding something to the project that the community really
needs/wants I’ve put together a wish list of features I would like you
to vote on. The feedback of the dev team and of users of ArgoUML is very
important here, because I will develop the features that the community
wants to. The list contains some ideas of my own and some inspired by
Bob, or by other members of the dev team on my first GUI thread [
http://argouml.tigris.org/servlets/BrowseList?list=dev&by=thread&from=643675
].
Any idea whatsoever is welcomed, and is immediately submitted to voting.
Wish list (in my preference order):
1. Drag a field from a class as a new entity
2. Bird’s eye view – a new panel showing a non editable, reduced size
image of the current diagram (Bob)
3. Class modification on the panel:
3a) possibility to modify visibility of attribute/methods by clicking an
icon in front of the name, or the current +, -, ~, # signs
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
3c) drag/drop reorder of attributes and operations (Bob)
4. Laser mode - instead of drawing an association all the way from class
X to class Y the user can just start to drag from class X towards class
Y. The edge being drawn will shoot ahead of the user’s mouse position
and attach to the first class in line when the user releases (Bob and
Jason Robbins)
5. An “Office 2007” like quick menu (the one that appears when a text is
selected, to allow quick editing – Font, Color…) for accessing most
common features. It would extend the current existing one that allows
the creation of associations and generalizations by adding: new
attribute, new operation, change visibility, stereotype…
6. A quick “Build class wizard” allowing to create a class from scratch
and to avoid the same repetitive tasks every time a class is created:
class name, attributes (visibility, type) and operations (visibility,
returned/received parameters)
7. Integration of classes between diagrams – A class created on a Class
diagram should easily be integrated on other diagrams (as an actor or as
a classifier role for example) and operations from the class should be
available for integration on these diagrams
The voting should be a classification of ideas above (with remarks) and
if new ideas are to be added, the list should be continued (i.e. next
idea should be 8).
My vote is: 1,2,3,4,5,6,7
This should be no propaganda, but the better the feedback and the new
ideas, the better and useful the work I’ll do for the community will be
(if I will be accepted ^_^).
Thank you for your time.
Cheers,
--
Bogdan SZANTO
-----------------------------------------------
Impossible is nothing ~ Nothing is impossible !
-----------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
