I fully agree, running a GWT app in native browser and being able to debug it is the way to go, hosted mode is history. However, for the time being, it looks like Google didn't really think their browser plug-in through for accomodate apps which are gradually introducing GWT by incorporating GWT modules into existing pages. If my app was fully GWT with one module running the whole app, then I would just do what you do.
I have seen others around the web posting similar frustrations, calling new GWT debugging "virtually impossible", now I understand why. The browser plug-in should really accept URL patterns that represent GWT modules you want to debug. I may be missing something here, but this appears as the most practical solution. On Mar 12, 12:11 pm, Trevis <[email protected]> wrote: > I find hat being able to debug in firefox with firebug and have gwt > breakpoints to be vastly surperior to old school hosted mode. > > I guess I haven't had the frustration that you have because I just > leave the browser minimized between debug sessions and refresh when > necessary. > > On Mar 11, 10:40 am, JazzyJava <[email protected]> wrote: > > > > > Helllo, > > I am testing an upgrade of our appliation fro GWT 1.7 to 2.0. All is > > fine, except I find that debugging now is a much bigger pain than it > > was in 1.7. I have a feeling I am missing something, since it's hard > > for me to believe that it is so much more inconvinient now. > > > In GWT 1.7 Hosted Mode browser, I could happily click on my links (GWT > > or non non-GWT modules), and when I clicked on the GWT module that had > > a breakpoint, the Eclipse debugger would kick in. > > > Our URL's are for the most part dynamic, i.e. they pass a bunch of > > dynamic URL query parameters to the GWT module. In GWT 2.0 debugging, > > I now have to copy-paste the dynamic URL into a browser window that > > has the address bar enabled, and manually add gwt.codesvr=xxxxxxx URL > > query parameter at the end. > > > This is major pain and I am not sure how I can justify an upgrade to > > 2.0 until I understand how to let my development team conveniently > > debug. > > > If anyone can shed some light on this pain, it will be very much > > appreciated. > > > Oleg- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
