Hello,

Here is a "with preview" module (It's just a modification of "gimpfu.py").
It enables you to code "from fu_preview import *" in your python plug-ins to add a preview.
It's given with no warranties at all. It's just a "proof of concept".

Here is an example (the preview has been added to the "groove" plugin):

Installation:

• uncompress the zip file
• copy the "pymod.env" file into the "environ" directory
• copy the "fu_preview.py" file into the "modules" directory

Use:
Replace the "from gimpfu import *" line by "from fu_preview import *"

Limitations:

• only for python plugins using gimpfu
• only for transformational plugins (not creation ones) that don't add new layers
• for now, the preview only reacts to preview moves, slider moves, toggle changes
• if you click "OK" (or "Cancel"?) before preview ends, you get error messages

I've tested it on Gimp 2.10 on Linux, on the "groove" plugin and on the "metalBox" plugin.

Enjoy!

Hi Claude.

A great revelation.

Tested with Win10_64bit Gimp-2.10.24.

First notes:
Put fu_preview.py in the "modules" directory - it doesn't work.
Placement in ... \lib\gimp\2.0\python\fu_preview.py - works.
Pymod.env seems redundant.???
Groove.py works fine with preview.
BoxEffect.py doesn't even register in the menu.
Trying to increase the preview by dragging will usually crash Gimp (but not always) - how to increase the preview window in fu_preview.py?

Thank you very much MareroQ for your valuable feedback,

"pymod.env" enables to put "fu_preview" in "modules" directory ... on Linux.
Here is the content of "pymod.env":
I should have noticed that it's Linux syntax.
Maybe, ": PYTHONPATH=%gimp_dir%\modules:%gimp_plug_in_dir%\python" (or something like that) works on Windows ?

For "BoxEffect.py", I would run Gimp from a command line to check error messages.

Sorry, I cannot test on Windows.

"Trying to increase the preview ..." : I have to investigate.

Hello,

I found an example of syntax for Windows in "default.env" and "pygimp.env" (in Windows Gimp installation)
andSo I guess a right syntax for Windows (to put in pymod.env) would be or

Is there any specific reason fu_preview.py is in "modules" (because it works without pymod.env in ...\lib\gimp\2.0\python \)?
"BoxEffect.py" does not give any error message in "console-message" mode (also not in pluginrc and with sys.stderr).

I did another test: renamed fu_preview.py to gimpfu.py and replaced the original gimpfu.py.
Result - BoxEffect.py works.
I also checked over a dozen other Python plugins - when do they use PF_TEXT, PF_COLOR, PF_PATTERN, PF_GRADIENT, PF_PALETTE ... ???... did not work.
So far this is a rather good solution for quick plugins as it increases (double?) The time (preview generating + generating output).

Edit:
By analyzing the last test from boxEffect.py, I discovered the cause.
In boxEffect.py, gimpfu appears twice (from gimpfu import * and from gimpfu import _query) - after changing gimpfu to fu_preview twice, the plugin works with preview.

Another solution (I tried it - it works) might be to add the code fu_preview.py to each plugin we want to preview (it's only 971 lines of code with a comment - and in Windows there is often a problem with multipart plugins).

Another point is completely different - groove.py needs to be upgraded for gmic-2.9.8. (different number of parameters for fx_curves_interactive).

A simple way to enlarge the preview window (without crashing Gimp):

1. Disable preview.
2. Drag the corner.
3. Turn on the preview again.

Example with embedded code for fu_preview (and customized fx_curves_interactive).
As with groove.py there was a problem with GMIC -fx_curves_interactive (but this is probably a temporary bug with the number of parameters in GMIC because running it gives an error).

Hello,

Thanks again, MareroQ, for your very good work.

I wanted that fu_preview.py won't be overwritten by a new version of Gimp.
(But, maybe, it's a bad idea since, in any case, fu_preview.py might not be compatible any more.)
Yes, I forgot that I have add this line (I've tested a version without this line)
You're right : for now, I only implemented PF_SLIDER and PF_TOGGLE.

I keep my fingers crossed for further rapid development.

I remembered (Ofnuts tip in another thread) how to enlarge the preview window on startup (without dragging the edges).
You need to edit the file gtkrc [... etc\gimp\2.0\gtkrc]

Replace the following lines:



on:



Maybe there are other ways?

Hello,

Thanks, MareroQ, for the Ofnuts's tip.

Here is a new version of the "with preview" module:

New features:
I've made an implementation for PF_COLOR, PF_SPINNER, PF_FONT, PF_STRING, PF_FLOAT, PF_INT, PF_TEXT, PF_PATTERN, PF_OPTION, PF_GRADIENT (not tested), PF_PALETTE (not tested)

Installation:

• uncompress the zip file
• copy the right "pymod_blabla.env" file into the "environ" directory
• copy the "fu_preview.py" file into the "modules" directory

If this doesn't work, put the "fu_preview.py" file into the same directory as "gimpfu.py".

Use:
Replace "gimpfu" by "fu_preview" in your plugin code.

Enjoy!

Many thanks for the new features.
I tested new functions - everything works.

Two minor problems:
- There is a problem when you use the selection
preview (strange shift) - but the result is correct.
- In case of using alpha channel (transparency) it has to be added to the image before using any plugin.

Are You going to add the last missing ones (PF_BRUSH, PF_CHANNEL, PF_DIRNAME, PF_FILE, PF_FILENAME, PF_VECTORS)?

Hello,
Thanks, MareroQ, for your very valuable feedback.

I have not even thought about the possibility of making a selection before using a filter.
This problem seems more complex to fix.
I don't understand.
I hope so. But, I would want to present a "GEGL graph" tutorial firstly.