From: Dan S. <dy...@fu...> - 2000-12-06 04:31:37
|
I've contributed my Makefile into the CVS, along with updating the /api/ and /util/ files with semi colons (that's enough ;'s for one night). The JSPack util that is needed to build the compressed DynAPI is released separately: http://www.dansteinman.com/jspack/ Also, I SERIOUSLY recommend removing the /js/ directory altogether. We don't want people submitting changes to the files in /js/ because that is the directory that is automatically created by the makefile. The examples need to be updated to point to /src/. Also it would be good to ensure that all the examples use the DynAPI include() so that the switch from /src/ to /js/ is a one line change. The DynAPI packages that are created by the makefile/jspack will not work correctly yet. If there is even one line that does not have a semi colon in the right spot nothing will work. The Makefile produces a duplicate copy of the /src/ tree with all the .js files compressed. It also creates .js packages of all the files in the subdirectories(eg /lib/dynapi.api.js) as well a "all" package which contains everything. It goes one step further to Jar and Gzip those package files. As I mentioned earlier the significant semi colon to look for is in this case: method = function() { }; // it occurs in event listeners and every prototype in the DynAPI Also it's better now to never do one line methods like: obj.prototype.method=function() {code} Just because it's not easy to spot where the ;'s go: obj.prototype.method=function() {code;}; // better to unwrap this The files that need to be updated with semi colons are in /gui/ and /ext/. At that point we should be able to build and a working compressed DynAPI. It's really quite a dramatic compression. From 100Kb of code down to 15Kb Jar and Gzip = 85%. Pretty darned cool if I say so. Robert will you be able to use jspack on the sourceforge server for cron jobs? Let me know of any problems, Dan |