Re: Justifying the GTK+ 3.0 ABI break

2008-07-28 Thread Murray Cumming
On Mon, 2008-07-14 at 17:30 +0200, Murray Cumming wrote: Every time that a parallel-installable GTK+ 3.0 has been proposed, and now that it has been decided, I have asked for a list of actual useful features that it will make possible. I've had no luck so far. We need to offer people a

Re: Justifying the GTK+ 3.0 ABI break

2008-07-16 Thread Sven Neumann
Hi, On Tue, 2008-07-15 at 20:22 -0400, Morten Welinder wrote: It really is the elaborate deprecation (as opposed to simply dropping in a comment and not maintaining the code any more) that is causing the burden. That's what the log say -- assuming gtkclist is representative -- which I would

Re: Justifying the GTK+ 3.0 ABI break

2008-07-15 Thread Morten Welinder
Or maintaining a bunch of deprecated API? I looked at the log for gtkclist.c and the majority of the changes over the past five years are a direct consequence of the api having been declared deprecated. Specifically there is a lot of defining and undefining of GDK_DISABLE_DEPRECATED going back

Re: Justifying the GTK+ 3.0 ABI break

2008-07-15 Thread Behdad Esfahbod
On Tue, 2008-07-15 at 20:01 -0400, Morten Welinder wrote: So the maintenance burden, to the extent there is one, is _caused_ by deprecation. This is ridiculous. It's perceived that way because all bugs against deprecated widgets is closed WONTFIX. It's not like if the widget was not

Re: Justifying the GTK+ 3.0 ABI break

2008-07-15 Thread Morten Welinder
So the maintenance burden, to the extent there is one, is _caused_ by deprecation. This is ridiculous Nobody is laughing and you are not reading what I wrote carefully enough. It really is the elaborate deprecation (as opposed to simply dropping in a comment and not maintaining the code any