> Is it possible to seperate the SDK's genarated .js code away from > custom.js > in case of make build? > E.g., I don't want to have sdk's code inside custom.js when I build > it.
I'm not sure that is a great idea. 1. A new SDK might mean a new interface, so your custom.js would have to change as well. 2. When the integrated script is compiled, the build system automatically throws away SDK classes that aren't used, optimising the space taken. That wouldn't be possible in the system you are proposing. 3. It's possible to compress the scripts, so making a single large file more efficient to download. Here, we have around 800K of JS source as well as the qooxdoo source and the built version, compressed, is just 210K. 4. Browsers download JS files in series - that means that you would incur a delay due to downloading the SDK file, parsing and running it, then downloading the custom.js file. 5. A single file is a huge advantage for releasing a new version. I've spent enough time with DLL hell to be very thankful that everything is in one compiled file. Hugh ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
