Comments on: Trace Manager (AS2) http://blog.sokay.net/2007/10/10/trace-manager/ flash game development discussion Sat, 31 Jul 2010 16:31:00 -0700 hourly 1 http://wordpress.org/?v=3.0.1 By: TraceManager (AS2) Update | blog.sokay.net http://blog.sokay.net/2007/10/10/trace-manager/comment-page-1/#comment-17013 TraceManager (AS2) Update | blog.sokay.net Wed, 20 Aug 2008 09:00:20 +0000 http://blog.sokay.net/2007/10/10/trace-manager/#comment-17013 [...] long ago, I posted about my old TraceManager class for supreme debugging, but it was flawed! Hans from ObjectPainters was kind enough to comment [...] [...] long ago, I posted about my old TraceManager class for supreme debugging, but it was flawed! Hans from ObjectPainters was kind enough to comment [...]

]]> By: jos http://blog.sokay.net/2007/10/10/trace-manager/comment-page-1/#comment-2638 jos Tue, 30 Oct 2007 14:00:00 +0000 http://blog.sokay.net/2007/10/10/trace-manager/#comment-2638 The only thing i'd add is, PLEASE namespace your class'! It gets really old having to have everything in the classpath root. net.sokay.TraceManager. tx! The only thing i’d add is, PLEASE namespace your class’! It gets really old having to have everything in the classpath root. net.sokay.TraceManager.

tx!

]]> By: Christopher J. Rock http://blog.sokay.net/2007/10/10/trace-manager/comment-page-1/#comment-2620 Christopher J. Rock Mon, 29 Oct 2007 20:22:27 +0000 http://blog.sokay.net/2007/10/10/trace-manager/#comment-2620 Thanks for the response Hans, Yeah, this definitely isn't the only resource out there dedicated to just tracing and debugging. And being able to use it without implementing it into the functions themselves would be nice. However, that wasn't really why I built it. I've been doing lots of work with engines that require tons of function nesting and traces become extremely labyrinthine. The TraceManager is built specifically for these reasons: 1. To create proper indentation of my traces so I can read them easily. 2. Allow me to easily update the format of my traces in the future. 3. Allow traces for all or specific functions or groups of functions to be flipped off and on easily. 4. Save all the processes of the program as a navigable array and a legible string, allowing my programs to have a "console" like mechanism or just keep all of their traces until a specific time when I want to see them. -I think #4 is very special. It keeps your programs from lagging due to excessive traces and while the class is designed to be turned on and off so you don't need it running in your final product, you can leave it in your final product for printouts of unforeseen bugs. Even when you're out of the debugging stage, you could easily retrieve data on new bugs just by hitting a designated "print" button. Or do the microsoft thing and ask others that use your software to e-mail you with error printouts or with an encrypted form of them. Anyway, this class is overkill for someone that's doing really light flashwork, but the organizational capabilities it presents for dealing with huge portions of data are what I like about it. I've decided to implement it into all my functions just so I never have to worry about tracing again. It looks like your function wrapper has interesting pieces to it though. I may have to go through the code and look for good ideas! Thanks for the response Hans,

Yeah, this definitely isn’t the only resource out there dedicated to just tracing and debugging. And being able to use it without implementing it into the functions themselves would be nice. However, that wasn’t really why I built it.

I’ve been doing lots of work with engines that require tons of function nesting and traces become extremely labyrinthine. The TraceManager is built specifically for these reasons:
1. To create proper indentation of my traces so I can read them easily.
2. Allow me to easily update the format of my traces in the future.
3. Allow traces for all or specific functions or groups of functions to be flipped off and on easily.
4. Save all the processes of the program as a navigable array and a legible string, allowing my programs to have a “console” like mechanism or just keep all of their traces until a specific time when I want to see them.

-I think #4 is very special. It keeps your programs from lagging due to excessive traces and while the class is designed to be turned on and off so you don’t need it running in your final product, you can leave it in your final product for printouts of unforeseen bugs. Even when you’re out of the debugging stage, you could easily retrieve data on new bugs just by hitting a designated “print” button. Or do the microsoft thing and ask others that use your software to e-mail you with error printouts or with an encrypted form of them.

Anyway, this class is overkill for someone that’s doing really light flashwork, but the organizational capabilities it presents for dealing with huge portions of data are what I like about it. I’ve decided to implement it into all my functions just so I never have to worry about tracing again.

It looks like your function wrapper has interesting pieces to it though. I may have to go through the code and look for good ideas!

]]> By: Shanti Braford http://blog.sokay.net/2007/10/10/trace-manager/comment-page-1/#comment-2610 Shanti Braford Mon, 29 Oct 2007 07:30:42 +0000 http://blog.sokay.net/2007/10/10/trace-manager/#comment-2610 Dude, ThugJacker rocks! LuvTank is sweet too. Dude, ThugJacker rocks! LuvTank is sweet too.

]]> By: Hans http://blog.sokay.net/2007/10/10/trace-manager/comment-page-1/#comment-2609 Hans Mon, 29 Oct 2007 06:57:53 +0000 http://blog.sokay.net/2007/10/10/trace-manager/#comment-2609 Hi Chris, take a look at http://objectpainters.com/blog/?p=62 if you like Which prints something like: => Entering testMethod with arguments 1,2,3 This is printed by testMethod => Entering testMethod2 This is printed by testMethod 2 Hi Chris,

take a look at http://objectpainters.com/blog/?p=62 if you like

Which prints something like:

=> Entering testMethod with arguments 1,2,3
This is printed by testMethod
=> Entering testMethod2
This is printed by testMethod 2

]]>