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

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