As a follow-up, I hacked a 'Close' button in to the DivLogger and, with that, I think it will work well for us. This way, once it pops up and shows the log-entry, the user can choose to get it off the screen with the close button. Then on a subsequent log entry, the DivLogger reappears.
I saw this is a proposed enhancement, too, so I added my star: http://code.google.com/p/gwt-log/issues/detail?id=3 Thanks, Eric On Jul 22, 6:35 am, Eric B <[email protected]> wrote: > Hi Fred, > > Thanks for the response. I'll give them a try, but up until now, I've been > avoiding the console loggers since I don't want our QA group to need those > tools open in order to capture errors for development. > > I like the concept of the window logger because it's not on the page like > the DivLogger, but is using the browser (which our QA group can easily > monitor). > > Anyway, I understand the priorities and I'll revisit the other loggers. > > Thanks, > > Eric > > > > On Wed, Jul 21, 2010 at 4:56 PM, Fred Sauer <[email protected]> wrote: > > Eric, > > > There's been no recent work on the WindowLogger. An inability or laziness > > on my part in figuring out how to scroll the Window as content has been > > added, probably led me to put entries in reverse order :) > > > Have you tried using the ConsoleLogger with FireBug[Lite], Chrome > > inspector, IEDeveloper Toolbar, etc? > > > On Wed, Jul 21, 2010 at 3:05 PM, EricB. <[email protected]> wrote: > > >> I saw in the documentation that WindowLogger is "experimental", but is > >> the behavior I'm seeing expected? > > >> - Oldest entries show up at top (DivLogger has oldest entries at the > >> bottom) > >> - No buttons at top to enable/disable certain Log levels. (DivLogger > >> has buttons at top allowing the user to enable/disable Log levels). > > >> I don't care too much about the buttons, but having all the newest > >> entries at the bottom of the page is tough. > > >> Not sure if it matters, but I'm on 3.0.1. > > >> Thanks, > > >> Eric > > >> -- > >> 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]<gwt-log%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/gwt-log?hl=en.- Hide quoted text - > > - Show quoted text - -- 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.
