This pluggable approach was used in ArgoPrint to handle document generation. It currently supports an XSLT and a Velocity plugin. I had a lot of trouble initially creating XSLTs to transform XMI and PGML into different document types and therefore decided to support Velocity as an alternative. The main advantage to Velocity is it's support for Java, which makes it possible to call ArgoUML's model API and fish out diagram and model information.
Mark On Thu, Jan 22, 2009 at 12:41 PM, Bob Tarling <[email protected]> wrote: > Hi Anthony > > We have some XSLT being used in ArgoUML. In particular with converting > the UML1.3 XMI to UML 1.4 XMI and also with upgrading our own XML file > formats between different ArgoUML releases. > > I'd agree with Tom though that there are simpler template languages > around that are likely to be more easily supported by a wider range of > developers. > > That said if we have the graphics generation pluggable then anyone can > develop any alternative they wish should they wish. > > I think XSLT is best for XML to XML transformation. Where we have a > requirement to call java code to fetch data values I think the simpler > template languages should suffice. > > Regards > > Bob > > > 2009/1/22 Anthony Rogers <[email protected]>: > > Hi Tom! > > > > Tom Morris wrote: > > > > On Thu, Jan 22, 2009 at 2:57 PM, Anthony Rogers <[email protected]> wrote: > > > > > > Did somebody say "template language"? WooHoo! :) > > > > I'm crazy about XSLT. > > > > > > I think XSLT is crazy too, > > > > Wait…are you saying "crazy" in a good way? That's what I meant—that I > love > > XSLT, not that I think it's "crazy" in the bad sense… > > > > but it's not a template language. > > > > It's not?! Perhaps there's a formal definition of a template language > that > > I'm not aware of. > > > > But all the work I've done in XSL is a bunch of templates. Templates > that > > define "when I encounter this, then output this" are at the heart of XSL. > > > > (Note that I'm now using "XSL" instead of "XSLT" for clarity. > Technically > > XSL is the language, and the term I should have been using all along. I > > have used "XSLT" loosely in my previous message because I picked up the > bad > > habit from others. :) > > > > If we were to go for a template language (which I doubt in this case), > we'd > > probably choose one which was easy to use. > > > > I agree that some XSL can be horribly complex, but for our purposes I > think > > it would be perfectly easy to use. If you doubt me, let me send you some > > example code with skeletal templates, and I'd bet that even someone who > has > > never seen XSL before in their life could probably read and understand > most > > of it in a few minutes. > > > > Yes, I really mean it. :) > > > > —Z > > ------------------------------------------------------ > > http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1043547 > > To unsubscribe from this discussion, e-mail: [ > [email protected]]. > -- Mark Fortner blog: http://feeds.feedburner.com/jroller/ideafactory ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1044036 To unsubscribe from this discussion, e-mail: [[email protected]].
