Re: [GtkGLExt] GtkGLExt in a Mozilla plug-in

[Braden McDaniel <braden endoframe com>]

Shane Blackett wrote:

> We are using GtkGLExt with Firefox and Mozilla(Gtk2 build).  This seems 
> to work fine.  We use the Xembed protocol which is implemented in gtk 
> with gtkplug.  This seems to work well with the current library.

So am I. Is your plug-in in-process, or out-of-process? (Mine is 
in-process.)

> It seems common in the initialisation of the plugin (set_window which 
> does get called multiple times) to check if that routine has been called 
> before and then only to do initialisation operations if it has not been 
> called before.

When the plug-in .so is reloaded, NPP_SetWindow is effectively called 
for the "first" time (i.e., static initialization of the .so has just 
happened). I don't see a way in the plug-in API to store data that will 
persist across instances of loading/reloading the plug-in .so; so, 
there's no way to determine if the plug-in .so has been loaded 
previously. And even if there were, there is the problem that 
libgtkglext itself has problems with being unloaded and reloaded.

> Our code is done with another layer in between called cmgui.  We hope to 
> open source this code shortly however as this is a heavyweight medical 
> imaging software it is involved.  www.cmiss.org
>
> If we can help further then let us know,

Sounds interesting. I suspect you haven't hit these problems because 
your plug-in is out-of-process. If that's not accurate, I'm truly 
intrigued. Presently I just don't see how GtkGLExt can possibly work 
with an in-process plug-in.

Braden