GTK+ 3.x wiki page

[Kristian Rietveld-3]

Hi all,

As promised in my previous e-mail I would create a wiki page over at
live.gnome.org to track the tasks and progress to get to GTK+ 3.0.  This
page can now be found here:

  http://live.gnome.org/GTK+/3.0/Tasks


regards,

-kris.
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@...
http://mail.gnome.org/mailman/listinfo/gtk-devel-list

hi,

Kristian Rietveld schrieb:
> Hi all,
>
> As promised in my previous e-mail I would create a wiki page over at
> live.gnome.org to track the tasks and progress to get to GTK+ 3.0.  This
> page can now be found here:
>
>   http://live.gnome.org/GTK+/3.0/Tasks
GSEAL also removed the ability to do e.g. statusbar->label to access the label
child of a statusbar (just an example - I know that its not public). Quite often
that the only way to achieve a certain effect. Besides now discussing where its
exposed I have a proposal for convenient access to those fields (related to task
#P4).

http://webcvs.freedesktop.org/gstreamer/gstreamer/gst/gstchildproxy.c?view=markup
http://webcvs.freedesktop.org/gstreamer/gstreamer/gst/gstchildproxy.h?view=markup

Would it be interesting mechanism for gtk+ too? Then maybe we should discuss
cleaning it up and adding it to gobject.

Stefan
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@...
http://mail.gnome.org/mailman/listinfo/gtk-devel-list

[Christian Dywan-2]

Am Fri, 11 Jul 2008 10:23:51 +0300
schrieb Stefan Kost <ensonic@...>:

> hi,
>
> Kristian Rietveld schrieb:
> > Hi all,
> >
> > As promised in my previous e-mail I would create a wiki page over at
> > live.gnome.org to track the tasks and progress to get to GTK+ 3.0.
> > This page can now be found here:
> >
> >   http://live.gnome.org/GTK+/3.0/Tasks
> GSEAL also removed the ability to do e.g. statusbar->label to access
> the label child of a statusbar (just an example - I know that its not
> public). Quite often that the only way to achieve a certain effect.
> Besides now discussing where its exposed I have a proposal for
> convenient access to those fields (related to task #P4).

The GSEAL work exposed and still exposes lots of places in Gtk+ where
the API is simply insufficient for certain tasks. Now people suddenly
need to request proper accessors and documentation, when before they
tried to get away with hacks or using private API. If you need
something that is not there or private, just file a bug with a use
case. And if new API is added, it's actually discoverable in the
reference.

ciao,
    Christian
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@...
http://mail.gnome.org/mailman/listinfo/gtk-devel-list