The uml2 diagram module is now in place. Try using the launcher "ArgoUML EUML with diagram2 and Java"
There is still a problem that the default diagrams created for the first project will be UML1.4 so do a file->new after starting (http://argouml.tigris.org/issues/show_bug.cgi?id=5836) I also adjusted the java reverse engineering so that it calls the new method of ArgoDiagram to create Figs instead of calling Fig constructors directly. e.g. instead of new FigClass(classifier, new Rectangle(0, 0, 0, 0), currentDiagram.getDiagramSettings()); I do currentDiagram.createDiagramElement(classifier, new Rectangle(0, 0, 0, 0)); The result being either FigClass or FigClass2 depending on UML diagram implementation. I tested reverse engineering using UML2 diagrams, EUML and the Java module. Some exceptions were shown which is hardly surprising but the correct diagrams and Figs were created. (Thomas - I also adjusted your sequence diagram rev eng so that it also uses this interface) So UML2 class diagrams or ready to code, other diagrams can be added at any time. Please join in and help. Andreas, I noticed I missed your last question > Or do you want to make the last step and create argouml-app2, > which means, that you effectively forked the project in the same > trunk? :-) No, there wouldn't be any point in splitting into two frameworks that do the same thing. The main thing that needs to be abstracted is UML2. I'd also like to see movement towards abstracting out GEF and this is certainly a step in the right direction. Regards Bob. 2009/8/9 Bob Tarling <[email protected]>: >> Do you want to more DiagramFactory, DiagramType etc out, too? >> Just worked with that stuff yesterday and other classes, like >> the ProjectManager (or the module I worked on yesterday) rely on >> that. > > I see no reason for DiagramFactory or DiagramType to change in the short term. > > Eventually though DiagramFactory will need its references to the > UML1.4 diagrams removed so that any diagrams can plug in. > > DiagramType will need expanding to include all the possible diagram > types, it is limited to only the UML1.4 diagrams at the moment. > > My next step will be creation of the diagram2 module and moving the > current structure2 modules into that. Based on my previous explanation > I think that is the place where UML2 diagram implementation can then > start to take place. > > After that I'll look at a simple factory for creating DiagramElements > so that things like the reverse engineering module can create a > FigClass or a FigClass2 without having to test any conditions or even > be aware that is is dealing with a GEF Fig class. > > Bob. > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2382220 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]]
