3402 posts
  • 8 Years of Membership
  • Affiliate Level 6
  • Author Level 8
  • Beta Tester
+8 more
vuzum
says

This is amazing, so I thought I should share it! :)

We’re all debugging, but so far I haven’t seen a better way to do it than this:

1. Take the class shared by BSS on github. http://www.bigspaceship.com/blog/labs/bss-classes-out/

Note: make sure you move the Adapter class to the right folder after you follow all steps

2. Install this AIR app. http://arthropod.stopp.se/

3. Try it out and enjoy! This is how it looks like: http://drp.ly/MMgr

This is amazing because it’s browser independent, and it also has the small button which allows you to keep the window in front of all apps! :)

It has changed the way I debug. I won’t ever use trace!

1633 posts fueledweb.com
  • Affiliate Level 2
  • Author Level 8
  • Collector Level 2
  • Top Monthly Author
+8 more
RimmonTrieu
says

nice, thanks for sharing :-)

1044 posts Freelance Flash and JavaScript Developer
  • Top Monthly Author
  • Trendsetter
  • Weekly Top Seller
  • 8 Years of Membership
+10 more
sike
says

Looks cool, I’ll try it later, thanks your sharing. :)

567 posts
  • 6 Years of Membership
  • Affiliate Level 2
  • Author Level 5
  • Collector Level 2
+5 more
iamdok
says

Just to clarify for anyone having trouble:

Imports required for browser tracing:

import com.bigspaceship.utils.Out;
import com.bigspaceship.utils.out.adapters.ArthropodAdapter;
Code required to register adapter:
Out.enableAllLevels();
Out.registerDebugger( new ArthropodAdapter() );
Code required for trace:
Out.info(this, "I will show up in the IDE and in Arthropod!"); 

When the Air app installs and starts for the first time, answer yes when it asks if you need the latest debug class. Save this class to the following folder (you will need to make the folders):

com.carlcalderon.arthropod

The air app will need to be running to out put the trace in the browser.

1665 posts
  • Trendsetter
  • Weekly Top Seller
  • Winner
  • Featured Author
+10 more
flashedge
says

Thanks, great tool! :D

I use demonster debugger which is awesome.

1572 posts
  • Top Monthly Author
  • Weekly Top Seller
  • 7 Years of Membership
  • Affiliate Level 4
+4 more
dSKY
says

I’m using Vizzy flash tracer
http://code.google.com/p/flash-tracer/
Basically it shows you all your traces in the app window.
No need for any additional classes, just a simple trace statement.

270 posts
  • 6 Years of Membership
  • Affiliate Level 1
  • Author Level 2
  • Collector Level 2
+1 more
magickaito
says

yes monster debugger is also great.

1744 posts Building the Web.
  • Top Monthly Author
  • Trendsetter
  • Weekly Top Seller
  • Beta Tester
+10 more
ZoomIt
says

I use ExternalInterface.call(“console.log(” + whatitrace + “)”)

Much simpler then what has been posted.

3402 posts
  • 8 Years of Membership
  • Affiliate Level 6
  • Author Level 8
  • Beta Tester
+8 more
vuzum
says
Thanks, great tool! :D I use demonster debugger which is awesome.

Thanks, didn’t know about this. I’ll go the route I choose because they implemented this slick thing which allows to set priorities for the traces, such as status, info, warning, etc..

I worked with it yesterday and boy was I productive! :D

I also see a lot of companies use github. Must see what all the fuss is about. :)

82 posts
  • 5 Years of Membership
  • Affiliate Level 4
  • Author Level 5
  • Bundle Boss
+6 more
Co-thinkers
says
I’m using Vizzy flash tracer
http://code.google.com/p/flash-tracer/
Basically it shows you all your traces in the app window.
No need for any additional classes, just a simple trace statement.

I’m using this tool too. Very good.

by
by
by
by
by
by