Re: Glib 2.10 / Pango 1.? for GNOME 2.14?
- From: Kjartan Maraas <kmaraas broadpark no>
- To: Federico Mena Quintero <federico ximian com>
- Cc: "release-team gnome org" <release-team gnome org>, GTK+ development mailing list <gtk-devel-list gnome org>, GNOME Desktop <desktop-devel-list gnome org>
- Subject: Re: Glib 2.10 / Pango 1.? for GNOME 2.14?
- Date: Wed, 18 Jan 2006 20:56:25 +0100
ons, 18,.01.2006 kl. 10.21 -0600, skrev Federico Mena Quintero:
> Sorry that I dropped the ball on this, and haven't followed all the
> discussion.
>
> Other than Pango optimizations and and GSlice in Glib, is there a
> compelling reason to use the new Glib/Pango in GNOME 2.14?
>
I think the pango optimization work is what prompted the move to Glib
2.9.x. Not sure the other stuff is really compelling, but...
> - Was the ABI issue resolved with respect to GObject floating
> references? Changing the object hierarchy sounds like a definite break
> to me.
Leaving this for others to answer.
>
> - There is no way yet to disable GSlice, so we can't valgrind apps.
>
We can't? I've been valgrinding apps successfully with jhbuild + glib
HEAD for some time now, what's broken?
> - Are there any apps using the new Glib APIs now?
>
I know gnome-utils started using g_slice_* from this release on and I
saw Christian and Alex discussing the use of it in gnome-vfs before the
release too, not sure whether any of that actually happened. Other than
that I don't know if anyone started using any newly added api's from
Glib/Pango.
Cheers
Kjartan
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]