How do Status and Audience affect the GUI

Development
1

Gramps 5.2 added plugin filtering for ‘installation’ with the creation of Addon Manager. And new Register option attribute/property called Audience and options for Status (EXPERIMENTAL, BETA) options were added.

But the application seems to have little awareness of the new registration attributes after installing.

For some other registration attributes, there’s some registration-based filtering of the GUI showing plugins with:

  • Debug Mode and audience=DEVELOPER (or is it based on a status=unstable?)
  • Catgory-based filtering in the ‘Gramplet add’ menus with navtypes=

Some filtering on the server admin side

  • make.py filtering the addons-__.json using the gramps_target_version

What are the (post installation) implications of the Status and Audience plugin registration attributes/properties?

2

@Nick-Hall made a recent comment in a MantisBT issue about this topic.

0013632: [Python Eval] Reset registration from Unstable to Stable to make accessible

Audience is only useful when selecting an addon to install.

Any plugin with a status of “Unstable” is only available in developer mode (running Gramps without the -O flag).

Installing an “Unstable” addon could be confusing to users not running in developer mode, since they won’t be able to see their newly installed addon. Perhaps we should restrict showing “Unstable” addons to developers?