If you're working on large projects: A while back, I think it was Ryan Matsikas (I hope I spelled his surname right) that said something really profound and which I try to apply to every Flash project I work on:
Just because Flash/ActionScript is getting more and more powerful and potent with every release doesn't mean we should use it for everything in a web RIA project. If you're working with a good back-end, database developer or software engineer, your app is better off leaving the "heavy-duty stuff" to back-end or server-side, letting Flash to do what it's best at - dealing with the front-end. We seem to forget this as Flash developers and spend too much time cooking up ways of letting Flash do things that a more powerful server-side language can do a lot faster without breaking a sweat. Why does the server-side do it faster? For one, it's got (often times) more RAM to play with... Just my 2 pence. /Johan On 12/20/05, Johan Lopes <[EMAIL PROTECTED]> wrote: > LOL. That's a great title for a Flash book. Quick, let's contact a publisher > :) > > /Johan > > On 12/20/05, Mike Boutin <[EMAIL PROTECTED]> wrote: > > Does anyone have any links on stuff "Not to do" in flash that maybe > > cause the plugin to slow down or halt. Maybe even some best practices > > when working on large projects? > > > > > > Thanks! > > > > > > _______________________________________________ > > 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
