2009/1/22 Anthony Rogers <[email protected]>: > 3 things: When I started with ArgoUML it was following the UML1.3 standard for XMI. That standard contained no definition of how UML tools were to save the diagrams themselves, only the non-visual UML model elements that those diagrams represent were clearly defined in XMI.
So all tools came up with their own format for saving the diagrams. Saving diagrams in XMI didn't come in as a standard until UML2 (although some tools did start to apply this standard in UML1.4). We are still working to get to that level. I assume ArgoUML was pre-SVG as someone decided to save the diagrams in PGML format. So in theory that could be transformed to SVG - but in practice no because the PGML we save isn't complete. The purpose of the PGML wasn't to be able to provide some other tool with a visual representation of the diagrams. It was only chosen as a way to store the diagrams for later load by ArgoUML. So anything ArgoUML didn't require in that file was left out to keep the file size low. For example there are certain text labels that aren't currently saved in the PGML because their location is recalculated when the project is loaded abd the text itself is available from the UML model. The PGML is created from a template language that can embed calls to java methods in the template. Much like Freemarker or Velocity but is entirely proprietary to GEF/ArgoUML If we did have the diagrams saved as XMI or even had full and complete PGML then I'd lean further toward XSLT (but maybe not all the way). We're not there yet though. Regards Bob ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1043590 To unsubscribe from this discussion, e-mail: [[email protected]].
