Re: [As2lib-updates] Flashout 2

[Simon W. <Sim...@gm...>]

General Mtasc Trace support is a nice idea. I will think about a good
implementations that leverages all its features. If you have any suggestions
I'd be more than pleased to hear them. ;)

Greetings,
Simon
--
Simon Wacker
www.simonwacker.com
www.as2lib.org
www.hq-heilbronn.de
www.flik-flak.de

----- Original Message ----- 
From: "Paul Ingalls" <in...@mu...>
To: "'martin heidegger'" <mas...@gm...>
Cc: "'Simon Wacker'" <Sim...@gm...>; <in...@mu...>
Sent: Tuesday, June 28, 2005 9:42 PM
Subject: RE: [As2lib-updates] Flashout 2


> Perhaps an MtascTRACEHandler would be more appropriate, as that is what
> flashout is really using.
>
> The -trace option for newer mtasc builds adds an interesting wrinkle to
> logging.  Not sure of the impact, but with some thought I bet you could 
> come
> up with an interesting mechanism to support lots of environments while
> leveraging it.  You'd just need a TRACE function defined for MMC builds.
>
> Worth some thought...
>
> -----Original Message-----
> From: martin heidegger [mailto:mas...@gm...]
> Sent: Tuesday, June 28, 2005 10:53 AM
> To: Paul Ingalls
> Subject: Re: [As2lib-updates] Flashout 2
>
> Uhh ... "Flashout_0_2_Handler" (its not release 2!) seems a little
> weird for me, He could change it any time and we would have to change
> it too "FlashoutTraceHandler" would be more appropiate but how to name
> the other class "FlashoutClassHandler"?
>
> yours
> Martin.
>
> 2005/6/28, Paul Ingalls <in...@mu...>:
>> That is correct, you need to use -trace Flashout.traceReplacer on the
> mtasc
>> commandline, but that is the default setting if you are using the new
>> Flashout where it would be required, so I didn't think it was a big deal.
>> If you are using old Flashout, it just calls the old stuff. But I'm not
> tied
>> to any implementation, I'd just like to see it supported in the official
>> cvs...:)
>>
>> Probably the cleanest would be to add a new Flashout2Handler or something
>> like that...
>>
>> Paul
>>
>> -----Original Message-----
>> From: Simon Wacker [mailto:Sim...@gm...]
>> Sent: Tuesday, June 28, 2005 9:16 AM
>> To: Paul Ingalls; as2...@li...
>> Subject: Re: [As2lib-updates] Flashout 2
>>
>> Flashout 0.2 support is already on my todo list. I just did not find the
>> time yet to implement, but I'll do that right away.
>> I used the async method for the old version because the old version's
>> Flashout log methods also call trace and I did not want this behavior.
> There
>>
>> is also one flaw with your suggested implementation because if you use
> e.g.
>> Flashout.debug you also have to specify TRACE in mtasc to make it 
>> working.
>> I'll nevertheless stick to that implementation because it is 'compatible'
>> with both Flashout versions.
>> Thanks for your help. ;)
>>
>> We plan to release the final as2lib version with all bugfixes etc. made
>> recently on Monday, the new FlashoutHandler etc. will also be included.
>>
>> Greetings,
>> Simon
>> --
>> Simon Wacker
>> www.simonwacker.com
>> www.as2lib.org
>> www.hq-heilbronn.de
>> www.flik-flak.de
>>
>> ----- Original Message -----
>> From: "Paul Ingalls" <in...@mu...>
>> To: <as2...@li...>
>> Cc: <in...@mu...>
>> Sent: Tuesday, June 28, 2005 2:28 AM
>> Subject: [As2lib-updates] Flashout 2
>>
>> > So I installed flashout 0.2.1.2 and my logger stopped working.  I 
>> > needed
>> > to
>> > make some tweaks to FlashoutHandler to get it going again.  Check out
> the
>> > following code -
>> >
>> > public function write(message:LogMessage):Void {
>> > var m:String = convertMessage(message);
>> > switch (message.getLevel()) {
>> > case AbstractLogLevel.DEBUG:
>> > Flashout.debug(m);
>> > break;
>> > case AbstractLogLevel.INFO:
>> > Flashout.info(m);
>> > break;
>> > case AbstractLogLevel.WARNING:
>> > Flashout.warning(m);
>> > break;
>> > case AbstractLogLevel.ERROR:
>> > Flashout.error(m);
>> > break;
>> > case AbstractLogLevel.FATAL:
>> > Flashout.fatal(m);
>> > break;
>> > default:
>> > Flashout.log(m);
>> > break;
>> > }
>> > }
>> >
>> > This should work in both old and new Flashout, instead of the asyncLog
>> > stuff
>> > that was there before which only worked in old Flashout.
>> >
>> > Is there any way we can get a fix into the cvs tree?
>> >
>> > Thanks,
>> >
>> > Paul
>> >
>> >
>> >
>> > -------------------------------------------------------
>> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>> > from IBM. Find simple to follow Roadmaps, straightforward articles,
>> > informative Webcasts and more! Get everything you need to get up to
>> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>> > _______________________________________________
>> > As2lib-updates mailing list
>> > As2...@li...
>> > https://lists.sourceforge.net/lists/listinfo/as2lib-updates
>> >
>> >
>>
>> -------------------------------------------------------
>> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>> from IBM. Find simple to follow Roadmaps, straightforward articles,
>> informative Webcasts and more! Get everything you need to get up to
>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>> _______________________________________________
>> As2lib-updates mailing list
>> As2...@li...
>> https://lists.sourceforge.net/lists/listinfo/as2lib-updates
>>
>
>