On Friday, February 28, 2003, at 12:08 AM, Sean A Corfield wrote: >> With Flash on the other hand the Directory Structure is no longer the >> starting point for organizing the code. > > It can be. Flash development seems to be shifting toward having almost > the 'code' in real ActionScript files - on the file system and > organized into components and libraries that you then assemble into > movies. Most of the work our Flash application development team is > doing uses single frame movies (so the whole timeline nonsense can be > effectively ignored) than include one or more .as files. Everything of > importance lives in human-readable source code, under version control.
This is definitely the way to go. I have even had good luck with using a C pre-processor and another pre-processor called m4 to assemble ActionScript files from several other ActionScript files. The idea is to include one external .as file for each movie. That .as file has movie-specific code which makes use of other included ActionScript objects. The pre-processing is done to ensure that you don't include the same low-level libraries or objects multiple times, unnecessarily increasing the size of your movie. Christian ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
