Hmm That reminds me on the consolidation efforts .. There is a lot of outdated, wrong information somewhere in the wiki - (including my translation pages as well). And I agree that all this things should be either deleted or made unavailable to public.. But who is going to do it? I guess thats the question since more than a year .. I am also afraid of deleting things I don't know - might be important for some people I always think..
Unfortunately I have no suggestion howto solve that problem without having to rewrite everything from scratch.. deleting the old pages immediately after rewriting.. kind regards Werner On Thu, Jan 24, 2013 at 1:26 PM, Pirmin Kalberer <[email protected]>wrote: > Hi Alex, > > Am Donnerstag, 24. Januar 2013, 10.40:00 schrieb Alexander Bruy: > > > > please note that most of this methods were marked as deprecated for > > a long time. Some of them are deprecated since QGIS 1.6 or even > > earlier. > > Where exactly is it marked as deprecated? At least not in the API docs [1]. > And the current PyQGIS cookbook shows it as an example [2]. > I'm only asking for a more user friendly way than having to read the C++ > source code first. > > Pirmin > > [1] > > http://qgis.org/api/1.8/classQgsMapLayerRegistry.html#a06a1339cd757608a61e3899a27f39e8a > [2] http://www.qgis.org/pyqgis-cookbook/loadlayer.html#map-layer-registry > > > > > On Thu, 24 Jan 2013 00:57:26 +0100 > > > > Pirmin Kalberer <[email protected]> wrote: > > > Hi all, > > > > > > I found the time for an OpenLayers plugin release with merged pull > > > requests > > > for Stamen map support and fixes for Python API breaks in master branch > > > (See https://twitter.com/PirminKalberer/status/294226472707715072 for > > > credits). The second point was quite annoying for many users and > myself. > > > It is a really bad practice to break the API without deprecation > messages > > > when calling these methods. There should be enough time (at least one > > > minor version) for developers for updating their plugins. In this case > it > > > would have been easy to keep the old API and add a deprecation message > > > similar to > > > http://code.activestate.com/recipes/391367-deprecated/ > > > > > > Regards > > > Pirmin > -- > Pirmin Kalberer > Sourcepole - Linux & Open Source Solutions > http://www.sourcepole.com > > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
