I just uploaded a new version of FlashCommand for OS X (.90), which fixes some issues with running with Adobe Flash CS3.

You can grab the latest version from here.

Thanks to rquigley and Patrick Palmer for helping to track down and fix a couple of issues.

I have been getting a bunch of email that the links to my FlashCommand for OS X download was no longer working. FlashComamnd is a command line tool written in python, that allows you to launch Flash authoring to compile FLAs.

Well, I found the files, and have re-uploaded them. You can find all of the information, including how to use and download the tool from here.

I have not tested this with Flash CS3, so if it doesnt work, let me know on the FlashCommand page.

Update : After making the post, I just decided to create a google code project for it, which you can find here. If you run into any issues, then post an issue on the project page.

I have fixed all of the download links for my FlashCommand command line compilers (and source).

You can download them from:

OS X

Windows

Sorry for any hassle. Thanks to Chafic Kazoun for helping me locate some lost files.

I have just uploaded the source code for the Windows version of my FlashCommand command line compiler for Flash MX 2004. You can download the source from here.

I haven’t touched this code in a long time, and it is not documented much. However I wanted to get it out to the community in case anyone wanted to add features or fix bugs.

Robin Debreuil, Owen van Dijk both helped me with some items and contributed some code.

You can download an OS X version of FlashCommand (which includes source) from here.

The only issue that I know of is that the installation code does not currently work.

Anyways, if you make changes or fix anything then post it in the comments. I am interested to see what (if anything) people do with this.

I have built an OS X version of my FlashCommand command line compiler for Flash MX 2004. This uses the Flash MX 2004 extensibility layer to allow you to compile Flash files (FLA) from the command line.

It has a ton of options, and will also catch and redirect any ActionScript compile errors to stdout.

Update : I have moved the source and downloads to its own Google Code project which can be found here.

Here is the usage info:

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.
-x : Specifies whether Flash should be closed after it is done processing. Optional.

Requires that python is installed on your system.

To install, download the file and copy the flashcommand file to somewhere within your path. Make sure to make it executable by running the following command:

chmod 755 flashcommand

If you find any bugs, or have questions or suggestions, then post them log an issue on the project page.

I am working on an OS X version of my FlashCommand command line compiler, and I ran into a problem of how to tell Flash to run a JSFL file from the command line. Gary Grossman came to the rescue with the answer.

You have to use AppleScript to tell Flash to load the file. Here is an example:

osascript -e ‘tell application “Flash” to open alias “Mac OS X:tmp:myTestFile.jsfl”‘

If you are calling this from a script that uses Unix file paths, then you can use the following command:

osascript -e ‘tell application “Flash” to open posix file “/tmp/myTestFile.jsfl”‘

This will open Flash and have it execute the specified JSFL file.

Community MX has posted an article on integrating the PrimalScript editor with Macromedia Flash. It includes a video tutorial on how to set up my FlashCommand command line compiler to compile directly from PrimalScript.

You can read the entire article here.

Well, I am finally releasing the first public version of FlashCommand. FlashCommand is a command line compiler for Flash MX 2004 Pro.

I am sorry it took so long to release, but I have been super swamped. I also ran into a bug where the installer no longer worked (it errors when trying to automatically set the path environment variable). This bug delayed the release, and I ended up just removing the installer. Hopefully, I will have time soon to track the issue down, and release an updated version with the installer.

IMPORTANT : This is something that I did in my own time, and is not supported by Macromedia. Use at your own risk. If you run into any issues (and you will), please post them in the comments. This will make it easier for me to keep track of issues and suggestions.

Here is a screen shot of ActionScript code being compiled from EditPlus. Notice that it catches the output (it will also catch compile errors if they occur). Btw, if anyone can figure out how to get this to work with SciteFlash, post the info in the comments.

Note, this is Windows only and requires the .NET framework. Sorry about that. I will try to make a portable version in the future.

Download FlashCommand

Download FlashCommand Source

Here is the usage information (from the readme):

FlashCommand.exe -e | -c | -p [-q] [-v] [-x] [-q] (-s <sourcefile>) ([-l] [<logfile>])
	([-o] <exportpath>) ([-f] <flashpath>) ([-t] <timeout>)

-version : Prints out information about the program.
-help | Prints out usage information.

-e : Specifies export action.
-c : Specifies save and compact action.
-p : Specifies publish action.

-l : Specifies whether output should be logged to a file. Optional. Takes an optional
	param specifying the path to the log file. If not specifies, log files will be
	place in \log
-q : Specifies quite mode. Optional. If specified, no output will be written to console
	(although it may still be logged).
-v : Specifies verbose mode.
-d : Specifies temp directory that will be used for temporary file.
-s : Specifies source files. Required.
-o : Specifies the output file if -e flag is also set. Optional. If not specifies,
	file will be output to same directory as source.
-x : Specifies whether Flash should be closed after it is done processing. Optional.
-k : Specifies whether the temp jsfl file should be deleted. Optional.

-f : Specifies Flash executable path. Optional.
-t : Specifies timeout value. Optional
-d : Specifies temp directory. Optional.

Thanks for Robin Debreuil, Owen van Dijk who provided valuable input and help.

Download FlashCommand

I am going to release a Flash Command line compiler that I built a while ago. It works with Flash MX 2004, and uses the extensibility layer. I just need to test a few things and make sure it still works. Assuming no major issues, I will release it in a couple of days.

Couple of notes:

• Written in C#, which means it is Windows only.

Written by me on my own time, which means that it is use at your own risk.

Here is the usage information:

FlashCommand.exe -e | -c [-q] [-v] [-x] [-q] (-s ) ([-l] []) ([-o] ) ([-f] ) ([-t] )

-version : Prints out information about the program.
-help | Prints out usage information.

-e : Specifies export action.
-c : Specifies save and compact action.

-l : Specifies whether output should be logged to a file. Optional. Takes an optional param specifying the path to the log file. If not specified, log files will be place in \log
-q : Specifies quite mode. Optional. If specified, no output will be written to console (although it may still be logged).
-v : Specifies verbose mode.
-d : Specifies temp directory that will be used for temporary file.
-s : Specifies source files. Required.
-o : Specifies the output file if -e flag is also set. Optional. If not specifies, file will be output to same directory as source.
-x : Specifies whether Flash should be closed after it is done processing. Optional.
-k : Specifies whether the temp jsfl file should be deleted. Optional.

-f : Specifies Flash executable path. Optional.
-t : Specifies timeout value. Optional
-d : Specifies temp directory. Optional.