Article written

  • on 14.09.2009
  • at 08:19 PM
  • by mich

Another Flash-FlexBuilder workflow: The basics 1

Sep14

You probably remember the mtasc compiler from the old AS2 times. One major benefit was the speed because it didnt compile the graphic assets all over again. With a right setup you can archive the same thing with Flash and Flex.
The key is the swc export feature of the Flash IDE:

Picture 8

If you export your MovieClips from Flash as Classes:

Picture 9

and add the swc in the Flex Builder as library:

Picture 10

you can access/create them by simply create a new instance:

Picture 12

You have to recompile (ctrl-enter in flash) the swc when you change something in your graphic assets. But in the FlexBuilder if you compile it just recompiles the source and includes the assets from the swc.
This workflow looks great in the first moment because you have autocomplete and strict typed access to the assets on the ControllerBarDraft. If you like to play around with the setup I made a simply actionscript FlexBuilder project that you can download here.

To use this workflow in an more advanced way, wait for the next article: Another Flash-FlexBuilder workflow: The Draft. Where I describe problems of this workflow as a nice workaround. Stay tuned.

subscribe to comments RSS

There is one comment for this post

  1. [...] my introduction article about my workflow I like to dig in a bit deeper and describe you my way of working with Flash and [...]

Please, feel free to post your own comment

* these are required fields

Developed by Dariusz Siedlecki and brought to you by FreebiesDock.com