<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I like this proposal!<div><br><div><div>On 2011-09-27, at 12:42 AM, Eric Lemoine wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br>On Sunday, September 25, 2011, Xavier Mamano (jorix) <<a href="mailto:xavier.mamano@gmail.com">xavier.mamano@gmail.com</a>> wrote:<br>> Hi,<br>><br>> In OL exists code labeled as *Deprecated* but it is not possible to<br>
> exclude deprecated code in compressed code, examples: "Util.js",<br>> "BaseTypes/Class.js", "BaseTypes/Element.js" ...<br>><br>> If these source files are split into two, for example "Util.js" and<br>
> "Util-deprecate.js" (with "@requires OpenLayers/Util.js"), so could easily<br>> create configuration files to exclude deprecated code.<br><br>Hi<br><br>I think that's an interesting idea.<br>
<br>People who do use deprecated code in their apps would need to include *-deprecate.js files in their builds but I guess this is something we can document in the release notes.<br><br>For classes I guess we would have lines like "MyClass.prototype.myDeprecatedFunction = function() { ... };" in the -deprecate.js files.<br>
<br>I'd see this as a smooth transition towards actually removing deprecated code, both for users and us developers.<br><br>What do others think about it?<br><br><br>-- <br>Eric Lemoine<br><br>Camptocamp France SAS<br>
Savoie Technolac, BP 352<br>73377 Le Bourget du Lac, Cedex<br><br>Tel : 00 33 4 79 44 44 96<br>Mail : <a href="mailto:eric.lemoine@camptocamp.com">eric.lemoine@camptocamp.com</a><br><a href="http://www.camptocamp.com/">http://www.camptocamp.com</a><br>
<br>
_______________________________________________<br>Dev mailing list<br><a href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a><br></blockquote></div><br></div></body></html>