Re: [libcroco-list] Two patches..

[Dodji Seketeli <dodji seketeli org>]

Hi David,

Yes, you are right. System colors cannot be hardcoded directly in
libcroco and I like your idea.

We could define the prototype of a user supplied system color handler:

typedef void (CRSystemColorHandler* ) (CRRgb *an_rgb, 
                                       const gchar *a_system_color) ;

That handler could be set via 
cr_rgb_set_system_color_handler (CRRgb *a_this,
                                 CRSystemColorHandler *a_handler) ;

Then, we could modify the code of
cr_rgb_set_from_name() so that each time it detects that
a user wants to set a rgb from a predefined system color, it calls the
system color handler to do it.

Is that the kind of thing you were thinking about ?

Thank you for your time.

Dodji.


On Sun, 2004-03-07 at 15:33, David A Knight wrote:
> On Sun, 2004-03-07 at 02:32 +0100, Benjamin Dauvergne wrote:
> > These two little patches finish the support for the "color:" property in
> > libcroco and sewfox.
> 
> This brings up the issue of supporting the system colours as defined at
> http://www.w3.org/TR/REC-CSS2/ui.html#system-colors
> 
> As libcroco doesn't depend on gtk, or qt etc. they can't be added in
> directly.  Would adding something along the lines of
> cr_rgb_set_system_colors() be useful?  That way an app can set the
> values up to match the theme in use and libcroco doesn't need to be
> toolkit specific.
> 
> 
> David