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

[Denis Rouzaud]

On 02/19/2016 11:29 AM, Nyall Dawson wrote:
>
>
> On 19 Feb 2016 19:35, "Etienne Trimaille" <etienne.trimaille at gmail.com 
> <mailto:etienne.trimaille at gmail.com>> 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 layers (using the symbol for the geometry 
> type and the EPSG if the checkbox is checked in the Processing settings)
> > - the same combobox for table fields (symbol with the kind of field 
> : integer, char ...)
> > - the same output field with the menu (save to temp file, save to 
> vector file, save to ...) like in processing.
>
> 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 consistency with core (and is also a lot of extra work!)
>

I would say, we even need to advertise the custom widgets.
All these widgets are availble in Qt Designer, it's quite easy to use 
them from there.



> Nyall
>
> > - ...
> > So I will try to use that and contribute to these wrappers if I can.
> >
> > 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 very nice settings in Processing like "use selected 
> features", default output format for vector and raster ... I think 
> plugins should try to more compliant with these settings.
> >
> >
> >
> >
> >
> > 2016-02-19 8:55 GMT+01:00 Paolo Cavallini <cavallini at faunalia.it 
> <mailto:cavallini at faunalia.it>>:
> >>
> >> Il 19/02/2016 08:53, Victor Olaya ha scritto:
> >> > I dont think it wil hurt to add it to the main repo. While we 
> develop,
> >> > and the methods are not used yet, it will be just a bunch of files
> >> > with dead code, so it is not risky, and maybe it is easier to engage
> >> > people that way
> >>
> >> I'd vote for it.
> >> Thanks, Victor.
> >>
> >> --
> >> Paolo Cavallini - www.faunalia.eu <http://www.faunalia.eu>
> >> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> >> _______________________________________________
> >> Qgis-developer mailing list
> >> Qgis-developer at lists.osgeo.org <mailto: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
> >
> >
> >
> > _______________________________________________
> > Qgis-developer mailing list
> > Qgis-developer at lists.osgeo.org <mailto: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
>
>
>
> _______________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20160219/a73db9b2/attachment.html>