BIT-101 [2003-2017]

So I am developing an app which loads some xml and parses it. Based on what’s in the xml, it loads another swf, and passes part of the xml over to the loaded swf. So right now I’m trying to develop the loaded movie. But I can’t just test it on its own. It really needs to be loaded by the other movie to make sure it’s integrating all just right. So this was my workflow:

1. Alter the code in PrimalScript and save it.
2. Go over to Flash and select the loaded movie fla.
3. Test that to generate the swf.
4. Close the swf.
5. Switch to the loading fla.
6. Test that to generate that swf, which then loads the loaded swf.

Frustrating.

As hell.

JSFL to the rescue. I replaced my compile.jsfl file that I have PrimalScript set up to run on F7. Here it is now:

fl.outputPanel.clear();
fl.documents[0].save();
fl.documents[0].publish();
fl.documents[1].save();
fl.documents[1].testMovie();

And here’s my new work flow:

1. Alter the code in PrimalScript and hit F7.

Flash saves and publishes the loaded movie (document 0), then saves and tests the loading movie, which loads the newly created swf. Gotta love it.