<?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: Why doesn&#8217;t Panel extend LayoutContainer?</title>
	<atom:link href="http://dougmccune.com/blog/2008/01/12/why-doesnt-panel-extend-layoutcontainer/feed/" rel="self" type="application/rss+xml" />
	<link>http://dougmccune.com/blog/2008/01/12/why-doesnt-panel-extend-layoutcontainer/</link>
	<description>A blog about Adobe Flex</description>
	<lastBuildDate>Sat, 13 Mar 2010 11:45:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rick Winscot</title>
		<link>http://dougmccune.com/blog/2008/01/12/why-doesnt-panel-extend-layoutcontainer/comment-page-1/#comment-57825</link>
		<dc:creator>Rick Winscot</dc:creator>
		<pubDate>Wed, 20 Feb 2008 21:30:19 +0000</pubDate>
		<guid isPermaLink="false">http://dougmccune.com/blog/2008/01/12/why-doesnt-panel-extend-layoutcontainer/#comment-57825</guid>
		<description>Inheritance would be easy... but in the end your subclasses would become heavily dependent on the parent implementation. This shouldn&#039;t be a problem as long as you understand the implications and you are fine with it. Deep object hierarchies can and usually do become a problem. Before you say yes to inheritance you should consider composition (which is what they are doing). The duplication buys you improved encapsulation/compartmentalization and can insulate your application from or ease the pains of refactoring when parent implementations change. Just a thought. Peace.</description>
		<content:encoded><![CDATA[<p>Inheritance would be easy&#8230; but in the end your subclasses would become heavily dependent on the parent implementation. This shouldn&#8217;t be a problem as long as you understand the implications and you are fine with it. Deep object hierarchies can and usually do become a problem. Before you say yes to inheritance you should consider composition (which is what they are doing). The duplication buys you improved encapsulation/compartmentalization and can insulate your application from or ease the pains of refactoring when parent implementations change. Just a thought. Peace.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boubalou</title>
		<link>http://dougmccune.com/blog/2008/01/12/why-doesnt-panel-extend-layoutcontainer/comment-page-1/#comment-44817</link>
		<dc:creator>Boubalou</dc:creator>
		<pubDate>Mon, 14 Jan 2008 15:41:52 +0000</pubDate>
		<guid isPermaLink="false">http://dougmccune.com/blog/2008/01/12/why-doesnt-panel-extend-layoutcontainer/#comment-44817</guid>
		<description>The response from Flex should be:

&quot;Because we can.&quot;

;)</description>
		<content:encoded><![CDATA[<p>The response from Flex should be:</p>
<p>&#8220;Because we can.&#8221;</p>
<p> <img src='http://dougmccune.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
