Hi,
it might be that you are missing the qooxdoo setting for qx.theme. Are
you including the application.json in your config? And are you building
on its jobs? If so, your jobs would inherit the "settings" key. Try
copying over the common/settings key from base.json and see what it
does. Alex was struggling with the same issue and solved it, but he is
on vacation currently.
Thomas
Gaetan de Menten wrote:
> I'm using an "extended" modern theme for my application, that is I'm
> inheriting from the theme and adding some states ("invalid", ...) to
> some widgets. It works fine in source form, but I systematically get
> the following exception as the first message in my console:
>
> The theme to use is not available: pinte.theme.Common Meta.js (line 108)
>
> While my theme seem to work flawlessly (except from this error
> message) in source form, the error seem fatal in "build" form. Any
> idea what might be causing this?
>
> My config.json does contain those lines:
> ...
> "QXTHEME" : "pinte.theme.Common",
> ...
>
> "include" :
> [
> "${APPLICATION}.Application",
> "${QXTHEME}"
> ],
>
> and pinte/theme/Common.js looks like this:
>
> qx.Theme.define("pinte.theme.Common", {
> title: "Common theme",
>
> meta: {
> appearance : pinte.theme.Appearance,
> color: pinte.theme.Color,
> decoration: pinte.theme.Decoration,
> font : qx.theme.modern.Font,
> icon : qx.theme.icon.Tango
> }
> });
>
> Thanks for any pointer...
>
-------------------------------------------------------------------------
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
