To debug the JavaScript in your browser you can either use your browsers dev tools or try using the experimental SDBG plugin for eclipse. When you use your browsers dev tools then you have to set breakpoints inside the browser, when you use SDBG you can set them in eclipse. It is important to understand that in both cases you are debugging JavaScript and not Java.
Indeed, when I open the dev tools in chrome (F12) and go to the "Sources" tab, I can open a lot of JS code and I can set breakpoints there. But I cannot see which JS code corresponds to the Java code that I want to analyze.
Even if I compile in "pretty" mode, I cannot see any correspondence. I think you have to know JS
With the help of SourceMaps (supported in IE11, FF, Chrome and I think latest Opera) the JavaScript will be mapped back to Java statements so you can more easily understand which Java code corresponds to the JavaScript code.
How does this work? Can you open Java sources and set breakpoints there then?
Is this the preferred way of debugging GWT code in SDM?
Will the eclipse integrated debugging return with a later GWT version?
Thanks
Magnus
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