But Brian, my problem was that the error message returned by the plugin installer
gave no indication as to what the error was or what was causing it.
I have been chasing the Graph View and Network Chart addon error messages for
sometime now. OK I have Graph View installed and working but I still can’t get the
Network Chart (0.0.25) installed. I see the same message as I reported in my original
post. There is nothing at all reported in terminal mode.
I guess I’ve been around software for so long that I still expect even spelling errors
to be located at /var/log/messages.
Perhaps this could be seen as an enhancement request for the Third Party Plugin Installer ?
There are Command line options for checking Prerequisites and debug logging … useful if you had problems that prevent Gramps loading far enough to use a gramplet. A few years ago Gramps use required a lot higher skill levels to install or use. Skills using command line options could be assumed.
Since installer wizards and pre-installs became common, users begin to expect a lot more hand holding. That’s not really likely in open source. Programming of Hand-holding is the most tedious, frustrating and bloat inducing kind of coding. It requires significant skills and creates features that are useful to users for the short time they are newbies. Volunteer programmers are more likely to want to work on features instead.
Gramps has several levels of troubleshooting tools. (Look at the See also section of the Prequisites Checker addon docs.) Depending on what you’re doing (installations, debugging, code exploration, optimizing tests, low overhead use), you can enable different levels… from inside the code or with overrides from the command line or environment variables.
But because added overhead means a performance hit and because there’s serious overlap possibilities with a plug-in framework, there’s wide latitude in which level is enabled. It is informative to occassionally run Gramps from the command line with debug messaging enabled.
If the add-on developer doesn’t enable logging, that’s their choice… or maybe an oversight.