Hi, I've got a legacy website that has quite a few different html pages, and we want to add GWT to them a little at a time. I tried just creating a new gwt module per page, to see how it would work. When switching between pages, we'll get a kind of annoying blank white screen before the javascript on the next page manipulates the DOM and renders itself.
I know GWT is meant to be a single page only, but is there any 'onDisplay()' phase that the javascript could override and be run in to generate the UI before it's shown to the user by the browser? I doubt there is otherwise the gwt team probably would have utilized it. The stages as I think they're happening for more detail: -User goes to my site, send back the gwt-compiled javascript file. -User sees blank white screen briefly. -Javascript generates UI, and now the browser renders it. -User clicks a link on my page to go to another page. -Browser gets new page, shows blank white screen again. -Javascript generates UI, and now the browser renders it. -Repeat. It's not the end of the world, just kind of annoying to see that blank white screen on every page hit. Is there anything we can do about it? Thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
