4 ms·
I don't even understand what the standalone Python interpreter is used for; for plug-ins wouldn't you expect the hosting application to integrate the interprete
by unwind 6y ago
I don't even understand what the standalone Python interpreter is used for; for plug-ins wouldn't you expect the hosting application to integrate the interpreter? That's at least my "traditional" view of how application plug-ins work.
On the other hand it's 20 years since I last worked with GIMP plug-ins, and back then it was C all the way.
- pjmlp 6y agoGIMP always supported their Scheme dialect.
- re 6y agoGIMP plugins run in a separate process from the main process. My guess is that the main motivation is resiliency, to prevent crashes in buggy plugins from taking down the whole program. The plugin is essentially a standalone program that loads a library to help it talk to the parent process, in the case of both C and Python, so there isn't a real need to embed the Python interpreter in another process like you would with a more "traditional" Python plugin architecture. https://wiki.gimp.org/wiki/Hacking:Plugins#GIMP_Plug-in_Architecture https://wiki.gimp.org/wiki/Hacking:Plugins#GIMP_Plug-in_Arch...
- unwind 6y agoThanks, that makes sense of course and I'm pretty sure me[-20 years] knew this but it has since been flushed out of the poor brain tissue.
- resoluteteeth 6y agoGimp has had python plugins for more than 20 years, so it probably hasn't changed since you worked with them before: https://www.gimp.org/docs/python/index.html https://www.gimp.org/docs/python/index.html