Hi list Ok for removing the deprecated methods, but we really need to have a documented wiki page with a list of deprecated methods and the appropriate replacement.
Classic use case : you have developed a plugin. After the api break, you have several warning and error about "this method does not exists" -> hop, you go to the dedicated web page and you can see which new method to use instead. Michael 2012/12/19 Nathan Woodrow <[email protected]> > Hey Alex, > > I think we should be removing them as I think that is a overall goal for > 2.0. I think we can just remove them. We should be able to diff the API > docs once 2.0 is out to find out which methods have been added or removed. > > That is my thinking anyway. > > - Nathan > > > On Wed, Dec 19, 2012 at 10:00 PM, Alexander Bruy <[email protected] > > wrote: > >> Hi all, >> >> anyone works on API (both C++ and Python) cleanup? As I can see there >> are about 90 deprecated methods available (for example, look at >> QgsRasterLayer class), maybe we have even more, because not all >> methods may be marked as deprecated. >> >> Should we remove them? If yes which procedure is correct? >> >> Thanks >> -- >> Alexander Bruy >> _______________________________________________ >> 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 > >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
