| Summary: | Ability to add or change the directory path(s) from which Krita loads Python plugins. | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | daniel.barinak |
| Component: | Scripting | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | halla |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
On linux, this should be possible by adding that location to XDG_DATA_DIRS, on Windows, MacOS and Android that won't work. (In reply to Halla Rempt from comment #1) > On linux, this should be possible by adding that location to XDG_DATA_DIRS, > on Windows, MacOS and Android that won't work. Any way this idea would see light on Windows, since thats the OS we are using? I didnt test but maybe would symlinks on pykrita folder work? I'm not sure about symlinks, I don't really have experience with them on Windows. On Windows, Qt uses a different system to find resource folders, so we'd still need to add an option in Krita itself to add a folder -- that's why I've confirmed this wish.
In plugins/extensions/pykrita/plugin/utilities.cpp, we need to add a line that adds a folder from a config option after
QStringList pluginDirectories = KoResourcePaths::findDirs("pythonscripts");
And probably also in some places in PythonPluginManager.cpp
|
I’m requesting a feature that would let users define custom paths for loading Python plugins in Krita. Currently, Krita only loads plugins from its default directories, but there’s no built-in way for me to specify an external or centralized location. In my case, I want to maintain a shared set of plugins stored in a centralized location—such as a network folder or version-controlled directory. This would make it easier to: Keep plugins updated in one place. Avoid duplicating plugins across multiple machines or user profiles. Ensure consistent plugin versions across different environments. Ideally, Krita would support this by allowing: A configurable plugin path in the settings. Or a way to define extra paths via a config file. This feature would significantly improve my workflow by making plugin management more flexible and scalable.