<?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: Enabling And Disabling A Button With Backbone.ModelBinding</title>
	<atom:link href="http://lostechies.com/derickbailey/2011/08/14/enabling-and-disabling-a-button-with-backbone-modelbinding/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/derickbailey/2011/08/14/enabling-and-disabling-a-button-with-backbone-modelbinding/</link>
	<description>Better Than Yesterday</description>
	<lastBuildDate>Mon, 20 May 2013 03:36:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Derick Bailey</title>
		<link>http://lostechies.com/derickbailey/2011/08/14/enabling-and-disabling-a-button-with-backbone-modelbinding/#comment-1849</link>
		<dc:creator>Derick Bailey</dc:creator>
		<pubDate>Mon, 03 Oct 2011 13:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/derickbailey/?p=523#comment-1849</guid>
		<description>there are definitely times when it should be the view&#039;s responsibility to update things and change how it looks. i&#039;m not sure i see a need to decouple the view object from the manipulation of the html, but maybe i&#039;m not thinking about the code the same way you are. can you provide an example of what you mean?

... also - would you mind posting this as an issue on github? it will be easier to deal with code examples, lengthy discussion (if needed), etc. over there: http://github.com/derickbailey/backbone.modelbinding/issues

thanks!</description>
		<content:encoded><![CDATA[<p>there are definitely times when it should be the view&#8217;s responsibility to update things and change how it looks. i&#8217;m not sure i see a need to decouple the view object from the manipulation of the html, but maybe i&#8217;m not thinking about the code the same way you are. can you provide an example of what you mean?</p>
<p>&#8230; also &#8211; would you mind posting this as an issue on github? it will be easier to deal with code examples, lengthy discussion (if needed), etc. over there: <a href="http://github.com/derickbailey/backbone.modelbinding/issues" rel="nofollow">http://github.com/derickbailey/backbone.modelbinding/issues</a></p>
<p>thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Strong</title>
		<link>http://lostechies.com/derickbailey/2011/08/14/enabling-and-disabling-a-button-with-backbone-modelbinding/#comment-1842</link>
		<dc:creator>Steve Strong</dc:creator>
		<pubDate>Fri, 30 Sep 2011 19:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/derickbailey/?p=523#comment-1842</guid>
		<description>Just started using Backbone.ModelBinding, and I&#039;m finding it very useful - thanks!  Quick question concerning the data-binding attributes for things like &quot;displayed&quot; - currently, these bind to the model which makes things easy since backbone is generating suitable change requests.  For some scenarios (such as your isValid example), this is just fine. 

However, I&#039;ve got screens where the decisioning as to whether some things should be displayed or not seems to be more of a view concern rather than a model concern, and adding properties to the model seems incorrect.  What do you think to a) the idea and b) the practicalities of being able to hook these types of data-bind attributes to view-generated events rather than the model directly?

Cheers,

Steve</description>
		<content:encoded><![CDATA[<p>Just started using Backbone.ModelBinding, and I&#8217;m finding it very useful &#8211; thanks!  Quick question concerning the data-binding attributes for things like &#8220;displayed&#8221; &#8211; currently, these bind to the model which makes things easy since backbone is generating suitable change requests.  For some scenarios (such as your isValid example), this is just fine. </p>
<p>However, I&#8217;ve got screens where the decisioning as to whether some things should be displayed or not seems to be more of a view concern rather than a model concern, and adding properties to the model seems incorrect.  What do you think to a) the idea and b) the practicalities of being able to hook these types of data-bind attributes to view-generated events rather than the model directly?</p>
<p>Cheers,</p>
<p>Steve</p>
]]></content:encoded>
	</item>
</channel>
</rss>
