The nice thing about DevMode was that if you made client changes that you could test them straight away without a redeploy. (We are using -noserver because our server is Jboss Fuse).I will need to rebuild and redeploy the application now for every client code change (or am I understanding this wrongly ?)
You understand it wrong. When you make a client code change you hit the recompile bookmarklet of SuperDevMode (which you can drag in your browser's bookmark bar) to trigger a recompile of your app. After the app is recompiled the page reloads automatically and you will see the changes. You only need to redeploy if you make server changes. When you activate SDM through its bookmarklet all client side code will be downloaded from the SDM code server and not from your Jboss Fuse server.
With GWT 2.6 the recompile time may take some time (its similar to a -draft compile)...how long that greatly depends on your app. However GWT trunk already has initial support for incremental/modular compilation. With incremental compilation turned on GWT will only recompile the GWT modules in which you have made changes and the ones that depend on them. So to make best use of incremental compilation your app should consist of multiple smaller GWT modules instead of a single large one.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment