Debugging using SuperDevMode is different but definitely not impossible. It also doesn't cost hours spotting a problem. Eclipse users often use the Eclipse plugin "SDBG" which allows you to debug your JavaScript code in your IDE: https://sdbg.github.io . IntelliJ users can do that out of the box.
To be clear: Old DevMode will not come back because Firefox / Chrome do not provide the required NPAPI anymore. And regardless of how often that topic will be discussed here the situation for Firefox / Chrome will not change. I think you can still use old DevMode in IE and of course in older versions of Firefox / Chrome, but no further work will be invested in old DevMode. Thats why it has been officially deprecated for the GWT 2.8 release. Instead work should be invested in improving the SourceMaps spec so the target language (in case of GWT its JavaScript) can be hidden more and more during debugging. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@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.
