Greetings developers, I think we should consider a way to flag existing plugins that are not compatible with the new 2.0 api. This will improve user experience by preventing install of plugins that do not work with the users current QGIS version.
Ideally all plugins would be converted to work with both 1.8 and 2.0, but this either won't happen completely or will take an unknown amount of time. This situation has already happened to those living on the bleeding edge (using 1.9 in production): http://gis.stackexchange.com/questions/57718/qgis-trace-tool-error/57724#57724 One way to do this is to implement a "QGIS maximum version" entry in the plugins metadata (or __init__.py). Alternatively there may be a way to do this with the plugin repository app, however I'm not familiar enough with its implementation to suggest how that could be done. Please provide feedback... -- gary -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Gary Sherman Chair, QGIS Project Steering Committee -Desktop GIS Book: *http://desktopgisbook.com -Alaska Novel: *http://alaskana.co -Geospatial Consulting & Hosting: *http://geoapt.com "We work virtually everywhere" -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
