Odd. There is an ie developer toolbar which has some of the same functionality as Firebug. It allows you to click on elements and inspect their HTML and CSS.
On Tue, Dec 1, 2009 at 11:44 AM, Ittai <[email protected]> wrote: > Hi Fred, > First thanks for answering and thanks for this great project! > Secondly, I've hidden the DivLogger by editing the *.gwt.xml and > adding <set-property name="log_DivLogger" value="DISABLED" /> as was > suggested in the GettingStarted tutorial. > I've tried using Firebug but there are some other css problems (the > css is per IE) which cloud the profiling. > The odd thing is that I'm currently opening my application via an MFC > control which uses IE (It's basically IE) and there I get the > rectangle; If I just removing using the DeferredCommand.addCommand(... > bit the application looks fine and no problems arise. > > Ittai > > On Nov 30, 7:37 pm, Fred Sauer <[email protected]> wrote: > > Perhaps you've hidden only the inner parts of the DivLogger via CSS, but > not > > all of it. > > > > You can use Firebug to easily see where the rectangle is coming from. > > > > Fred > > > > > > > > On Mon, Nov 30, 2009 at 9:21 AM, Ittai <[email protected]> wrote: > > > Hi, > > > I've followed the GettingStarted tutorial and everything worked great > > > however when I deployed my app to my webserver (apache tomcat) I saw > > > that an additional white blank rectangle is showing. I'm not sure how > > > it got there however once I comment out the code in my entry point > > > class from the example: > > > public void onModuleLoad() { > > > Log.setUncaughtExceptionHandler(); > > > DeferredCommand.addCommand(new Command() { > > > public void execute() { > > > onModuleLoad2(); > > > } > > > }); > > > } > > > public void onModuleLoad2() {...} > > > and return to the regular way of just having my onModuleLoad and still > > > calling Log.setUncaughtExceptionHandler(); in it then that rectangle > > > disappears. > > > I think it might be related to say that I've turned off the DivLogger > > > and turned on the WindowLogger. > > > Other then that the log works great however I'm afraid that if I leave > > > it like it is now the Log might not catch all exceptions as is stated > > > in the tutorial. > > > > > I'd appreciate any help > > > Ittai > > > > > -- > > > > > You received this message because you are subscribed to the Google > Groups > > > "gwt-log" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<gwt-log%[email protected]> > <gwt-log%[email protected]<gwt-log%[email protected]> > > > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/gwt-log?hl=en. > > > > -- > > Fred Sauer > > Developer Advocate > > Google Inc.1600 Amphitheatre Parkway > > Mountain View, CA 94043 > > [email protected] > > -- > > You received this message because you are subscribed to the Google Groups > "gwt-log" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<gwt-log%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/gwt-log?hl=en. > > > -- Fred Sauer Developer Advocate Google Inc.1600 Amphitheatre Parkway Mountain View, CA 94043 [email protected] -- You received this message because you are subscribed to the Google Groups "gwt-log" 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/gwt-log?hl=en.
