Re: Compatibility stuff

[Havoc Pennington <hp redhat com>]

Martin Baulig <martin home-of-linux org> writes: 
> * there's a hell lot of code out there which is using things like
>   object->klass, klass->type etc. which is now using GTK_OBJECT_GET_CLASS
>   and GTK_CLASS_TYPE.
> 
>   To ease migration to GTK+ 2.0, I'd like to suggest that we add these
>   macros to GTK+ 1.2.x. When we do this, people can start to port their
>   existing code to use these new macros when they feel like it without
>   breaking it on the GNOME 1.x platform.

We don't really want to create apps that depend on a specific .x from
1.2.x, normally interfaces are not added in the stable branch.  (We
added those theme-engine-only interfaces in 1.2.9, but those shouldn't
create apps that depend on 1.2.9, so it seemed relatively safe.)

Also, the flat-out port to 2.0 is really quite soon.

> * there's a lot of code using gtk_object_class_add_signals().
> 
>   Would it be possible to add this function to gtkcompat.h and let it
>   just print a warning that it's deprecated ?

Compile time warnings are preferred to runtime spew; it's easier to
clean up apps that way. The solution to using this function is to
simply remove it, it serves no purpose anymore. Changes-2.0.txt should
probably have better notes on this if it doesn't.

> * there's also a hell lot of code out there which is using the `finalize'
>   method of GtkObject.
> 
>   This may sound a bit hackish,

Yes... ;-)

>  but what do you think about adding
>   something like the following to GTK+ 1.2.x ?

Again, apps that depend on a specific 1.2.x are not good.

Havoc