Joel, Do I read this correctly that stacktraces in exceptions will just be available (also on IE if the emulated mode is enabled at compile time) ? That would make my current implementation of finding the source of a Trace statement just work without changes. Great stuff.
David On Fri, Nov 6, 2009 at 3:27 PM, Joel Webber <[email protected]> wrote: > It wouldn't be perfect, but you might be able to get some utility from the > code in StackTraceCreator (in the Core module) in the 2.0 release branch. It > can't get stack traces on all browsers by default (IE requires an extra flag > that generates a fair amount of overhead -- don't use lightly), but could > help somewhat. > > On Fri, Nov 6, 2009 at 5:22 AM, Miroslav Pokorny > <[email protected]> wrote: >> >> Why not just include the class.method name at the start of each and every >> message String sent to your logging method...Its a pain but it works. >> >> On Fri, Nov 6, 2009 at 7:06 PM, stuckagain <[email protected]> wrote: >>> >>> Hi, >>> >>> Would it be possible to implement a Trace mechanism that (when >>> enabled) would be able to autodetermine from where it is called >>> (classname.method). In plain java I have such a thing implemented in >>> my tracing package and it really helps in keeping trace statements >>> really simple. >>> >>> In the GWT client I'm using the incubator log API (I also tried out >>> gwt-log from Fred), but none of the log/trace packages that exist >>> today are able to detect from where they are called to give a better >>> output. >>> >>> It looks to me that I will actually need compiler support to be able >>> to implement such a thing. >>> >>> I read in this newsgroup that there is work going on to make >>> stacktraces available in the browser. Could that mechanism be reused >>> to implement what I need ? (In plain Java I get the stacktrace and >>> find the stack element just before the trace statement). >>> >>> David >>> >> >> >> >> -- >> mP >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
