Re: Debugging client side

Thank you very much: the gwt.codesvr was actually lost in one of the redirection used in the authentication process. I never even thought of it (thing is, just now I learn its purpose)!!!
Regarding compilation, I was aware of the double arrows, but they don't work if I don't recompile the code (in that case they're useless anyway).
In case others need it, I reduces the compile time  by specifying to compile just for Chrome/Safari, by adding in the module .gwt.xml the folloing tag:

<set-property name="user.agent" value="safari" />


On Wednesday, December 5, 2012 4:35:40 PM UTC+1, Thomas Broyer wrote:

On Wednesday, December 5, 2012 4:28:10 PM UTC+1, dcheeky77 wrote:

Something which might be connected: is it normal that for each change I make to the code I need to compile again everything? Now the whole recompilation takes 40 seconds, so it's becoming a bit of nuisance... :|
If I don't recompile, changes are not seen, neither on the "server" code, nor on the "client"...

Any ideas?

My guess is that you're actually running your app in "prod mode", i.e. the URL is missing the ?gwt.codesvr= bit to trigger DevMode.

As for server-side code, you have to click the "reload server" double-spinning-arrow button to have your server-side classes reloaded. If that doesn't do the trick, then maybe you just disabled "Project → Build Automatically" in Eclipse?

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/KwY95YYzAsgJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.