Friday, May 23, 2014

Re: Google Chrome 35 GWT plugin incompatibility

Am Donnerstag, 22. Mai 2014 16:25:30 UTC+2 schrieb stuckagain:
I tried out SuperDevMode yesterday in Chrome ... not impressed. I think this is going to be a nightmare unless they find a way to show objects and fields as we know them in Java.

Explain, explain? :) I found every object I looking for inside the chrome tools.

I don't think its a nightmare its just something new to work with. And sure, I would love to use "CTRL + Left Mouse Click" to navigate through my source-map classes :)
I work with the SuperDevMode for 1-2 month now. The first few weeks, I hated to work with it too, but today, I don't want to got back to the DevMode. The main issue for us was the long compile time of our gwt project. Therefore, we had to split it into two projects and right now, our recompile time drops from 70 seconds to 15 seconds. Sure, you don't have the eclipse/intellij debugger, but the Chrome F12 Tool is pretty good and the debugging is "much closer" to your real application. For example, you can inspect your elements DOM-state while you hold your program in a breakpoint.

Alex

--
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+unsubscribe@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.

No comments:

Post a Comment