05-01-2024, 02:46 PM
Just a follow up. I decided to still use a bridge between Gimp and the pipeline (Prism) - to be able to handle different versions of each. I have it mostly working, with a lot of frustration on the way. But found some ways to help in the coding. And I thank you for the suggestions.
The architecture is now:
- a Gimp plugin that registers the menu items, and each menu item will call a subprocess.Popen to the bridge. The bridge will load Prism into its own Py3 enviro.
- another Gimp plugin that launches from the menu that will start a loop that opens a socket between this plugin and Prism. This is inside the Gimp enviro. When a command is received from Prism, it will execute inside Gimp and sends back a response on the socket.
That is actually working pretty well and doesn't seem to fail. A pleasant surprise.
I have this working on Gimp 2.10, but I should be able to adapt it to 2.99(3) as well.
But I do have some other questions that I will put in another thread.
J.
The architecture is now:
- a Gimp plugin that registers the menu items, and each menu item will call a subprocess.Popen to the bridge. The bridge will load Prism into its own Py3 enviro.
- another Gimp plugin that launches from the menu that will start a loop that opens a socket between this plugin and Prism. This is inside the Gimp enviro. When a command is received from Prism, it will execute inside Gimp and sends back a response on the socket.
That is actually working pretty well and doesn't seem to fail. A pleasant surprise.
I have this working on Gimp 2.10, but I should be able to adapt it to 2.99(3) as well.
But I do have some other questions that I will put in another thread.
J.