This post covers two things. Debugging Laboratory2D games from Eclipse and Using Chrome to debug Laboratory2D games.

So, Eclipse.

I was busy working in Flash Builder (which is built on eclipse) earlier today, 

And one thing i realised is that I never got around to figuring out why I could not get Eclipse to Run the executable, and then connect to it to debug in one keypress. 
Later on in the evening I tried my hand at installing some other platform features, like C++, to see if that had any handy tools for doing it, and it turns out it did. 

It was called a Launch Group, Where I could even specify a delay on each of the stages. Seeing as I have only 2, it was simple.

What does this give me now?

The same features as before, but all on a single button or shortcut. Now when I press F5 I can tell Eclipse to run the game, connect, and show me the scripts running inside the virtual machine. The file with the little chromium icon is in fact the version 'downloaded' from the Laboratory2D executable, as is in the execution state. If you change this file, you can push the changes immediately back into the virtual machine without restarting anything. Check this out (it will be made better when I have time).

Debugging from Chrome

Since node.js was released, a huge interest in everything Javascript and V8 have been powering development on all fronts. One of these, is called Node-Inspector , which allows you to debug Node.js applications from chrome using the native chrome debugging tools that you normally see in web pages. The cool thing is, I use v8, just like node.js does so it allows me to use the same tools. 

You can check out the video of how it works here, which also includes live editing the values running inside the windows application running Laboratory2D.

Hopefully soon when I am finishing up the rest of the video tutorials these will also get nice voice overs, captions and more.