Looking at an old version, it apparently contains
com/google/gwt/core/ext/TreeLogger, com/google/gwt/dev/shell/remoteui/**,
and com/google/gwt/dev/protobuf/**. (i.e. remoteui and its dependencies)
On Monday, November 24, 2014 1:05:46 AM UTC+1, Brandon Donnelson wrote:
Anybody got the
I'm investigating the possibility of creating a js chrome dev tools
extension to talk OOPHM with GPE OOPHM. So far it looks potential feasible
to use what's in place on in GPE to do the communicating with some new
browser extension. Although I do see having to write some new bidirectional
If you mean replacing the DevMode plugin with pure JS in Chrome Dev
Tools, I don't think it's practical. You need synchronously re-entrant
code execution. Javascript's only synchronous blocking call is XHR
sync. But you also need re-entrancy, and when you are
debugging/pausing execution, you run
Leif at Vaadin already was exploring the possibility of having a devmode in
pure JS, his experimental work is at https://github.com/Legioth/devmodejs,
afaik although it's feasible (he succeed debugging some stuff) it is very
slow, apart from other issues like memory allocation, etc.
On Mon, Nov
Somebody previously experimented with it:
https://github.com/Legioth/devmodejs
On Mon, Nov 24, 2014 at 9:49 AM, 'Ray Cromwell' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
If you mean replacing the DevMode plugin with pure JS in Chrome Dev
Tools, I don't think
Ah ha, nice. Thanks for sharing. I remember seeing Lief's work now that you
bring that up.
Ok I'm ending my OOPHM hacking, although I'd like to look at the
possibility of using IDE to remotely control browser dev tools and work
with the SDM systems, or in other words I like what Ray said.
