Hi Derrell, > This seems to be getting pretty far out of line. I started a "make build" > nearly 1/2 hour ago, and *it's still running*! With all of these variants and > rebuilding each application multiple times and what not, this is really pretty > unreasonable. > we have added two new optimizations to the build:
- removal of debugging code - browser optimized builds especially the second one uses some time because a separate build for each supported browser (IE, Gecko, Webkit, Opera) and a "normal" version is generated. We have enabled these optimization by default becasue we want as many users (including us ourself) to test it and because we think that for the build the time the make process takes is not that important. You can however always turn off the optimizations selectively. The Makefile variables are: APPLICATION_OPTIMIZE_STRINGS = false // takes some time but improves the performance on IE6 dramatically. Should be true if IE6 should be supported APPLICATION_OPTIMIZE_VARIABLES = false // a bit faster than string optimization. Reduces the files sizes and obfucates the source APPLICATION_OPTIMIZE_REMOVE_DEBUG = false // not very expensive. Removes debugging code like runtime checks and assertions. Should always be true. APPLICATION_OPTIMIZE_BROWSER = false // build takes four times longer. Reduces code size by about 30KB and removes runtime checks. More information on the new optimizations and how they work can be found in our wiki (http://qooxdoo.org/documentation/user_manual/variants). > I think it's time to either modularize qooxdoo, or create "object files" from > each javascript file (or group of files), or something. Granted, applications > needn't go through this whole procedure, but even there the two gripes I get > from the Samba team about qooxdoo is that (a) it takes way too long to build > the application (a couple of minutes just for the gui portion of a Samba > build), and (b) there's too much source (13 MB or 30 MB or something like that > -- either one is huge by Samba standards). If qooxdoo were modularized, only > those modules needed by an application need be retrieved and saved and both > the build time and the source size would be reduced. > The generator already caches the tokenized JavaScript files. You can observe that the first dependency detection takes much more time than the following ones. There is however still much room for improvements. To your problems: a) Try to turn off browser optimization. This will reduce the time to build the application by about 70% b) The biggest part of qooxdoo are propably the icons sets. If you just check in the tools, and framework/source without the not needed images you should have a reasonable qooxdoo size. > I'm not sure exactly how to accomplish this modularization. It may be easier > to create object files and then do a "simple" linking. In any case, I think > it's worth beginning discussion on the best way to substantially decrease > build time. > You are right, with every new build optimization the time to build increases. At some time we have to rework the generator address the build time issues. I still have no idea how to do the modularization but maybe with some more caching/object files we could cut the build time. Best Fabian ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
