<?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: Overriding core UIComponent Methods</title>
	<atom:link href="http://codeofdoom.com/wordpress/2009/02/19/override-core-uicomponent-methods/feed/" rel="self" type="application/rss+xml" />
	<link>http://codeofdoom.com/wordpress/2009/02/19/override-core-uicomponent-methods/</link>
	<description></description>
	<lastBuildDate>Sun, 29 Jan 2012 03:53:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Josh Tynjala</title>
		<link>http://codeofdoom.com/wordpress/2009/02/19/override-core-uicomponent-methods/comment-page-1/#comment-141</link>
		<dc:creator>Josh Tynjala</dc:creator>
		<pubDate>Tue, 17 Mar 2009 21:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://codeofdoom.com/wordpress/?p=179#comment-141</guid>
		<description>Calling addChild() in commitProperties() is quite common when the children are created based on the properties that are passed to the component. For instance, anything with item renderers must create its children in commitProperties() or maybe even updateDisplayList() because you probably won&#039;t know how many children you need until you have some data or even the dimensions of the component. I wouldn&#039;t say this is too strange. Obviously, if a specific number of children need to exist throughout the entire life of the component, then yes, absolutely, create them in createChildren().</description>
		<content:encoded><![CDATA[<p>Calling addChild() in commitProperties() is quite common when the children are created based on the properties that are passed to the component. For instance, anything with item renderers must create its children in commitProperties() or maybe even updateDisplayList() because you probably won&#8217;t know how many children you need until you have some data or even the dimensions of the component. I wouldn&#8217;t say this is too strange. Obviously, if a specific number of children need to exist throughout the entire life of the component, then yes, absolutely, create them in createChildren().</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carsten Schlipf</title>
		<link>http://codeofdoom.com/wordpress/2009/02/19/override-core-uicomponent-methods/comment-page-1/#comment-59</link>
		<dc:creator>Carsten Schlipf</dc:creator>
		<pubDate>Fri, 20 Feb 2009 19:55:45 +0000</pubDate>
		<guid isPermaLink="false">http://codeofdoom.com/wordpress/?p=179#comment-59</guid>
		<description>Great article! Thank you very much.</description>
		<content:encoded><![CDATA[<p>Great article! Thank you very much.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

