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

[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.
Eventually it could also help to point to "good" plugins?

:Stefan

[1] http://giswiki.hsr.ch/QGIS_for_Devs#Guidelines

2016-02-19 13:59 GMT+01:00 Etienne Trimaille <etienne.trimaille at gmail.com>:
> 2016-02-19 13:28 GMT+01:00 Victor Olaya <volayaf at gmail.com>:
>>
>> I dont think that many plugin developers are aware of them
>
>
> Yes, exactly. I've heard of them one time.
> Maybe we could add them into the plugin builder as an example. Developers
> will see them in the code.
>
>> I will be happy to provide guidance to any plugin authors that want to
>> convert their plugins into Processing providers
>
> Is there a list of the public API of Processing ?
> For plugins developpers, there are many classes in Processing but a lot of
> them shouldn’t be used outside of Processing I guess, right ?
> I can see : tools/vector, tools/raster, core/GeoAlgorithm, core/parameters
> ...
>
>
>> 2016-02-19 13:24 GMT+01:00 Neumann, Andreas <a.neumann at carto.net>:
>> > 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 for Python plugin authors to make them
>> > aware?
>> >
>> > Andreas
>> >
>> > On 2016-02-19 11:36, Denis Rouzaud wrote:
>> >
>> >
>> >
>> > On 02/19/2016 11:29 AM, Nyall Dawson wrote:
>> >
>> >
>> > On 19 Feb 2016 19:35, "Etienne Trimaille" <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>:
>> >>>
>> >>> 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
>> >>> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
>> >>> _______________________________________________
>> >>> 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
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> 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
>> >
>> >
>> >
>> > _______________________________________________
>> > 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
>> >
>> >
>> >
>> > _______________________________________________
>> > 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
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > 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
>> _______________________________________________
>> 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
>
>
>
> _______________________________________________
> 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