[QGIS-Developer] Understanding plugin management in QGIS: Meta data fields

[Nyall Dawson]

On Wed, 1 Apr 2020 at 05:22, Etienne Trimaille
<etienne.trimaille at gmail.com> 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 particular plugin has processing capabilities or not.
The standalone tool will only load plugins which expose processing
capabilities (since the others are of no value to the tool, and just
slow down startup time).

It's completely independent from other options though -- you can have
plugins which add all kinds of things to the QGIS interface and also
expose processing capabilities (e.g. DataPlotly). Likewise you could
potentially have a plugin which exposes server capabilities AND
processing functionality.

Hope that clarifies!

Nyall

>
>
> Le mar. 31 mars 2020 à 20:35, Sebastian M. Ernst <ernst at pleiszenburg.de> a écrit :
>>
>> 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 plugin", i.e. all of its versions of it at once) can be
>> "experimental". So `experimental` is actually a property of a plugin
>> version. Am I correctly understanding this?
>>
>> As far as `deprecated` goes, I have not figured out the dynamics yet. Is
>> it also tied to a version or does a plugin author mark all (past)
>> versions of a plugin as deprecated by uploading a deprecated "final"
>> release?
>>
>> What's the story behind `trusted`? I'd guess that plugins of this kind
>> can be published without a review and a plugin manager on the client
>> should not care about this field.
>>
>> I understand that `id` is *the* unique identifier for a plugin.
>> Eventually, it will be the folder name of the plugin module and it
>> usually equals the name of the plugin distribution zip-file (without the
>> `.zip` file extension). If this is correct: What's the purpose of
>> `zip_repository`? Its description reads "the remote repository id".
>>
>> Reading through the original plugin manager's code, there are actually a
>> few more meta data fields that appear to be undocumented (or at least
>> not listed in a central place): `hasProcessingProvider` and `server`,
>> both of them more or less booleans. Just to be safe here: Is my
>> understanding correct that there are basically three types of Python
>> plugins: "regular", server and processing provider?
>>
>> Best regards,
>> Sebastian
>> _______________________________________________
>> QGIS-Developer mailing list
>> QGIS-Developer at lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer