The problem may have been an old hosted.html file that existed from an old SDK. Right now, there is a problem where that file is not re-generated when the SDK is switched. I believe that you would have achieved the same effect if you had blown away the generated directory for your app under the war folder.
System.out.println/System.err.println statements in server code will appear in Eclipse's Console View. At this time, there is no real way to contribute logging statements to the Development Mode View from your application; the statements that appear there are generated by GWT's TreeLogger, which is a part of GWT's infrastructure. On Wed, Dec 9, 2009 at 2:41 AM, Nathan <nathan.shel...@gmail.com> wrote: > Okay, well now I feel silly. I dunno if this is a bug, or if my post > will help anyone else, but here's what I did to get it working: > > I did a full compile in Eclipse. I uploaded the site to my test > host. I browsed there (to make sure it was working) then I went BACK > to Eclipse, re-ran the project, then browsed to it and Firefox figured > it out and said I needed to install the plugin, then everything > worked. > > Quite strange. My guess is I didn't need to upload and browse to the > site, but it seems like you need to do a full compile before just > doing Development Mode...? > > Hope that'll help someone else. Everyone can just ignore my questions > for help now. > > -nathan > > On Dec 9, 2:33 am, Nathan <nathan.shel...@gmail.com> wrote: > > Hey everyone. I just upgraded to GWT 2.0 today, all my code still > > compiles, I clicked run and it said "hey browse to this place with any > > browser!" and I did, and everything looked groovy. > > > > Then I go and try to fix a bug. I throw in a quick logging statement, > > like I used to in Hosted Mode in 1.7, I started with a > > System.out.println, figuring it would print to the console. No dice, > > I only get console logs from server-side code, not java-side code. > > Well, okay. Back to the previous system: Window.alert(...)...Also, no > > dice. For some reason, in Development mode, Window.alert isn't > > working - nothing pops up. > > > > I can compile and deploy live and it works great. > > > > I tried to poke around online, but I found nothing, but I did notice > > that the conversations about RC2 talk about needing a Browser GWT > > Plugin. Neither Chrome nor FF asked me to install a plugin, they just > > "worked" ... > > > > Am I missing something? How can I install the plugin if it doesn't > > ask? Is the plugin still necessary? How would my browsers *mostly* > > work without it? I am so confused by this. > > > > Also, just to make sure, is the "Development Mode" tab in Eclipse the > > tab that my logging statements should be going to? That's what I'm > > gathering, but I wanted to double check there wasn't some other view I > > somehow disabled and that's my problem? > > > > Thanks a bunch! > > > > -nathan > > -- > > 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-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > -- 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-tool...@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.
