<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Merb CRUD - ie: how to properly destroy things</title>
	<link>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/</link>
	<description>web development and stuff</description>
	<pubDate>Wed, 19 Nov 2008 15:18:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Adam Christensen</title>
		<link>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-40</link>
		<author>Adam Christensen</author>
		<pubDate>Wed, 13 Aug 2008 12:53:29 +0000</pubDate>
		<guid>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-40</guid>
		<description>Man...glad you posted that.  I know you told this to me once, but it didn't hit me that I needed to create the delete action to serve up my destroy page until I wanted the better delete solution.</description>
		<content:encoded><![CDATA[<p>Man&#8230;glad you posted that.  I know you told this to me once, but it didn&#8217;t hit me that I needed to create the delete action to serve up my destroy page until I wanted the better delete solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jarrod</title>
		<link>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-32</link>
		<author>Jarrod</author>
		<pubDate>Thu, 17 Jul 2008 17:33:37 +0000</pubDate>
		<guid>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-32</guid>
		<description>Ah... yes... in fact I do exactly the same thing as far as unobtrusively binding to the anchor. I tend use an ajax call in place of injecting a form into the DOM though (since i already have a fallback page in place I can fully lean on javascript and avoid having to refresh the entire page). I didn't go into great detail on that part of the implementation simply because I felt it was outside the scope of the article. Thanks for the comments guys!</description>
		<content:encoded><![CDATA[<p>Ah&#8230; yes&#8230; in fact I do exactly the same thing as far as unobtrusively binding to the anchor. I tend use an ajax call in place of injecting a form into the DOM though (since i already have a fallback page in place I can fully lean on javascript and avoid having to refresh the entire page). I didn&#8217;t go into great detail on that part of the implementation simply because I felt it was outside the scope of the article. Thanks for the comments guys!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean McCleary</title>
		<link>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-31</link>
		<author>Sean McCleary</author>
		<pubDate>Thu, 17 Jul 2008 16:26:34 +0000</pubDate>
		<guid>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-31</guid>
		<description>I prefer to have delete links to have a delete class that an unobtrusive javascript binds on dom:loaded.  The delete links have the URL, but the binding onclick grabs the link and creates a confirmation and form to post a restful delete.  I realize that this technique does not have a fall back for those without javascript enabled.  However, I do believe that this deletion confirmation page that Merb creates would be a perfect fall back in the event that users did not have javascript enabled.

Our techniques are fairly similar, and I will more than likely start adding an interim confirmation page for the non-javascript enabled.  The biggest need for having a non-javascript option is accessibility issues with screen readers.  For projects, I try to find out from the client if they are willing to pay for me to include development for non-javascript enabled browsers.</description>
		<content:encoded><![CDATA[<p>I prefer to have delete links to have a delete class that an unobtrusive javascript binds on dom:loaded.  The delete links have the URL, but the binding onclick grabs the link and creates a confirmation and form to post a restful delete.  I realize that this technique does not have a fall back for those without javascript enabled.  However, I do believe that this deletion confirmation page that Merb creates would be a perfect fall back in the event that users did not have javascript enabled.</p>
<p>Our techniques are fairly similar, and I will more than likely start adding an interim confirmation page for the non-javascript enabled.  The biggest need for having a non-javascript option is accessibility issues with screen readers.  For projects, I try to find out from the client if they are willing to pay for me to include development for non-javascript enabled browsers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jarrod</title>
		<link>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-30</link>
		<author>Jarrod</author>
		<pubDate>Thu, 17 Jul 2008 05:20:27 +0000</pubDate>
		<guid>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-30</guid>
		<description>&lt;p&gt;Sean I am not sure I follow you... what is your preferred solution for providing UI that results in the destruction of a record? And which framework are you talking about - Rails or Merb?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Sean I am not sure I follow you&#8230; what is your preferred solution for providing UI that results in the destruction of a record? And which framework are you talking about - Rails or Merb?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cameron Senior</title>
		<link>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-29</link>
		<author>Cameron Senior</author>
		<pubDate>Thu, 17 Jul 2008 01:25:07 +0000</pubDate>
		<guid>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-29</guid>
		<description>+1 on what Sean was saying.  

I agree whole heartedly with that. Plus the ease with which you can modify/override the delete action unobtrusively with Jquery etc makes it a no brainer in my book.</description>
		<content:encoded><![CDATA[<p>+1 on what Sean was saying.  </p>
<p>I agree whole heartedly with that. Plus the ease with which you can modify/override the delete action unobtrusively with Jquery etc makes it a no brainer in my book.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean McCleary</title>
		<link>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-28</link>
		<author>Sean McCleary</author>
		<pubDate>Wed, 16 Jul 2008 23:54:49 +0000</pubDate>
		<guid>http://jarrodspillers.com/articles/merb-crud-ie-how-to-properly-destroy-things/#comment-28</guid>
		<description>I like the idea of graceful degradation.  If you are committed to making your entire app designed to be fully functional without javascript and you happen to have some extra time and determination to be sure everything degrades gracefully then go for it.  For me, graceful degradation means one of three things: more work, limited coolness in UI, or both.  

My main problem with the inline javascript approach is that it is obtrusive.  I don't like to pollute my HTML with inline script especially when that script is rendered repeatedly by a loop.  Yuck.</description>
		<content:encoded><![CDATA[<p>I like the idea of graceful degradation.  If you are committed to making your entire app designed to be fully functional without javascript and you happen to have some extra time and determination to be sure everything degrades gracefully then go for it.  For me, graceful degradation means one of three things: more work, limited coolness in UI, or both.  </p>
<p>My main problem with the inline javascript approach is that it is obtrusive.  I don&#8217;t like to pollute my HTML with inline script especially when that script is rendered repeatedly by a loop.  Yuck.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
