Playing devil's advocate here: I code in IntelliJ but I must say that I really like the experience that the Chrome Developer Tools are providing. >From pure debugging point of view (stepping through the code) I actually prefer the Dev Tools over the IDE because with the Dev Tools I can easily change CSS styles, modify the DOM and see the results directly in the browser. Furthermore Chrome Dev Tools has some really good performance and profiling tools built in.
There are a couple of pain points of course and things I would like to see changed. - Bi-directional breakpoints: Currently if I want to set a breakpoint I have to do it inside Chrome Deve Tools. It would be nice to be able to set the breakpoint in my IDE and then debug inside Chrome Dev Tools and vice versa. - Sometimes Dev Tools crash or freeze (if you debug a huge project) or try to display an array with many values. On Tuesday, February 4, 2014 12:05:30 PM UTC+1, Cristiano wrote: > > >> No, really, the way forward is better tooling for SuperDevMode to provide >> a similar experience to DevMode (i.e. never leave the IDE), and even allow >> setting breakpoints and do step-by-step within JSNI. >> >> Oh if this is possible than I'm ok, I was thinking that with SuperDevMode > I would had been obliged to debug and breakpointing on browser development > tools. > Then I need to have a look at it. > > ...and yes if that is possible I agree that it is the way forward. > > -- 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+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/groups/opt_out.
