|
Yes this should work because the XRayLoggerListenerClass is
listening log-events and tracing with
_global.com.blitzagency.xray.XrayTrace.getInstance().trace( type,
message);
Cheers,
Sönke
Ive just taken a look
at this & it does seem nice. I am wondering tho
When I am using XRAY
I like that my trace statements work the same when compiled with MMC or MTASC
but using the zeroi will it be able to do this with just
trace?
Jim
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ralf Bokelberg
Sent: 24 March 2006 07:12
To: Open Source Flash Mailing
List
Subject: Re: [osflash]
zero impact logging package
It's not a hamtasc feature. The main
logger broadcasts the log messages to its listeners. Probably as2lib works
similar. But what makes the difference is that the app code doesn't need a
reference to the logging classes. So copletely switching tracing on and off
can be done by changing the commandline.
On 3/24/06, erixtekila <[EMAIL PROTECTED]>
wrote:
>>
>> Here is a little excerpt from my
ant build script:
>> <arg value="-trace"/><arg
value="zeroi.logging.LoggerClass.log"/>
>> <arg
value="zeroi/logging/LoggerClass"/>
>> <arg
value="zeroi/logging/TextFieldLoggerListenerClass"/>
>> <arg
value="zeroi/logging/XRayLoggerListenerClass"/>
>> <arg
value="zeroi/logging/SOSLoggerListenerClass"/>
mtasc allows
multiple classes to take trace output or is it a hamtasc
feature
?
Another possibility is to use an ala log4J framework to handle
with
different loggers.
as2lib uses the differents logging solution
around I think
perhaps not
SOS
btw.
-----------
erixtekila
http://blog.v-i-a.net/
_______________________________________________
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
