John Grden wrote:
> PS> the reason I don't hook up to the logging of Flex is that I just 
> didn't have the time and it seemed kinda convoluted.  Since they have 
> a debugger, and there's no Output panel like there is in Flash IDE, I 
> don't really see a need to play ball with theirs yet.  Xray will be 
> working with Flex soon (output already works), and that's my debugger 
> of choice ;) 
>
right, well the only way to debug the log is in the console of flex 
builder i guess, i had to make a log console window in my webcam 
broadcaster, to log its output :)

> So, that's been my reasoning.  Of course, if there's some compelling 
> reason to use their trace or hook up to it, then I'm sure I'll do the 
> work.  

well i made my own log appender so it logs to a textbox instead of 
trace, its like log4j, log4net etc.

> but right now, mine does more and has runtime log levels with a cool 
> window that's easily managed.  Also, mine gives you class 
> package/method making the call for the traces - i'm not sure the Flex 
> logging classes do that, but I could be wrong.

it doesnt do stack backtracing ? ill check this out, and ill try and 
load this app and find out what the other can do all good.


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

Reply via email to