Hi Martin, I solved the thing, but I'm not happy about the qooxdoo way - I need to call qx.core.Init.ready().
The main problem is that qooxdoo not contains possibility for setting custom loaders. I don't want to pack my application with qooxdoo so I always need to call qx.core.Init.ready() after 1.0.1, maybe in next version it will be something else, I don't know. I think that I submitted bug report about this, but no change from that time. So is there any possibility to include custom loading possibility in qooxdoo, this can't be too hard, it's only about defining simple "entry-point" API that will be called when my loader finishes loading all necessary files. So what do you think, will it be possible? -- Best regards - Petr Kobalicek <http://kobalicek.com> On Thu, Apr 22, 2010 at 9:17 AM, MartinWittemann <[email protected]> wrote: > > Well, sounds like something has changed in qooxdoo if you can not upgrade > from 1.0.1 so you can expect as much help as everybode else here. ;) But as > long as I don't have more information than "it does not work" I can't do > much. I don't even know what you are doing different than we do in our > loader. > > As far as I know, we did not change anything in the initialization process > of an application on intense. So maybe its a bug ... or someone else knows > more. > Best, > Martin > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/Application-onScriptLoaded-tp4909328p4941311.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
