Re: Docs for the gtk-style-context branch changes

[Benjamin Otte <otte gnome org>]

Carlos Garnacho <carlosg <at> gnome.org> writes:

> 1) Keep GtkStyle in 3.0, encourage people verbally to use
> GtkStyleContext instead.
> 
> 2) Keep GtkStyle, but not include in gtk.h, force people to take a
> decision between being lazy and using the brand new stuff.
> 
> 3) Remove GtkStyle, port all GTK+ widgets, force people to move forward.
> 
For 1) or 2) what people will do is:
  nothing
People will certainly not fix working code (it works after all) and they will 
continue to use gtk_paint_foo() functions, because they know how to. Unless 
your code provides very obvious advantages that people actually do want to 
use, they will continue using what works.

For 3) what will happen is:
  moaning
Then people will realize porting is easy and do the boring work. As I'm 
assuming porting isn't hard and  is basically search/replace, that should be 
easy.
Note that you might be expected to fix (some of) the GNOME apps that use 
these APIs.

Also, all gtk_paint_foo() functions change their prototype from GTK2 to GTK3, 
so everyone will have to touch that function while porting. So it seems like 
a good time to make people do the switch.

So I'm strongly leaning towards 3), even though that'd mean you get to do 
more work, probably a lot more work.

Benjamin