I was using galileo and whenever I tried to breakpoint in client code it would never hit it. I chalked it up as either not working or not supported, and didn't investigate further.
Recently I updated to the latest eclipse with the latest plugin, and indeed it works...very happy about that. On Sep 11, 10:21 am, Ian Bambury <[email protected]> wrote: > If you are using Eclipse, in hosted mode you can debug it in the normal way > - e.g. put breakpoints in, examine values etc. > Ian > > http://examples.roughian.com > > 2009/9/11 davis <[email protected]> > > > > > Thanks Ian -- was banging my head against the wall, and this narrowed > > it down. > > > How are people typically debugging the java GWT client code -- since > > you can't breakpoint it -- I assume the only way is to compile it down > > with pretty printing and use something like firebug? > > > I separate the logic as much as possible with MVP and write straight > > JUnit tests for presenter classes, but this isn't a silver bullet > > against all possible pitfalls. > > > The problem was code that stores references to RootPanel div wrappers, > > and later it tried to add these to VerticalPanel. You obviously can't > > add RootPanel to other panels. This was a simple typo mistake, and > > once corrected, the problem went away. The bummer in all this is that > > I didn't get any warning or error or exception, it just generated > > javascript without my div elements. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
