Hi developers, OpenLayers is not ready to use Closure Compiler ADVANCED_OPTIMIZATIONS. Now the resulting code fails.
With adjustments in the source, the resulting code can run, and the result is: 46 kb for lite.cfg, less than 40% of "jsmin" try http://xamamano.appspot.com/ol/46kb/example.html this (with basic changes get 57kb, see http://code.google.com/intl/ca/closure/compiler/docs/api-tutorial3.html#propnames Inconsistent Property Names ; and with more work is obtained 46kb, see "very pure javascript" in http://osgeo-org.1803224.n2.nabble.com/OpenLayers-without-warnings-using-the-Closure-Compiler-in-VERBOSE-mode-tc5916529.html OpenLayers without warnings... ) I have several reasons to believe that the use of advanced optimizations is inappropriate to distribute the OpenLayers code. ADVANCED_OPTIMIZATIONS can only be suitable for building customized projects, but currently is unbeatable in this area. NOTE: All calculations are not including the license (5kb) Regards, Xavier Mamano -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Advanced-Closure-Compiler-for-OpenLayers-lite-cfg-46-kb-tp5931700p5931700.html Sent from the OpenLayers Dev mailing list archive at Nabble.com. _______________________________________________ Dev mailing list d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-dev
