[Qgis-developer] QGIS 3 plugins - require implementation as processing algs?

[Ricardo Filipe Soares Garcia da]

+1 it is a great idea. I've been teaching a few training courses on Python
and QGIS for prospecting plugin writers and I'm always reccommending
creating new plugins via processing rather than standalone (after going
through what is possible and what is not).

The main issue here, in my opinion, is the lack of documentation on
processing. In my training courses I usually provide a UML class diagram
with the main classes of processing and then direct people directly to the
source code at github. I think this scares them a bit, but I haven't found
a better way.

What about improving  processing's docstrings with more detail and then
including them in the QGIS docs site as Sphinx docs?
I can volunteer to help out with writing some of these docstrings, if
needed.

Best regards

On Monday, September 12, 2016, Paolo Cavallini <cavallini at faunalia.it>
wrote:
> Il 12/09/2016 08:22, Alexander Bruy ha scritto:
>> +1 from me too.
>>
>> As Victor said we already have enough documentation and
>> there are many Processing providers in our repo which can
>> be used as examples.
>
> Hi,
> sure, we just have to make all this very easy to find and follow.
> Thanks.
>
> --
> 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

-- 
___________________________ ___ __
Ricardo Garcia Silva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20160912/9aa0e4c5/attachment.html>