On Thu, Mar 23, 2000 at 09:18:22AM -0800, Peter McCombs wrote:
> Hi everybody,
>
> I don't know how active this list is, or if there is anyone here who can
> point me in the right direction.
>
> I'm doing some Linux development and would like to add support for plugins
> to my program. Kind of like what the Gimp does, with that neat procedural
> database. Now, the Gimp is REALLY big with a lot of source code to look
> through, so I was hoping there might be someone with experience in this
> matter to give me some quick ideas.
>
Well, I'm vaguely familar with gimp internals, though the plugin
interface is something I avoid like the plague.
But I have a basic idea how gimp plugins work. The first thing
is that they are seperate executables. The Gimp will fork off the plugin
code, and pass any meta info the plugins needs (image type, etc) over
a pipe to the plugin. The actual image data is communicated via shared memory
on systems that support it. The protocol thats passed over the pipe is
fairly complicated. More info about it can be found in libgimp/gimpwire*
and gimpprotocol*, and app/plug_in.c. The plugin procedures get registered
the first time a new plugin is found, and "cached" in ~/.gimp/pluginrc.
Aside from that, I dont really know.
But more than likely, you just want to dynamically load code
bits at runtime, aka dlopen and friends. Or the glib GModule stuff
for a slightly more abstracted version of the same stuff.
Adrian
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
