dperez schrieb:
> I have tried to comment the extend key, and seen no effect:
>
> qx.Theme.define("qx.theme.ext.Appearance",
> {
> // extend : qx.theme.classic.Appearance,
>
> title : "Ext",
>
> appearances : ......
>
> }
>
> So, the extend clause adds an unneeded dependency.
> Am I right?
>
>
> dperez wrote:
>
>> Hi,
>>
>> Is it intended to derive the ext.Appearance class from classic.Appearance?
>> It seems that the ext class redefines all the appearance entries, so there
>> is no need to inherit.
>> In this way, if I like more the ext appearance as a starting point, I
>> could remove from my build the classic one, which takes about 40kb
>>
>> Regards,
>> David
>>
>>
>
>
Hi David,
the inheritance was mainly used for convenience because we could start
with only a small subset and build the whole theme from there. At the
point we are now, I think we can remove the dependency and keep both
appearances manually in sync. I have done this change in svn now.
Best Fabian
-------------------------------------------------------------------------
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
