hi sönke!
dooooh! that's it!!! now sos is responding... :-)
for anyone using as2ant; this is how it has to be set up:
<mtasc
src=""
classpath="${src.dir}:${core.dir}:${classCollection.dir}"
swf="${build.dir}/${targetswf}" main="false" version="${version}"
frame="${classFrame}"
trace="org.osflash.zeroi.logging.LoggerClass.log">
<argument value="org/osflash/zeroi/logging/LoggerClass"/>
<!-- Outcomment your logging target -->
<argument
value="org/osflash/zeroi/logging/publisher/SOSPublisher"/>
<!-- <argument
value="org/osflash/zeroi/logging/publisher/TextFieldPublisher"/>
-->
<!-- <argument
value="org/osflash/zeroi/logging/publisher/XRayPublisher"/> -->
<!-- <argument
value="org/osflash/zeroi/logging/publisher/LuminicPublisher"/> -->
</mtasc>
now i'll try to use the logconfig-feature wich sounds really
promising when you have a bunch of traces from different
classes ;-)
thanks for the quick response and 'rock on'!
henrik
Sönke Rohde wrote:
hi henrik,
thanks for your feedback.
the trace-function your are
setting is "logtrace" but has to be "log":
org.osflash.zeroi.logging.LoggerClass.log
I
hope that is it but anyway I have never tested zeroi with as2ant but
should of course work from theory.
Cheers,
Sönke
greetings ralf & s?hnke,
first of all: thx a lot for this really useful aproach! :)
i immediatly tried to use zeroi but ran into some problems...
i use the as2ant-tasks from simon quite often; when trying
to implement zeroi i'm not able to see anything in sos...
<mtasc src=""
classpath="${src.dir}:${core.dir}:${classCollection.dir}"
swf="${build.dir}/${targetswf}" main="false" version="${version}"
frame="${classFrame}"
trace="org.osflash.zeroi.logging.LoggerClass.logtrace">
<argument value="org/osflash/zeroi/logging/LoggerClass"/>
<argument
value="org/osflash/zeroi/logging/publisher/SOSPublisher"/>
</mtasc>
any hints/ideas how i have to
set up my build.xml correctly?
i guess it has something to do with the way i use the argument-
tag... the classpath contains everything necessary and my
test-class is set back to use 'normal' trace-statements inside
the as-code *?*
thx in advance!
henrik
--
Henrik Weber
Certified Flash Developer
__freemind design__
www.freemind-design.de
-----Original Message-----
Date: Wed, 16 Aug 2006 20:02:12 +0800
From: iiley <[EMAIL PROTECTED]>
Subject: Re: [osflash] Zeroi is ready to rumble
To: "Open Source Flash Mailing List" <[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Hi Ralf,
This is a cool project, nice to see it, gonna to down and use it now. :)
Thanks for the great things!
2006/8/16, Ralf Bokelberg <[EMAIL PROTECTED]>:
>
> Dear Osflashers,
>
> i'm proud to announce that Zeroi finally became an official osflash
> project.
>
> http://osflash.org/zeroi
>
> The main idea of Zeroi is to be able to use any logging system (like
> SOS, admin tool, luminic box, ...) in your MTASC project, without
> having to change the code of your app. In fact your code doesn't even
> need to know about Zeroi. Inside your app you only use trace
> statements. The traces are forwarded to the logging system of your choice.
> That's what the name Zeroi is standing for: Zero Impact.
>
> To make Zeroi even more useful, S?hnke Rohde added the possibility to
> configure your logging system by xml. You can filter logs on a
> class or package base, e.g. suppress every log from class XY with a
> loglevel <= WARN
>
> As always,
> your comments, testimonials, and maybe new code is much appreciated.
>
> Cheers
> Ralf & S?hnke.
|
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org