<?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: Integrating Design Drafts Into Your Rails App</title>
	<atom:link href="http://www.pathf.com/blogs/2008/08/integrating-design-drafts-into-your-rails-app/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2008/08/integrating-design-drafts-into-your-rails-app/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Fri, 05 Dec 2008 07:42:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Pathfinder Development &#187; What makes a good requirement document for an agile project</title>
		<link>http://www.pathf.com/blogs/2008/08/integrating-design-drafts-into-your-rails-app/#comment-4049</link>
		<dc:creator>Pathfinder Development &#187; What makes a good requirement document for an agile project</dc:creator>
		<pubDate>Thu, 06 Nov 2008 19:22:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1080#comment-4049</guid>
		<description>[...] Alice's post about wireframes, and Noel's post about how you can allow a designer to write the HTML within a rails [...]</description>
		<content:encoded><![CDATA[<p>[...] Alice&#8217;s post about wireframes, and Noel&#8217;s post about how you can allow a designer to write the HTML within a rails [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pathfinder Development &#187; A Look Back At Past Posts</title>
		<link>http://www.pathf.com/blogs/2008/08/integrating-design-drafts-into-your-rails-app/#comment-3507</link>
		<dc:creator>Pathfinder Development &#187; A Look Back At Past Posts</dc:creator>
		<pubDate>Fri, 03 Oct 2008 17:02:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1080#comment-3507</guid>
		<description>[...] project that included integrated design drafts, named-scope based reporting, and aggressive markup in the helpers had it's post-mortem this week. [...]</description>
		<content:encoded><![CDATA[<p>[...] project that included integrated design drafts, named-scope based reporting, and aggressive markup in the helpers had it&#8217;s post-mortem this week. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Łukasz Adamczak</title>
		<link>http://www.pathf.com/blogs/2008/08/integrating-design-drafts-into-your-rails-app/#comment-2969</link>
		<dc:creator>Łukasz Adamczak</dc:creator>
		<pubDate>Tue, 12 Aug 2008 11:07:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1080#comment-2969</guid>
		<description>Thanks for the idea!
The routes.rb solution didn't work for me (nested controllers).

You can even simplify it - render the template directly from the before_filter - it will halt the filter chain.

And you can use params[:format] to extract the format.</description>
		<content:encoded><![CDATA[<p>Thanks for the idea!<br />
The routes.rb solution didn&#8217;t work for me (nested controllers).</p>
<p>You can even simplify it - render the template directly from the before_filter - it will halt the filter chain.</p>
<p>And you can use params[:format] to extract the format.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noel Rappin</title>
		<link>http://www.pathf.com/blogs/2008/08/integrating-design-drafts-into-your-rails-app/#comment-2741</link>
		<dc:creator>Noel Rappin</dc:creator>
		<pubDate>Sun, 03 Aug 2008 16:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1080#comment-2741</guid>
		<description>1. You probably could do most or all of this with a route, but I find that hard to debug when things go wrong.

2. Yes, that's very similar -- I wanted to be able to manage my solution without having to touch any respond_to block in the code, but I like the way yours looks too.

Noel</description>
		<content:encoded><![CDATA[<p>1. You probably could do most or all of this with a route, but I find that hard to debug when things go wrong.</p>
<p>2. Yes, that&#8217;s very similar &#8212; I wanted to be able to manage my solution without having to touch any respond_to block in the code, but I like the way yours looks too.</p>
<p>Noel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Mathers</title>
		<link>http://www.pathf.com/blogs/2008/08/integrating-design-drafts-into-your-rails-app/#comment-2730</link>
		<dc:creator>David Mathers</dc:creator>
		<pubDate>Sat, 02 Aug 2008 09:54:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1080#comment-2730</guid>
		<description>Similar thoughts?

http://locomotivation.com/2008/06/28/redesign-your-site-in-place-using-rails-custom-mime-types</description>
		<content:encoded><![CDATA[<p>Similar thoughts?</p>
<p><a href="http://locomotivation.com/2008/06/28/redesign-your-site-in-place-using-rails-custom-mime-types" rel="nofollow">http://locomotivation.com/2008/06/28/redesign-your-site-in-place-using-rails-custom-mime-types</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Amiri</title>
		<link>http://www.pathf.com/blogs/2008/08/integrating-design-drafts-into-your-rails-app/#comment-2728</link>
		<dc:creator>Andy Amiri</dc:creator>
		<pubDate>Fri, 01 Aug 2008 21:06:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1080#comment-2728</guid>
		<description>I'm probably missing something but couldn't you just use a route namespace to accomplish the same thing? Maybe that doesn't give you enough control?</description>
		<content:encoded><![CDATA[<p>I&#8217;m probably missing something but couldn&#8217;t you just use a route namespace to accomplish the same thing? Maybe that doesn&#8217;t give you enough control?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
