Hi thron, thank for responses.
I'm porting our code to new and I decided to make some things more
clear than in previous version and in future to share theme I made.
But I'm getting troubles to get my theme working.
I created single package for my theme named qxet (qooxdoo extended
themes) and here I have theme called light. Theme is designed to take
things from qooxdoo Classic theme and I'm using assets as in qooxdoo
Classic theme package:
from qxet.light.Decorator:
/*
#asset(qx/decoration/Classic/*)
#asset(qxet/decoration/Light/*)
*/
qx.Theme.define("qxet.light.Decoration",
{
aliases:
{
decoration: "qx/decoration/Classic",
qxetdecoration: "qxet/decoration/Light"
},
... etc...
Problem is that qxet path is not resolved. The question is ... why? I
compiled it using generate.py and in build version I have:
qx/resource/qx/...
qx/resource/qxet/...
so generator build directory structure right, but why qooxdoo tries
different paths for qxet and qx ?
I will probably share theme early and you can look at the sources, but
I think this will be generator issue.
Another thing is that why I need to manually exclude "qx.theme.moderm"
and "qx.theme.classic" if I'm not using them? I have this in
config.json:
"include" :
[
// Qooxdoo classes
"qx.application.*",
"qx.bom.*",
"qx.core.*",
"qx.data.*",
"qx.dom.*",
"qx.event.*",
"qx.html.*",
"qx.io.*",
"qx.io2.*",
"qx.lang.*",
"qx.locale.*",
"qx.log.*",
"qx.type.*",
"qx.ui.*",
"qx.util.*",
"qx.xml.*",
"qx.Bootstrap", "qx.Class", "qx.Interface", "qx.List",
"qx.Mixin", "qx.Theme"
// Theme
,"${QXTHEME}"
],
But qooxdoo includes also Modern and Classic theme that is not
demanded (QXTHEME equals to "qxet.Light").
Thanks for advance
- Petr
2009/9/17 thron7 <[email protected]>:
>
>
> Petr Kobalíc(ek wrote:
>> Hi,
>>
>> is there a preferred mechanism to make new themes ?
>
> Are you aware of this documentation:
> http://qooxdoo.org/documentation/0.8/ui_custom_themes ?
>
>> I made one theme
>> that is using Classic theme as a base, but I had problems with other
>> images I wanted to include (or override).
>
> You can easily shadow images (or resources in general) if you add a
> foreign name space to your app's resource folder, e.g. like
>
> .../source/resource/qx/static/blank.gif
>
> When creating your app, this image would take precendence over the
> resource with the same id (qx/static/blank.gif) in the qooxdoo SDK.
>
>> Also if I made theme from
>> scratch, are somewhere differences between qooxdoo versions (0.82 vs
>> .83, ...) ?
>>
>
> I'm not aware of any. - Have you checked the release notes?!
>
> T.
>
>>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
