<?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: Yaclml in pictures, part II: Templating</title>
	<atom:link href="http://www.3ofcoins.net/2010/01/21/yaclml-in-pictures-part-ii-templating/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.3ofcoins.net/2010/01/21/yaclml-in-pictures-part-ii-templating/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 02 Sep 2010 16:54:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Felipe D.</title>
		<link>http://www.3ofcoins.net/2010/01/21/yaclml-in-pictures-part-ii-templating/comment-page-1/#comment-8806</link>
		<dc:creator>Felipe D.</dc:creator>
		<pubDate>Wed, 27 Jan 2010 15:49:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.3ofcoins.net/?p=94#comment-8806</guid>
		<description>Thanks for posting this!  I had no idea how to even approach TAL since the wiki page was pretty hard to follow but now it makes sense.

This certainly opens up a few more possibilities for creating web apps with (or without) UCW.</description>
		<content:encoded><![CDATA[<p>Thanks for posting this!  I had no idea how to even approach TAL since the wiki page was pretty hard to follow but now it makes sense.</p>
<p>This certainly opens up a few more possibilities for creating web apps with (or without) UCW.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward Tate</title>
		<link>http://www.3ofcoins.net/2010/01/21/yaclml-in-pictures-part-ii-templating/comment-page-1/#comment-8648</link>
		<dc:creator>Edward Tate</dc:creator>
		<pubDate>Fri, 22 Jan 2010 07:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.3ofcoins.net/?p=94#comment-8648</guid>
		<description>Wow, let me just say thank you for this tutorial!!! I wasn&#039;t using tal templates before today as I couldn&#039;t find any documentation on the subject and now here you are, the angel comes. :)</description>
		<content:encoded><![CDATA[<p>Wow, let me just say thank you for this tutorial!!! I wasn&#8217;t using tal templates before today as I couldn&#8217;t find any documentation on the subject and now here you are, the angel comes. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Three of Coins &#187; Blog Archive &#187; Yaclml in pictures, part I: HTML generation</title>
		<link>http://www.3ofcoins.net/2010/01/21/yaclml-in-pictures-part-ii-templating/comment-page-1/#comment-8629</link>
		<dc:creator>Three of Coins &#187; Blog Archive &#187; Yaclml in pictures, part I: HTML generation</dc:creator>
		<pubDate>Thu, 21 Jan 2010 14:02:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.3ofcoins.net/?p=94#comment-8629</guid>
		<description>[...] Could Yaclml HTML generation be better?  Sure thing.  It could step away from macros (at a performance penalty, though), and use functions, which would return and consume HTML fragments (or consume strings, or actually any Lisp values—including closures for lazy evaluation).  This would introduce first-class HTML fragment object, giving us sort of DOM and possibility of passing around and manipulating already generated HTML fragments, and wouldn&#8217;t requre the &lt;:AH and &lt;:AI helper macros (or actually would require only one of those).  That seems to be what core-server guys are doing with their DOM programming support.  I don&#8217;t use it yet, partly because I don&#8217;t need this kind of functionality and I&#8217;m more acquainted with Yaclml; partly because I don&#8217;t want to buy into core-server as a whole—core-server is a monolith and ripping DOM support out of it would require substantial amount of work—and partly because I use the second part of Yaclml, which I will describe in the following article: HTML and XML templating. [...]</description>
		<content:encoded><![CDATA[<p>[...] Could Yaclml HTML generation be better?  Sure thing.  It could step away from macros (at a performance penalty, though), and use functions, which would return and consume HTML fragments (or consume strings, or actually any Lisp values—including closures for lazy evaluation).  This would introduce first-class HTML fragment object, giving us sort of DOM and possibility of passing around and manipulating already generated HTML fragments, and wouldn&#8217;t requre the &lt;:AH and &lt;:AI helper macros (or actually would require only one of those).  That seems to be what core-server guys are doing with their DOM programming support.  I don&#8217;t use it yet, partly because I don&#8217;t need this kind of functionality and I&#8217;m more acquainted with Yaclml; partly because I don&#8217;t want to buy into core-server as a whole—core-server is a monolith and ripping DOM support out of it would require substantial amount of work—and partly because I use the second part of Yaclml, which I will describe in the following article: HTML and XML templating. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
