One thing that is different with the real application opposed to the
playground, is that the real app starts off with index.html, which loads
'<myappname>.js' - generated code from qooxdoo - which in turn loads a bunch
of things including 'Application.js' which the actual code I'm trying to get
to work. I looked at <myappname>.js and don't understand it completely, but
it seems to have a bunch of timeouts for compatibility with different
browsers. I'm wondering if the timeout I'm getting (eventually) is coming
from one of these? Maybe one of the qooxdoo resources is failing to load,
leading to the hang behavior in IE6???
Anyway, it appears to require being built as an entire application for the
problem to surface, as I was able to run the code fine as a standalone in
the playground.
Ken
On Tue, Oct 6, 2009 at 9:44 AM, Ken MacDonald <[email protected]> wrote:
> Hmmm. The playground example works fine in my IE6, while the actual code
> still fails. I have repeatedly cleared cache, restarted server. This past
> time, I used generate.py to distclean/clean/source-all to see if that
> helped. My client/IE6 machine is XP/SP3, and my server is the same (actually
> running on a VMWare on the same system).
> Ken
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
