The current make.py is actually already a little too overambitious. It tries to build all the PO translation files and different language addon-xx.json files. Perhaps it could limit itself to writing the addons-en.json and maybe the native language .json file.
The rest of the PO file’s term translations could be done as a separate tool. And the other JSON files could be yet another operation. It is likely that all the Weblate data was why the full master build of Gramps is needed.
There’s an opportunity to evolve the process. Without the flexibility in language, the make should adapt nicely to an add on Tool.
Using the stripped down make.py as a foundation, an addon (Developer audience tool) would only need the following functionalities:
- has a text field for a folder path with File Chooser (like the Database path in the Preferences)
- uses the major_version
- adds the local path to the Addon Manager Projects corresponding to the generated JSON listing file
- Open the Addon Manager to the Projects tab so the JSON can be tested.