It depends on how many files you want to manage. I think from a OOP perspective, you would want to have one fla and two doc classes. As long as it doesn't effect your timeline (or headaches) to get everything to work together.
Nathan Mynarcik nat...@mynarcik.com www.mynarcik.com <http://www.mynarcik.com/feed/rss.xml> <http://www.twitter.com/NMynarcik> <http://www.facebook.com/pages/Nathan-Mynarcik-Interactive-Web-Developer/265263144230> <http://www.linkedin.com/in/nathanmynarcik> On Mon, Dec 13, 2010 at 3:28 PM, Mendelsohn, Michael < michael.mendels...@fmglobal.com> wrote: > Hi list... > > I'm developing an AIR app that will have a companion online swf. The two > pieces share much of the same code to render the UI and its various > behaviors. > > I haven't started building the online swf yet, and I'm approaching the > point in the AIR app where I am dealing solely with the AIR apis. Would it > make sense to have just one fla, but switch out the document class when it > comes time to publish each piece, or just make two flas? I'm looking for > best practices in how to do this. > > Thanks! > - Michael M. > > > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
