Although this isn't implemented there is a way to accomplish it if you
really needed to.
Before your class do something like:
var my_input =
{
// style info here
};
then later:
"input" : input,
"input-focused" : qx.lang.Object.mergeWith(
{
// focused propertied here
}, my_input),
"input-disabled" : qx.lang.Object.mergeWith(
{
// disabled propertied here
}, my_input);
It's not a very neat way but it will work if wanted this in your own
themes.
Fabian Jakobs wrote:
> Gaetan de Menten schrieb:
>> Hi again,
>>
>> I see there is a lot of repetition in decorations. For example, the
>> "input-focused" and "input-disabled" decorations only differ from the
>> "input" decoration for a few keys each. It would certainly make
>> decorations declarations shorter to have some kind of inheritance
>> system in place.
>>
>> Does something like this already exist for decorations? If so, why
>> isn't it used? Is it a run-time lookup (which would slow things down
>> obviously but make the JS files shorter to download), or is it a
>> compile-time expansion? Is such a system planned?
>>
> There is no inheritance of individual decorations in a theme. We just
> did not see the need for it yet and it is not on our roadmap. Personally
> I am reluctant to add just another level of complexity to the theming
> system. I would rather live with some repetition in the decoration theme.
>
> Best Fabian
>
>
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
