GNOME Bugzilla – Bug 779322
Introduce a global "third-party" plug-ins folder
Last modified: 2018-05-24 17:29:18 UTC
We are currently seeing some fallout from third-party plug-in packs on some platforms - if those come with (additional) DLL files in the Microsoft windows platform, they got the potential to wreck the whole GIMP installation. It's likely not trivial for third-party plug-in maintainers to add a new plug-ins directoy *and* activate this for the user (we might probably want to add API for this, if it isn't there yet). But we could easily have an empty plug-ins/third-party directory and have that as party of the default setup. This would be a first step in a "we want those plug-ins to go there" approach.
I think this is a great idea to avoid confusing the user as to which plug-ins are or are not officially part of GIMP. A possible folder name might be "Community extensions", perhaps located below the last separator, on the same Filter menu level as G'MIC and whatever raw processor plug-in(s) the user might want to use. It also might be nice to label third-party "8-bit only" plug-ins as "8-bit only". Well, to be honest, I already made such a folder for my patched version of GIMP. But there's no API (way above my coding level), and so the plug-ins have to be modified by hand to make sure they go in the right folder (I only have three such plug-ins installed: Resynthesizer, Liquid Rescale, and Saul Goode's Luminosity masks). Technically G'MIC and whatever raw processor plug-in9(s) a user might want to use are also third-party plug-ins. But imho these are too generally useful to be buried in a sub-menu.
How would this be different from the already present personal assets directories ~/.gimp-2.8/[scripts|plug-ins] ? And why doesn't the recently published guide to those directories encourage the use of the personal directories over the global directories?
global vs. user. There is a difference. Think "available to all users on a system, but obviously third-party "
(In reply to Elle Stone from comment #1) > I think this is a great idea to avoid confusing the user as to which > plug-ins are or are not officially part of GIMP. > > A possible folder name might be "Community extensions", perhaps located > below the last separator, on the same Filter menu level as G'MIC and > whatever raw processor plug-in(s) the user might want to use. > > It also might be nice to label third-party "8-bit only" plug-ins as "8-bit > only". > > Well, to be honest, I already made such a folder for my patched version of > GIMP. But there's no API (way above my coding level), and so the plug-ins > have to be modified by hand to make sure they go in the right folder (I only > have three such plug-ins installed: Resynthesizer, Liquid Rescale, and Saul > Goode's Luminosity masks). > > Technically G'MIC and whatever raw processor plug-in9(s) a user might want > to use are also third-party plug-ins. But imho these are too generally > useful to be buried in a sub-menu. Hmm, it seems I completely misunderstood what this bug report is actually about. It's actually about what folder on the file system the plug-in is installed to, and doesn't have anything at all to do with what "folder" on the menu tree the plug-in appears in when the user wants to use a particular plug-in.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/1061.