> I'm just throwing the idea here, in case anyone's interested in > pursuing it, as an alternative to SuperDevMode, to continue running > the code "in Java", debugged using your preferred Java debugger.
Thinking more about it, I think continuing to use the Java debugger (or the existing ClientBrowserChannel/etc. infrastructure) sounds hard. I think it'd be simpler if we could get chromedevtools (or some project like it) to: a) Support multiple browsers b) Support sourcemaps I don't think there would need to be anything GWT specific about it, but we could still provide users with an "hey, I'm in Eclipse setting debug points and inspecting variables"-type experience. Well, I guess we'd probably have to hook into Eclipse/the JDT to tell us when break points were set in .java files and tell chromedevtools "hey, when this line gets hit, pull up the debugger". But then after that the chromedevtools' debugging UI could take over and do the appropriate source mapping when/if needed. It wouldn't be "the Java debugger", but close enough. And as long as there are JS+sourcemap files on disk, it seems like the same basic IDE plugin/browser protocols/etc. should work for GWT, Coffeescript, clojurescript, etc. And surely more people than just us want this sort of setup. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
