<?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: No exclude.xml in Flash CS3 for AS3: Solution via Bridge Pattern	</title>
	<atom:link href="https://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html/feed" rel="self" type="application/rss+xml" />
	<link>https://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html</link>
	<description>Software &#124; Fitness &#124; Gaming</description>
	<lastBuildDate>Tue, 31 Mar 2009 17:27:54 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Roger Gonzalez		</title>
		<link>https://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html/comment-page-1#comment-161670</link>

		<dc:creator><![CDATA[Roger Gonzalez]]></dc:creator>
		<pubDate>Tue, 31 Mar 2009 17:27:54 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html#comment-161670</guid>

					<description><![CDATA[Oh, and manotosh, just crack open your SWC and look inside to see what dependencies got dragged in.

Incidentally, just because the SWC is big, doesn&#039;t mean that an application compiled from that SWC will also be big.  Library projects include everything referenced by every definition in the library.  Applications that reference libraries exclude anything that isn&#039;t a transitive dependency.

Excluding stuff for which there are actual hard references is dangerous.  It is much better to try to sever extra dependencies, most cleanly by using interfaces.]]></description>
			<content:encoded><![CDATA[<p>Oh, and manotosh, just crack open your SWC and look inside to see what dependencies got dragged in.</p>
<p>Incidentally, just because the SWC is big, doesn&#8217;t mean that an application compiled from that SWC will also be big.  Library projects include everything referenced by every definition in the library.  Applications that reference libraries exclude anything that isn&#8217;t a transitive dependency.</p>
<p>Excluding stuff for which there are actual hard references is dangerous.  It is much better to try to sever extra dependencies, most cleanly by using interfaces.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Roger Gonzalez		</title>
		<link>https://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html/comment-page-1#comment-161669</link>

		<dc:creator><![CDATA[Roger Gonzalez]]></dc:creator>
		<pubDate>Tue, 31 Mar 2009 17:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html#comment-161669</guid>

					<description><![CDATA[Just as some insight into why things are the way they are:

You have to understand that the Flex compiler and Flash compiler only share the core AS3 compiler, and this is a pretty hairy prospect as it is, given that one version is C++ and one version is Java.  The .FLA format is actually some sort of terse serialization of the in-memory structures of the C++ app, so supporting that in Flex is pretty much infeasible.

So, the question was that given that, we&#039;d previously (Royale/Flex 1.0) gone down the path of shrugging and giving up on more than bare minimum compatibility.  For Flex 2, we decided that although pure 100% source interoperability was still too hard to tackle, the best approach was to interoperate well at the SWC level.  Thus, everything in Flex (and to a lesser degree, in Flash Authoring) is oriented around slinging around baskets of definitions in SWC format.

I shared many of your concerns you express here, which is why I created -link-report and -exclude and -load-externs and the Modules system (particularly the AS3 API, not the flimsy MXML-friendly facade).

Basically, until I did that, there was no solution in either product.  I got a lot of grief for adding it to Flex because it highlighted its omission in Flash, but I stand by my decision to at least provide the option somewhere.

I&#039;m a bit of an odd duck, though as typical Flex/Flash developers go, though.  I just build my own stuff on top of SimpleApplication and use Flash to build pretty assets.  If they&#039;re pure media, I embed them.  If they have some code attached (which I try to avoid) I link them as SWCs.  I make heavy use of modules and interfaces, and other than cross-site issues and some annoyances with embedded fonts, life is grand.  :-)]]></description>
			<content:encoded><![CDATA[<p>Just as some insight into why things are the way they are:</p>
<p>You have to understand that the Flex compiler and Flash compiler only share the core AS3 compiler, and this is a pretty hairy prospect as it is, given that one version is C++ and one version is Java.  The .FLA format is actually some sort of terse serialization of the in-memory structures of the C++ app, so supporting that in Flex is pretty much infeasible.</p>
<p>So, the question was that given that, we&#8217;d previously (Royale/Flex 1.0) gone down the path of shrugging and giving up on more than bare minimum compatibility.  For Flex 2, we decided that although pure 100% source interoperability was still too hard to tackle, the best approach was to interoperate well at the SWC level.  Thus, everything in Flex (and to a lesser degree, in Flash Authoring) is oriented around slinging around baskets of definitions in SWC format.</p>
<p>I shared many of your concerns you express here, which is why I created -link-report and -exclude and -load-externs and the Modules system (particularly the AS3 API, not the flimsy MXML-friendly facade).</p>
<p>Basically, until I did that, there was no solution in either product.  I got a lot of grief for adding it to Flex because it highlighted its omission in Flash, but I stand by my decision to at least provide the option somewhere.</p>
<p>I&#8217;m a bit of an odd duck, though as typical Flex/Flash developers go, though.  I just build my own stuff on top of SimpleApplication and use Flash to build pretty assets.  If they&#8217;re pure media, I embed them.  If they have some code attached (which I try to avoid) I link them as SWCs.  I make heavy use of modules and interfaces, and other than cross-site issues and some annoyances with embedded fonts, life is grand.  :-)</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: andar909		</title>
		<link>https://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html/comment-page-1#comment-112581</link>

		<dc:creator><![CDATA[andar909]]></dc:creator>
		<pubDate>Mon, 11 Aug 2008 04:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html#comment-112581</guid>

					<description><![CDATA[hi, andar here, i just read your post.  i like very much.  agree to you, sir.]]></description>
			<content:encoded><![CDATA[<p>hi, andar here, i just read your post.  i like very much.  agree to you, sir.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: manotosh		</title>
		<link>https://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html/comment-page-1#comment-92362</link>

		<dc:creator><![CDATA[manotosh]]></dc:creator>
		<pubDate>Wed, 11 Jun 2008 05:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html#comment-92362</guid>

					<description><![CDATA[I have been searching for solution to exclude class using flash 9 IDE, but realised _exclude is removed. I then used flex  library projects to create code library and use it in flash, I took the advantage of refering other library projects as library path to do the type checking of clases which I dont want to include. Things works fine till I realised that the file size of exported swc form flex is much larger than flash exported swc. I created one single class without any composition or inheritance and compiled both from flash and from flex libray projects, the flash exported file size is 11k where as flex exported swc size is 20k. Does anybody know what extra goes into flex swc? I plan to use flex as a code compiler to take the advantage of excluding classes. Does anybodu know any other solution?]]></description>
			<content:encoded><![CDATA[<p>I have been searching for solution to exclude class using flash 9 IDE, but realised _exclude is removed. I then used flex  library projects to create code library and use it in flash, I took the advantage of refering other library projects as library path to do the type checking of clases which I dont want to include. Things works fine till I realised that the file size of exported swc form flex is much larger than flash exported swc. I created one single class without any composition or inheritance and compiled both from flash and from flex libray projects, the flash exported file size is 11k where as flex exported swc size is 20k. Does anybody know what extra goes into flex swc? I plan to use flex as a code compiler to take the advantage of excluding classes. Does anybodu know any other solution?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: tonypee		</title>
		<link>https://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html/comment-page-1#comment-82809</link>

		<dc:creator><![CDATA[tonypee]]></dc:creator>
		<pubDate>Fri, 09 May 2008 04:23:53 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/2007/09/no-excludexml-in-flash-cs3-for-as3-solution-via-bridge-pattern.html#comment-82809</guid>

					<description><![CDATA[sorry i was meaning to link to: http://blog.touchmypixel.com/archives/16]]></description>
			<content:encoded><![CDATA[<p>sorry i was meaning to link to: <a href="http://blog.touchmypixel.com/archives/16" rel="nofollow ugc">http://blog.touchmypixel.com/archives/16</a></p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
