Thanks for the feedback. > The main problem will be Search Engine. You will have to rely on htmlunit to > fix it (generates static version of webpages).
The search engine result isn't important. What do you main by "htmlUnit to fix it"? > you can still optimize it by including the javascript content inside your > html/jsp/php page. You can use code splitting to improve it too. What do you mean by "putting javascript in the html page directly"? Isn't gwt bootstrapping already directly contained in html and in control of loading all the resources as such that you have to wait till gwt performed all the bootstrapping through his own js files... > But it can be a lost of time if all these points are not thought before > starting. In my case it concerns 3 existing gwt app's that contains code splitting and MVPC. I am setting up new html pages to change the look and feel. These app's should be one but the code splitting isn't optimal yet such that the left over becomes too big. See issue 6612 about this: (http://code.google.com/p/google-web- toolkit/issues/detail?id=6612) The advantage of having a full page gwt is also that these applications can more easily integrated later on. > We released our website in full gwt (http://www.weecod.com), so it is Thanks for the link, it gives me a good example about a full page gwt app. I think I go for the full page gwt app. If it get's too slow, it's easy to change it. - Ed -- 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.
