That's indeed what I ended up doing.

Nevertheless, I think there's a lot of power in the GObject system
concerning runtime type information that is currently lost when using the
mm bindings.
Most importantly, there seem to be no wrappers for GParamSpec at all. Also,
Glib::Interface is not as flexible as GTypeInterface, in that it does not
allow casting any Glib::Object to an interface instance. Gst::Interface in
combination with Gst::ElementInterfaced seems like something that worked,
but they are no longer available with the removal of
gst_implements_interface.

In its simplest form, wrapping GParamSpec would probably look something
like Glib::Value, though I guess there would be a lot of overlap with
Glib::Property, which is part of the reason I am not too keen on attempting
this.
Would there be a need for something like Glib::ObjectInterfaced<T,T,..,T>?
I for one would certrainly like an alternative to
Gst::Interface/Gst::ElementInterfaced.

If there is, I might give it a try sometime...

Cheers,
-Dirk








On 29 October 2013 18:14, Murray Cumming <[email protected]> wrote:

> You may at least use glibmm's .defs-generating code for this as
> inspiration:
>
> https://git.gnome.org/browse/glibmm/tree/tools/extra_defs_gen/generate_extra_defs.cc
>
> --
> Murray Cumming
> [email protected]
> www.murrayc.com
> www.openismus.com
>
>
_______________________________________________
gtkmm-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gtkmm-list

Reply via email to