Hi, Features proposed in the patch http://trac.osgeo.org/openlayers/ticket/2972 #2972 for use of the Closure Compiler:
- Use any OpenLayers configuration (*.cfg) - Show where there have been compilation errors: source file and line number (source code is used, not jsmin) - Maximize the checks but discard massive warnings (9676 warnings reported using "- warning_level VERBOSE"!) - Ensure the verification of undeclared variables (distractions make these variables as global, see #2960 and #2971) - Use externs to declare names of other products, commercial maps, Proj4js ... - Use SIMPLE_OPTIMIZATIONS, which compresses the code by 20% (ADVANCED_OPTIMIZATIONS requires a study of the pros and cons) - Launch the Java compiler from phython (discard the use of the Service API. To call the compiler uses material from "Closure Library") In the previous post did not have time to detail the features. Now I do not go more in detail so as not to bore people:-) Regards, Xavier Mamano -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Call-the-Clousure-Compiler-using-build-build-py-in-2-1x-tp5823963p5823963.html Sent from the OpenLayers Dev mailing list archive at Nabble.com. _______________________________________________ Dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-dev
