user-guide:pluginmanager
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| user-guide:pluginmanager [2024/05/27 16:18] – created timob | user-guide:pluginmanager [2025/10/15 08:37] (current) – [Usage from commandline] Tim | ||
|---|---|---|---|
| Line 14: | Line 14: | ||
| On the last tab " | On the last tab " | ||
| + | ===== Deleting/ Deactivating plugins ===== | ||
| + | 1. The parameter file: GroIMP can load options as parameters from either: the default file (in ~/ | ||
| + | The preference file is loaded when groimp starts and its content is used instead of java preferences when an option is queried in groimp. The option name follow the complete name of its registry path (I will provide a list of all option and their paths in the wiki). But for example the option useJRT can be defined as : | ||
| + | / | ||
| + | 2. The plugin manager is accessible from the GUI under " | ||
| + | And (maybe?) if users create new plugins and decide to share them, It could make them available for all other users. | ||
| + | From the plugin manager GUI, you can " | ||
| + | install will try to download it from the given source then dump it in the selected path (selected in the options/ by default ~/ | ||
| + | update: each plugin display its available versions. By selecting a different version you can upgrade/ | ||
| + | disable is more usefull for me to debug. It set some groimp option to load the given plugin as disabled. They are then not usable from groimp. But they are not removed. It adds the option under the currently used property file (either one passed with " | ||
| + | remove simply delete the plugin. It removes it from the computer (so be careful). For groimp instances where the installation path is not writable (usually on windows if you don't run groimp in admin) then, there is an option in groimp to " | ||
| + | The list of available plugin is provided by the " | ||
| + | You can add your repositories that contains plugin metadata as (a JSON that contains the plugins data or a local directory in which some groimp plugin exist). | ||
| + | All of these actions are doable from groim commands. Thus, accessible from the api, cli, and in headless with the command parameter. | ||
| Line 28: | Line 42: | ||
| + | ===== Usage from commandline ===== | ||
| + | |||
| + | it is possilbe to install plugins without opening GroIMP by using the following commands: | ||
| + | < | ||
| + | #install | ||
| + | java -jar core.jar --headless -- -cmd / | ||
| + | |||
| + | #uninstall | ||
| + | java -jar core.jar --headless -- -cmd / | ||
| + | |||
| + | #disable | ||
| + | java -jar core.jar --headless -- -cmd / | ||
| + | |||
| + | </ | ||
| + | |||
| + | ====== Grogra.de mirror ====== | ||
| + | |||
| + | The main plugin manager repository, as well as most of the released plugins, are hosted on gitlab.com. | ||
| + | If you for any reason cant access gitlab.com a mirror is provided at: https:// | ||
| + | |||
| + | To enable this mirror in the plugin manager, go to the " | ||
| + | Set the new repository to " | ||
| + | {{ : | ||
user-guide/pluginmanager.1716819525.txt.gz · Last modified: 2024/05/27 16:18 by timob
