Sign up

Split out GStreamer adapter as obvious separate thing

I think it would be good to separate out GStreamerD as a totally separate package to GtkD. My reasoning is that GStreamer is usable with many different UIs, in particular it can be used with Qt. Tying GStreamerD to GtkD is perhaps presenting the wrong impression, i.e. that GStreamerD is only usable with GtkD.

Re: Split out GStreamer adapter as obvious separate thing

On 06/06/2016 11:55 AM, Russel Winder wrote:

I think it would be good to separate out GStreamerD as a totally separate package to GtkD. My reasoning is that GStreamer is usable with many different UIs, in particular it can be used with Qt. Tying GStreamerD to GtkD is perhaps presenting the wrong impression, i.e. that GStreamerD is only usable with GtkD.

I would probably go further en split up the large GtkD library into:
glib, gtk and maybe cairo an pango.

Probably also necessary since GStreamer does depend on glib/gobject.

Re: Split out GStreamer adapter as obvious separate thing

The Go binding I use separates out:

cairo
gdk
glib
gtk
pango

and uses the build framework to ensure compiling things in the correct order. Yes GStreamer requires all the GObject stuff.

If it were then possible to get qtd in a working and compatible with glib and gstreamer state, lige would be good!