I get that this is impossible to keep maintaining the previous Dev mode, but without it GWT cannot be debugged properly anymore. See the following for example: http://stackoverflow.com/questions/25105469/how-to-debug-using-superdev-mode
In SDM You cannot watch, it's impossible to check which type or what's the problem exactly during debug - it basically made working with GWT impossible. The only thing that helps me get going with GWT development is the regular Dev mode - which you can use the full features of debugging, and solving the problem in seconds - not hours And as far as i can see, this will not be improved anytime soon - since Chrome is simply translating source maps, it's not debugging a JVM program - and will be the same for all other browsers that will support source maps. Oh.. and what about IE? will they support source maps - you just killed it there i guess.. 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. Super dev mode is a nice idea and feature, but it doesn't work - tried it for some time... Also tried it on 2.8.0 - still useless.. same problems - far from the basic needs of debugging -- 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.
