Hi, I don't see much value in removing these classes from the code base now, because I strongly believe in custom build profiles, and they don't have a footprint in the rest of the library.
I do, however, see value in removing the mentioned layers along with all of Layer.EventPane. This means that we won't have any layers that use their own map pane any more (including Layer.Google and Layer.VirtualEarth). Layer.GoogleNG will then replace Layer.Google, and Layer.Bing will replace Layer.VirtualEarth. Making this simplification would allow us to remove some legacy code from other classes as well. Andreas. On Aug 2, 2011, at 11:50 , Frederic Junod wrote: > Hello, > > As you may know, the Yahoo! Maps AJAX API service will be stopped on > September 13, 2011 [1]. > Do we want to keep the OpenLayers.Layer.Yahoo class in 2.11 or simply > drop it now? > > The same applies to OpenLayers.Layer.MultiMap [2]. > > Regards, > > fredj > > [1] > http://developer.yahoo.com/blogs/ydn/posts/2011/06/yahoo-maps-apis-service-closure-announcement-new-maps-offerings-coming-soon/ > [2] > http://blog.multimap.com/2010/11/19/important-news-about-the-multimap-open-api/ > -- > Frédéric Junod > Camptocamp SA > _______________________________________________ > Dev mailing list > d...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/openlayers-dev -- Andreas Hocevar OpenGeo - http://opengeo.org/ Expert service straight from the developers. _______________________________________________ Dev mailing list d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-dev
