This is the first of two plug-in modules for porthole. This one as the name suggests is to launch etcproposals from within porthole. It is very basic for now but plan to enhance it more. Etc-porposals has a small api to allow apps to refresh its screen, etc.. Reproducible: Always
Created attachment 151709 [details] ebuild
Can't you just ship and install it with porthole and detect at runtime if etc-proposals is installed? Not much point IMO to create separate packages for mostly trivial plugins.
I suppose it would not be that difficult to change the plugin module to detect if the target package is installed and disable itself. For a profuse plugin, that module is unlikely to change. Etc-proposals has potential for more interaction with porthole and could evolve somewhat at a different pace to the base porthole code. That said, minor version bumps to porthole could easily take care of that. I understand the need to find a balance between adding yet another package to the tree vs adding more (potential) bloat to a package. I think in this case the tree wins :) I'll work on the plugins and report back.
My preference on this is to add it to the porthole ebuild with a local USE flag (etc-proposals).
too late :) I have it modified for auto-detection of the target command along with auto-disabling as an active plug-in. Actually I think it will work quite well. I will add a re-scan button to refesh the plug-in list for a running porthole in the next release. For now if a plug-in is installed while active, porthole will need to be re-started to see it. I only have etc-proposals and profuse so far anyway. Also plug-ins are not active by default. They must be enabled via the plug-in settings dialog.
