I used to do that. It's great because you avoid _root altogether, and never have collisions with other content there.
The downside I ran into is if your SWF is loaded into another one, you need to remember to do: MyLoader.content.someApp.method vs. MyLoader.content.method And since you can't enforce this via interfaces (the name of the movieclip app thing), it's just 1 small thing. ----- Original Message ----- From: "Manuel Saint-Victor" <[EMAIL PROTECTED]> To: "Flashcoders mailing list" <[email protected]> Sent: Friday, February 17, 2006 5:25 PM Subject: Re: [Flashcoders] coding the main stage as if it were a class I've seen that technique used and wondered how well it would work. So then you would have that class extend MovieClip-right? Is there any weirdness that comes up that I would want to look out for in this case? Would you have the constructor in the class file just call init(); and do the setup in there? _______________________________________________ [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 _______________________________________________ [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
