"Working", maybe, but if you look at some performance data, or even the code itself, you'll note that it's disgustingly inefficient, gobbling memory and CPU like there's no tomorrow, even when it's not doing anything. I downloaded it and ran it for about 5 minutes; it looks like a neat concept, but its author has a lot of learning to do.
I'd take another look, I've done much work on it - less memory/CPU than Quartz, assuming that's anything to go by. :) Pointers on how to improve it would be appreciated though. :)
EDIT: Okay, it now is a lot better again thanks to Phanx' feedback. OptionHouse FTW. :)