On Wed, 23 Feb 2011 10:57:25 +0100, torbenh wrote:
oh come on. do you mean Dave's library will have a so called
specialized "gtk shell" for each toolkit out there? wrapping everything
under gtk is not what i would call a "pretty good solution" at least the
one we've agreed about earlier.
Fons is right suggesting a common-denominator term: the lv2_ui
descriptor should have carried a system window-id instead, in
alternative to, a plain toolkit-dependent widget pointer that
lv2_gtk_ui's been doing all this time as LV2UI_Widget*. on X11 based
systems it would cast to a Window type; on windows it would be a HWND;
i'm sure there's something native and equivalent on macosx/carbon/cocoa
w/e... depending on the system the plugins are built/targeted then the
host will/must "know" what to do with that window-id--embed, show, hide,
realize, destroy, trap and send events, etc... look, it is this
window-id in fact the corner stone for the gtk-socket to xembed a
qt-widget on the clam example.
imnsho, a GtkWidget* is not, cannot and never will be the way to
"toolkit agnosticism" :) why is that not obvious to you?
rncbc aka Rui Nuno Capela
Linux-audio-dev mailing list