I’ve been playing with the fantastic three.js library lately, and for a project I needed a way to determine where an object in 3D space was on the page in 2D. I’ve gotten something working after reading through articles, documentation and commentary on three.js’ github issues page.
In the example below I have a div (the red circle) that’s being absolutely positioned on top of where I’ve determined the sphere to be.
Andy Lemay made a very useful post on how to use fluid to run Amazon CloudPlayer as its own app. In a nutshell: You can download an excellent application called Fluid to create a desktop version of a webpage - in this case, the newly released Amazon Cloud Player. This worked great, however I was hoping to get keyboard shortcuts and Growl notifications working. Luckily, Fluid has a UserScript API to allow you to write UserScripts (essentially just js files) which can be loaded into the web application.
Now to poke around! Digging into the page and js files in Amazon CloudPlayer revealed a nice API that I figured I could hack into. TextMate’s ‘Reformat Document’ was a huge help here to turn the minimized js files into something human readable.
I use a tail command alias (from FlashApe) to constantly output the contents of my flashlog file to the terminal which makes reading output very useful. However, if you use FlexBuilder/FlashBuilder at all, you’ll notice it will dump millions of useless comments such as
Just resizing the design view is enough to dump tons of these statements into your trace output, which gets very annoying. While working on a project, a friend of mine had the idea of somehow removing these statements, which got me thinking.