Re: GMenuModel has landed

[Simon McVittie <simon mcvittie collabora co uk>]

On Tue, 13 Dec 2011 at 14:21:37 +0900, Tristan Van Berkom wrote:
> I would have to disagree about treemodel, data models, yes, would
> be nice to push down the stack from way on top in GTK+, but why
> not glib ? Of course I think the treemodel interface would have to
> be re-engineered to reach our expectations of excellence before
> being pushed all the way down to glib, but I think that would be
> more appropriate than "dumping it into libgio just because".

GLib is lower down the stack than GObject, so nothing in GLib can use the
GObject dynamic type system. So, anything sufficiently object-oriented that
it benefits from being a GObject has to go in either GObject or GIO.

At the moment, libgobject is literally just the abstract GObject type system
(including GValue, GType, signals, etc.), and doesn't have any "real-world"
functionality: all the actual uses of GObject are in GIO (or in separate
projects, of course). I think that's a reasonable definition of the layering.

In most distributions, GLib, GObject and GIO are all the same binary package
anyway (e.g. libglib2.0-0 in Debian and derivatives), so you either have
all or none.

    S