> http://argouml.tigris.org/wiki/Tasks_for_UML_2.x_Support
This page splits out work on property panels as if they are a part of working on a diagram. That is not really the case. We could have someone work on panels for just those elements on a class diagram but the user can still load some XMI that contain other elements that will fail if they select them in the explorer and they display in an incomplete property panel. I'd suggest the blocks in that wiki for Class Diagram Implementation, Use Case Diagram Implementation are reorgansied to contain also other relevant subsystem as main blaock such as Property Panels and Explorer. I don't think we can release any single diagram until those are working. I'm happy to edit the wiki if this is agreeable but didn't want to go to the effort unless others follow my logic. I don't know how much work will be required in the explorer to get it to UML2.x. For adding model elements via right-click in the explorer that should be fine as that is driven by calls to the model. But I don't know how much the tree structure is fixed for UML1.4, I've only ever looked at the explorer when I have to. I don't know it in-depth. Presume the UML structure is fixed there quite heavily and chgin that for UML2 may be difficult to keep compatible with UML1.4. Preferably the explorer could be adapted to query the metamodel and be driven by it but that may be too much effort at the moment. Could we instead split a second explorer implementation following UML2 design with ArgoUML loading one or the other depending on the UML implementation? (hopefully there will still be some common logic we can keep in just one place). If we can first get the explorer into its own eclipse subproject we can have only the eUML launcher include the replacement at startup and current standard Argo load the existing explorer. Bob. > (Please contribute!) > > (The starting point for all UML2 wiki pages is > http://argouml.tigris.org/wiki/UML_2.x_support) > > The work of Bogdan is far from being complete, but the great > thing about his work is, that he achieved some substantial > breakthroughs: model event handling and undo model changes. > I really recommend to have a look on his well done reports: > http://argouml.tigris.org/wiki/Status_of_eUML > > Let's safe ArgoUML from losing acceptance and interoperability! > > Regards, > Thomas > > P.S.: I also have two conrete questions we could start thinking about: > > The first one: How will the legacy UML 1.4 projects be handled? > I think if we can make it a little easier by doing a "hard cut" > (and maintain two ArgoUML separated streamlines for a while: > UML1.4 and UML 2.x). Because I don't know how much it takes to > create a migration tool. The worst would be to make ArgoUML > deal with both UML1.4 and UML2 models... > > The second one: Can our first UML2 release be with very limited > functionality, growing steadily from release to release, or do > we aim for a full ArgoUML 0.28 replacement or...? > (Since the UML2 work will take a lot time, I'd suggest to only > release maintainance releases 0.28.x from now on.) > > -- > Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: > http://www.gmx.net/de/go/multimessenger01 > > ------------------------------------------------------ > http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1492835 > > To unsubscribe from this discussion, e-mail: > [[email protected]]. > To be allowed to post to the list contact the mailing list moderator, email: > [[email protected]] > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1495848 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
