GIMP 2.8 plug-in protocol

[bootchk]

GIMP 2.8 plug-in protocol

[bootchk]

My first guess is that it has something to do with the parameters to the
register() function, which is part of the plugin protocol.
(The protocol is something like: you must use the MAIN macro and define
a register() function, a run() function, etc.)
I suspect it has to do with the menu item and menu path parameters to
register(). GIMP has been in the process of changing that. Possibly in
2.8 they are refusing what until now has only been deprecated (advised
against, but supported.)

Just my first guess, I will study it further.

On Sat, 2012-02-11 at 17:43 -0800, Joe Lee wrote:

How can I help make Resynthesizer work in GIMP 2.8? I just built it, and when I tried to run it, I got the following two errors:

GIMP Message
gimp_plug_in_handle_proc_run: ERROR

Resynthesize Message
Could not execute plug-in "resynthesizer-gui" (/opt/gimp/lib/gimp/2.0/plug-ins/resynthesizer-gui) because it uses an obsolete version of the plug-in protocol.

What is the plug-in protocol, and where can I find documentation about it?

---

Reply to this email directly or view it on GitHub:
#5

[jplee]

Thanks for the pointers! This is enough information for me to start digging deeper and doing some studying of my own.

[bootchk]

A description of the plugin registration protocol for the Scheme
language is in section 5 at:

http://www.gimp.org/tutorials/Basic_Scheme/

A description for Python is at:

http://www.gimp.org/docs/python/pygimp.html

A description for C is at:

http://developer.gimp.org/writing-a-plug-in/1/index.html

These might be outdated.

I don't have a link to the latest 2.8 documentation for the changed
protocol.

Probably reading the GIMP source is your best bet.

Again, I suspect they changed the parameters to register concerning menu
item and path.

On Sun, 2012-02-12 at 22:14 -0800, Joe Lee wrote:

Thanks for the pointers! This is enough information for me to start digging deeper and doing some studying of my own.

---

Reply to this email directly or view it on GitHub:
#5 (comment)

[bootchk]

I think my above theory is wrong. I found the error message in libgimp/gimp.c. Now I believe the message pertains to the so-called "wire protocol", the IPC inter process communication between a plugin process and the main GIMP process. If so, I think that compiling a plugin against the correct library would fix your problem. In other words, you might be compiling the plugin against the 2.6 libgimp, inadvertantly, whereas it should be compiled against the 2.7.5 libgimp (the nightly build, which you are calling 2.8 but which i believe to be a candidate for 2.8, since 2.8 has not actually been released.)

I could still be wrong.