Ha! Okay, that’s not that much of news (even for me). But what astonishes me is how much this speed gap can be, especially when it comes to massive data calculations. I somehow always had a somewhat 20 percent speed decrease in mind (I was just presuming, me dumb). But for a 3d particle test we’re talking factor 8!!

Now this made me curious… so I’ve tested with Debug and Release Player both debug and release SWFs:

Debug Player running Debug SWF

Debug Player running Release SWF

Release Player running Debug SWF

Release Player running Release SWF

A few conclusions:

• Never release a SWF file with debug code (or otherwise said: put only stuff online from bin-release, never bin-debug). Though common users won’t notice the speed decrease, your friendly flash developers may, at least if you’re app is somewhat cpu intensive. And of course: debug SWF are much bigger in size (just in case you give a fuck about flash devs ;-)
• Speed tests should be played in the release player. Why? After all, I wouldn’t care if the relation would stay the same. Usually you just need to know how much faster one thing is compared to the other one, so that would do it. But unfortunately the ratio won’t always be the same. In the above example the ration is 3.66 for debug and 2.92 for release. And it can differ muuuuch more.

The last one bugs me quite a bit. It’s just a pain in the ass to export a release build each time you wanna compare performance. And it also means you can’t do quick’n'dirty trace outputs for the time result (not a biggy if you’re testing within a Flex project though).

So here we go with two wishes for Adobe:

• Let us quickly test release builds within Flex Builder (a simple command would do it – I thought it might be «Run Testapp» (instead of «Debug Testapp»), but that just doesn’t bring up the Debugger (and same speed)
• An option to turn off debugging mode in Debug Player!!! That would solve almost all problems, and we could also use our Plugin for normal browsing without performance penalties (is this why Youtube eats so much cpu here?

Related posts:

1. Switch Flash Browser Plugin on Mac OS X
2. Flash Player 10 – I love speed
3. Test Flex/Flash throttled (aka Simulate Download)

Though I’ve written some posts about how to code within Flex Builder and compile from there using Flash IDE, I personally don’t like that at all and only use it for some few older AS3 projects. There are better methods, ways to compile from within Flex Builder while still being able to make use of Flash comfort.

There’s a neat way to embed a library without loosing any functionality (like little scripts). I’ve first seen it at Grant Skinner (who’s doing great stuff, one of my favorites in the flash community really). Let’s say, you have a assets.fla and a published assets.swf. Now here we go:

[SWF(width="750", height="500", frameRate="30", backgroundColor="#111111")]
dynamic public class MyApplication extends Sprite
{
 
	[Embed(source="assets/assets.swf", mimeType="application/octet-stream")]
	public var StageAssets:Class;
 
	public function GlobusFlow()
	{
		loadEmbedded( StageAssets );
	}
 
	public function loadEmbedded( cls : Class ) : void {
		trace( "[Preloader] Loading embedded" );
		var loader : Loader = new Loader();
		loader.contentLoaderInfo.addEventListener( Event.COMPLETE , this.handleComplete );
		var context : LoaderContext = new LoaderContext( false , ApplicationDomain.currentDomain );
		loader.loadBytes( new cls() , context );
	}
 
	protected function handleComplete( e : Event ) : void {
		var app : Sprite = Sprite( LoaderInfo( e.target ).content );
		this.loaded( app );
	}
 
	protected function loaded(target:Sprite):void {
		var background : MovieClip = target as MovieClip;
 
		var mainChildren : Array = [];
		for ( var i:int = 0 ; i<background.numChildren ; i++ ) {
			mainChildren.push( background.getChildAt(i) );
		}
		for each ( var child : DisplayObject in mainChildren ) {
			if ( child.name ) {
				this[ child.name ] = child;
			}
			this.addChild( child );
		}
 
		stage.stageWidth = background.width;
		stage.stageHeight = background.height;
	}
}

This does a bit more than just make the library available. In loaded() we’ll loop through all assets that are «on stage» in the loaded/embedded movieclip (assets.swf), and add each of them to our stage. That leads to a state that’s quite similar to as if we’d code within assets.fla itself. Hmm… well, really, that sounds more complicated than it is :-) It mainly gives you the feeling of being able to code within a SWF file. You can visually do your stuff in assets.fla, you can add a background and whatever to its stage, keep a nice library with graphics, animations, sounds and fonts.. and schwupps, here you go!

If you have Fonts embedded in your library, there’s a tiny little more to do:

protected function loaded(target:Sprite):void {
	// ... (all the other stuff, see above)
	registerFont( 'BoldFont' );
}
 
public static function registerFont( fontLinkageId : String ) : void {
	var fontClass : Class = getDefinitionByName( fontLinkageId ) as Class;
	Font.registerFont( fontClass );
}

If you just wanna embed fonts without any registering, you can also go like that:

[Embed(source='assets/fonts.swf' , symbol='BoldFont')]
public var BoldFont : Class;

Of course, instead of embedding everything, you can also load this dynamically (I mean, after all we have the Loader ready, don’t we? :) The advantage of that is that you can give your assets to some dumb Flasher and he can mess around with it without you having to recompile the app.

I know, this is all snippets and frickets, I’m just too lazy right now to build an example Flex project. Still I hope it’s of some use for one or the other.

Related posts:

1. Test Movie from Flex to Flash (easy way)
2. Test Flex/Flash throttled (aka Simulate Download)

In Flash we have a menu command called «Simulate Download» to see how things run at different bandwidth situations. But how to achieve this in Flex?

I’ve been using Sloppy for a long time. It’s little java app that can be started via a simple web click. It’s really easy to use and does very well what it does. For debugging your app (your flash website) throttled in Flex Builder simply follow these steps:

1. Open the Sloppy website
2. Click the little Sloppy icon:
   
   
3. A «sloppy.jnlp» file is downloaded. Open it if doesn’t open automatically.
4. The actual application will be downloaded and started. If it asks you to trust: trust! :-)
5. Enter the address of your html file in the bin-debug or bin-release folder. It should be a webserver address. I usually create a symbolic link of my project directory and put it into my local webserver directory.
   
6. Click «Go» – this will start the Sloppy proxy and open the page in your default browser. 
7. Copy the address from the browser window (usually http://127.0.0.1:7569/your/path)
   
8. You may close the window. Go to Flex Builder and open the project properties (right click on project folder, last item). In an Actionscript Project, switch to ActionScript Build Path.
    
9. Enter the copied address into «Output folder URL», clear the html name (e.g. App.html).
   
10. Click «OK» and you’re done. You can now Run and Debug as if your website was hosted on some server and you had a 256K ADSL connection (instead of your T1).

Note: I tried to automate the whole thing (with Ant of course) and succeeded to a certain limit. What I did was download Sloopy’s source code (java), modify it so it can handle more terminal attributes and build the  .jar file. This can be run on command line, which will start the sloopy server. So I created an ant file that does all that for me, but this ant file would only be cool, if it could also trigger the run or debug commands and modify the output folder url. I haven’t found a way (at least not a satisfying one) to do this, so I might just follow the manual street for once ;)

Another note: If you are windows user, you might wanna try this Firefox plugin: Firefox Throttle

Related posts:

1. Test Movie from Flex to Flash (easy way)
2. Develop in Flex Builder, publish in Flash IDE (Mac OS X)
3. Flash Debug Speed

<?xml version="1.0" encoding="UTF-8"?>
<project name="Publish" default="Publish" basedir="./">
	<!-- project specifics -->
	<target name="Publish">
		<concat destfile="build.jsfl">
			fl.getDocumentDOM().testMovie();
		</concat>
		<exec executable="open" failonerror="true" logerror="true">
			<arg line="build.jsfl" />
		</exec>
		<delete file="build.jsfl" />
	</target>
</project>

This tests the frontmost document in Flash IDE. (basically what does this plugin). Tested on Mac OS X 10.5.5 with Flex Builder Pro 3.0.2 and Flash CS4.

No need for FlashCommand. No need to alter the file for other projects. Just a super easy file for people with not too many requirements.

You can still go more advanced with something like that:

<?xml version="1.0" encoding="UTF-8"?>
<project name="Build Project" default="Publish and Test" basedir="../">
	<!-- common -->
	<property name="browser" value="Safari"/>
	<property name="log.path" value="${user.home}/Library/Preferences/Macromedia/Flash Player/Logs/flashlog.txt"/>
 
	<!-- project specifics -->
	<property name="fla.path" value="${basedir}/main.fla"/>
	<property name="swf.path" value="${basedir}/result.swf"/>
	<property name="test.path" value="http://localhost/projects/test/index.html" />
 
	<target name="Publish and Test">
		<antcall target="Publish"/>
		<antcall target="Clear Log"/>
		<antcall target="Open in Browser"/>
	</target>
 
	<!-- publish swf -->
	<target name="Publish">
		<concat destfile="build.jsfl">
			var sourceFile = "#FLA#";
			var outputFile = "#SWF#";
			var doc = fl.getDocumentDOM();
			if ( !doc || sourceFile.indexOf( doc.path ) &lt; 0 ) {
				doc = fl.openDocument(sourceFile);
			}
			doc.exportSWF(outputFile, true);
			<filterchain>
				<replacetokens begintoken="#" endtoken="#">
					<token key="FLA" value="file:///${fla.path}"/>
					<token key="SWF" value="file:///${swf.path}"/>
				</replacetokens>
			</filterchain>
		</concat>
		<exec executable="open" failonerror="true" logerror="true">
			<arg line="build.jsfl" />
		</exec>
		<delete file="build.jsfl" />
	</target>
 
 
	<!-- Open in local browser -->
	<target name="Open in Browser">
		<exec executable="open">
			<arg line="-a ${browser} ${test.path}" />
		</exec>
	</target>
 
	<!-- Clear Debug Log -->
	<target name="Clear Log">
		<concat destfile="${log.path}">                                                                                                            
		.: Sev Log File :.
 
</concat>
		<exec executable="open">
			<arg line="-a console '${log.path}'" />
		</exec>
	</target>
 
</project>

This has pretty much the same results as posted here.

I have created a Flex Project that contains all necessary files (fla, main class, build file). Just download and import into Flex:

Download Flex Project

Update: Mirko Sablijic sent me a Hello World project for Windows (he runs Vista):

Download Flex Project (Windows)

Related posts:

1. Test Flex/Flash throttled (aka Simulate Download)
2. Develop in Flex Builder, publish in Flash IDE (Mac OS X)
3. Flex Project – SVN Strategy

Once you got used to developing for Flash in Flex Builder, you hate to do any programming in Flash IDE. Still you sometimes might have to: Flex Builder won’t allow to publish into a FLA file. (There are of course many other reasons, like supporting older AS1/AS2 projects, we don’t go into that here.) Thanks to Eclipse’s ability to be customized, there are ways to make things at least a little easier. I give here a little overview of how I’ve set up my environment, based on several helpful resources I’ve found in the web.

1. Install FlashCommand
2. Install Ant

And for each project:

1. Create/modify Ant file
2. Create Actionscript project
3. Set up project and FLA file

What you need

• Flex Builder
• Flash IDE (CS3 or CS4)

Install FlashCommand

flashcommand is a python script by Mike Chambers that lets you compile FLA files from the command line using Flash IDE. Download it and put it wherever you want.

Install ANT

If you’re used to FDT (or Eclipse in any way) you may well know Ant. Ant is the premier build tool for any developers working in Eclipse, with many many cool possibilites to automate your workflow. Here’s how you install Ant in Flex Builder 3 Standalone:

1. Go to Help > Software Updates > Find and Install
2. Search for new features to install, click next
3. Select «The Eclipse Project Updates», click finish
   Note: If you do not have the option above click «New Remote Site» and enter «The Eclipse Project Updates» as the name and «http://update.eclipse.org/updates/3.3» as the url.
4. In Eclipse project updates look for «Eclipse Java Development Tools …» – it might be in «Eclipse SDK Eclipse 3.3.2» but this depends on what version you have installed and what version is currently available. Select it and click next.
5. Accept licence agreement, click next. Then click «Finish» to start download.
6. Once downloaded, click «Install all»
7. Restart Eclipse (you’ll be asked to)

Create Project

1. Create a new Actionscript Project in Flex Builder
2. Add a new «build» directory in the project root
3. Add your FLA file(s) and assets to the build folder and your source files to the src folder
   (I also strongly recommend adding external libraries to and «externals» directory and use svn:externals property on it, but that’s another story)
4. Add build paths. You have to do this at least twice:
   • In the Flash IDE for the FLA: Publish Settings > Actionscript 3 «Settings…». Don’t forget to add the src folder at least.
     Test your FLA once done. It should compile just fine.
   • In Flex Builder: Project > Properties > ActionScript Build Path. Add your external libraries here. This is used so Flex knows where to lookup your classes, it won’t actually be needed for compiling, because that’s what Flash IDE’s gonna do.
5. Now you’re almost done: you can edit your classes in Flex Builder and switch to Flash IDE to publish and/or test your movie. We’re gonna make this a little more comfortable with Ant and flashcommand.

Add Ant build file

1. Create a new file build.xml in the root folder and open it with Ant Editor (in Flex Builder aka Eclipse)
2. Edit the build.xml according your setup (see below for example)
3. Add build.xml to Ant View (Window > Other Views…)
4. Run an action by double clicking it in Ant View: there you go!! It will compile in Flash IDE and open in your browser for testing!

Sample Ant build.xml

	<?xml version="1.0" encoding="UTF-8"?>
	<!-- ====================================================================== 
	     Nov 28, 2008 1:37:54 AM                                                        
 
	     MyProject    
	     Compile in Flash IDE
 
	     sev                                                                
	     ====================================================================== -->
	<project name="MyProject" default="Compile and Run" basedir="./">
	        <!-- project specifics -->
	        <property name="browser" value="Safari"/>
	        <property name="swf.filename" value="MyProject"/>
	        <property name="html.filename" value="fla/index.html" />
 
	        <!-- Flash IDE Commandline compiler -->
	        <property name="python" value="/usr/bin/python" />
	        <property name="flash.command" value="/path/to/flashcommand" />
 
	        <!-- directories -->
			<property name="user.path" value="/Users/yourname"/>
 
	        <property name="build.dir" value="${basedir}/build" />
 
	        <property name="main.fla" value="${build.dir}/${swf.filename}.fla" />
	        <!-- paths -->
	        <property name="output.path" value="${build.dir}/${swf.filename}.swf" />
 
			<!-- you can also point to the file:///path/to/index.html -->
	        <property name="local.path" value="http://localhost/projects/MyProject/${html.filename}"/>
	        <property name="log.path" value="${user.path}/Library/Preferences/Macromedia/Flash Player/Logs/flashlog.txt"/>
 
	        <!-- Compile python flashcommand -e  -s build/MyProject.fla -o build/MyProject.swf 
 
	        usage: flashcommand -e | -c | -p [-v] [-x] (-s <sourcefile>) ([-o] <exportpath>) ([-t] <timeout>)([-d] <tempdir>) [-j]
 
	        Options and arguments:
 
	        -a : Prints version and about information.
	        -c : Specifies save and compact action. 
	        -d : Specifies temp directory that will be used for temporary files. Optional.
	        -e : Specifies export action.
	        -h : Prints usage information.
	        -j : Specifies that the generated JSFL file should be printed. If this option is specified, Flash will not be executed.
	        -o : Specifies the output file if -e flag is also set. Optional. If not specified, file will be output to same directory as source.
	        -p : Specifies publish action.
	        -s : Specifies source file. Required.
	        -t : Specifies timeout value. Optional.
	        -v : Specifies verbose mode. Optional.
	        -f : Specifies that the Flash authoring version installed is a version other than Flash CS3
	        -x : Specifies whether Flash should be closed after it is done processing. Optional.    
 
	        -->
 
	<target name="Compile and Run">
		<antcall target="Compile in IDE"/>
		<antcall target="Clear Log"/>
		<antcall target="Open in Browser"/>
	</target>
 
        <target name="Compile in IDE">
        		<echo>${flash.command} -e -c -s ${main.fla} -o ${output.path}</echo>
                <exec executable="${python}" failonerror="true" logError="true">
                        <arg line="${flash.command}" />
                        <arg line="-e " />
                        <arg line="-s ${main.fla} "/>
                        <arg line="-o ${output.path}"/>
                </exec>
        </target>
 
 
        <!-- Open in local browser -->
        <target name="Open in Browser">
                <exec executable="open">
                        <arg line="-a ${browser} ${local.path}" />
                </exec>
        </target>
 
        <!-- Clear Debug Log -->
        <target name="Clear Log">
 
        	<concat destfile="${log.path}">                                                                                                            
.: Sev Log File :.
 
</concat>
            <exec executable="open">
                    <arg line="-a console '${log.path}'" />
            </exec>
        </target>
	</project>

Update: Lee Brimelov just released a plugin for Eclipse, that provides this functionality (more or less) with a single click of an icon. It’s an alpha version, and you won’t have all the Ant flexibility (well, you could still install Ant), but you can avoid most of the installation hazzle, and that’s pretty cool. Unfortunately I couldn’t get it to work so far.

Update 2: It bugged me that every time I execute this action Flash would pop up. To work around that I slightly modified the FlashCommand script (it actually checks wether the FLA file is already open, and if so won’t call the open command). Also I had to leave away the -c option (save and compact), something I don’t need anyway. So now when you execute the command from Flex the following happens:

1. The little publish dialog pops up (Fla is exported to SWF)
2. The HTML file is opened in the browser (which comes to front), as well as the Console displaying the trace output

Also I have bound the «Launch last external tool» command in Flex Builder to a key combo. Now things run pretty smooth and as much satisfying as compiling via Flash can be. Btw, I also looked into this Eclipse plugin – as it seems the only thing it does is to tell Flash to «Test Movie» with the frontmost open document. That’s absolutely okay for most people, but I’m glad for the extra functionality I get with this solution (at the cost of more initial effort of course). Download here the modified FlashCommand: flashcommand.zip

Related posts:

1. Test Movie from Flex to Flash (easy way)
2. Test Flex/Flash throttled (aka Simulate Download)
3. Flex Project – SVN Strategy

There’s also one for Actionscript 3 (xpath-as3). But.. well… I wanted to go for some real speed! I like XPath a lot, but we now have native E4X selection in Actionscript 3, quite a different concept of node selection, and the conversion of XPath to E4X obviously results in quite a compromise in performance.

So all I need is a decent E4X parser. And hey, I found one! E4XParser from Digital Primates. It does its job really well, especially considering the very compact code it consists of. Thanks to some preparsing and caching, it’s also quite fast.

Still I thought I can do better :-) So I planted myself for a day (and a night) in front of my displays and hacked the hell out of it. The result is a little library which does pretty much the same thing as E4XParser, though pretty much more and a little faster too (15% to 50%). It’s about half as fast as the native E4X selection (once parsed). You can do nearly anything you can do with E4X. Use it like this:

import com.betabong.xml.e4x.E4X;
var result : XMLList = E4X.evaluate( xmllist , "author.( name.@last == 'Jobs' )" );
 
// E4X.evaluate( source : XMLList , expression : String ) : XMLList

 
If your source is XML, just do XMLList( xml ), if your result should be xml, do xml = result[0]

Test it here

Restrictions: You can’t use AND/OR in comparisions. So, this won’t go: author.( name.@first == ‘Steve’ && name.@last == ‘Jobs’ ) – though this is only a real limitations for OR. do this for AND: author.( name.@first == ‘Steve’ ).( name.@last == ‘Jobs’ ).

What you can do: Yes, you can do quite advanced stuff like author.( name.@first == name.@last ) or car.@rating.average() (one of the few proprietary functions I added). Or even

*..car.( @brand.toLowerCase() == 'volvo' ).( parent().( localName() == 'group' ).@rating > @rating )

– a weird example, I admit, but fancy, ain’t it? :-)

This is the first time ever I’m releasing part of my library as Open Source (MIT licence). As soon as I’ll find some time (and if I see any interest), I’m gonna put this into Google Code, so everybody can easily checkout and participate. Until then download it from here:

Download (zip 13kb)

Related posts:

1. Simplicity follows Performance – parsing Strings in Actionscript 3
2. Alchemy – THE cool new flash feature!
3. Nested inner functions can be evil

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" creationComplete="create()" click="destroy()">
	<mx:Script>
		<![CDATA[
			private var dispatcher : Sprite;
 
			private function create() : void {
				dispatcher = new Sprite();
				// listen to inner function
				dispatcher.addEventListener( Event.ENTER_FRAME , function( e : Event ) : void { trace( e.type ); } );
			}
 
			private function destroy() : void {
				// this should free created dispatcher from memory
				dispatcher = null;
				// what we would need is:
				// dispatcher.destroy() or dispatcher.removeEventListener( Event.ENTER_FRAME )
				// or dispatcher.removeAllEventListeners()
			}
		]]>
	</mx:Script>
</mx:Application>

The dispatcher will just live on. The mean thing is that in method «destroy» we don’t even have a chance to get rid of the sprite anymore – it just lives on and on (and dispatches its event every time it enters a frame to the listener function.) So 3 objects will just not be freed in memory because of our inner function listener: 1. the dispatcher object, 2. the listener function (the inner function) and 3. the creating object, because the listener function (or its method closure) is bound to the creating method create() scope.

We also can’t use the addEventListener’s flag to use weak references, because the listener method wouldn’t have any other references and would «dye» instantely. So what you should do right now is something like that:

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" creationComplete="create()" click="destroy()">
	<mx:Script>
		<![CDATA[
			private var dispatcher : Sprite;
 
			private function create() : void {
				dispatcher = new Sprite();
				dispatcher.addEventListener( Event.ENTER_FRAME , handler );
			}
 
			private function destroy() : void {
				dispatcher.removeEventListener( Event.ENTER_FRAME , handler );
				dispatcher = null;
			}
 
			private function handler( event : Event ) : void {
				trace( e.type );
			}
		]]>
	</mx:Script>
</mx:Application>

That’s clean code. Good bye dispatcher, good bye sprite! But sometimes it can be quite difficult to maintain this. I personally would wish that actionscript objects, especially the EventDispatcher class, would provide a destroy() method. Calling it gets rid of all event listeners and also would unlisten to everything it has listened to. And for DisplayObjects it would also perform other operations like removing itself from its parent and destroying all children.

I’d also like to see the following method like this in EventDispatcher:

EventDispatcher.removeListener( type : String = null , listener : Function = null , useCapture : Boolean = false );
 
// so this would remove all listeners
EventDispatcher.removeListener();
 
// and this all listeners to enter frame
EventDispatcher.removeListener( Event.ENTER_FRAME );

I get around many issues by implementing something like a IEventListener interface:

interface IEventListener {
function listenTo( dispatcher : IEventDispatcher , type : String , listener : Function , useCapture : Boolean = false ) : void;
functon unlistenTo( dispatcher : IEventDispatcher , type : String , listener : Function , useCapture : Boolean = false ) : void;
function destroy() : void; // will remove myself as event listener from all registered dispatchers
}

Way to go :-)

Related posts:

1. Weak Method Closure
2. Garbage Collector and Dictionary
3. Metatunnel 1k Demo: AS vs. JS

Finally I was forced to rethink this strategy because I wanted to let other people work on a project. As many actionscript projects, this one also heavily relies on external libraries, most of them hosted by Google Code, another one being my own (closed) lib. So should I tell people: «hey, just svn checkout from here and there and then relink the libs in the project properties but don’t check in the updated settings for christ’s sake!»No. Too shaky, really.

Fortunately, SVN provides a fucking cool way to solve this issue: svn:externals. Ha! This is so awesome, you won’t believe it ;-) Okay, here are the steps to follow (on a mac at least):

Create a flex project:

• project
  • html-template
  • src

Add a new directory:

• project
  • html-template
  • src
  • externals

Now put this on your svn, either by svn add or by putting in the repos and checking out again (well.. just as you did). If you’ve already got bin-debug or bin-release directories, just remove them on the repos and svn update (they are created with each publish in flex).

Now let’s say our project resides in ~/Documents/projects/project (path to project). Do the following in Terminal:

cd ~/Documents/projects/project/externals
svn svn propedit svn:externals .

This should open an editor (in my case I’ve defined textmate as my editor by doing:)

export EDITOR='mate -w'

Enter the following (example libraries):

caurinatweener http://tweener.googlecode.com/svn/trunk/as3/
as3corelib http://as3corelib.googlecode.com/svn/

You can also add a specific release:

caurinatweener -r23 http://tweener.googlecode.com/svn/trunk/as3/

(in TextMate save and close, if you use vim you know what to do anyway)

Now comes the magic part:

svn up

This will checkout all defined libraries into externals/xyz!! you do svn commit and now every time somebody checks out your project (or your externals directory) all the libs will be checked out automatically! I think this is just fucking awesome! :-)

Now in Eclipse all paths to your external libraries will be relative to the project (of course you have to add the libs there or change the paths – you should know how to do that ;))

Now all we need to is ignoring bin-release and bin-debug. We don’t want these directories to be in our svn repos:

cd ~/Documents/projects/project
svn svn propedit svn:ignore .

enter a list of directories or files to be ignored. in our case:

bin-debug
bin-release

That’s it! Thanks, svn!

Related posts:

1. Develop in Flex Builder, publish in Flash IDE (Mac OS X)
2. Test Movie from Flex to Flash (easy way)
3. SVN Hook – auto-upload to FTP