Thanks, I read it carefully: - *<img> *tags do *not* block *page evaluation*. - The *body.onload()* event will only fire once *all external resources are fetched*, including images and frames. - The GWT selection script will be fetched and evaluated like a normal script tag, but the compiled script will be fetched *asynchronously*. - Once the GWT selection script has started, its *onModuleLoad()* *can*be called at *any point after the outer document has been parsed*. - *<img> tags are not guaranteed to be done loading when onModuleLoad()is called. *
It seems that it is not unexpected that image loading block gwt execution? It would be great if there is anyway to avoid it (execute gwt as soon as document has been parsed). Thanks, -ali On Wednesday, May 16, 2012 10:56:45 PM UTC+4:30, Joseph Lust wrote: > > The loading order and which elements are blocking to GWT's execution is > explained > well > here<https://developers.google.com/web-toolkit/doc/latest/DevGuideOrganizingProjects#DevGuideBootstrap>. > > By changing the order of said items you can speed up the apparent loading > of the page. > > You can also see other examples of how to make a splash screen with GWT > such as > this<http://turbomanage.wordpress.com/2009/10/13/how-to-create-a-splash-screen-while-gwt-loads/> > . > > > Sincerely, > Joseph > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/zfaUNhYdQdgJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
