In 0.7 you need to define it completely. The most users think this is
more convenient because they have the full styling of a widget in one place.
However with the current trunk and finally 0.7.1 you will have the
possibility to add a base:true to include the super class definiton with
lower priority.
"include" works only for entries in the same class. Your example would
mean a recursion of spinner inside the same theme.
In 0.7.1 this would look like:
"spinner" :
{
base : true,
style : function(states)
{
return {
height:20
};
}
},
Hope this improves the usability for such situations.
Sebastian
dperez schrieb:
> I have already changed the height in the spinner to 20, but I lose the top
> and bottom borders.
> I'm investigating why. Very strange.
>
> When extend the Ext appearance, and I want to redefining the 'spinner'
> entry.
> Should the full entry be redefined or I just can the new height value?
> This fails:
>
> "spinner" :
> {
> include:"spinner",
> style : function(states)
> {
> return {
> height:20
> };
> }
> },
>
>
>
> Sebastian Werner wrote:
>> No, I think not. Height is quite a functional property. That the widget
>> comes with a default height is a good choice in this case. If the user
>> or the appearance theme changes the font one must also correct the
>> height there. Theme and user values have higher priority than init
>> values so that is possible without any problems.
>>
>
-------------------------------------------------------------------------
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
