On Thu, Oct 9, 2008 at 1:12 PM, Fabian Jakobs <[EMAIL PROTECTED]> 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.
>>
> Wow, this is a really ugly bug. We should modify the templates to fix
> it for the moment but usually the order of the includes should not
> matter. The dependency detection should be able to detect this
> dependency. Could you open a bug for this issue?
http://bugzilla.qooxdoo.org/show_bug.cgi?id=1463
--
Gaëtan de Menten
http://openhex.org
-------------------------------------------------------------------------
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
