I did something like this in qxbuild:
1. Replace qx.event.handler.Application.onScriptLoaded(); ----> ;
This step can be added as a job to generator. It's postprocessing of
output the generator created, not possible in source mode.
2. When you need to start-up, call qx.core.Init.ready();
It's a hack, but works for me. Some time ago I wanted custom initialization
functionality, but it's probably still not in qooxdoo.
For more details look at qxbuild's trunk, it's very dynamic:
http://code.google.com/p/qxbuild/
Best regards
Petr Kobalicek
On Mon, Aug 23, 2010 at 12:31 AM, Andrey Kovalev <[email protected]> wrote:
>
> Actually I still wanted to know if it's possible to create a code which I
> suggested below.
> But currently I found a solution. I use
> window.qxsettings = {}
> and qx.core.Setting.get("...") in my classes.
> --
> View this message in context:
> http://qooxdoo.678.n2.nabble.com/Is-it-possible-to-exclude-main-class-from-bootstrap-tp5450468p5450917.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
