-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/02/2012 07:31 PM, Horst Düster wrote: > +1 on Mayeuls comment > > [email protected] schrieb: > >> >>> oh, yes, you're right - it's PostGIS Manager that requires >>> shp2pgsql, >> not SPIT. My mistake. Sure, duplication of tools is bad. But >> removing SPIT would mean removing the *only* (correct?) QGIS GUI >> tool to load shapefiles into postgis without external >> dependencies. Do we want to get read of this before putting it in >> DB manager?
The same with me (beside the fact that I just learned howto use SPIT (thanks Horst)) it seems much more clearer to me using SPIT than using the dbmanager (for now) .. Don't get me wrong .. dbmanager is great but as long as SPIT is more intuitive (maybe because it just does ONE thing) I'd like to wait with removing it until a filedialog import has been implemented that creates something like the batch upload which you currently see when you add more than one shapefile .. But I am quite sure guiseppe will have that soon :) So.. - -1 from me for removing it right now (and probably think about the dependencies too which mayeul pointed out) Beside that .. What about creating hints for obsolete plugins that are getting removed with a hint that the function has been integrated/extended/moved to "the new plugin" .. or maybe a hint inside the plugin that this will become obsolete soon because the function will be available in core/new-plugin-name. marking plugins like that for at least one "official"-release-period will probably easen the migration for the user too.. kind regards Werner -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+hhAcACgkQDAH1YiCxBgkkdwCeOiDF96J6FTJdbQe+8IVb1ESG NwIAnj3euWQOLrYBjion8y0ifngCGLWL =E8B0 -----END PGP SIGNATURE----- _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
