In order to improve my development efficiency I was thinking if I can
get away from having to generate the JavaScript files when running the
GWT compiler at all at development time.

My build scripts build both the server and client just fine and
everything works nicely. Because my app is fairly complex I run the
GWT shell with -noserver (after deploying all the necessary things on
the server).

Now most of the time I don't actually every need the client-side
JavaScript because after redeploying my app I go straight to hosted
mode. Is there a way to make the GWT compiler only generate the files
needed to support hosted mode?

I messed around a bit and I get away with copying my public folder
into the right place and adding (from a previous build) the saved
module JavaScript file, hosted.html and history.html. The problem
though are the serialization policy files on the server. They are just
a list of class names but I would have to know exactly what the
compiler is putting into them in order to generate the right MD5
checksum for the file name. The files may actually change all the time
if I do changes to the server side so I wouldn't get away with using
old ones.

If I ever really need the JavaScript files at dev time I can always
press the Compile button in GWTShell.

Any ideas?

My ideas:

1) Use custom field serializers so I don't need the policy files?

2) Maybe a dummy generator to prevent the compiler from generating any
JavaScript. How would I go about this?

What do you think?

Thanks
Christian

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to