It pretty much has to be seperate. A lot of people have to do this merely for search engine reasons (that is, dynamic content using # isnt well handeled by crawlers - assuming they handel javascript at all, which most dont).
The typical way is to make a basic PHP based site which GWT provides a shiny alternative view too. While I dont know precisely what you need, you could (for example) have the PHP take data from MySQL and echo it out formated beween <NOSCRIPT> tags, but also have the data avaliable for the javascript by echoing it to javacript var. Either way, its a pain. On Sep 6, 3:43 pm, raks <[email protected]> wrote: > Hi, > > I am very taken with GWT and I believe will make maintaining my company's > site easier. > > However, they say they need to maintain a non JavaScript version of the > site. > > Any ideas how we can do this? Would it have to be a seperate site? Can the > app be partitioned in some way? > > Thanks > > Raks -- 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.
