Hi,
if the first part of an application (not the boot part) is big and
complex, there are only a few things that come into my mind (because we
had the same challenge):
1. Set up a very very simple start screen, that can be loaded quickly
to give the user an option, with wich part / screen / page / view /
whatever of the application he wants so start. So the user is busy and
will not complain about load times.
2. Differ between load time of resources (js, png, jpg, html, css,
...), the time that will be taken for js code exection and the number of
XHRs. You can optimize load times by using the full capacity of the
browser cache (have a look at HTTP-Header) and minimize the number of
XHRs ! That will be good for your application anyway.
3. Show something like a splash screen an wait animation, the users
will like it even though the load times are the same :)
We decided to ignore IE7 becuase the JS Engine is crap. :-)
HTH,
Rob.
Mit freundlichen Grüßen / Best regards
Dipl.-Inf. (FH) Robert Nimax
Geschäftsbereich Materialwirtschaft
INFORM GmbH, Pascalstraße 23, 52076 Aachen, Germany
Telefon: (+49) 2408 9456-1700, Fax: (+49) 2408 9456-1750
E-Mail: [email protected], Web:
http://www.inform-software.com
INFORM Institut für Operations Research und Management GmbH
Registered AmtsG Aachen HRB1144 Gfhr. Adrian Weiler
>>> hgc2002 <[email protected]> 7/27/2011 10:04 >>>
I've been working with versions 1.4, 1.4.2 and now 1.5 and the loading
time
of the framework is still a problem.
I'm not talking about my application. I'm talking about the pure Qx
framework. Even using Parts, I don't see how to split the framework
itself
in loadable chunks. Who could be able to do that?!
I'm using IE7 and IE8. In Chrome (version 10 to 12), the loading time
is
normaly half of the time in any IE version. Surprinsingly, the rest of
interactions of the loaded aplication with the server is very much
quicker
in IE than Chrome. Very strange, but at least one nice surprise.
I've seen than roadmap for version 1.6 (december 2011) includes
"Introduce a
self-contained low-level library". Is this the first try to make a
short
basic part of the framework to load in first place (much quicker than
current), then the rest?
Have somebody worked in making the load time of the framework itself
less
notable in IE?
Thanks,
Herman Gomez
Spain.
-----
la vida es una incesante cadena de oportunidades para aprender y
triunfar.
life is an endless chain of opportunities to learn and succeed.
lo más importante: ser selectivo, responsable y perseverante.
the most importantly: to be selective, responsible and persevering.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/framework-loading-too-slow-in-internet-explorer-IE-tp6627504p6627504.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
