Re: About GTK+ 3.0 and deprecated things

2008/7/16 Colin Leroy <colin colino net>:
> On Wed, 16 Jul 2008 09:51:03 +0100, Bastien Nocera wrote:
> Hi,
>> IMO, if you're still using GtkCTree and GtkCList, which were
>> deprecated when GTK+ 2.0 was released 6 years ago, you're asking for
>> trouble.
> Well, they do work for us. When GTK+ 2.0 was released six years ago, we
> were already too busy with the rest of the rewriting code-that-worked to
> do it. Two years and nine days, exactly, between the first commit to
> the GTK2 branch and the first GTK2 release after 497 commits. And we
> never came to replace the GtkCtrees because a) they work and b) we
> didn't have the time/motivation.

If using deprecated and unmaintained code is not a problem for you, I
suppose there's no real reason to be worried about GTK+ 3.x either..?

I wish people would stop fighting against the "code cleanup release",
unless they really want to switch to an alternative widget library.
GTK+ isn't seeing the love it needs, and the strict API/ABI policy of
GTK+ 2.x mixed with "leaky" public interfaces is seen (by the people
doing the work) as one of the biggest problems why that is.

If you prevent fixing that with all this stop-energy, it's not going
to take long for new applications start choosing something less dead
as their widget set of choice.

So please let the code be revived _now_ when there's a chance it's not
going to be just undead after the operation and direct the energy to
implementing the canvas, css theming and animations and whatever. The
good news is that you don't need to wait for 3.x, you can start the
work already! The new API and its policy is already known and in SVN
if I'm not mistaken, so go and hack away!

Kalle Vahlman, zuh iki fi
Powered by
Interesting stuff at

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]