Qooxoo devs, i'm waiting if it's possible to add explicit initialization :-)
Derrell, just one note about your solution. Your solution to not use application main() method will not work. Because domloaded event is fired by IE too early, there is no such application class declared - qooxdoo only prints warning that class can't be instantiated. I really need explicit initialization possibility, don't know about different solution. Cheers - Petr 2009/3/9 Petr Kobalíček <[email protected]>: > Hi Derrell, > > I understand you. But my problem with this solution is that > application using qxbuild needs different code than application that > uses qooxdoo build system. And this all for IE :) > > For me this is no problem, I'm not using IE and I can tell customers > to not use IE in admin, but for other people using qxbuild this can be > problem. I think that it's needed only little work in framework to > make solution to this problem. > > For me best way is this: > - add qxsettings["qx.noinit"] = true possibility > - add static method init() to qx.core.Init to force initialization. > > I think that it's clear, but I don't know if this will be acceptable > for qooxdoo developers. > > Cheers > - Petr > > 2009/3/9 Derrell Lipman <[email protected]>: >> 2009/3/9 Petr Kobalíček <[email protected]> >>> >>> Hi Derrell, >>> >>> I tested it now and it's the same behavior. I think that only solution >>> is ability to tell qooxdoo to initialize manually. >>> >>> Main problem for me is that IE is not preserving the script order, so >>> I must append scripts one-by-one (I tested in head and body too). >>> >>> Personally, I think that manual initialization is good idea, currently >>> for example qxbuild is able to show simple progress bar to visualize >>> application loading, i think that it's nice :-) >> >> In qx.core.Init it adds a listener for the "ready" which calls >> application.main(). That's probably what you want to defer. As an interim >> (or maybe permanent) measure, you can do nothing in your application.main() >> (except maybe saving a reference to its superclass) and instead, put your >> start-up code in some other method. Then, after you've loaded all of your >> scripts, you you can call that other method which in turn calls the >> application.main superclass to initialize everything (in most cases, it >> initializes the theme manager and creaes the root widget; see >> qx.application.AbstractGui.main) and then creates all of your widgets. >> >> Hope that helps a bit for the time being. >> >> Derrell >> >> >> >> ------------------------------------------------------------------------------ >> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA >> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise >> -Strategies to boost innovation and cut costs with open source participation >> -Receive a $600 discount off the registration fee with the source code: SFAD >> http://p.sf.net/sfu/XcvMzF8H >> _______________________________________________ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> > ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
