On 16 January 2012 22:21, John Ralls wrote:
>
>
> There's one thing that could make it better: Put it on GnomeLive! so that
> it's easy to find, even for people who don't read this list.
>
Done: [1]
Feel free to improve the markup.
Regards
[1] https://live.gnome.org/GTK%2B/GTKCSSStyling
--
On 01/16/2012 11:21 PM, John Ralls wrote:
> On Jan 16, 2012, at 1:04 PM, Benjamin Otte wrote:
>
>> CSS goes in, styled windows come out. You can't explain that.
>>
>> And quite frankly, that sucks. So here's a high-level overview of how
>> the GTK CSS machinery works in master.
> [SNIP]
>
> Benjam
> 7) Ditch theme engines
I like it! No more insanely weird bugs that eventually get
tracked down to a theme engine doing things wrong.
(Weird as in: the last thing people think of when, say,
floating-point numbers get truncated, is that the theme
has changed part of the locale.)
I hope you reali
On Jan 16, 2012, at 1:04 PM, Benjamin Otte wrote:
> CSS goes in, styled windows come out. You can't explain that.
>
> And quite frankly, that sucks. So here's a high-level overview of how
> the GTK CSS machinery works in master.
[SNIP]
Benjamin,
That's a great write-up. Thanks for the great
CSS goes in, styled windows come out. You can't explain that.
And quite frankly, that sucks. So here's a high-level overview of how
the GTK CSS machinery works in master. I'll also include some mentions
of changes I expect to make in the future to improve per- and
conformance, but I'll be sure to
