I think GWT is best utilized in a full page scenario because of "code sharing" of re-usable components. If you go the other route and "just" embed GWT code in different host pages (i.e. application with multiple entry points) you lose the benefits of javascript code re-use of reusable components because every entrypoint will have its own module.nocache.js file which has to be transferred to the client. If you create a re-usable component (let's say a CellTable component) which is used in different places (in both entry points) the same code will be part of the module.nocache.js file and thus downloaded two times. It probably doesn't make a big difference for small web-sites where some parts are done with GWT but for complex apps where you might re-use a lot of components it might be an issue. However in case you go with the one host page (one entry point) solution you will probably not use any of the your backend's flow controls (MVC) but it will solely act as a data-backend.
-- 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/-/cuYO25r6uJ8J. 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.
