<?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 for Mitchell Simoens&#039; Blog</title>
	<atom:link href="http://mitchellsimoens.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://mitchellsimoens.com</link>
	<description>Blog about Ext JS and Sencha among other things!</description>
	<lastBuildDate>Fri, 10 May 2013 14:44:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Ext.define and listeners as a property&#8230; bad! by Mitchell Simoens</title>
		<link>http://mitchellsimoens.com/2011/12/ext-js-4/ext-define-and-listeners-as-a-property-bad/#comment-2446</link>
		<dc:creator>Mitchell Simoens</dc:creator>
		<pubDate>Fri, 10 May 2013 14:44:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.mitchellsimoens.com/?p=59#comment-2446</guid>
		<description><![CDATA[Using on() will also get cleaned up on component destruction (this wasn&#039;t true in older versions). I use mon when I need to listen to an event on something like an element.]]></description>
		<content:encoded><![CDATA[<p>Using on() will also get cleaned up on component destruction (this wasn&#8217;t true in older versions). I use mon when I need to listen to an event on something like an element.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Breakpoint a lost art? by Jones sabo for example sabo declared a</title>
		<link>http://mitchellsimoens.com/2012/09/javascript/breakpoint-a-lost-art/#comment-2445</link>
		<dc:creator>Jones sabo for example sabo declared a</dc:creator>
		<pubDate>Mon, 29 Apr 2013 17:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://mitchellsimoens.com/?p=178#comment-2445</guid>
		<description><![CDATA[Maybe you can write next articles referring to this article. I wish to read more things about it! Nice post. I was checking continuously this blog and I&#039;m impressed! Very helpful info specifically the last part :)]]></description>
		<content:encoded><![CDATA[<p>Maybe you can write next articles referring to this article. I wish to read more things about it! Nice post. I was checking continuously this blog and I&#8217;m impressed! Very helpful info specifically the last part <img src='http://mitchellsimoens.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ext.define and listeners as a property&#8230; bad! by stewardsencha</title>
		<link>http://mitchellsimoens.com/2011/12/ext-js-4/ext-define-and-listeners-as-a-property-bad/#comment-2444</link>
		<dc:creator>stewardsencha</dc:creator>
		<pubDate>Mon, 29 Apr 2013 00:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.mitchellsimoens.com/?p=59#comment-2444</guid>
		<description><![CDATA[Very helpful thank you Mitchell.

My understanding is that if we use mon, then we are not required to un (or free or destroy), ie we could drop the beforeDestroy logic. So why would you choose to write the on/un pair instead of a single mon in construction?

My guess is that if I knew more about managed listeners I would be able to invent something that fit the &quot;depends on what you want to do&quot; bill.

This stuff goes on forever. Your blogs help a lot.]]></description>
		<content:encoded><![CDATA[<p>Very helpful thank you Mitchell.</p>
<p>My understanding is that if we use mon, then we are not required to un (or free or destroy), ie we could drop the beforeDestroy logic. So why would you choose to write the on/un pair instead of a single mon in construction?</p>
<p>My guess is that if I knew more about managed listeners I would be able to invent something that fit the &#8220;depends on what you want to do&#8221; bill.</p>
<p>This stuff goes on forever. Your blogs help a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Client side associations by Mitchell Simoens</title>
		<link>http://mitchellsimoens.com/2013/03/ext-js-4/client-side-associations/#comment-2441</link>
		<dc:creator>Mitchell Simoens</dc:creator>
		<pubDate>Wed, 10 Apr 2013 13:17:37 +0000</pubDate>
		<guid isPermaLink="false">http://mitchellsimoens.com/?p=220#comment-2441</guid>
		<description><![CDATA[This blog post was created in my extjs category. Porting it to Sencha Touch 2 should be pretty similar but I have not looked at this yet.]]></description>
		<content:encoded><![CDATA[<p>This blog post was created in my extjs category. Porting it to Sencha Touch 2 should be pretty similar but I have not looked at this yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Client side associations by Greg M. Silverman</title>
		<link>http://mitchellsimoens.com/2013/03/ext-js-4/client-side-associations/#comment-904</link>
		<dc:creator>Greg M. Silverman</dc:creator>
		<pubDate>Thu, 28 Mar 2013 02:46:28 +0000</pubDate>
		<guid isPermaLink="false">http://mitchellsimoens.com/?p=220#comment-904</guid>
		<description><![CDATA[Hi Mitchell,
I saw this blog post and got all excited, especially since I am having this exact issue with associated models. However, my excitement soon turned to disappointment when I realized that the loadRawData method is NOT available in ST 2.1.1 ... any suggestions on a solution to this problem for this platform? 

Danke Schoen!

Greg--]]></description>
		<content:encoded><![CDATA[<p>Hi Mitchell,<br />
I saw this blog post and got all excited, especially since I am having this exact issue with associated models. However, my excitement soon turned to disappointment when I realized that the loadRawData method is NOT available in ST 2.1.1 &#8230; any suggestions on a solution to this problem for this platform? </p>
<p>Danke Schoen!</p>
<p>Greg&#8211;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Client side associations by Neil</title>
		<link>http://mitchellsimoens.com/2013/03/ext-js-4/client-side-associations/#comment-505</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Wed, 13 Mar 2013 09:38:21 +0000</pubDate>
		<guid isPermaLink="false">http://mitchellsimoens.com/?p=220#comment-505</guid>
		<description><![CDATA[Ah - I see the issue (i think). Cheers!
I was thinking about the idea of having two stores - one for AddressBooks, and one for Contacts, with some way of linking the two... much like you would design a DB with two tables. If you wanted the app to also store the make, model and colour of the car(s) each contact owned, then this would add another dimension (so another table in the DB analogy). I&#039;m just trying to figure out best-practice way of handling these kind of multi-dimensional datasets in Sencha (i&#039;m using Touch, but I guess the same applies to EXT JS).]]></description>
		<content:encoded><![CDATA[<p>Ah &#8211; I see the issue (i think). Cheers!<br />
I was thinking about the idea of having two stores &#8211; one for AddressBooks, and one for Contacts, with some way of linking the two&#8230; much like you would design a DB with two tables. If you wanted the app to also store the make, model and colour of the car(s) each contact owned, then this would add another dimension (so another table in the DB analogy). I&#8217;m just trying to figure out best-practice way of handling these kind of multi-dimensional datasets in Sencha (i&#8217;m using Touch, but I guess the same applies to EXT JS).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Client side associations by Mitchell Simoens</title>
		<link>http://mitchellsimoens.com/2013/03/ext-js-4/client-side-associations/#comment-499</link>
		<dc:creator>Mitchell Simoens</dc:creator>
		<pubDate>Tue, 12 Mar 2013 20:52:41 +0000</pubDate>
		<guid isPermaLink="false">http://mitchellsimoens.com/?p=220#comment-499</guid>
		<description><![CDATA[If you are worried about response size, then you can not return the associated data and when you execute the getter for the association then it will load the data on the fly (for that one record not all).]]></description>
		<content:encoded><![CDATA[<p>If you are worried about response size, then you can not return the associated data and when you execute the getter for the association then it will load the data on the fly (for that one record not all).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lesson in the getElementConfig method and config object by Mitchell Simoens</title>
		<link>http://mitchellsimoens.com/2013/02/sencha-touch-2/lesson-in-the-getelementconfig-method-and-config-object/#comment-498</link>
		<dc:creator>Mitchell Simoens</dc:creator>
		<pubDate>Tue, 12 Mar 2013 20:51:34 +0000</pubDate>
		<guid isPermaLink="false">http://mitchellsimoens.com/?p=198#comment-498</guid>
		<description><![CDATA[Sencha Touch 2 uses these methods throughout the framework and would take much effort to change. I would think it would be quite safe to use them.]]></description>
		<content:encoded><![CDATA[<p>Sencha Touch 2 uses these methods throughout the framework and would take much effort to change. I would think it would be quite safe to use them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Client side associations by Neil</title>
		<link>http://mitchellsimoens.com/2013/03/ext-js-4/client-side-associations/#comment-497</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Tue, 12 Mar 2013 20:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://mitchellsimoens.com/?p=220#comment-497</guid>
		<description><![CDATA[Thanks for your great articles - I just discovered your blog ;-)
I&#039;m interested in your example of address book with associated users, as it&#039;s similar to something i&#039;m working on. 
In the JSON, every user has user ID 1 (Mitchell) in his address book. This means that the data for Mitchell is being duplicated for every instance it appears (whereas all we actually need is the ID in order to reference Mitchell&#039;s contact info.
Is there a more efficient way of doing this? I can see the JSON file growing unnecessarily large once a few of these associations are in place... especially if each contact has a lot of data]]></description>
		<content:encoded><![CDATA[<p>Thanks for your great articles &#8211; I just discovered your blog <img src='http://mitchellsimoens.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /><br />
I&#8217;m interested in your example of address book with associated users, as it&#8217;s similar to something i&#8217;m working on.<br />
In the JSON, every user has user ID 1 (Mitchell) in his address book. This means that the data for Mitchell is being duplicated for every instance it appears (whereas all we actually need is the ID in order to reference Mitchell&#8217;s contact info.<br />
Is there a more efficient way of doing this? I can see the JSON file growing unnecessarily large once a few of these associations are in place&#8230; especially if each contact has a lot of data</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lesson in the getElementConfig method and config object by Stephen</title>
		<link>http://mitchellsimoens.com/2013/02/sencha-touch-2/lesson-in-the-getelementconfig-method-and-config-object/#comment-486</link>
		<dc:creator>Stephen</dc:creator>
		<pubDate>Mon, 11 Mar 2013 17:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://mitchellsimoens.com/?p=198#comment-486</guid>
		<description><![CDATA[In the docs the getElementConfig and getTemplate methods are flagged as private - can we rely on them being there in the future?]]></description>
		<content:encoded><![CDATA[<p>In the docs the getElementConfig and getTemplate methods are flagged as private &#8211; can we rely on them being there in the future?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
