>> 6) [ only if we really wanted hosts to have a "real" handle on the >> plugin GUI window ] the library would need to contain a way to >> pass in an X "Window", and wrap it up as a native drawing area >> for each toolkit. i would prefer not to do this for now, if ever. > >What about reparenting the window like the window manager does? > I must confess: I don't know anything about programming this >but have "heard" about the concept. AFAIK, any window can be >absorbed by a container -- but I don't know what this really and >programmatically means. So it's just an idea ...
the problem is getting the GUI toolkit to use an externally created window to parent one of its own. i wouldn't want to rely on XEMBED for this, and there is probably no need to. i know that GDK has gdk_window_new_foreign(), which does 50% of the work. don't know about Qt, but i will check. --p