Hi Alexander, for the other diagrams, we need to specify how they will be created from the sources during import. There is a reason why most UML tools only generate class diagrams, because for other diagrams it makes no sense. For example: I see no way to create sequence diagrams for the whole code, because there are too many sequences. And for a state diagram (which Fujaba does), one need to identify the state of a class, and its transitions, which is very hard. Maybe we should create a table for all diagram types and how they can be generated during import, maybe in a dev Wiki.
I think it's enough to greate the static model only, and later generate other diagrams from the model, not from the code. Just my opinion. Regards, Thomas -------- Original-Nachricht -------- > Datum: Sat, 14 Jun 2008 16:29:50 +0200 > Von: alexander krohn <[EMAIL PROTECTED]> > An: [email protected] > Betreff: [argouml-dev] create diagrams from reverse-engineered code > hi. > > under org.argouml.uml.reveng is a DiagramInterface. this is used by > ImportCommon to create class-diagrams for imported/reverse-engineered > stuff. > > what if i want to create other diagram-types while importing source-files? > > i can't find a way, so i assume it doesn't exist yet ;) > > so the way is to create SequenceDiagramInterface, > ActivityDiagramInterface, etc. to the reveng-package and add an import > option "create diagram-type x". > > correct? any thoughts? > > maybe any experiments done already on this stuff? > > thanks in advance. > > regards, > > alexander > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
