On Wed, 1 Apr 2020 at 21:34, Sebastian M. Ernst wrote:
>
> Hi Etienne, Nyall,
>
> thanks for your replies.
>
> >> Then a plugin can have or not a processing provider (not related to the
> >> statement before).
> >
> > Just to expand on this -- this tag was added to aid in
> >
Hi Etienne, Nyall,
thanks for your replies.
>> Then a plugin can have or not a processing provider (not related to the
>> statement before).
>
> Just to expand on this -- this tag was added to aid in
> https://github.com/qgis/QGIS/pull/34617 , [...]
Ok, this makes sense. I just tried to trace
On Wed, 1 Apr 2020 at 05:22, Etienne Trimaille
wrote:
> Then a plugin can have or not a processing provider (not related to the
> statement before).
Just to expand on this -- this tag was added to aid in
https://github.com/qgis/QGIS/pull/34617 , and expose the metadata
about whether a
Hi,
You will find some answers in the QGIS Documentation about "deprecated",
"hasProcessingProvider" ...
https://docs.qgis.org/3.10/en/docs/pyqgis_developer_cookbook/plugins/plugins.html#plugin-metadata
I'm going to add the "server" one.
> So `experimental` is actually a property of a plugin
Hi everyone,
I am still trying to wrap my head around plugin management. Looking at
(Python) plugin metadata, I have a few questions.
The meta data contains the fields `experimental` and `deprecated`.
Having written plugins, I believe that certain versions of a plugin (but
not "the entire
