gmane.comp.lang.javascript.qooxdoo.devel

Custom 0.8 theme "not available"?

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,

(Continue reading)

headers

thron7 | 8 Oct 10:19

Re: Custom 0.8 theme "not available"?

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" :
>       [

(Continue reading)

headers

Gaetan de Menten | 9 Oct 12:07

Re: Custom 0.8 theme "not available"?

On Wed, Oct 8, 2008 at 10:19 AM, thron7 <thron7 <at> users.sourceforge.net> wrote:

> 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.

Ok, I dug deeper into the issue and found out what is happening. The
thing is that my custom theme classes are only loaded after the
theme.manager.Meta.initialize method is called. I've found a simple
workaround, which might be the correct fix: I simply modified my
config.json to read:

  "jobs" :
  {
    "common" :
    {
      "include" :
      [
        "${QXTHEME}",
        "${APPLICATION}.Application"
      ],

instead of the (generated stuff from migration script):

      "include" :
      [
        "${APPLICATION}.Application",

(Continue reading)

headers

Fabian Jakobs | 9 Oct 13:12

Re: Custom 0.8 theme "not available"?

Gaetan de Menten schrieb:
> On Wed, Oct 8, 2008 at 10:19 AM, thron7 <thron7 <at> users.sourceforge.net> wrote:
>
>   
>> 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.
>>     
>
> Ok, I dug deeper into the issue and found out what is happening. The
> thing is that my custom theme classes are only loaded after the
> theme.manager.Meta.initialize method is called. I've found a simple
> workaround, which might be the correct fix: I simply modified my
> config.json to read:
>
>   "jobs" :
>   {
>     "common" :
>     {
>       "include" :
>       [
>         "${QXTHEME}",
>         "${APPLICATION}.Application"
>       ],
>
> instead of the (generated stuff from migration script):
>

(Continue reading)

headers

Gaetan de Menten | 9 Oct 13:38

Re: Custom 0.8 theme "not available"?

On Thu, Oct 9, 2008 at 1:12 PM, Fabian Jakobs <fabian.jakobs <at> 1und1.de> wrote:
> Gaetan de Menten schrieb:
>>
>> Ok, I dug deeper into the issue and found out what is happening. The
>> thing is that my custom theme classes are only loaded after the
>> theme.manager.Meta.initialize method is called. I've found a simple
>> workaround, which might be the correct fix: I simply modified my
>> config.json to read:
>>
>>   "jobs" :
>>   {
>>     "common" :
>>     {
>>       "include" :
>>       [
>>         "${QXTHEME}",
>>         "${APPLICATION}.Application"
>>       ],
>>
>> instead of the (generated stuff from migration script):
>>
>>       "include" :
>>       [
>>         "${APPLICATION}.Application",
>>         "${QXTHEME}"
>>       ],
>>
>> *IF* this is the correct fix, it should be applied to at least
>> tool/data/config/base.json and
>> component/skeleton/migration/config.tmpl.json.

(Continue reading)