Hi Liraz, I get that this is impossible to keep maintaining the previous Dev mode, > but without it GWT cannot be debugged properly anymore. >
I can debug apps in SDM, I can set Java breakpoints on code and on exceptions. It works for me under IDEA + Chrome. > See the following for example: > > http://stackoverflow.com/questions/25105469/how-to-debug-using-superdev-mode > <http://www.google.com/url?q=http%3A%2F%2Fstackoverflow.com%2Fquestions%2F25105469%2Fhow-to-debug-using-superdev-mode&sa=D&sntz=1&usg=AFQjCNELGPBX-uQQvEQ0qQULjMUqB-uAEA> > > In SDM You cannot watch, > I can watch members and locals. Yes they have a bit different names, but I can inspect objects. > it's impossible to check which type or what's the problem exactly during > debug > Type of a variable ? use sout v.getClass() - it basically made working with GWT impossible. > > And as far as i can see, ... , it's not debugging a JVM program - ... > There is no JVM when JS executes, so that there is nothing to debug in JVM. > You have to get the Dev mode back, and to make the legacy Dev mode better > - not the super dev mode that is aimed to source maps - i think it's a > mistake. > Consider using GWT 2.7, it supports DevMod -Kirill -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
