Have a look at ARP http://osflash.org/projects/arp
With ARP you don't use the main timeline at all. A base MovieClip/Class acts as the root (because of the lack of being able to assign a class to the main stage - without hacks). The base Class is usually called "Application" and all the content goes in there. The Application MovieClip is the only thing on stage. Content inside the Application is made visible/invisible as needed. This comes close to using the Form fla document type (which you can also use with ARP by the way), but without actually using the v2 component framework. Here's what an Application looks like in the IDE, including the Project Panel. http://muzakdeezign.com/arp/arp_application.jpg There's no ActionScript in the FLA (part from some stop actions here and there). Everything goes in Classes, assigned to MovieClips. This kind of approach easily 'translates' into Flex as well, using a ViewStack container with custom MXML Components. Oh, and classes should be named after their purpose.. - Application, Home, Products, Contact, etc.. for Form/View type classes. - ScrollBar, MenuButton, Preloader, etc.. for control type classes. regards, Muzak ----- Original Message ----- From: "misa" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, May 29, 2007 5:02 PM Subject: [Flashcoders] Site structure with classes > Hello group, > I'm wondering is there something like 'the best way to structure a flash > site'. How should the classes be named, should we use > frames in the root timeline and should we use frames at all (expect for > animations)? Any advice or help is welcome! > > Thanks, > Mihajlo Nikolic _______________________________________________ [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
