Indeed, the 2 first recommandations to start to write "clean" Flash code are : - stop thinking procedural programming > think OO programming and package all you class in external .as files, You might check www.gmodeler.com for UML ActionScript class modeling. - stop thinking timeline-based programming > think event-based programming with broacaster/listener mechanism. There is an undocumented ASBroadcaster class, but the best is to rewrite it (you can find a Broadcaster.as class in the Petmarket sample application). A broadcaster would act as the controller if you use a Model View Controller approach.
Don't forget : - the Flash Components to encapsulate and build reusable client components, (you might check the new Branden Hall's Outlet component in order to build external shared components libraries : http://www.waxpraxis.org/downloads/outlet.zip) - the drawing APIs to dynamically build your interface. At the end, you'll spend most of your time coding ActionScript. That's why a lot of people are using an external ActionScript editor. It might be DreamweaverMX or SciTE|Flash (excellent! http://www.bomberstudios.com/sciteflash/) Benoit Hediard www.benorama.com > -----Message d'origine----- > De : Sean A Corfield [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 28 février 2003 06:08 > À : CF-Talk > Objet : Re: OT - Fusebox for Flash? > > > On Thursday, Feb 27, 2003, at 09:55 US/Pacific, dwayne 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. > > > If you are worth your weight in code, I'm sure you can agree that all > > well developed applications require order and organization. > > Agreed. > > > With out the directory we are left to depend on Timelines and > > Libraries. > > You can pretty much ignore those and work just in ActionScript, > organizing your files and classes in directory structures as needed. > > > The whole timeline concept seems like HTML pages that cascade and > > disappear and reappear, that underlay and overlay, and.... It's just > > confusing to me. > > I agree that timeline-based programming is a major paradigm shift for > many developers. Fortunately it can be pretty much ignored :) > > Sean A Corfield -- http://www.corfield.org/blog/ > > "If you're not annoying somebody, you're not really alive." > -- Margaret Atwood > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
