[Qgis-developer] Preventing plugin conflicts at 2.0
anitagraser at gmx.at
Thu Apr 11 08:53:38 PDT 2013
I think this is very important to reduce stress caused by the API and
therefore plugin break.
On Thu, Apr 11, 2013 at 4:39 PM, Gary Sherman <gsherman at geoapt.com> wrote:
> 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
> 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):
> 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:
> -Alaska Novel:
> -Geospatial Consulting & Hosting:
> "We work virtually everywhere"
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Qgis-developer