>> 2. prebuilt version. Not sure >> why it might not improve speed. Need to establish is yes or not is >> would have impact on perfs and why. > > You could create a pre-build qooxdoo using ["qx.*"] as include and > ["qx.test"] and maybe some as exclude in the config (see the BOM > skeleton's config for a primer). >
Ok, we could also fine tune that prebuilt version so it use all potentially used component because for our generated apps, we use only a subset of all possible qx component. > Then in the actual application, load this qooxdoo.js file in the HTML > page via <script>. You might have to provide a few settings, too. Then > load the application script.js. In the application config, exclude > ["qx.*"], so only the application files get compiled together, excluding > all framework classes. Then you'll see. > That's the problem, it would force us to have different source code for the app loading depending if we are using the prebuilt version or not. I guess that the generate overall process can be cut in 2 parts : 1. computation (saved in the cache) 2. merge of all computations in one as small as possible file. Could we call 2 from outside ? This would allows us to use a prebuilt version and continue to use the toolchain. Not sure if I'm clear ... :-) ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
