Rod wrote:
So why doesn't the PDB in Gimp allow GEGL to use all of Gimps procedures to create better filters?
Clearly with all the examples here you call the plug-in and enter its parameters and like magic the filter works.
So why not ask the developers (those guys and gals that write all code for Gimp), to allow the procedure data base and GEGL to interact? Or is that not feasible?
Seems to me Gimp developers are looking to remove all but GEGL from Gimp anyways. So why not grab what they can from existing USER created plugins and scripts to grow GEGL in phenomenal ways?
Right now GEGL being written by users of Gimp has too many limitations.
I say release the craken and allow GEGL and GPDB to mate and create artistic babies together.
![Bump!! :bump](./images/smilies/bump.gif)
In the grand scheme of things (Gimp3),the PDB is used only to call plugins since plugin code (C, Python, JavaScript, Lua...) will use Glib objects to interact with Gimp. And GEGL also has a GLib interface, and so can be called from C, Python , JavaScript, Lua...
Didn't dive into the details, though
![Smile :)](./images/smilies/icon_smile.gif)