Re: Gtk3 and theming - a proposal (with code)
- From: "Robert Staudinger" <robert staudinger gmail com>
- To: "Alberto Ruiz" <aruiz gnome org>
- Cc: gtk-devel-list gnome org
- Subject: Re: Gtk3 and theming - a proposal (with code)
- Date: Mon, 13 Oct 2008 16:24:44 +0200
On Mon, Oct 13, 2008 at 3:06 PM, Alberto Ruiz <aruiz gnome org> wrote:
> And if you allow engines to access widgets, widgets can only do things
> that have been thought of /before/, which is a problem with worst
> consequences. Plus, you can easily add that information on the widget
> renderer function with a GtkStyle replacement.
> The CSS engine would not have been possible like that, because the
> theming api doesn't provide any other alternative. That's exactly why
> it should be fixed.
>> If the nesting of a composite widget is part of the stable gtk API,
> Is it? A widget implementation is not part of the stable gtk api at
> all, that's one of the reasons sealing is so important, letting people
> access to the private members is been preventing Gtk+ from substantial
> changes and improvements.
This is not the point. Engines are accessing the widgets by their
public and stable API.
It would also be possible to introduce aliases for the sake of
theming, e.g. "GtkTreeViewColumnHeader" for a GtkButton inside a
treeview. Maybe such an approach would be feasible to bridge the gaps
between the "widget access" and the "no widget access" camps?
] [Thread Prev