Hi all, Christian Boulanger wrote: > I had proposed compiler options like this: > > --xslt-use-stylesheet=/path/to/stylesheet.xsl \ > --xslt-output-dir=/path/to/source/class \ > --xslt-use-template-dir=/path/to/dir/containing/xml/templates,\ > /path/to/dir/containing/more/xm/templates > > and some attribute in the top-level widget node that indicates where the > generated javascript class code is to be put. The generated code is then > optimized and "compiled" with the rest of the source code. For the benefit of clean interfaces, there might be a better way. The generator of qooxdoo is already doing too many (divergent) things, IMHO. Having a separate migrator is probably proof for that. Rather than integrating on the generator level, pushing even more functionality into it, you could integrate *on top of it*. In the case of the XSLT code generation, that is a distinct and self-contained step *before* any of the classical qooxdoo tools kick in, and has also a distinct interface to the later steps: the file system.
So why not have a separate QxTransformer environment and build system, alongside to standard qooxdoo, and *above both* e.g. a make file that drives the XSLT tranformation first, generating qooxdoo code into a skeleton-like environment, and then invokes the skeleton make file to generate the qooxdoo application. That would be a natural integration to me. Bottom line: Rather than making QxTransformer a part of qooxdoo, make qooxdoo a part QxTransformer (that's actually what it is). Whether this top-level make file could be sufficiently generalized and should be maintained as part of the qooxdoo source tree remains open, but I don't quite see that at the moment. =Thomas ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
