Re: About GTK+ 3.0 and deprecated things

["Guillaume Cottenceau" <gcottenc gmail com>]

>> The 1.x -> 2.0 change was painful for everyone who had an app that
>> needed porting, however I find it pretty irrelevant in comparison to
>> 2.x -> 3.0.
>
> Well, if no libgtk-compat is planned, it will be about as painful
> for users of the deprecated and removed widgets/functions.

Isn't it a little bit exaggerated?

The GTK+ team wants to remove official support for deprecated things;
the larger part of it (from probably a lot of application porting
perspectives, and apparently yours) is probably GtkCList and GtkCTree:
they were marked deprecated more than 6 years, when GTK+ 2.0 was
released (and GtkItemFactory is deprecated in GTK+ 2.4, released more
than 4 years ago). If I use wikipedia to get a definition for
deprecation, I can read:

the term deprecation is applied to software features that are
superseded and should be avoided. Although deprecated features remain
in the current version, their use may raise warning messages
recommending alternate practices, and deprecation may indicate that
the feature will be removed in the future.

I sympathize with the actual problems you're having with your
application still using GtkCTree etc all over the place, and I do
understand that it's pretty frustrating to have to do "useless" work
of porting (though, GtkTreeView is much more powerful and has a better
and more robust look so your app will look better and work on it in
the future will then be easier). But really, I think that the GTK+
team, who writes a great library for us application developers, should
be able to move forward; and moving forward also means that after a
reasonable amount of time, deprecated stuff is removed - and, really,
do you really think that more than 6 years cannot be considered a
reasonable amount of time?

-- 
Guillaume Cottenceau - http://zarb.org/~gc/