<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Processing, Ported to JavaScript</title>
	<atom:link href="http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/feed/" rel="self" type="application/rss+xml" />
	<link>http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/</link>
	<description>Motion graphics, live visuals, VJing, video production, and interactive art</description>
	<pubDate>Thu, 20 Nov 2008 12:49:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Create Digital Motion &#187; Processing + iPhone, Via JavaScript, SpiderMonkey, OpenGL ES</title>
		<link>http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-110628</link>
		<dc:creator>Create Digital Motion &#187; Processing + iPhone, Via JavaScript, SpiderMonkey, OpenGL ES</dc:creator>
		<pubDate>Tue, 03 Jun 2008 15:39:11 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-110628</guid>
		<description>[...] my complaints about trying to run Processing in JavaScript in a browser, the recent port of Processing&#8217;s syntax to JavaScript has a lot of potential. Part of the underlying lesson here: platform-independence is cool. So where [...]</description>
		<content:encoded><![CDATA[<p>[...] my complaints about trying to run Processing in JavaScript in a browser, the recent port of Processing&#8217;s syntax to JavaScript has a lot of potential. Part of the underlying lesson here: platform-independence is cool. So where [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Create Digital Motion &#187; Processing.js: Very Cool, But JavaScript Nuts Go Overboard</title>
		<link>http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-105356</link>
		<dc:creator>Create Digital Motion &#187; Processing.js: Very Cool, But JavaScript Nuts Go Overboard</dc:creator>
		<pubDate>Thu, 15 May 2008 21:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-105356</guid>
		<description>[...] projects are fantastic. I&#8217;m a believer in experiments and proof of concept. So when I saw the port of Processing to JavaScript, I was impressed. I think this stuff is valuable, even if it&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] projects are fantastic. I&#8217;m a believer in experiments and proof of concept. So when I saw the port of Processing to JavaScript, I was impressed. I think this stuff is valuable, even if it&#8217;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Resig - Processing.js Aftermath</title>
		<link>http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-104930</link>
		<dc:creator>John Resig - Processing.js Aftermath</dc:creator>
		<pubDate>Wed, 14 May 2008 06:07:46 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-104930</guid>
		<description>[...] Scott Hanselman, Kottke, Simon Willison, Peter Kirn, and [...]</description>
		<content:encoded><![CDATA[<p>[...] Scott Hanselman, Kottke, Simon Willison, Peter Kirn, and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steve cooley</title>
		<link>http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-104891</link>
		<dc:creator>steve cooley</dc:creator>
		<pubDate>Tue, 13 May 2008 20:38:15 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-104891</guid>
		<description>I don't know why my comment didn't go live on the author's original post, but the example graphic as seen here is either entirely by or extremely influenced by Jared Tarbell, http://complexification.net</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know why my comment didn&#8217;t go live on the author&#8217;s original post, but the example graphic as seen here is either entirely by or extremely influenced by Jared Tarbell, <a href="http://complexification.net" rel="nofollow">http://complexification.net</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tatu Guerra</title>
		<link>http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-104329</link>
		<dc:creator>Tatu Guerra</dc:creator>
		<pubDate>Sat, 10 May 2008 14:39:17 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-104329</guid>
		<description>Well, as I said before I'm ignorant at subject. Thx very much for the explanation Peter. I got the point.

thx</description>
		<content:encoded><![CDATA[<p>Well, as I said before I&#8217;m ignorant at subject. Thx very much for the explanation Peter. I got the point.</p>
<p>thx</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Kirn</title>
		<link>http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-104239</link>
		<dc:creator>Peter Kirn</dc:creator>
		<pubDate>Fri, 09 May 2008 19:40:46 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-104239</guid>
		<description>@Tatu: Nope, that won't work. Quartz Composer using JavaScript to script other events in QC -- and uses QC as the renderer. This implementation assumes you're using the *browser* as the renderer; that's the only reason you'd even want to use it. The browser is what's putting stuff on the screen.

I should say it explicitly: there is a HUGE advantage to running Processing on Java as it was designed. All these additional libraries, all its performance features, its ability to do high-quality rendering, OpenGL -- all of this is dependent on Java as the platform.

Compare Quartz Composer, which does only a few things, isn't extensible, is proprietary and closed-source (Java is open), and is chained to the Mac platform.</description>
		<content:encoded><![CDATA[<p>@Tatu: Nope, that won&#8217;t work. Quartz Composer using JavaScript to script other events in QC &#8212; and uses QC as the renderer. This implementation assumes you&#8217;re using the *browser* as the renderer; that&#8217;s the only reason you&#8217;d even want to use it. The browser is what&#8217;s putting stuff on the screen.</p>
<p>I should say it explicitly: there is a HUGE advantage to running Processing on Java as it was designed. All these additional libraries, all its performance features, its ability to do high-quality rendering, OpenGL &#8212; all of this is dependent on Java as the platform.</p>
<p>Compare Quartz Composer, which does only a few things, isn&#8217;t extensible, is proprietary and closed-source (Java is open), and is chained to the Mac platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tatu Guerra</title>
		<link>http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-104237</link>
		<dc:creator>Tatu Guerra</dc:creator>
		<pubDate>Fri, 09 May 2008 19:36:45 +0000</pubDate>
		<guid isPermaLink="false">http://createdigitalmotion.com/2008/05/09/processing-ported-to-javascript/#comment-104237</guid>
		<description>I'm prety ignorant with programming. But I have a question about this subject. Wouldn't be useful JavaScript in Processing to connect Processing and QuartzComposer, once Qartz also work with JS?</description>
		<content:encoded><![CDATA[<p>I&#8217;m prety ignorant with programming. But I have a question about this subject. Wouldn&#8217;t be useful JavaScript in Processing to connect Processing and QuartzComposer, once Qartz also work with JS?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
