Re: [Qgis-developer] A common set of functions for QGIS plugins

2016-02-19 Thread Paolo Cavallini
On 2016-02-19 17:28, Stefan Keller wrote: I support Etienne's proposal regarding UI guidelines. I'm sproradically collecting these here [1], like the "File open..." dialog which remembers the directory, or preferring GeoPackage over Shapefiles for storing. There are quite some more things which

[Qgis-developer] Plugin [284] Semi-Automatic Classification Plugin approval notification.

2016-02-19 Thread noreply
Plugin Semi-Automatic Classification Plugin approval by lucasupervised. The plugin version "[284] Semi-Automatic Classification Plugin 4.9.3" is now approved Link: http://plugins.qgis.org/plugins/SemiAutomaticClassificationPlugin/ ___ Qgis-developer

Re: [Qgis-developer] A common set of functions for QGIS plugins

2016-02-19 Thread Stefan Keller
Hi, I support Etienne's proposal regarding UI guidelines. I'm sproradically collecting these here [1], like the "File open..." dialog which remembers the directory, or preferring GeoPackage over Shapefiles for storing. There are quite some more things which to my mind when thingking of UI.

[Qgis-developer] Plugin [564] Pic2Map approval notification.

2016-02-19 Thread noreply
Plugin Pic2Map approval by pcav. The plugin version "[564] Pic2Map 3.0 Experimental" is now approved Link: http://plugins.qgis.org/plugins/Pic2Map/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info:

[Qgis-developer] Plugin [933] Raster legend sensitive approval notification.

2016-02-19 Thread noreply
Plugin Raster legend sensitive approval by pcav. The plugin version "[933] Raster legend sensitive 0.3 Experimental" is now approved Link: http://plugins.qgis.org/plugins/rasterlegendsensitive/ ___ Qgis-developer mailing list

Re: [Qgis-developer] A common set of functions for QGIS plugins

2016-02-19 Thread Victor Olaya
+1 to promote the custom widgets. I dont think that many plugin developers are aware of them, since there is no documentation about them AFAIK 2016-02-19 13:24 GMT+01:00 Neumann, Andreas : > Hi, > > The upcoming user conference in Girona may be a good opportunity to present >

Re: [Qgis-developer] A common set of functions for QGIS plugins

2016-02-19 Thread Neumann, Andreas
Hi, The upcoming user conference in Girona may be a good opportunity to present and advertise about both the common set of Python functions, but also about the standard and custom widgets. The CfP is still running and they are looking for more submissions. Maybe someone could do a presentation

Re: [Qgis-developer] A common set of functions for QGIS plugins

2016-02-19 Thread Denis Rouzaud
On 02/19/2016 11:29 AM, Nyall Dawson wrote: On 19 Feb 2016 19:35, "Etienne Trimaille" > wrote: > > I'm discovering that 'old' topic. > Yes, I really like the idea, but I wasn't aware about that. > I think the UI should be

Re: [Qgis-developer] A common set of functions for QGIS plugins

2016-02-19 Thread Nathan Woodrow
On Fri, Feb 19, 2016 at 8:29 PM, Nyall Dawson wrote: > Just a little advice - we need to push people toward the standard widgets > for these, eg QgsFieldComboBox, QgsMapLayerComboBox. Reimplementing then > with new Python versions isn't a good idea, since it breaks

Re: [Qgis-developer] A common set of functions for QGIS plugins

2016-02-19 Thread Nyall Dawson
On 19 Feb 2016 19:35, "Etienne Trimaille" wrote: > > I'm discovering that 'old' topic. > Yes, I really like the idea, but I wasn't aware about that. > I think the UI should be more uniform between plugins and QGIS, for instance to have : > - the same combobox about

Re: [Qgis-developer] A common set of functions for QGIS plugins

2016-02-19 Thread Victor Olaya
> > By the way, is it possible to recommend on the pyqgis cookbook (or the qgis > documentation) to use the processing framework more often ? A lot of plugins > are useful but we can't use them in batch mode or in complex workflow. > Moreover, they often produce only shapefile. > There are some

Re: [Qgis-developer] A common set of functions for QGIS plugins

2016-02-19 Thread Nathan Woodrow
Given that we have 3.0 on the cards and that has a planned API break and refactor I think this stuff is better planned for that so we can all focus effort on making that good. Thoughts? On Fri, Feb 19, 2016 at 6:35 PM, Etienne Trimaille < etienne.trimai...@gmail.com> wrote: > I'm discovering

[Qgis-developer] plugin isse GeODinQGIS

2016-02-19 Thread Boehnke, Christian [FCG]
Hello, we have an issue with our new plugin "GeODinQGIS". Unfortunately it is impossible for me to change the plugin title in the repository from "GeODin QGIS" to "GeODinQGIS", without white spaces. The version title with white spaces causes an error in the QGIS plugin manager as the plugin

Re: [Qgis-developer] A common set of functions for QGIS plugins

2016-02-19 Thread Etienne Trimaille
I'm discovering that 'old' topic. Yes, I really like the idea, but I wasn't aware about that. I think the UI should be more uniform between plugins and QGIS, for instance to have : - the same combobox about layers (using the symbol for the geometry type and the EPSG if the checkbox is checked in

Re: [Qgis-developer] Output directory

2016-02-19 Thread Paolo Cavallini
Il 18/02/2016 09:06, Victor Olaya ha scritto: > I added this handy method to our library of common utils > > https://github.com/qgis/pyqgis_wrappers/blob/master/parfait/gui.py#L24 > > It basically stores the path entered by the user, along with the > caller method, so the next time the user is