Hi, in qwt (which is built with maven), I have a "qooxdoo" maven module that packages qooxdoo (js + images) into a jar file. However, that's probably not what you want to do because that Jar contains the original JavaScript sources of every qooxdoo file (in individual files, without compression, plus dependency information). Qwt's servlet re-implements the necessary parts of qooxdoo's build system in Java to serve requests: it computes the source files you actually need, and it performs JS compression (not as good as qooxdoo's, but good enough for qwt).
What you could do: invoke qooxdoo's build system from a maven module to generate one qooxdoo file that contains all the JavaScript you need for your application. Package this JavaScript in the module's jar file (and maybe add the images) and reference into this jar file from your server. You'd need Pythin 2.4+ on your build machine ... Regards Michael Vincent Vandenschrick schrieb: > Dear qooxdoo users, > > I'm leading the Jspresso project. Jspresso is an opensource LGPL > framework dedicated at building business RIAs that can be deployed using > various UI technologies without needing any UI specific skills (nor UI > code). Until now, I've implemented the following UI engines for Jspresso : > - Swing > - Canoo ULC (server-side swing-like library) > - WingS (serverside AJAX UI library) > - Flex > > I am currently evaluating qooxdoo as a UI candidate for Jspresso since I > was really impressed by the quality of the internal architecture as well > as the overall L&F of qooxdoo applications. I think that the integration > would be quite straightforward based on what has been achieved for the > Flex (over BlazeDS) front-end (all server-side code can be reused and > only the client engine has to be ported). The clean qooxdoo MVC binding > architecture would perfectly fit. > > I still have several concerns that I would like to have suggestions for : > > - I've never developed a line of Javascript (not a big issue since 6 > month ago I had never touched a line of ActionScript and the Flex > frontend is fine now). What would you recommend for the development > environment? I would like to stick to Eclipse though and have the > qooxdoo build integrated to the overall FW build just by handling a new > source folder in the Eclipse java project. Same goes for debugging. As > an example, FlexBuilder allowed me to seamlessly integrate a flex source > folder into the FW java project. > > - The actual Jspresso builds are entirely performed using maven. This is > really a must-have for me. Reading the docs, qooxdoo relies on custom > Python scripts for all the operations that have to be handled on a > qooxdoo project. But I've read on the mailing lists that some users did > perform an integration into maven. The Jspresso/qooxdoo engine would > actually be a maven module for me. As an example, I've used the > flex-mojos maven plugin to seamlessly integrate the Jspresso/flex > frontend as a maven project module. I don't think that there is such a > plugin available for qooxdoo. I'm taking any advice on how to make the > qooxdoo build part of an overall maven multi-module build... > > Thanks for your suggestions, > Vincent > > ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
