<?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/"
	>

<channel>
	<title>Mental Notes &#187; Eclipse</title>
	<atom:link href="http://stephan.acidcats.nl/blog/category/eclipse/feed/" rel="self" type="application/rss+xml" />
	<link>http://stephan.acidcats.nl/blog</link>
	<description>from the trenches of software development</description>
	<lastBuildDate>Sun, 01 Mar 2009 19:44:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>FDT &amp; automatic class name generation in Flash CS3</title>
		<link>http://stephan.acidcats.nl/blog/2007/11/25/fdt-automatic-class-name-generation-in-flash-cs3/</link>
		<comments>http://stephan.acidcats.nl/blog/2007/11/25/fdt-automatic-class-name-generation-in-flash-cs3/#comments</comments>
		<pubDate>Sun, 25 Nov 2007 20:48:08 +0000</pubDate>
		<dc:creator>stephan</dc:creator>
				<category><![CDATA[Eclipse]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[Programming]]></category>

		<guid isPermaLink="false">http://stephan.acidcats.nl/blog/2007/11/25/fdt-automatic-class-name-generation-in-flash-cs3/</guid>
		<description><![CDATA[The function flash.utils.getDefinitionByName has been discussed in various other places (amongst others here and of course in the documentation), but it took a bit of a mental jump to use it as the solution for the problem that linked library instances without a class are not known inside FDT.Suppose we have a library item with a [...]]]></description>
			<content:encoded><![CDATA[<p>The function <code>flash.utils.getDefinitionByName</code> has been discussed in various other places (amongst others <a href="http://www.mikechambers.com/blog/2006/06/22/actionscript-3-get-a-class-reference-by-class-name/">here</a> and of course <a href="http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/flash/utils/package.html#getDefinitionByName()">in the documentation</a>), but it took a bit of a mental jump to use it as the solution for the problem that linked library instances without a class are not known inside FDT.Suppose we have a library item with a linkage id of &#8220;square&#8221;, and we decide not to attach a class to it. Flash CS3 reminds us that it will create one for us, and if we code inside the Flash IDE, we can happily write: <code>var s:Sprite = new square(); addChild(s);</code>However, FDT will show an error, because it doesn&#8217;t have a clue what you&#8217;re talking about. To solve this, use <code>getDefinitionByName("square")</code>, as shown in the following example:
<div class="dean_ch" style="white-space: wrap;">
<ol>
<li class="li1">
<div class="de1">&nbsp;</div>
</li>
<li class="li1">
<div class="de1"><span class="kw4">package</span> <span class="br0">&#123;</span></div>
</li>
<li class="li1">
<div class="de1">&nbsp; &nbsp; <span class="kw1">import</span> <span class="kw6">flash.display</span>.<a href="http://www.google.com/search?q=MovieClip%20inurl:http://livedocs.adobe.com/flex/201/langref/%20inurl:MovieClip.html&#038;filter=0&#038;num=100&#038;btnI=lucky"><span class="kw5">MovieClip</span></a>;</div>
</li>
<li class="li1">
<div class="de1">&nbsp; &nbsp; <span class="kw1">import</span> <span class="kw6">flash.display</span>.<a href="http://www.google.com/search?q=Sprite%20inurl:http://livedocs.adobe.com/flex/201/langref/%20inurl:Sprite.html&#038;filter=0&#038;num=100&#038;btnI=lucky"><span class="kw5">Sprite</span></a>;</div>
</li>
<li class="li2">
<div class="de2">&nbsp; &nbsp; <span class="kw1">import</span> <span class="kw6">flash.utils</span>.<span class="kw7">getDefinitionByName</span>;</div>
</li>
<li class="li1">
<div class="de1">&nbsp; &nbsp; </div>
</li>
<li class="li1">
<div class="de1">&nbsp; &nbsp; <span class="kw1">public</span> <span class="kw4">class</span> Application extends <a href="http://www.google.com/search?q=MovieClip%20inurl:http://livedocs.adobe.com/flex/201/langref/%20inurl:MovieClip.html&#038;filter=0&#038;num=100&#038;btnI=lucky"><span class="kw5">MovieClip</span></a> <span class="br0">&#123;</span></div>
</li>
<li class="li1">
<div class="de1">&nbsp; &nbsp; &nbsp; &nbsp; </div>
</li>
<li class="li1">
<div class="de1">&nbsp; &nbsp; &nbsp; &nbsp; <span class="kw1">private</span> static const LINKAGE_SQUARE:<a href="http://www.google.com/search?q=String%20inurl:http://livedocs.adobe.com/flex/201/langref/%20inurl:String.html&#038;filter=0&#038;num=100&#038;btnI=lucky"><span class="kw5">String</span></a> = <span class="st0">&quot;square&quot;</span>; </div>
</li>
<li class="li2">
<div class="de2">&nbsp;</div>
</li>
<li class="li1">
<div class="de1">&nbsp; &nbsp; &nbsp; &nbsp; <span class="kw1">public</span> <span class="kw3">function</span> Application <span class="br0">&#40;</span><span class="br0">&#41;</span> <span class="br0">&#123;</span></div>
</li>
<li class="li1">
<div class="de1">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <span class="kw2">var</span> s:<a href="http://www.google.com/search?q=Sprite%20inurl:http://livedocs.adobe.com/flex/201/langref/%20inurl:Sprite.html&#038;filter=0&#038;num=100&#038;btnI=lucky"><span class="kw5">Sprite</span></a> = <span class="kw1">new</span> <span class="br0">&#40;</span><span class="kw7">getDefinitionByName</span><span class="br0">&#40;</span>LINKAGE_SQUARE<span class="br0">&#41;</span><span class="br0">&#41;</span><span class="br0">&#40;</span><span class="br0">&#41;</span>;</div>
</li>
<li class="li1">
<div class="de1">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <span class="kw7">addChild</span><span class="br0">&#40;</span>s<span class="br0">&#41;</span>;</div>
</li>
<li class="li1">
<div class="de1">&nbsp; &nbsp; &nbsp; &nbsp; <span class="br0">&#125;</span></div>
</li>
<li class="li2">
<div class="de2">&nbsp; &nbsp; <span class="br0">&#125;</span></div>
</li>
<li class="li1">
<div class="de1"><span class="br0">&#125;</span></div>
</li>
<li class="li1">
<div class="de1">&nbsp;</div>
</li>
</ol>
</div>
]]></content:encoded>
			<wfw:commentRss>http://stephan.acidcats.nl/blog/2007/11/25/fdt-automatic-class-name-generation-in-flash-cs3/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>More JavaDocs comments in ActionScript in Eclipse</title>
		<link>http://stephan.acidcats.nl/blog/2006/07/03/more-javadocs-comments-in-actionscript-in-eclipse/</link>
		<comments>http://stephan.acidcats.nl/blog/2006/07/03/more-javadocs-comments-in-actionscript-in-eclipse/#comments</comments>
		<pubDate>Mon, 03 Jul 2006 13:21:42 +0000</pubDate>
		<dc:creator>stephan</dc:creator>
				<category><![CDATA[Eclipse]]></category>

		<guid isPermaLink="false">http://stephan.acidcats.nl/blog/2006/07/03/more-javadocs-comments-in-actionscript-in-eclipse/</guid>
		<description><![CDATA[With the FDT plugin, Eclipse turns your JavaDoc comments into popups that appear whenever hovering over a code that has JavaDoc comments attached to it. This can be any class, member variable or function. Attaching comments is done by putting a comment right over the element you wish to attach it to, in JavaDoc style:
/**my [...]]]></description>
			<content:encoded><![CDATA[<p>With the FDT plugin, Eclipse turns your JavaDoc comments into popups that appear whenever hovering over a code that has JavaDoc comments attached to it. This can be any class, member variable or function. Attaching comments is done by putting a comment right over the element you wish to attach it to, in JavaDoc style:<br />
<code>/**my comment for myElement*/<br />
myElement<br />
</code></p>
<p>For a long time, it has been a habit to use long separation lines consisting of dashes for functions. Though this may increase separation of functions in a class file a little, those long lines also appear in the popup that Eclipse creates. It is therefore strongly recommended to let go of the little dashes, and use &#8220;clean&#8221; comments, like this:<br />
<code>/**<br />
*    The function description<br />
*    @param ...: a parameter description<br />
*    @return : description of the return value<br />
*/<br />
</code></p>
<p>For public variables, a single line JavaDoc comment can be added on the line over the declaration:<br />
<code>/** objects of type MyData */<br />
public var myList:Array;</code></p>
]]></content:encoded>
			<wfw:commentRss>http://stephan.acidcats.nl/blog/2006/07/03/more-javadocs-comments-in-actionscript-in-eclipse/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>JavaDoc comments for member variables in Actionscript</title>
		<link>http://stephan.acidcats.nl/blog/2006/06/23/javadoc-comments-for-member-variables-in-actionscript/</link>
		<comments>http://stephan.acidcats.nl/blog/2006/06/23/javadoc-comments-for-member-variables-in-actionscript/#comments</comments>
		<pubDate>Fri, 23 Jun 2006 13:52:36 +0000</pubDate>
		<dc:creator>stephan</dc:creator>
				<category><![CDATA[Eclipse]]></category>
		<category><![CDATA[Flash]]></category>

		<guid isPermaLink="false">http://stephan.acidcats.nl/blog/?p=4</guid>
		<description><![CDATA[When defining a member variable of type Array, put a Javadoc comment (/** */) on the line above the declaration, so it will appear when hovering over a reference to the member variable. Example:

/** of type SubjectData */
private var mSubjects : Array;

]]></description>
			<content:encoded><![CDATA[<p>When defining a member variable of type Array, put a Javadoc comment (/** */) on the line above the declaration, so it will appear when hovering over a reference to the member variable. Example:<br />
<code><br />
/** of type SubjectData */<br />
private var mSubjects : Array;<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://stephan.acidcats.nl/blog/2006/06/23/javadoc-comments-for-member-variables-in-actionscript/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

