Saturday, May 24, 2014

Re: Google Chrome 35 GWT plugin incompatibility

I think you need both a Dev mode and a Super dev mode environment for effective debugging. I use Chrome for Superdev and have a VM with IE 9 for Dev mode. Sometimes you get exceptions without a stack trace in the browser console under Superdev. You then need Eclipse and Dev mode to discover the cause. While Dev mode loads, go and make yourself a cup of tea.

I heard IE 9 is the quickest for Dev mode. It is still limited becauae Eclipse is liable to run out of memory if you make a change and refresh browser. Yes you can tinker with its memory settings, but this is tricky.

Superdev is getting better all the time as Chrome debugging tools improve. I am looking forward however, to being able to debug in Superdev within Eclipse.

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