Great idea Nicolas! It sounds like a simle and clear approach.
The next upgrade of the Tigris site will provide a wiki that I plan to use for the developer's documentation (what today is called the Cookbook). That could be the place for such discussions. There is a wiki set up for the user community at http://www.argouml-users.net. /Linus 2008/6/18, Nicolas Raoul <[EMAIL PROTECTED]>: > > Hi all, > > Here are my two cents about sequence diagrams: > > --- About the migration of old sequence diagrams: > > Let's face it, sequence1 is so broken there is no point thinking about > migration issues. I might be wrong, but I guess nobody maintains their > sequence diagrams using the current ArgoUML. > > --- About sequence2: > > I have been following the discussions about sequence2's stability, and > I posted quite a lot of bugs about it, all of them have been fixed. I > think that even though it does not feel snappy, at least it is very > usable and should be the default in the next release. So I agree with > Bob on issue 5159. > > --- My proposal for a simpler sequence diagram UI: > > Sequence diagrams are radically different from other UML diagrams: We > don't need to let humans move graphical elements around. Given the > logical description of the actors and actions, a program can generate > a perfect-looking diagram. This is not true for class diagrams, for > instance, where the user needs the ability to adjust the vertical and > horizontal position of each class. > > The user should not have to care about the graphical position of > actors and actions. > All that matters is the order of the actors and actions. > > I see the sequence diagram more like a spreadsheet: one actor per > column, one action per row. I can add a new row, remove an existing > row, insert a row between two existing rows, and I do not want to > bother about vertical and horizontal spacing. The program should > handle this for me. When I insert a new row, the program should move > down all of the following rows. When I move an action, the program > should make it intuitive just like when moving a tab in Firefox. Same > for a group of actions. When moving an action with several > "sub-actions", the sub-actions should move with the action. A comment > is a specialized row. > > That is less hassle for the user, a cleaner model/UI separation, and > the zargo file only contains the model, not the UI-related fluff, > avoiding unnecessary migrations. > > What do you think about this ? > Is there a wiki place for such brainstorming ? > > Cheers, keep up the good work :-) > Nicolas Raoul. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
