<?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: Ajax Head Pattern; Unobtrusive Rails Apps</title>
	<atom:link href="http://ajaxian.com/archives/ajax-head-pattern-unobtrusive-rails-apps/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/ajax-head-pattern-unobtrusive-rails-apps</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: dkubb</title>
		<link>http://ajaxian.com/archives/ajax-head-pattern-unobtrusive-rails-apps/comment-page-1#comment-266879</link>
		<dc:creator>dkubb</dc:creator>
		<pubDate>Sun, 24 Aug 2008 22:55:51 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=4157#comment-266879</guid>
		<description>I think its great that people are starting to come to the realization that there are better ways than RJS.  One of the reasons that RJS fails is that you have to write the server side logic twice: once for JS enabled browsers, and once for everything else, including REST API clients and non-JS browsers.

I&#039;ve taken a similar approach to this on several projects, but I used Jester (http://jesterjs.org) and LowPro to add the JS logic unobtrusively.  First I coded up the plain HTML interface and got everything working for non-JS enabled browsers.  Then I updated the controllers to accept/render XML and JSON and made sure the RESTful API was solid.  Finally I used LowPro and Jester to unobtrusively add the JS logic to the existing HTML, complete with AJAX controls and other niceties.  All JS enabled browsers became just another consumer of the existing RESTful API.

In the end this worked out quite well, and resulted in a nice separation of behavior, presentation and content.</description>
		<content:encoded><![CDATA[<p>I think its great that people are starting to come to the realization that there are better ways than RJS.  One of the reasons that RJS fails is that you have to write the server side logic twice: once for JS enabled browsers, and once for everything else, including REST API clients and non-JS browsers.</p>
<p>I&#8217;ve taken a similar approach to this on several projects, but I used Jester (<a href="http://jesterjs.org" rel="nofollow">http://jesterjs.org</a>) and LowPro to add the JS logic unobtrusively.  First I coded up the plain HTML interface and got everything working for non-JS enabled browsers.  Then I updated the controllers to accept/render XML and JSON and made sure the RESTful API was solid.  Finally I used LowPro and Jester to unobtrusively add the JS logic to the existing HTML, complete with AJAX controls and other niceties.  All JS enabled browsers became just another consumer of the existing RESTful API.</p>
<p>In the end this worked out quite well, and resulted in a nice separation of behavior, presentation and content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Schorsch</title>
		<link>http://ajaxian.com/archives/ajax-head-pattern-unobtrusive-rails-apps/comment-page-1#comment-266832</link>
		<dc:creator>Schorsch</dc:creator>
		<pubDate>Thu, 21 Aug 2008 22:49:43 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=4157#comment-266832</guid>
		<description>way to go ... any inline js and rjs really sucks. Im working with jquery and  jamalMVC to achive such lovely unubstrusiveness. This keeps every portion of your code so clean be it js , ruby, html, css</description>
		<content:encoded><![CDATA[<p>way to go &#8230; any inline js and rjs really sucks. Im working with jquery and  jamalMVC to achive such lovely unubstrusiveness. This keeps every portion of your code so clean be it js , ruby, html, css</p>
]]></content:encoded>
	</item>
</channel>
</rss>

