[Qgis-developer] organizing plugins
Borys Jurgiel
borysiasty at aster.pl
Thu Apr 29 09:11:36 EDT 2010
Dnia czwartek, 29 kwietnia 2010 o 13:08:28 Micha Silver napisał(a):
> > * file format conversions
>
> as a plugin
>
> > * importing text files
>
> could be in core
>
> > * dxf reading/conversion
>
> plugin
>
> > * WFS support
>
> yes, core functionality
>
> > * GPS support
>
> plugin
>
I'd like to see one coherent subsystem for opening (and saving) data - no
matter if they are files, databases, web services or gps devices.
No we have the main "Add vector layer" window with various sources unusable or
with limited functionality (CSV, GRASS, PostGis) + separate plugins providing
the same data source with full functionality. Also we have a big mess with
SQLite/SpatiaLite: spatialite layer creation in core, spatialite layer adding
in plugin, OGR's sqlite layer adding and saving in core. Do we really need the
two sqlite formats?
So even if some providers would be pluggable, they should integrate with other
providers, and not sink in the plugin menu.
Maybe it's an answer for the old question: should we rather keep all plugins
in their menu, or deploy them into all existing menus. What about keeping
providers all together and separately other plugins all together.
More information about the Qgis-developer
mailing list