What category should be used for ‘diagnostic’ testbed plug-ins? Probably for Developer Audience, but how else to categorize them?
Background:
Last year, the Perplexity AI was agonizing to use for “wish-coding”. This year is the same.
However, wish-coding using ChatGPT ( launched from the sidebar when browsing the GitHub repo) was more successful.
I expect to need more of such exploratory tools. The list of paths/variables above is one example. And the questions recently asked about MediaRefs rectangles targets another possibility.
Yesterday, began exploring how to detect the locale being used in the Gramps GUI. (The goal is to learn enough to make the “Local Term” default to the current locale for the 1st column of Glossary Terms… instead of just assuming English.) So after Perplexity frustrated beyond endurance when trying to do this same “Python Eval” style code to explore gramps.gen.utils.grampslocale, I switched to ChatGPT in the GitHub repo.
Since that AI had access the Gramps code as context, it seemed reasonable try to make it a gramplet too. I’ve lost track of this thread (and its Python code snippet) far too many times. A gramplet would be harder to misplace.
I gave it the Prerequisites Checker as a example of what was desired. Even so, after getting past the usual cycle of resolving errors reported to the console, we went round and round with tests only showing blank gramplets but no console messages. (Which was the identical problem during another earlier attempt at making a gramplet. )
Eventually, we got to the code for the following Locale Checker gramplet for the Dashboard and fully commented it:
- Environment Inspector
list installed languages and values for environment variables, Gramps constants
