Moonshine

May 9, 2009 01:05 PM - by Walter Reel 

After seeing processing.js stuff all over the place I figured I would try my hand at some canvas hacking. Here are the results. This only really works for Firefox but that's alright. <canvas> is bleeding edge.

I have to say that it was pretty fun. I'm kind of bummed that there isn't any text rendering support in some of the other browsers but that may be a minor thing. The real interesting thing will be how well it composites with other DOM elements. If I had to guess it should play as well as an animated gif file since that is basically a dynamic image that integrates well with the DOM. It's a little strange to think of it that way because it's so different from flash applications in which you really need to draw lines in the sand about where dynamic DOM elements go and where flash will live (that's why when you're at youtube you only get two drop-down suggestions when typing in the search box on a video page).

A pretty gosh darn cool thing about <canvas> in Firefox is that if you right click "save image" you get the <canvas> render state as a png image.

G Money - May 10, 2009 @ 08:41PM
You may enjoy [this](http://ejohn.org/blog/new-processingjs-and-sizzlejs-sites/)
G Money - May 10, 2009 @ 08:41PM
(this)[http://ejohn.org/blog/new-processingjs-and-sizzlejs-sites/]
G Money - May 10, 2009 @ 08:42PM
<a href="http://ejohn.org/blog/new-processingjs-and-sizzlejs-sites/">this</a>
G Money - May 10, 2009 @ 09:01PM
Oh well. Anyway, you may enjoy that if you haven't seen it already.
wreel - May 11, 2009 @ 01:29PM
I took at look at those. Actually some of the experiments using processing.js was the motivator to play with the technology to begin with. The one thing that I don't like about processing.js is that I'm not familiar with Processing (the original Java one) so there isn't much incentive to write in a language to be processed by JavaScript when I feel comfortable with JavaScript already.
Name
Comment
Challenge
Response