<?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: Filters 0.1 Released</title>
	<atom:link href="http://www.thesamet.com/blog/2006/12/07/filters-01-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thesamet.com/blog/2006/12/07/filters-01-released/</link>
	<description>The Ramblings of a Freelance Software Developer</description>
	<pubDate>Sun, 06 Jul 2008 02:19:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Ben Bangert</title>
		<link>http://www.thesamet.com/blog/2006/12/07/filters-01-released/#comment-973</link>
		<dc:creator>Ben Bangert</dc:creator>
		<pubDate>Thu, 21 Dec 2006 00:20:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesamet.com/blog/2006/12/07/filters-01-released/#comment-973</guid>
		<description>Myghty has had filters since its inception as well, which essentially just need to take an argument and return. The function style for a filter seems universal enough that there's little reason I can see for filters to be bound to a specific template language.

Of course, I'm somewhat curious when one would decide that something should be used as a filter vs a normal function call. In Django for example, they *have* to use filters for a lot of those since they can't just call Python functions (the template language won't allow normal function calls).

So what they would have to write as {{ file_size &#124; tg.filesizeformat() }} you could write in Kid as ${ tg.filesizeformat(file_size)}. If you have something you need to format 3 times, it definitely makes more sense to use a filter style than wrapping all those functions. Maybe someone else has some good set of guidelines for when you'd use one instead of the other?</description>
		<content:encoded><![CDATA[<p>Myghty has had filters since its inception as well, which essentially just need to take an argument and return. The function style for a filter seems universal enough that there&#8217;s little reason I can see for filters to be bound to a specific template language.</p>
<p>Of course, I&#8217;m somewhat curious when one would decide that something should be used as a filter vs a normal function call. In Django for example, they *have* to use filters for a lot of those since they can&#8217;t just call Python functions (the template language won&#8217;t allow normal function calls).</p>
<p>So what they would have to write as {{ file_size | tg.filesizeformat() }} you could write in Kid as ${ tg.filesizeformat(file_size)}. If you have something you need to format 3 times, it definitely makes more sense to use a filter style than wrapping all those functions. Maybe someone else has some good set of guidelines for when you&#8217;d use one instead of the other?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Italo Maia</title>
		<link>http://www.thesamet.com/blog/2006/12/07/filters-01-released/#comment-957</link>
		<dc:creator>Italo Maia</dc:creator>
		<pubDate>Sun, 10 Dec 2006 21:37:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesamet.com/blog/2006/12/07/filters-01-released/#comment-957</guid>
		<description>Adorei!

Loved!</description>
		<content:encoded><![CDATA[<p>Adorei!</p>
<p>Loved!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thesamet</title>
		<link>http://www.thesamet.com/blog/2006/12/07/filters-01-released/#comment-952</link>
		<dc:creator>thesamet</dc:creator>
		<pubDate>Thu, 07 Dec 2006 13:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesamet.com/blog/2006/12/07/filters-01-released/#comment-952</guid>
		<description>Alastir, you could be right. It makes sense to add a convenience decorator that does both.</description>
		<content:encoded><![CDATA[<p>Alastir, you could be right. It makes sense to add a convenience decorator that does both.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alastair</title>
		<link>http://www.thesamet.com/blog/2006/12/07/filters-01-released/#comment-951</link>
		<dc:creator>alastair</dc:creator>
		<pubDate>Thu, 07 Dec 2006 13:17:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesamet.com/blog/2006/12/07/filters-01-released/#comment-951</guid>
		<description>Why have two decorators rather than one? Aren't we always going to write both of them?

Put another way, is there a use for writing just one of the decorators and not the other?</description>
		<content:encoded><![CDATA[<p>Why have two decorators rather than one? Aren&#8217;t we always going to write both of them?</p>
<p>Put another way, is there a use for writing just one of the decorators and not the other?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Django-like filters for Kid (and Genshi) &#124; Nadav Samet&#8217;s Blog</title>
		<link>http://www.thesamet.com/blog/2006/12/07/filters-01-released/#comment-950</link>
		<dc:creator>Django-like filters for Kid (and Genshi) &#124; Nadav Samet&#8217;s Blog</dc:creator>
		<pubDate>Thu, 07 Dec 2006 09:22:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesamet.com/blog/2006/12/07/filters-01-released/#comment-950</guid>
		<description></description>
		<content:encoded><![CDATA[<br />
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.249 seconds -->
<!-- Cached page served by WP-Cache -->
