Hi all, I am also +1 on having "-deprecated" files whereever possible.
A simple but very good idea, both for having smaller builds and educating users to change client code to be independant of deprecated code. Best regards, Marc On 25.09.2011 13:38, Xavier Mamano (jorix) wrote: > Hi, > > In OL exists code labeled as *Deprecated* but it is not possible to > exclude deprecated code in compressed code, examples: "Util.js", > "BaseTypes/Class.js", "BaseTypes/Element.js" ... > > If these source files are split into two, for example "Util.js" and > "Util-deprecate.js" (with "@requires OpenLayers/Util.js"), so could easily > create configuration files to exclude deprecated code. > > NOTE: In the far future the advanced optimization of "Closure Compiler" > can also help, but not in the medium term. > > Xavier Mamano > > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/OL-build-Why-put-in-the-code-compressed-code-deprecated-tp6828967p6828967.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 > _______________________________________________ Dev mailing list d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-dev
