<?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: Integrating Knockout and jQueryMobile</title>
	<atom:link href="http://www.scottlogic.co.uk/blog/colin/2012/10/integrating-knockout-and-jquerymobile/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.scottlogic.co.uk/blog/colin/2012/10/integrating-knockout-and-jquerymobile/</link>
	<description>Colin Eberhardt&#039;s Technology Adventures</description>
	<lastBuildDate>Fri, 17 May 2013 09:50:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Juan Mendez</title>
		<link>http://www.scottlogic.co.uk/blog/colin/2012/10/integrating-knockout-and-jquerymobile/#comment-127056</link>
		<dc:creator>Juan Mendez</dc:creator>
		<pubDate>Fri, 12 Apr 2013 20:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottlogic.co.uk/blog/colin/?p=2293#comment-127056</guid>
		<description><![CDATA[i haven&#039;t applied KO to JQM yet. This is a good introduction and you point it out in some cases binding to an element such as a button can be a little bit trivial. Interesting how you used instead a viewmodel per page. I see how they are global and you intereact between each other when its time to move to another page, and target its viewmodel before navigating to the page. I first thought if the viewmodel can remain a single one, and tailoring binding handlers which update to the page which is only visible. I also wonder if KO is a little bit too much and if its best to use an observer pattern for changes made. Don&#039;t get me wrong, i love KnockoutJS, but seems like for these projects is a little bit complicated.]]></description>
		<content:encoded><![CDATA[<p>i haven&#8217;t applied KO to JQM yet. This is a good introduction and you point it out in some cases binding to an element such as a button can be a little bit trivial. Interesting how you used instead a viewmodel per page. I see how they are global and you intereact between each other when its time to move to another page, and target its viewmodel before navigating to the page. I first thought if the viewmodel can remain a single one, and tailoring binding handlers which update to the page which is only visible. I also wonder if KO is a little bit too much and if its best to use an observer pattern for changes made. Don&#8217;t get me wrong, i love KnockoutJS, but seems like for these projects is a little bit complicated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dew Drop &#8211; October 24, 2012 (#1,428) &#124; Alvin Ashcraft&#039;s Morning Dew</title>
		<link>http://www.scottlogic.co.uk/blog/colin/2012/10/integrating-knockout-and-jquerymobile/#comment-111578</link>
		<dc:creator>Dew Drop &#8211; October 24, 2012 (#1,428) &#124; Alvin Ashcraft&#039;s Morning Dew</dc:creator>
		<pubDate>Wed, 24 Oct 2012 12:46:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottlogic.co.uk/blog/colin/?p=2293#comment-111578</guid>
		<description><![CDATA[[...] Integrating Knockout and jQueryMobile (Colin Eberhardt) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Integrating Knockout and jQueryMobile (Colin Eberhardt) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
