just add <script ... src="[modulename].nocache.js></script> to the html pages that you want to include your GWT module in
-jason On Feb 5, 2009, at 2:11 PM, RussAbbott wrote: > > Thanks. I had found this page (http://code.google.com/docreader/ > #p=google-web-toolkit-doc-1-5&s=google-web-toolkit- > doc-1-5&t=DevGuideWebMode) but it wasn't as clear as the page you > cited. > > Now I have another question. In this task, I'm attempting to use GWT > to enhance an existing web page. I've done the development by using a > mock-up of the page that the server actually generates. That is I took > a generated page from my browser, saved it as html, and did my > development in terms of that html. In reality I'll need to insert my > GWT code into generated html pages as they are generated. I'm sure > that the documentation tells me how to do that, but I couldn't find > it. > > I looked at the html generated by the compiler in my development > environment hoping to find an onModuleLoad(). But it was the same as > the html I started with. I thought I might simply put an onModuleLoad > () call in the generated page as a way get the whole thing going on > the client side. But apparently that's not the way to do it. Would you > let me know the right way. What is it that gets the generated GWT > code to start running on the client side? > > Thanks. > > -- Russ > > On Feb 5, 12:13 pm, Jason Essington <[email protected]> wrote: >> O.K. the compiler spits out pretty much everything that was in a >> public path, so expect to see those in the output (www) directory. >> in addition you'll likely see some of the following: >> >> [module_name].nocache.js - this is the bootstrap file that loads the >> actual GWT module. >> >> [hash].cache.html - These are the actual javascript payload files >> tailored for each individual browser/i18n combination. >> >> [hash].cache.png - These are generated imagebundle files >> >> [hash].gwt.rpc - these are rpc serialization policy files >> >> clear.cache.gif - blank gif used by GWT for some tasks >> >> history.html - used for history support >> >> hosted.html - used for hosted mode support (debugging against a live >> server) >> >> You'll want to deploy all of these. The hosted.html could be omitted, >> however that would prevent you from stepping through the code running >> on your live site, so just leave it. >> >> -jason >> >> On Feb 5, 2009, at 12:14 PM, RussAbbott wrote: >> >> >> >>> When I compile my GWT application I get 13 files, including >>> the .html >>> and .nocache.js files. Apparently these two files are not >>> sufficient >>> to run the application. (If I launch the .html file in isolation >>> along >>> with the .js file the application doesn't work.) Does that mean >>> that >>> when I'm ready to deploy I have to copy the entire generated >>> directory >>> to my server? >> >>> Thanks. >> >>> -- Russ Abbott > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
