[Qgis-developer] Plugins: "standalone" versus more tightly integrated
matthias at opengis.ch
Mon Nov 14 04:28:55 PST 2016
The opt-in approach was for plugin development in general. As long as
the API is there, anyone is free to use it or not. What's done for a
specific plugin - like qgis2web in this case - is up to its developer.
Anyway, for an example of what's possible now, have a look at the globe
plugin which uses the plugin API to register additional pages.
On 11/14/2016 12:57 PM, Tom Chadwin wrote:
> Hi Matthias
> Yes, I'm talking about qgis2web, but thought the discussion was generally
> relevant. I'm not sure I agree with the opt-in approach. I think either it
> stays as it is, or the single dialog disappears, and it is embedded as
> Nathan suggests. Users could then configure the qgis2web panes in their QGIS
> UI layout, but I don't think the single dialog would remain.
> Thanks for the thoughts
> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
> View this message in context: http://osgeo-org.1560.x6.nabble.com/Plugins-standalone-versus-more-tightly-integrated-tp5295643p5295650.html
> Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
More information about the Qgis-developer