On Tue, Jul 26, 2011 at 3:53 PM, David Chandler <drfibona...@google.com> wrote: > ... Unfortunately, the Google instant search team hasn't yet tackled the > instant dev mode > plugin problem ;-)
Here's the solution -- ditch the plugins entirely. Instead, develop a Java applet that functions as a JPDA server that knows how to translate the state of the running GWT app into the JPDA protocol so a remote Java debugger can understand it. The applet would be embedded into the module's primary .html page. The concept of "devmode" basically goes away and instead the GWT compiler would have a "DEBUG" output format which would include code that passes state information to the JPDA Java applet as the javascript executes. Have youse guys considered anything like this? The JPDA applet is just a SMOP, but I'd have to guess adding a "DEBUG" output format to the GWT compiler would be pretty big. "F5/Refresh" performance would need consideration in this too. It's a totally half-baked idea right now, but I wanted to toss it out to see if the smarties at google think it's worth further thought. eric -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
