Hello, I think GWT is more suited for a "single" page application, where in the same "page" gets refreshed with different contents. For the dynamic pages u can use the #!request, #!price, etc.. in the URL to load different contents.
Leave the static pages as is, just link these 2(static and GWT app) using simple anchors. Though, i think this kind of hybrid approach is very difficult to maintain and change, for large apps or sites. "I don't want to create a separate GWT module for every url "- Yes, not a very scalable way to develop the app. U have one URL and use the #! approach to store the current history or "Place". Thanks, Subhro. On Thu, Dec 16, 2010 at 1:57 PM, Andrey <mino...@gmail.com> wrote: > Hello! > > Consider we have a web site with static pages like: > /index > /products > /contacts > ... > > And we want to add dynamic GWT pages like: > /request (a request form) > /register (register form) > /price (price calculator) > ... > > What is the best way to perform this? > > I don't want to create a separate GWT module for every url because it > takes too much time to compile them all. > > Thanks in advance! > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
