<?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: Design Patterns in ActionScript&#8211;Factory Method</title>
	<atom:link href="http://ntt.cc/2008/10/08/gang-of-four-gof-design-patterns-in-actionscript-factory-method.html/feed" rel="self" type="application/rss+xml" />
	<link>http://ntt.cc/2008/10/08/gang-of-four-gof-design-patterns-in-actionscript-factory-method.html</link>
	<description>Flex,Flash,Ajax and Freebie Resource for Developers and Designers</description>
	<lastBuildDate>Sun, 14 Mar 2010 13:43:29 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: localToGlobal &#187; Blog Archive &#187; news review -&#62; 41th week of 2008</title>
		<link>http://ntt.cc/2008/10/08/gang-of-four-gof-design-patterns-in-actionscript-factory-method.html/comment-page-1#comment-2182</link>
		<dc:creator>localToGlobal &#187; Blog Archive &#187; news review -&#62; 41th week of 2008</dc:creator>
		<pubDate>Sun, 12 Oct 2008 19:53:21 +0000</pubDate>
		<guid isPermaLink="false">http://ntt.cc/2008/10/08/gang-of-four-gof-design-patterns-in-actionscript-factory-method.html#comment-2182</guid>
		<description>[...] &gt; Gang of Four (GOF) Design Patterns in ActionScript–Factory Method - Ntt.cc [...]</description>
		<content:encoded><![CDATA[<p>[...] &gt; Gang of Four (GOF) Design Patterns in ActionScript–Factory Method &#8211; Ntt.cc [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daz</title>
		<link>http://ntt.cc/2008/10/08/gang-of-four-gof-design-patterns-in-actionscript-factory-method.html/comment-page-1#comment-2170</link>
		<dc:creator>Daz</dc:creator>
		<pubDate>Thu, 09 Oct 2008 00:43:53 +0000</pubDate>
		<guid isPermaLink="false">http://ntt.cc/2008/10/08/gang-of-four-gof-design-patterns-in-actionscript-factory-method.html#comment-2170</guid>
		<description>It would be good if you made it clear how you would actually use the second, more complex factory. If I wanted to create a new eagle, for example, how would I go about this. If I created a new birdFactory and called getBird how would the function know if I wanted an eagle or a penguin?</description>
		<content:encoded><![CDATA[<p>It would be good if you made it clear how you would actually use the second, more complex factory. If I wanted to create a new eagle, for example, how would I go about this. If I created a new birdFactory and called getBird how would the function know if I wanted an eagle or a penguin?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ntt.cc</title>
		<link>http://ntt.cc/2008/10/08/gang-of-four-gof-design-patterns-in-actionscript-factory-method.html/comment-page-1#comment-2164</link>
		<dc:creator>Ntt.cc</dc:creator>
		<pubDate>Wed, 08 Oct 2008 00:57:53 +0000</pubDate>
		<guid isPermaLink="false">http://ntt.cc/2008/10/08/gang-of-four-gof-design-patterns-in-actionscript-factory-method.html#comment-2164</guid>
		<description>hi, Steven Sacks

I know that class names should begin with an uppercase first letter and are usually nouns. start with lowercase letters is really bad. But that is only the guidelines apply to naming classes, isn&#039;t it?
BTW, I read the following post about class name:
http://www.adobe.com/devnet/flash/articles/as_bestpractices_02.html
&quot;
The following guidelines apply to naming classes:

    * Begin a class name with an uppercase letter.
    * Write class names in mixed case when it&#039;s a compound or concatenated word.
    * Begin with an uppercase letter for a compound or concatenated word. A good example is NewMember.
    * Class names are usually nouns or qualified nouns. A qualifier describes the noun or phrase. For example, instead of &quot;member,&quot; you might qualify the noun by using NewMember or OldMember.
    * Clear names are more important than short names.
    * Don&#039;t use acronyms and abbreviations. The exception to this rule is if acronyms or abbreviations represent the standard way to use a term (such as HTML or CFM). For commonly used acronyms, use mixed cases such as NewHtmlParser instead of NewHTMLParser for improved readability.
    * Use meaningful and simple names that are descriptive of the class contents. To avoid being vague or misleading, use generic names.
    * Sometimes a class name is a compound word. A qualifier might describe the noun or phrase. For example, instead of &quot;member,&quot; you might qualify the noun using NewMember or OldMember.
    * Do not pluralize the words you use in the class name (such as Witches or BaldPirates). In most cases, it is better to leave the words as qualified nouns instead. A qualifier describes the noun or phrase. For example, instead of &quot;cat&quot; or &quot;buckaneer,&quot; you might qualify the noun by using BlackCat or OldBuckaneer.
    * Don&#039;t use a class name in the properties of that class because it causes redundancy. For example, it does not make sense to have Cat.catWhiskers. Instead, Cat.whiskers is much better.
    * Don&#039;t use nouns that also might be interpreted as verbs. For example, Running, or Gardening. Using these nouns might lead to confusion with methods, states, or other application activities.
    * Use unique class names for each class in a single application.
    * Do not name classes so that they conflict with the names of built-in classes in Flash.
    * Try to communicate the relationship that a class has within a hierarchy. This helps display a class&#039;s relationship within an application. For example, you might have the Widget interface, and the implementation of Widget might be PlasticWidget, SteelWidget, and SmallWidget.
&quot;
anyway, thanks for your advice and I will fix it from next post. ( although flex builder allow me type lowercase letters as my class name. :)  )</description>
		<content:encoded><![CDATA[<p>hi, Steven Sacks</p>
<p>I know that class names should begin with an uppercase first letter and are usually nouns. start with lowercase letters is really bad. But that is only the guidelines apply to naming classes, isn&#8217;t it?<br />
BTW, I read the following post about class name:<br />
<a href="http://www.adobe.com/devnet/flash/articles/as_bestpractices_02.html" rel="nofollow">http://www.adobe.com/devnet/flash/articles/as_bestpractices_02.html</a><br />
&#8221;<br />
The following guidelines apply to naming classes:</p>
<p>    * Begin a class name with an uppercase letter.<br />
    * Write class names in mixed case when it&#8217;s a compound or concatenated word.<br />
    * Begin with an uppercase letter for a compound or concatenated word. A good example is NewMember.<br />
    * Class names are usually nouns or qualified nouns. A qualifier describes the noun or phrase. For example, instead of &#8220;member,&#8221; you might qualify the noun by using NewMember or OldMember.<br />
    * Clear names are more important than short names.<br />
    * Don&#8217;t use acronyms and abbreviations. The exception to this rule is if acronyms or abbreviations represent the standard way to use a term (such as HTML or CFM). For commonly used acronyms, use mixed cases such as NewHtmlParser instead of NewHTMLParser for improved readability.<br />
    * Use meaningful and simple names that are descriptive of the class contents. To avoid being vague or misleading, use generic names.<br />
    * Sometimes a class name is a compound word. A qualifier might describe the noun or phrase. For example, instead of &#8220;member,&#8221; you might qualify the noun using NewMember or OldMember.<br />
    * Do not pluralize the words you use in the class name (such as Witches or BaldPirates). In most cases, it is better to leave the words as qualified nouns instead. A qualifier describes the noun or phrase. For example, instead of &#8220;cat&#8221; or &#8220;buckaneer,&#8221; you might qualify the noun by using BlackCat or OldBuckaneer.<br />
    * Don&#8217;t use a class name in the properties of that class because it causes redundancy. For example, it does not make sense to have Cat.catWhiskers. Instead, Cat.whiskers is much better.<br />
    * Don&#8217;t use nouns that also might be interpreted as verbs. For example, Running, or Gardening. Using these nouns might lead to confusion with methods, states, or other application activities.<br />
    * Use unique class names for each class in a single application.<br />
    * Do not name classes so that they conflict with the names of built-in classes in Flash.<br />
    * Try to communicate the relationship that a class has within a hierarchy. This helps display a class&#8217;s relationship within an application. For example, you might have the Widget interface, and the implementation of Widget might be PlasticWidget, SteelWidget, and SmallWidget.<br />
&#8221;<br />
anyway, thanks for your advice and I will fix it from next post. ( although flex builder allow me type lowercase letters as my class name. <img src='http://ntt.cc/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Sacks</title>
		<link>http://ntt.cc/2008/10/08/gang-of-four-gof-design-patterns-in-actionscript-factory-method.html/comment-page-1#comment-2162</link>
		<dc:creator>Steven Sacks</dc:creator>
		<pubDate>Tue, 07 Oct 2008 17:01:17 +0000</pubDate>
		<guid isPermaLink="false">http://ntt.cc/2008/10/08/gang-of-four-gof-design-patterns-in-actionscript-factory-method.html#comment-2162</guid>
		<description>Class names should never start with lowercase letters.</description>
		<content:encoded><![CDATA[<p>Class names should never start with lowercase letters.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
