Improve usability of Toggle Compendium Pack Visibility macro

[Jagusti]

Context

• Existing GM Toolkit macro: Toggle Compendium Pack Visibility

What is the motivation or use case?

The Toggle Compendium Pack Visibility macro script can be manually adjusted to restrict to packs from specific sources and/or package types. This change would provide a user interface to make it easier to select or specify constraints and configurations.

From v11, it is also possible to fallback to a defined default ownership configuration, which may be used to quickly reset changes.

What do you expect to happen?

• Add dialog prompt to allow choice of new ownership levels
  • based on DOCUMENT_OWNERSHIP_LEVELS
  • default to LIMITED for non-GM users and OWNER for GM users
• Add Reset option to set to Default Pack Ownership settings
• Add Toggle option to switch between Limited and Observer for selected packs and roles
• Add option to constrain to one or more package type (eg, "Actor","Item", "JournalEntry", "Scene", "Macro")
• Add option to restrict to packs from specific sources, either
  • selected WFRP4e module
  • selected other compatible modules
  • manually defined list of modules
  • default: all available packs for the wfrp4e
• Add Toolkit option to check and offer offer to toggle visibility of newly installed modules on load

Additional context

This probably won't be backwards compatible prior to v11.

References

Spun out of #225

[Jagusti]

Add Toolkit option to check and offer offer to toggle visibility of newly installed modules on load

This might need a cunning / laborious hack, as there's no record of newly installed modules.

If instead I can intercept a save operation on the Module Management form app, ...
(maybe in or around ModuleManagement._updateObjector SettingsConfig.reloadConfirm)

... then I can retrieve the checked list of modules using

ModuleManagement.prototype.getData().modules.filter(m => m.active)

... and compare it with the actually active list of modules using

game.modules.filter(m => m.active)

If there's a meaningful difference, I can set a temporary world flag which I check on reload to prompt the GM about toggling compendium visibility. Once confirmed (either way), I can delete the flag.

There may be some benefit to using the hasPacks property to determine a meaningful difference, as I only really care about those modules with compendia.

ModuleManagement.prototype.getData().modules.filter(m => m.active && m.hasPacks)

[Jagusti]

On Hold until I've made some progress with #288 or #287.