<?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: Another good use of interfaces</title>
	<atom:link href="http://www.zedia.net/2008/another-good-use-of-interfaces/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zedia.net/2008/another-good-use-of-interfaces/</link>
	<description>Flash, ActionScript, SEO and everything in between</description>
	<lastBuildDate>Sat, 04 Feb 2012 08:16:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: james</title>
		<link>http://www.zedia.net/2008/another-good-use-of-interfaces/comment-page-1/#comment-7609</link>
		<dc:creator>james</dc:creator>
		<pubDate>Thu, 21 Jul 2011 11:14:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.zedia.net/2008/another-good-use-of-interfaces/#comment-7609</guid>
		<description>interfaces are great for polymorphism where necessary, but it used to be considered a bad idea, as class abstraction can become a nightmare in terms of tight coupling and dependencies.  The really useful thing that I find for them is when defining a contract between you the developer and the developer who implements your code.  If you specify an interface then when the developer comes to extend the class that implements that interface they are forced to stick to the implementation details that you have defined in the class.  This allows for the class to be extended whilst maintaining the same method signatures so that the compiler can allocate memory without problems in the case of run time type identification etc.</description>
		<content:encoded><![CDATA[<p>interfaces are great for polymorphism where necessary, but it used to be considered a bad idea, as class abstraction can become a nightmare in terms of tight coupling and dependencies.  The really useful thing that I find for them is when defining a contract between you the developer and the developer who implements your code.  If you specify an interface then when the developer comes to extend the class that implements that interface they are forced to stick to the implementation details that you have defined in the class.  This allows for the class to be extended whilst maintaining the same method signatures so that the compiler can allocate memory without problems in the case of run time type identification etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Håvard Terland</title>
		<link>http://www.zedia.net/2008/another-good-use-of-interfaces/comment-page-1/#comment-6238</link>
		<dc:creator>Håvard Terland</dc:creator>
		<pubDate>Sat, 12 Mar 2011 14:58:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.zedia.net/2008/another-good-use-of-interfaces/#comment-6238</guid>
		<description>I was afraid of interfaces, before I found this! Favorited + liked.</description>
		<content:encoded><![CDATA[<p>I was afraid of interfaces, before I found this! Favorited + liked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interface trick (main swf &#8211;&#62; load external swf and want to call it function) &#171; CODE@蝴蝶。夢</title>
		<link>http://www.zedia.net/2008/another-good-use-of-interfaces/comment-page-1/#comment-5310</link>
		<dc:creator>Interface trick (main swf &#8211;&#62; load external swf and want to call it function) &#171; CODE@蝴蝶。夢</dc:creator>
		<pubDate>Fri, 23 Jul 2010 03:33:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.zedia.net/2008/another-good-use-of-interfaces/#comment-5310</guid>
		<description>[...] http://www.zedia.net/2008/another-good-use-of-interfaces/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.zedia.net/2008/another-good-use-of-interfaces/" rel="nofollow">http://www.zedia.net/2008/another-good-use-of-interfaces/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: philmill</title>
		<link>http://www.zedia.net/2008/another-good-use-of-interfaces/comment-page-1/#comment-4761</link>
		<dc:creator>philmill</dc:creator>
		<pubDate>Tue, 26 Jan 2010 22:26:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.zedia.net/2008/another-good-use-of-interfaces/#comment-4761</guid>
		<description>I never thought about using an interface this way.  I too had issues importing the class of the external swf and trying to cast it without errors.  Thank you.</description>
		<content:encoded><![CDATA[<p>I never thought about using an interface this way.  I too had issues importing the class of the external swf and trying to cast it without errors.  Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hadi</title>
		<link>http://www.zedia.net/2008/another-good-use-of-interfaces/comment-page-1/#comment-3935</link>
		<dc:creator>Hadi</dc:creator>
		<pubDate>Wed, 26 Aug 2009 17:02:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.zedia.net/2008/another-good-use-of-interfaces/#comment-3935</guid>
		<description>Thanks for sharing, I&#039;ve been shifted to AS3 for 6 month and up to this moment I was afraid of interfaces but now, I will be using it in my projects, it&#039;s surely great. thank you</description>
		<content:encoded><![CDATA[<p>Thanks for sharing, I&#8217;ve been shifted to AS3 for 6 month and up to this moment I was afraid of interfaces but now, I will be using it in my projects, it&#8217;s surely great. thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ryan galax</title>
		<link>http://www.zedia.net/2008/another-good-use-of-interfaces/comment-page-1/#comment-3926</link>
		<dc:creator>ryan galax</dc:creator>
		<pubDate>Fri, 21 Aug 2009 20:37:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.zedia.net/2008/another-good-use-of-interfaces/#comment-3926</guid>
		<description>great stuff here

thanks a lot !!!</description>
		<content:encoded><![CDATA[<p>great stuff here</p>
<p>thanks a lot !!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How to use interface in ActionScript 3 &#124; Details about interfaces in AS3 &#124; zedia flash blog</title>
		<link>http://www.zedia.net/2008/another-good-use-of-interfaces/comment-page-1/#comment-3356</link>
		<dc:creator>How to use interface in ActionScript 3 &#124; Details about interfaces in AS3 &#124; zedia flash blog</dc:creator>
		<pubDate>Wed, 04 Mar 2009 16:12:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.zedia.net/2008/another-good-use-of-interfaces/#comment-3356</guid>
		<description>[...] Another good use of interfaces [...]</description>
		<content:encoded><![CDATA[<p>[...] Another good use of interfaces [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zedia.net</title>
		<link>http://www.zedia.net/2008/another-good-use-of-interfaces/comment-page-1/#comment-3270</link>
		<dc:creator>zedia.net</dc:creator>
		<pubDate>Mon, 19 Jan 2009 21:21:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.zedia.net/2008/another-good-use-of-interfaces/#comment-3270</guid>
		<description>hehe

Nah I meant the main movie because the main movie is loading each sections. But in the case of a preloader, your three point would be exact.

Read this other post for more information about complex preloaders:
http://www.zedia.net/2008/external-preloader-more-complex-cases/</description>
		<content:encoded><![CDATA[<p>hehe</p>
<p>Nah I meant the main movie because the main movie is loading each sections. But in the case of a preloader, your three point would be exact.</p>
<p>Read this other post for more information about complex preloaders:<br />
<a href="http://www.zedia.net/2008/external-preloader-more-complex-cases/" rel="nofollow">http://www.zedia.net/2008/external-preloader-more-complex-cases/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sideDoor</title>
		<link>http://www.zedia.net/2008/another-good-use-of-interfaces/comment-page-1/#comment-3269</link>
		<dc:creator>sideDoor</dc:creator>
		<pubDate>Mon, 19 Jan 2009 21:04:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.zedia.net/2008/another-good-use-of-interfaces/#comment-3269</guid>
		<description>I meant: Keep up the great work!</description>
		<content:encoded><![CDATA[<p>I meant: Keep up the great work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sideDoor</title>
		<link>http://www.zedia.net/2008/another-good-use-of-interfaces/comment-page-1/#comment-3267</link>
		<dc:creator>sideDoor</dc:creator>
		<pubDate>Mon, 19 Jan 2009 08:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.zedia.net/2008/another-good-use-of-interfaces/#comment-3267</guid>
		<description>Above, when you wrote:

&quot;So in my external swf document class I made certain it implemented the interface I was going to us and in my main movie I type casted the loader.content to that interface (Type).&quot;

...did you not mean...

&quot;...and in my PRELOADER movie I type casted the loader.content to that interface...&quot;, instead of main movie?  (Main movie is what you originally declared to be the &quot;shell&quot; movie of your application).

In this case, I gather that you&#039;re using:

1. Actions layer of the preloader.swf contains the preloader code and loads the shell movie.
2. On complete, you run the closing animation of the preloader, and when complete, you call an init() method of the document class from the loaded.
3. But in order to have access to the document class init() method, you need to access it through type-casting the loader.content property to an interface that ensures the init() method?

I&#039;m not totally clear here: Is there anyway you can show the classes involved in a simple implementation or a UML diagram or post a zip of the structure?

Thanks very much!  Keep of the great work!
sd</description>
		<content:encoded><![CDATA[<p>Above, when you wrote:</p>
<p>&#8220;So in my external swf document class I made certain it implemented the interface I was going to us and in my main movie I type casted the loader.content to that interface (Type).&#8221;</p>
<p>&#8230;did you not mean&#8230;</p>
<p>&#8220;&#8230;and in my PRELOADER movie I type casted the loader.content to that interface&#8230;&#8221;, instead of main movie?  (Main movie is what you originally declared to be the &#8220;shell&#8221; movie of your application).</p>
<p>In this case, I gather that you&#8217;re using:</p>
<p>1. Actions layer of the preloader.swf contains the preloader code and loads the shell movie.<br />
2. On complete, you run the closing animation of the preloader, and when complete, you call an init() method of the document class from the loaded.<br />
3. But in order to have access to the document class init() method, you need to access it through type-casting the loader.content property to an interface that ensures the init() method?</p>
<p>I&#8217;m not totally clear here: Is there anyway you can show the classes involved in a simple implementation or a UML diagram or post a zip of the structure?</p>
<p>Thanks very much!  Keep of the great work!<br />
sd</p>
]]></content:encoded>
	</item>
</channel>
</rss>

