Re: [osflash] Zeroi is ready to rumble

henrik weber (freemind-design) Fri, 18 Aug 2006 06:57:50 -0700

first of all: yippie! :)
it works as expected; the missing debug-level is showing up and i'm happy for today ;)

concerning the logmessage:
i already understood the behaviour when looking at your code... but i don't know if it
is really useful to show this kind of feedback everytime...
i thought a logic to show a 'normal' trace-statement on the LOG-level (luminicbox has
this level for example; don't know whether sos has something similar) would be more
logical. what do you think about it?

remember that many os-projects have trace-statements in their classes -> you soon
have a lot (read: way too many) 'key not found' messages in your debugger...

anyways: i'm really happy with zeroi right now and it is definetly a huge step in the
right direction.

btw: a collection of how to's about implementing the available debuggers into eclipse-
views would be a nice addition for the osflash-page ;)

greeetz!

henrik

Sönke Rohde wrote:

btw: the logmessage "key not found" comes up when the first char of the logmessage doesn't match a LogLevel prefix like d for Debug, i for Info, w for WARN, e for ERROR, f for FATAL, t for TEMP

Cheer,

Sönke

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of henrik weber (freemind-design)
Sent: Friday, August 18, 2006 2:15 PM
To: [email protected]
Subject: Re: [osflash] Zeroi is ready to rumble

hi zeroid's ;)

2 short observations/bugs(?):

-sometimes sos/luminicbox shows this :
'LogLevel::getLevelByKey 73>> key not found [ANY CHARACTER]'
i found out that it happens if any of the classes of the project monitored by
zeroi has a standard trace-statement... pretty annoying, cause the LogLevel-
class broadcasts this message on ERROR-level.

-in my classes i categorized my default trace-methods as
trace("d [SOME TEXT HERE]");
the more important trace messages have been assigned to INFO-level and
real errors are categorized in ERROR and FATAL...
however the 'normal' debug-messages don't show up in the debugger; may-
be i'm doing something wrong but i'm only able to see them if i change from
"d" to "i"

i don't use logconfig-features (yet)... but i can't see how this could help with
the problems i ran into... any hints from the 'experts'? ;)

thx in advance!

henrik

-------- Original Message --------

Subject: Re: [osflash] Zeroi is ready to rumble

Date: Thu, 17 Aug 2006 10:41:53 +0200

From: henrik weber (freemind-design) <[EMAIL PROTECTED]>

Reply-To: [EMAIL PROTECTED]

Organization: freemind-design

To: [email protected]

References: <[EMAIL PROTECTED]>

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"/>
    
    <argument value="org/osflash/zeroi/logging/publisher/SOSPublisher"/>
    
    
    
</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

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Re: [osflash] Zeroi is ready to rumble

Reply via email to