<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>InsideRIA</title>
<link rel="alternate" type="text/html" href="http://www.insideria.com/" />
<link rel="self" type="application/atom+xml" href="http://www.insideria.com/atom.xml" />
<id>tag:www.insideria.com,2008-01-28://34</id>
<updated>2008-11-24T14:00:00Z</updated>
<subtitle>InsideRIA.com is an online community developed by O’Reilly and sponsored by Adobe Systems Incorporated. Our goal is to create an invaluable resource for information on the ever-changing state of design and development of rich Internet applications (RIAs).</subtitle>
<generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.21-en</generator>

<entry>
<title>The Official &quot;visible vs alpha vs removeChild()&quot; Showdown</title>
<link rel="alternate" type="text/html" href="http://www.insideria.com/2008/11/visible-false-versus-removechi.html" />
<id>tag:www.insideria.com,2008://34.34058</id>

<published>2008-11-24T14:00:00Z</published>
<updated>2008-11-24T14:00:00Z</updated>

<summary><![CDATA[Flash Player&#39;s display API offers three different tools for hiding display 
objects from the screen: the visible variable, the 
alpha variable, and the removeChild() method. All 
three tools achieve the same end result&#8212;hiding a graphic&#8212;but each tool serves 
a different structural need. Hence, there is no single answer to the question 
&quot;Should I hide graphics with visible, alpha, or 
removeChild()?&quot; Instead, 
developers must choose the approach that suits the task at hand based on a 
variety of factors. Before we consider those factors, let&#39;s take a look at 

visible, alpha, and removeChild() in 
action. ]]></summary>
<author>
<name>Colin Moock</name>
<uri>http://www.oreillynet.com/pub/au/568</uri>
</author>

<category term="Adobe Feed" scheme="http://www.sixapart.com/ns/types#category" />

<category term="Features" scheme="http://www.sixapart.com/ns/types#category" />

<category term="actionscript" label="actionscript" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="flashplayer" label="flashplayer" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="graphics" label="graphics" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://www.insideria.com/">
<![CDATA[Flash Player&#39;s display API offers three different tools for hiding display 
objects from the screen: the visible variable, the 
alpha variable, and the removeChild() method. All 
three tools achieve the same end result&#8212;hiding a graphic&#8212;but each tool serves 
a different structural need. Hence, there is no single answer to the question 
&quot;Should I hide graphics with visible, alpha, or 
removeChild()?&quot; Instead, 
developers must choose the approach that suits the task at hand based on a 
variety of factors. Before we consider those factors, let&#39;s take a look at 

visible, alpha, and removeChild() in 
action. ]]>
</content>
</entry>

<entry>
<title>The Charges Against ActionScript 3.0</title>
<link rel="alternate" type="text/html" href="http://www.insideria.com/2008/07/the-charges-against-actionscri.html" />
<id>tag:www.insideria.com,2008://34.24399</id>

<published>2008-07-15T07:00:00Z</published>
<updated>2008-07-15T07:00:00Z</updated>

<summary>More than a year has passed since Flash CS3 was released to widely positive reviews, but many Flash users are still frustrated by some of the workflow changes introduced by ActionScript 3.0. The truly problematic changes are relatively few, but together they have a deep effect on the typical Flash user&apos;s daily job. In the spirit of working toward solutions, and of giving a formal voice to the collective grumbling of everyday Flashers, this article provides a guide to The Charges Against ActionScript 3.0. The list of accusations follows...</summary>
<author>
<name>Colin Moock</name>
<uri>http://www.oreillynet.com/pub/au/568</uri>
</author>

<category term="Features" scheme="http://www.sixapart.com/ns/types#category" />

<category term="actionscript" label="actionscript" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="adobe" label="adobe" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="cs3" label="cs3" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="flash" label="flash" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://www.insideria.com/">
More than a year has passed since Flash CS3 was released to widely positive reviews, but many Flash users are still frustrated by some of the workflow changes introduced by ActionScript 3.0. The truly problematic changes are relatively few, but together they have a deep effect on the typical Flash user&apos;s daily job. In the spirit of working toward solutions, and of giving a formal voice to the collective grumbling of everyday Flashers, this article provides a guide to The Charges Against ActionScript 3.0. The list of accusations follows...
</content>
</entry>

<entry>
<title>ActionScript 3.0: Is It Hard or Not?</title>
<link rel="alternate" type="text/html" href="http://www.insideria.com/2008/01/actionscript-30-is-it-hard-or.html" />
<id>tag:blogs.oreilly.com,2008:/insideria//34.22719</id>

<published>2008-01-18T16:20:40Z</published>
<updated>2008-01-18T16:20:40Z</updated>

<summary>
In parts of the Flash community, ActionScript 3.0 seems to have gained a reputation for being &#8220;hard&#8221; &#8212;- particularly among those who have not yet tried the new language. Colin Moock, author of Essential ActionScript 3.0, explores this issue and offers code examples comparing earlier versions of ActionScript to version 3.0.</summary>
<author>
<name>Colin Moock</name>
<uri>http://www.oreillynet.com/pub/au/568</uri>
</author>

<category term="Features" scheme="http://www.sixapart.com/ns/types#category" />

<category term="actionscript" label="actionscript" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="flash" label="flash" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="howto" label="how-to" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://www.insideria.com/">

In parts of the Flash community, ActionScript 3.0 seems to have gained a reputation for being &#8220;hard&#8221; &#8212;- particularly among those who have not yet tried the new language. Colin Moock, author of Essential ActionScript 3.0, explores this issue and offers code examples comparing earlier versions of ActionScript to version 3.0.
</content>
</entry>

</feed>