Hi Fabian,
Fabian Jakobs wrote:
> I'll give you a small example. Take the "backgroundColor" property. You
> can define a symbolic color in a theme - lets call it "focus". If you
> set the background color using:
>
> this.setBackgroundColor("focus");
>
> Three things happen:
>
> 1. check whether the passed value is defined in the current color theme
> 2. inform the theme manager that this widget is using the themed color
> by registering a callback function, which is called on theme changes
> 3. Let the theme manager transform the symbolic color name into a CSS color
> 4. apply the transformed color
>
> We could drop step three, which would reduce the memory usage but then
> switching themes would really become expensive. We had to scan all
> defined objects, find all properties, which accept themed colors, and
> update the computed color value. Right now I am a bit skeptical about
> this approach.
It would be less expensive than the initial rendering of the ui,
wouldn't it? What about only a single callback "colors have changed" or
even "themes have changed" that widgets react on by applying steps 1, 3,
and 4 if needed? I guess it's not that easy, I'm just trying. ;-)
Best regards, Ralf
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
