On Tuesday, February 4, 2014 8:05:16 AM UTC+1, Cristiano wrote: > > Hi Brian, > > I wonder how does it works the development mode plugin? > Isn't it possible to replace it with something in pure javascript that is > based on Web Sockets? >
No, because we need blocking I/O, synchronous communication with the DevMode code server. Leif Åstrand (from Vaadin) tried something using synchronous XMLHttpRequests, but even synchronous XMLHttpRequests are going to disappear. The only solution would be to use the remote debugging protocols so you can really pause the execution in the browser while you do things in Java. I had started a proof of concept using the Flash Debugger to connect to an Adobe AIR runtime a while ago, could be used as a starting point if you want; but connecting a remote debugger (or using the debugger APIs from an extension) generally disables the browser's dev tools (at least it's the case in Chrome, don't know about Firefox). https://code.google.com/p/gwt-in-the-air/source/browse/branches/oophm/oophm/src/net/ltgt/gwt/air/shell/ Debugging in Eclipse the Javascript code is one of the most important > aspect of using GWT for me and I would be happy if it is possible to save > it. > The idea going forward is to use SourceMaps and remote debugging from the IDE, leveraging the same IDE code (and effort!) as for other "compiled to JS" languages (CoffeeScript, etc. or even just JS with a minifier or js2js compiler) -- 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+unsubscr...@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/groups/opt_out.
