We talked about it a bit back when we started on Super Dev Mode. The
main drawback is that if we take over the remote debugging protocol
for a different purpose, what happens when you want to use a debugger?
Also, there's no web standard as far as I know; each browser has its
own protocol that
On Wed, Dec 12, 2012 at 1:24 PM, Brian Slesinsky skybr...@google.comwrote:
We talked about it a bit back when we started on Super Dev Mode. The
main drawback is that if we take over the remote debugging protocol
for a different purpose, what happens when you want to use a debugger?
Also,
I agree this would be sexy and seems like where we should go, but it's
a long term thing. chromedevtools was only my list of things to
eventually (ha) play with.
I would think surely browsers would end up with a standard debug
protocol at some point--maybe Chrome/GWT could help drive that effort
Hey,
Since Thomas brought up changes to dev mode, I've been thinking about
how to implement an incremental dev mode.
After playing with SuperDevMode, it is better (no extensions/etc.), but
AFAICT it still starts over from let's build a ResourceOracle, now
let's build a TypeOracle, etc.
Seems
How would you deal with re-entrancy though, e.g.
Java - JS - Java - JS
If you simulate a synchronous call from JS to Java by breaking, what
happens when Java calls back into JS? Everytime I thought about doing
this, it basically boils down to emulating continuations with CPS
transform, and that
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
I hadn't seen this before, but they seem to be tackling
cross-browser/in-IDE debugging:
http://www.eclipse.org/webtools/jsdt/debug/
- Stephen
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
