Re: GWT 2.5 dev mode unable to refresh

fyi: I've now tried super-dev-mode.  It's cool that it is pure JS, but every time I make a change I have to recompile (via the "dev mode on" bookmark), this is really slow as our app is around 2MB of JS (using the gwt plugin I just refresh the page - okay, sometime I have to restart the server).  Also, the Chrome debugger doesn't seem as full featured as the Eclipse debugger.

...but, yes, it does fix the problem.  :-)

On Wednesday, February 27, 2013 11:31:18 AM UTC+11, James Nelson wrote:

Have you guys considered trying out the new super-dev-mode?

I only save the sluggish dev mode for when I absolutely have to have a java debugger to find out what's going on.

Super-dev-mode will cost you a few seconds per page refresh (though, OOM popping your JVM is much, much slower),

but it also gets rid of a very nasty class of bugs: "Ones you shouldn't bother with in the first place".

Performance in dev mode and compiled mode are very different,

even down to how asynchronicity and some timing works.

What makes production mode fast makes dev mode slow (jsni).

And, if you have the choice, always optimize for production.

Oh, and in regards to your upgrade woes, make sure you manually delete and gwt unit caches you have left,
a cached unit from one version will likely be incongruent with the new 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.