Maybe because there is no translation anymore directly supported by
color properties. You can use qx.util.ColorUtil.rgbToRgbString(Array) to
translate a color array first. An array is not directly usable. The
theme system cache the result. So the performance disadvantage is not
that dramatic. But if you use this all over in your custom code it could
be. Be warned :)
Sebastian
dperez schrieb:
> Hi all,
>
> Why the entries of a Color theme have an array format:
>
> qx.Theme.define("TColor", {
> title: 'RDS estandar',
> colors: {
> 'omi': [ 0xFF, 0xB0, 0xA0 ]
> }
> }
>
> and on the other hand, colors in borders don't accept array syntax:
>
> qx.Theme.define('Borde', {
> title: 'RDS',
> extend: qx.theme.ext.Border,
> borders: {
> 'barra-botones': {
> styleBottom: 'dotted',
> widthBottom : 1,
> colorBottom: '#999' // [0x99, 0x99, 0x99] isn't
> valid!!!!!!!!!
> }
> }
> });
>
> Why do we have 2 incompatible syntaxes?
>
> Regards,
> David
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
