<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>

<channel>
	<title>ActionScript 3 Design Patterns &#187; Class Relations</title>
	<atom:link href="http://www.as3dp.com/category/class-relations/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.as3dp.com</link>
	<description>OOP Techniques for Flash and Flex Developers</description>
	<lastBuildDate>Thu, 08 Jul 2010 21:18:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/us/</creativeCommons:license>
		<item>
		<title>ActionsScript 3.0 Design Pattern Relations Part IV: Creation</title>
		<link>http://www.as3dp.com/2010/02/18/actionsscript-3-0-design-pattern-relations-part-iv-creation/</link>
		<comments>http://www.as3dp.com/2010/02/18/actionsscript-3-0-design-pattern-relations-part-iv-creation/#comments</comments>
		<pubDate>Fri, 19 Feb 2010 02:26:33 +0000</pubDate>
		<dc:creator>William B. Sanders</dc:creator>
				<category><![CDATA[Class Relations]]></category>
		<category><![CDATA[Creates]]></category>

		<guid isPermaLink="false">http://www.as3dp.com/?p=2685</guid>
		<description><![CDATA[ne of the least discussed  relations in Design Patterns is where one participant creates an instance of another. Basically, the pattern calls for one class to instantiate another class. This relationship is indicated by a broken line with an arrowhead pointing to the class that has been instantiated. (The Participant Relations diagram above shows [...]]]></description>
		<wfw:commentRss>http://www.as3dp.com/2010/02/18/actionsscript-3-0-design-pattern-relations-part-iv-creation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/us/</creativeCommons:license>
	</item>
		<item>
		<title>ActionsScript 3.0 Design Pattern Relations Part III: Inheritance</title>
		<link>http://www.as3dp.com/2010/02/09/actionsscript-3-0-design-pattern-relations-part-iii-inheritance/</link>
		<comments>http://www.as3dp.com/2010/02/09/actionsscript-3-0-design-pattern-relations-part-iii-inheritance/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 14:33:57 +0000</pubDate>
		<dc:creator>William B. Sanders</dc:creator>
				<category><![CDATA[Inheritance]]></category>

		<guid isPermaLink="false">http://www.as3dp.com/?p=2582</guid>
		<description><![CDATA[n open triangle on a line from a child class to the parent class indicates the inheritance symbol in Design Pattern class diagrams. In the Participant Relations diagram above, you can see symbols for both single and multiple inheritance in red. Inheritance in design patterns is so common, pointing out which designs do not use [...]]]></description>
		<wfw:commentRss>http://www.as3dp.com/2010/02/09/actionsscript-3-0-design-pattern-relations-part-iii-inheritance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/us/</creativeCommons:license>
	</item>
		<item>
		<title>ActionsScript 3.0 Design Pattern Relations Part II: Aggregation</title>
		<link>http://www.as3dp.com/2010/01/26/actionsscript-3-0-design-pattern-relations-part-ii-aggregation/</link>
		<comments>http://www.as3dp.com/2010/01/26/actionsscript-3-0-design-pattern-relations-part-ii-aggregation/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 20:58:39 +0000</pubDate>
		<dc:creator>William B. Sanders</dc:creator>
				<category><![CDATA[Aggregation]]></category>
		<category><![CDATA[Class Relations]]></category>
		<category><![CDATA[Delegation]]></category>

		<guid isPermaLink="false">http://www.as3dp.com/?p=2476</guid>
		<description><![CDATA[I&#8217;m tempted to say that aggregation is a stronger form of acquaintance, and that wouldn&#8217;t be far from wrong. In fact, in certain contexts it may be perfectly correct. Gamma, et al point out that the differences between the two  is a matter of intent rather than explicit language mechanisms. That makes it a [...]]]></description>
		<wfw:commentRss>http://www.as3dp.com/2010/01/26/actionsscript-3-0-design-pattern-relations-part-ii-aggregation/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/us/</creativeCommons:license>
	</item>
		<item>
		<title>ActionsScript 3.0 Design Pattern Relations Part I: Acquaintances</title>
		<link>http://www.as3dp.com/2010/01/16/actionsscript-3-0-design-pattern-relations-part-i-acquaintances/</link>
		<comments>http://www.as3dp.com/2010/01/16/actionsscript-3-0-design-pattern-relations-part-i-acquaintances/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 15:58:45 +0000</pubDate>
		<dc:creator>William B. Sanders</dc:creator>
				<category><![CDATA[Acquaintance]]></category>
		<category><![CDATA[Association]]></category>
		<category><![CDATA[Class Relations]]></category>
		<category><![CDATA[Delegation]]></category>

		<guid isPermaLink="false">http://www.as3dp.com/?p=2374</guid>
		<description><![CDATA[his post is the first in a series where I hope to discuss all of the key relationships between classes in Design Patterns. To help identify posts in this series I&#8217;ve created a general diagram with all of the different kinds of relationships between classes. I did not include the boxes for pseudo-code or divide [...]]]></description>
		<wfw:commentRss>http://www.as3dp.com/2010/01/16/actionsscript-3-0-design-pattern-relations-part-i-acquaintances/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/us/</creativeCommons:license>
	</item>
		<item>
		<title>No New is Good New: Using Inheritance, Composition, Delegation and anything else other than New in ActionScript 3.0 Design Patterns</title>
		<link>http://www.as3dp.com/2008/09/19/no-new-is-good-new-using-inheritance-composition-delegation-and-anything-else-other-than-new-in-actionscript-30-design-patterns/</link>
		<comments>http://www.as3dp.com/2008/09/19/no-new-is-good-new-using-inheritance-composition-delegation-and-anything-else-other-than-new-in-actionscript-30-design-patterns/#comments</comments>
		<pubDate>Fri, 19 Sep 2008 22:12:15 +0000</pubDate>
		<dc:creator>William B. Sanders</dc:creator>
				<category><![CDATA[Class Relations]]></category>
		<category><![CDATA[Principles]]></category>

		<guid isPermaLink="false">http://www.as3dp.com/?p=199</guid>
		<description><![CDATA[
Before examining why instantiating instances using new is not a good thing, let me explain where I got the idea. It came from the GoF (indirectly) and the Freemans’ Head First Design Patterns (directly). This is not to say that both acquaintance and aggregation type relationships cannot hold a reference to another class by instantiating [...]]]></description>
		<wfw:commentRss>http://www.as3dp.com/2008/09/19/no-new-is-good-new-using-inheritance-composition-delegation-and-anything-else-other-than-new-in-actionscript-30-design-patterns/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/us/</creativeCommons:license>
	</item>
	</channel>
</rss>
