Well MTASC seems to be the buzziest technology in the Flash world these days. Jester just coined the acronym FAME – Flashout, Eclipse, ASDT, MTASC. (I know he didn’t come up with the process, but I think he was the first to acronymize it.) While I’m sure the Eclipse route is great, I myself couldn’t be pried from PrimalScript, and have already posted my workflow here in a couple of other posts. Not to be outdone on acronyms though, I came up with one that describes my setup: PB & JaM: PrimalScript, Batch-files, JSFL and MTASC!
One thing I’m loving about the batch file approach is how you can customize your compile, even compiling and running multiple swfs. For instance, I’ve blogged about other solutions where I need to compile a swf, then compile another swf and load the first into the second. With MTASC this is such a breeze. You just write your batch file so that it compiles the loaded swf, then compiles the loader, and then, only if everything compiled ok, it runs the loader swf. In fact, in many cases, I don’t need to compile both, so I just comment out the line for the one I don’t need to recompile. Thus the batch file becomes sort of a make file.
Another thing I just saw and I’m going to try to fit into my flow is this swfmill xml generation tool. Since this is all command line stuff, it should be able to be dropped right into my batch file. I’m liking where this is going.