Hi Alias,
you should take a look at the AS2LIB AOP framework. This enables you to
"weave" logging statements around methods and that is probably what you
are looking for. I had the same problem and the AOP stuff solved this
very elegant. You can define filters to only log the packages or methods
that you actually want.
On top of that, the AS2LIB itself is the ideal framework for logging
since it supports almost every logger out there (SOS, LuminicBox, etc).
There's a sample of a presentation on Simon Wacker's site but I can't
find the link at the moment. I suggest you check his site for the link
and download the example. www.simonwacker.com
Good luck and have fun !
regards,
Christophe
Alias wrote:
>Hi guys,
>
>Once again, I'm looking at loggers...
>
>OK, what I need is this - every class I have uses systrace trace
>commands, which output the following format:
>
>trace("ClassName.functionName(parameter1, parameter2, ...parameterN)");
>
>What I'd like, ideally, is a logger that takes each of these traces,
>filters them, and outputs them to the output panel, a seperate window
>via localconnection or whatever. I'm on the cusp of just writing my
>own, but I'm wondering if there's a logger which already does this
>which I could use?
>
>I really just want to give it classnames that I'm listening to, and
>filter out everything else. I don't mind going through all my code and
>changing trace to something else, but I'd prefer to keep it in the
>single parameter format.
>
>Does this sound familiar to anyone? Any direction much apreciated.
>
>Cheers,
>Alias
>
>_______________________________________________
>osflash mailing list
>[email protected]
>http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>
>
>
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
