[OpenLayers-Dev] Re: move deprecated code

[Xavier Mamano (jorix)]

Great! Better today than tomorrow.

A thought:
This may cause some errors to users by the use of undeclared functions, the
Closure Compiler can be 
very helpful to detect the use of undeclared functions. But it requires some
work.

To take this step should be to abandon the use of OpenLayers.Class, and use
pure JavaScript. It may 
be gradual because Class now is compatible with the use of pure JavaScript.
IDEs or other 
validation tools also will benefit from this work.

Xavier Mamano


erilem wrote:
> 
> On Wednesday, November 9, 2011, Tim Schaub <tschaub@> wrote:
>> I should add that I think we should have an explicit deprecation
>> strategy that encourages people to stop using deprecated code.  I'd
>> propose that we mark code as deprecated and keep it in the main lib
>> for one release - including a list of newly deprecated
>> methods/properties in the release notes.  We could leave deprecated
>> methods in the main lib for one release and then move them to
>> deprecated.js.  In the subsequent minor release, we wouldn't have
>> changed the api, but people would have to include deprecated.js to get
>> the old stuff.
> 
> Hi
> 
> Thanks for putting this patch together. I agree with the approach. We can
> even hope to release 2.13 quickly after 2.12.
> 
> When you say mark code as deprecated do you mean having *deprecated*
> strings in the API doc strings, or do you also mean displaying deprecation
> messages in the console?
> 
> 
> 
> -- 
> Eric Lemoine
> 
> Camptocamp France SAS
> Savoie Technolac, BP 352
> 73377 Le Bourget du Lac, Cedex
> 
> Tel : 00 33 4 79 44 44 96
> Mail : eric.lemoine@
> http://www.camptocamp.com
> 
> _______________________________________________
> Dev mailing list
> Dev at .osgeo
> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
> 


--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/move-deprecated-code-tp6976459p6979097.html
Sent from the OpenLayers Dev mailing list archive at Nabble.com.