Windows runtime and package Dev-Cpp for GTK+ 2.10.8

2007-06-22 Thread Benoit Carpentier
Dear all, I released a Windows runtime and a package for Dev-Cpp based on GTK+ 2.10.8. You can find this on : gtk.alkia.org Regards, BenoƮt Carpentier, "GTKool" - Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail

Re: Blacklisting themes?

2007-06-22 Thread Federico Mena Quintero
On Fri, 2007-06-22 at 09:20 -0400, Jody Goldberg wrote: > I don't think Morten's intent was to handle the blacklist at the > application level. A more practical approach would be a bugbuddy > extension that would compare the current theme engine and version > against a central collection of known

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Tim Janik
On Fri, 22 Jun 2007, Tommi Komulainen wrote: > On 6/22/07, Tim Janik <[EMAIL PROTECTED]> wrote: >> c) note that the actual compilation changes could easily be ironed out >> by Gtk+ by doing s/_tips_data_list/tips_data_list/ but was introduced >> deliberately, to catch remaining tips_data_l

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Sven Neumann
Hi, On Fri, 2007-06-22 at 10:27 +0200, Tim Janik wrote: > so far, my take on the issue is that PyGtk should adapt to that > change by not using tooltips->tips_data_list I have attached a patch to http://bugzilla.gnome.org/show_bug.cgi?id=449318 that removes access to private GtkTooltips struct m

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Matthias Clasen
On 6/22/07, Sven Neumann <[EMAIL PROTECTED]> wrote: > Hi, > > On Fri, 2007-06-22 at 10:27 +0200, Tim Janik wrote: > > > so far, my take on the issue is that PyGtk should adapt to that > > change by not using tooltips->tips_data_list > > I have attached a patch to > http://bugzilla.gnome.org/show_bu

Re: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Owen Taylor
On Fri, 2007-06-22 at 15:36 +0200, Murray Cumming wrote: > On Fri, 2007-06-22 at 13:58 +0100, Gustavo J. A. M. Carneiro wrote: > > On Qui, 2007-06-21 at 23:39 -0300, Johan Dahlin wrote: > > > Joseph Sacco wrote: > > > > The currently available version of pygtk is the stable branch. I would > > > >

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Tommi Komulainen
On 6/22/07, Tim Janik <[EMAIL PROTECTED]> wrote: > c) note that the actual compilation changes could easily be ironed out > by Gtk+ by doing s/_tips_data_list/tips_data_list/ but was introduced > deliberately, to catch remaining tips_data_list uses in third-party > code which should be

Re: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Murray Cumming
On Fri, 2007-06-22 at 13:58 +0100, Gustavo J. A. M. Carneiro wrote: > On Qui, 2007-06-21 at 23:39 -0300, Johan Dahlin wrote: > > Joseph Sacco wrote: > > > The currently available version of pygtk is the stable branch. I would > > > expect the development branchof pygtk to adapt. > > > > > I'm r

Re: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Ghee Teo
Gustavo J. A. M. Carneiro wrote: > On Qui, 2007-06-21 at 23:39 -0300, Johan Dahlin wrote: > >> Joseph Sacco wrote: >> >>> The currently available version of pygtk is the stable branch. I would >>> expect the development branchof pygtk to adapt. >>> >>> >> I'm ready to adapt but o

Re: Blacklisting themes?

2007-06-22 Thread Jody Goldberg
On Fri, Jun 22, 2007 at 02:04:17PM +0200, Benjamin Berg wrote: > On Thu, 2007-21-06 at 20:25 -0500, Federico Mena Quintero wrote: > > On Tue, 2007-06-19 at 15:08 -0400, Morten Welinder wrote: > > > > > The application programmer has no choice in the matter and cannot > > > really test with > > > a

Re: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Gustavo J. A. M. Carneiro
On Qui, 2007-06-21 at 23:39 -0300, Johan Dahlin wrote: > Joseph Sacco wrote: > > The currently available version of pygtk is the stable branch. I would > > expect the development branchof pygtk to adapt. > > > I'm ready to adapt but only if the general consent is that API changes > are okay. >

Re: Blacklisting themes?

2007-06-22 Thread Benjamin Berg
On Thu, 2007-21-06 at 20:25 -0500, Federico Mena Quintero wrote: > On Tue, 2007-06-19 at 15:08 -0400, Morten Welinder wrote: > > > The application programmer has no choice in the matter and cannot > > really test with > > all kinds of themes and all kinds of versions of them. But the > > resultin

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Murray Cumming
On Fri, 2007-06-22 at 11:20 +0200, Tim Janik wrote: > On Fri, 22 Jun 2007, Murray Cumming wrote: > > > On Fri, 2007-06-22 at 11:03 +0200, Tim Janik wrote: > >> On Fri, 22 Jun 2007, Murray Cumming wrote: > >> > >>> On Fri, 2007-06-22 at 10:46 +0200, Tim Janik wrote: > On Fri, 22 Jun 2007, Murr

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Tim Janik
On Fri, 22 Jun 2007, Murray Cumming wrote: > On Fri, 2007-06-22 at 11:03 +0200, Tim Janik wrote: >> On Fri, 22 Jun 2007, Murray Cumming wrote: >> >>> On Fri, 2007-06-22 at 10:46 +0200, Tim Janik wrote: On Fri, 22 Jun 2007, Murray Cumming wrote: > On Fri, 2007-06-22 at 10:27 +0200, Ti

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Murray Cumming
On Fri, 2007-06-22 at 11:03 +0200, Tim Janik wrote: > On Fri, 22 Jun 2007, Murray Cumming wrote: > > > On Fri, 2007-06-22 at 10:46 +0200, Tim Janik wrote: > >> On Fri, 22 Jun 2007, Murray Cumming wrote: > >> > >>> On Fri, 2007-06-22 at 10:27 +0200, Tim Janik wrote: > >> > b) GtkTooltips is go

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Tim Janik
On Fri, 22 Jun 2007, Murray Cumming wrote: > On Fri, 2007-06-22 at 10:46 +0200, Tim Janik wrote: >> On Fri, 22 Jun 2007, Murray Cumming wrote: >> >>> On Fri, 2007-06-22 at 10:27 +0200, Tim Janik wrote: >> b) GtkTooltips is going to be deprecated in 2.12 anyways, so there is little us

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Murray Cumming
On Fri, 2007-06-22 at 10:46 +0200, Tim Janik wrote: > On Fri, 22 Jun 2007, Murray Cumming wrote: > > > On Fri, 2007-06-22 at 10:27 +0200, Tim Janik wrote: > > >> b) GtkTooltips is going to be deprecated in 2.12 anyways, so there > >> is little use in continuing to use it anyway. > >> c) note

Re: GType typedef API/ABI break.

2007-06-22 Thread Murray Cumming
On Fri, 2007-06-22 at 10:40 +0200, Tim Janik wrote: > > > What does %zu do? What bug does this solve? > > printf-ing a GType. so far, the "correct" way to print it would > have been to use %lu if GLIB_SIZEOF_LONG == GLIB_SIZEOF_SIZE_T, > and %zu (prints size_t) otherwise, allthough sizeof (GType)

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Tim Janik
On Fri, 22 Jun 2007, Murray Cumming wrote: > On Fri, 2007-06-22 at 10:27 +0200, Tim Janik wrote: >> b) GtkTooltips is going to be deprecated in 2.12 anyways, so there >> is little use in continuing to use it anyway. >> c) note that the actual compilation changes could easily be ironed out >>

Re: GType typedef API/ABI break.

2007-06-22 Thread Tim Janik
On Fri, 22 Jun 2007, Murray Cumming wrote: > On Fri, 2007-06-22 at 10:05 +0200, Tim Janik wrote: >> On Fri, 22 Jun 2007, Murray Cumming wrote: >>> For instance, glibmm's library contains a >>> void get_defs(unsigned long) >>> But now, when building gtkmm, the linker is looking for >>> void get_

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Murray Cumming
On Fri, 2007-06-22 at 10:27 +0200, Tim Janik wrote: > > As noted in bug http://bugzilla.gnome.org/show_bug.cgi?id=449318, > > there was a recent gtk+ API change. jdahlin just barely told me that > > the changed API has existed since 1998, long before gtk+-2.11.x (and > > pointed me to http://bugzi

Re: Automake requirements for gtk+, glib

2007-06-22 Thread Tim Janik
On Thu, 21 Jun 2007, Daniel Macks wrote: > On 6/16/07, Matthias Clasen <[EMAIL PROTECTED]> wrote: >> >> No. automake versions are not compatible. >> Simply changing the requirements is not an option. > > Following up to http://bugzilla.gnome.org/show_bug.cgi?id=448828 > on-list because it's a deve

Re: GType typedef API/ABI break.

2007-06-22 Thread Murray Cumming
On Fri, 2007-06-22 at 10:05 +0200, Tim Janik wrote: > On Fri, 22 Jun 2007, Murray Cumming wrote: > > > I sent this to gtk-list by mistake. Re-sending it to gtk-devel-list: > > > > I think the recent change to the GType definition is causing linker > > errors by changing the GType definition from g

Re: Fwd: gtk+ API change; who should fix it? (A.k.a. Why isn't GNOME 2.19.4 released yet?)

2007-06-22 Thread Tim Janik
On Thu, 21 Jun 2007, Elijah Newren wrote: > Just realized that pygtk and gtk-devel-list subscribers may not be on > d-d-l. So I'm forwarding this. See > http://mail.gnome.org/archives/desktop-devel-list/2007-June/msg00109.html > for the thread and discussion. Please jump in. > > -- Forw

Re: GType typedef API/ABI break.

2007-06-22 Thread Tim Janik
On Fri, 22 Jun 2007, Murray Cumming wrote: > I sent this to gtk-list by mistake. Re-sending it to gtk-devel-list: > > I think the recent change to the GType definition is causing linker > errors by changing the GType definition from gulong to gsize. We are > left with the #else definition that was