Re: Getting rid of Dev mode for future GWT releases

This topic has been beaten to absolute death. 

DevMode is dead because Chrome and Firefox killed it, nothing the GWT Team or Steering Committee or anybody else could control.

If you need the breakpoints in the IDE, spend the $150 for IntelliJ and get on the SuperDevMode train.

E

On Friday, December 11, 2015 at 7:18:56 PM UTC-5, Peter Donald wrote:

On Saturday, 12 December 2015, <geek.m...@gmail.com> wrote:

So - my opinion - reducing the functionality of the debugger (moving from DevMode to SDM, for example) is in fact a loss of useful features and a reduction in the power of the tools at my disposal. I can use SDM - but it only covers like 50% of the functionality I use in a JVM debugger.

 

I keep hearing that SDM is not as good as DevMode but our experience is that it is better in almost every way. This may be because we IntelliJ idea.

In Both you can run the debugger from the ide, set break points, inspect variables. DevMode has the advantage that variables are easier to decipher. SDM has the  advantage of speed for both startup and refresh and during debug. SDM also never has to deal with differences between different modes and can debug regular JavaScript / other is languages

The one disadvantage will surely be fixed in time so I never really understand why people lament the imminent demise of DevMode

--
Cheers,

Peter Donald

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.