GNOME Bugzilla – Bug 740969
wayland: Provide GIR introspection typelibs
Last modified: 2016-03-17 03:47:12 UTC
Currently it's not possible to work with GTK+ in backend specific ways from non-C code for Wayland. Please provide a GdkWayland-3.0.gir to be able to do so, alongside GdkX11-3.0.gir and GdkWin32-3.0.gir In particular, I can't use GStreamer with GTK+ on Wayland, because I can't set the native handle in python due to lack of gdk_wayland_window_get_wl_surface via python or anything else but C/C++ (ignoring potential further issues with subsurfaces and the like afterwards).
is it possible to use Wayland types through introspection?
Well, calling wl_registry_bind requires you to wrap structures, but the rest is all proxy objects, so yeah, if there are bindings around the C API. Bashing the wire protocol directly won't work for any number of reasons.
(In reply to comment #2) > Well, calling wl_registry_bind requires you to wrap structures, but the rest is > all proxy objects, so yeah, if there are bindings around the C API. in order to have bindings around the C API we'll need a "wayland-gobject" wrapper library, like we do for cairo. > Bashing the wire protocol directly won't work for any number of reasons. yeah, I don't expect that to happen.
for this to happen, somebody with first-hand experience with introspection will have to do the work.
As I said in comment #3, we're going to need a libwayland-gobject ancillay library to provide GType wrappers of Wayland types; GTK would then depend on that library, and then we'll be able to generate introspection data like we do for X11. Otherwise, language bindings won't be able to use the API.
I'm going to close this. If somebody is interested enough to work on this, they can open a new bug or reopen this one. I don't really know what wayland-specific calls you'd want to make, anyway - I haven't yet found a reason to use wayland-specific API in gtk itself.