And if you're going to be working on a collection of different external .as files, it's always a good idea to look at using a versioning system such as Subversion/SVN - http://subversion.tigris.org
Versioning systems aren't a great deal of help with binary files such as .flas, but are a great help with text files such as .as files, .xml files and anything else you have lying about. Subdividing your .fla file into a number of smaller files as Zeh suggests, and making your classes external then stuffing the whole thing in Subversion is about the best solution that you can get. It's not ideal - multiple people working on .flas never is. An alternative strategy is to use MTASC and Swfmill to generate all your .swfs from text-based sources files (.as files and .xml files) and not to have any top-level .fla files at all (although you'd probably need .flas for some graphical assets). That, combined with Subversion, can be a lot easier to control. Sharing binary source files between people is always a pain - sorry! Cheers, Ian On 6/15/06, Danny Kodicek <[EMAIL PROTECTED]> wrote:
Not forgetting external script files too, of course. Danny
_______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
