I’ve been writing some Flash components recently. I really like how they designed the component framework, and I’m curious to see how Flash 9 will improve on it. But they really need to do something about the Write->Test cycle that you have to use.

Now keep in mind where I’m coming from. I’m used to developing Java or C++ GUI apps, where you have an Ant XML or Makefile that runs through your dependency tree and builds your app. Then you run it and see what happens with your latest edits. Not so for Flash components.

First, you need your FLA file with any symbols and objects your code is going to reference, and an object representing the component. OK. Cool.

Next you have a separate .as file with your code. Still cool.

To build, you right click on the component symbol in the FLA and select “Convert to Compiled Clip”. You then get a new symbol with your compiled component.

Now we can run, right? Mmmm.. No.

You’ve got to have a separate test FLA sitting around first. Then you copy your compiled component from the component FLA library to your test doc’s library. If you already have a previous one there, you have to tell it to overwrite it with a dialog box. Then, assuming the symbol is on the stage, you can run it. Pheeeew.

Admittedly, it’s not that hard. But all this mousing around each time I want to test is very annoying. I want a more efficient update pipeline.

Does anyone have a trick they use to make the Write->Test cycle faster?