Yesterday, 10:07 AM
GimpHelpers is meant be copied to the directory with the rest of the Python code, something like this:
{your user profile}/plug-ins
└── your-script-name
├── gimphelpers.py
├── your-script-name.py
└── (some more files are possible)
So you have one copy of gimphelpers per script, or if that bothers you can use a soft link to some common instance.
gimphelpers is a bit in a state of flux currently, and I didn't update the demos to match (but the only place where I expect problems are calls to getConfigArgs where
you can add a * in front of the list of names, or remove the brackets (went for varargs instead of a list).
And looking at it, minimalist demo hasn't been updated either when I found a better way to declare the procedure, so your best bet currently is full-dialog. However, given the interest, I'll update the lot this afternoon while you sleep.
You can also read the IDEsetup file that tells you about some environment variables that are useful when checking the code. Without the proper setup:
> ./full-dialog.py
Traceback (most recent call last):
File "/home/bd/Code/Gimp/gimphelpers/full-dialog/./full-dialog.py", line 26, in <module>
gi.require_version('Gimp', '3.0')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 122, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gimp not available
and with the proper setup run the plugin in a terminal to check that everything is OK.
>./full-dialog.py
./full-dialog.py is a GIMP plug-in and must be run by GIMP to be used
because you get that final message when the plugin runs the last line, so everything else has been syntax checked. If you get there, the plugin will likely register correctly when add to Gimp and then you can start debugging the code.
{your user profile}/plug-ins
└── your-script-name
├── gimphelpers.py
├── your-script-name.py
└── (some more files are possible)
So you have one copy of gimphelpers per script, or if that bothers you can use a soft link to some common instance.
gimphelpers is a bit in a state of flux currently, and I didn't update the demos to match (but the only place where I expect problems are calls to getConfigArgs where
you can add a * in front of the list of names, or remove the brackets (went for varargs instead of a list).
And looking at it, minimalist demo hasn't been updated either when I found a better way to declare the procedure, so your best bet currently is full-dialog. However, given the interest, I'll update the lot this afternoon while you sleep.
You can also read the IDEsetup file that tells you about some environment variables that are useful when checking the code. Without the proper setup:
> ./full-dialog.py
Traceback (most recent call last):
File "/home/bd/Code/Gimp/gimphelpers/full-dialog/./full-dialog.py", line 26, in <module>
gi.require_version('Gimp', '3.0')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 122, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gimp not available
and with the proper setup run the plugin in a terminal to check that everything is OK.
>./full-dialog.py
./full-dialog.py is a GIMP plug-in and must be run by GIMP to be used
because you get that final message when the plugin runs the last line, so everything else has been syntax checked. If you get there, the plugin will likely register correctly when add to Gimp and then you can start debugging the code.