<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Shader Source Code</title>
	<atom:link href="http://kickingbear.com/blog/archives/5/feed" rel="self" type="application/rss+xml" />
	<link>http://kickingbear.com/blog/archives/5</link>
	<description>stupid cocoa tricks</description>
	<lastBuildDate>Wed, 14 Oct 2009 03:48:26 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Keith Lazuka</title>
		<link>http://kickingbear.com/blog/archives/5/comment-page-1#comment-425</link>
		<dc:creator>Keith Lazuka</dc:creator>
		<pubDate>Fri, 03 Jul 2009 12:34:23 +0000</pubDate>
		<guid isPermaLink="false">http://kickingbear.com/dispatches/?p=5#comment-425</guid>
		<description>&lt;p&gt;Hi Guy,&lt;/p&gt;

&lt;p&gt;Thanks for sharing your ideas regarding expressing your custom drawing code as a data structure. I wanted to send you an email, but I can&#039;t find your email address, so I&#039;m just going to you use this comment box instead!&lt;/p&gt;

&lt;p&gt;Anyway, your Cocoa Shaders blog post was very influential to me, and I implemented a similar system in Python. It suited my purpose, but I never did anything with shaders in Cocoa until I discovered the &quot;TTStyle&quot; code in Joe Hewitt&#039;s Three20 library for the iPhone. He has implemented a shader system very similar to yours, except that it it expressed strictly as a linked list.&lt;/p&gt;

&lt;p&gt;So while I was reading Joe&#039;s shader code, I remembered what you said about building a tool to construct shader trees. Since one of the purposes of Three20&#039;s shader system is to allow clients of the library to customize/theme its view components, I figured that this would be a perfect place for a more user-friendly tool to play around with the shader lists. And so I began building TTStyleBuilder (http://www.vimeo.com/5429347).&lt;/p&gt;

&lt;p&gt;Anyway, I just wanted to show you what I built since your blog post was the inspiration.&lt;/p&gt;

&lt;p&gt;Thanks!
-keith
www.thepolypeptides.com&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi Guy,</p>

<p>Thanks for sharing your ideas regarding expressing your custom drawing code as a data structure. I wanted to send you an email, but I can&#8217;t find your email address, so I&#8217;m just going to you use this comment box instead!</p>

<p>Anyway, your Cocoa Shaders blog post was very influential to me, and I implemented a similar system in Python. It suited my purpose, but I never did anything with shaders in Cocoa until I discovered the &#8220;TTStyle&#8221; code in Joe Hewitt&#8217;s Three20 library for the iPhone. He has implemented a shader system very similar to yours, except that it it expressed strictly as a linked list.</p>

<p>So while I was reading Joe&#8217;s shader code, I remembered what you said about building a tool to construct shader trees. Since one of the purposes of Three20&#8217;s shader system is to allow clients of the library to customize/theme its view components, I figured that this would be a perfect place for a more user-friendly tool to play around with the shader lists. And so I began building TTStyleBuilder (<a href="http://www.vimeo.com/5429347)" rel="nofollow">http://www.vimeo.com/5429347)</a>.</p>

<p>Anyway, I just wanted to show you what I built since your blog post was the inspiration.</p>

<p>Thanks!
-keith
<a href="http://www.thepolypeptides.com" rel="nofollow">http://www.thepolypeptides.com</a></p>]]></content:encoded>
	</item>
</channel>
</rss>
