Hey, I know I've been quiet on the GWT front lately, but I've really enjoyed seeing all of the reviews/commits going by. Great stuff.
You've probably seen it, but there's a Mozilla post about next-gen dev tools: http://paulrouget.com/e/devtoolsnext I posted a comment on it, but given we have GWT/Googlers here on the list, wanted to reiterate: it seems like if we ever want SuperDevMode editing/debugging to be anywhere near as sexy/seamless as JvmDevMode debugging, we'd want a simple *cross-browser* protocol for doing all of the IDE-ish things like step in/out/reload CSS/etc. I don't think GWT has the man power, either in Google or out, to build per-browser hacks into GPE to do all of this sexy stuff from scratch (i.e. we're trying to get out of the per-browser/extension game). Googlers, or anyone else, any comments on whether Chrome devs are thinking the same thing? I know Chrome has wire protocols, but specifically on a standard debugging protocol... Seems like a lot of the new Chrome dev tool stuff I've seen lately is about rebuilding an IDE inside of Chrome, which just seems so very backwards from what GWT users would like to see. - Stephen -- -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "Google Web Toolkit Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
