<?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"
	>
<channel>
	<title>Comments on: Custom Flex components: Providing default yet overridable behavior</title>
	<atom:link href="http://www.returnundefined.com/2007/09/custom-flex-components-providing-default-yet-overridable-behavior/feed" rel="self" type="application/rss+xml" />
	<link>http://www.returnundefined.com/2007/09/custom-flex-components-providing-default-yet-overridable-behavior</link>
	<description>Like my original design?</description>
	<pubDate>Sat, 22 Nov 2008 04:35:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: return undefined; &#187; flexmdi: Customizing default behaviors</title>
		<link>http://www.returnundefined.com/2007/09/custom-flex-components-providing-default-yet-overridable-behavior#comment-7306</link>
		<dc:creator>return undefined; &#187; flexmdi: Customizing default behaviors</dc:creator>
		<pubDate>Fri, 14 Sep 2007 14:31:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.returnundefined.com/2007/09/custom-flex-components-providing-default-yet-overridable-behavior/#comment-7306</guid>
		<description>[...] flexmdi handles a lot of the mundane tasks of an MDI interface for you: minimizing, maximizing, closing, etc. However, we also realize that the out of the box behavior will not always fit your exact needs. Consequently, one of our biggest architectural goals (and challenges) was how to provide enough default behavior that getting up and running was lightning fast while still allowing the fine grained control a truly useful project provides. I described the basic method we used in a previous post, but wanted to give an example more specific to flexmdi now that its live. [...]</description>
		<content:encoded><![CDATA[<p>[...] flexmdi handles a lot of the mundane tasks of an MDI interface for you: minimizing, maximizing, closing, etc. However, we also realize that the out of the box behavior will not always fit your exact needs. Consequently, one of our biggest architectural goals (and challenges) was how to provide enough default behavior that getting up and running was lightning fast while still allowing the fine grained control a truly useful project provides. I described the basic method we used in a previous post, but wanted to give an example more specific to flexmdi now that its live. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nwebb</title>
		<link>http://www.returnundefined.com/2007/09/custom-flex-components-providing-default-yet-overridable-behavior#comment-7146</link>
		<dc:creator>nwebb</dc:creator>
		<pubDate>Tue, 11 Sep 2007 19:13:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.returnundefined.com/2007/09/custom-flex-components-providing-default-yet-overridable-behavior/#comment-7146</guid>
		<description>Useful ... and a nice example. Thanks :)</description>
		<content:encoded><![CDATA[<p>Useful &#8230; and a nice example. Thanks :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
