yeah, horses for courses... if you want to better encapsulate stuff, i find it easier to work with arrays (in fp10 vectors) and pass them around if needs be. tying your code to specific timelines gives you more work to do if you want to reuse that code imho.
for something quick and dirty in timeline code though that you know you don't want to reuse then whatever's clever. Mr. Jason Merrill is right though about having cleanup functions for whatever you create being a great way to not getting into trouble later i reckon... On 23 February 2010 20:47, Merrill, Jason <[email protected]>wrote: > >> Doesn't storing them in an array create a set of references that will > need > to be cleaned up? > > Absolutely (if the app performance even needs cleaning up and/or the > items are even removed). But that's easily taken care of with a cleanup > function. So for small uses, as I mentioned, may not be worthwhile, but > I am thinking long term scalability. I just hate to see people default > to dynamic naming all the time when architecturally, using arrays as > storage is better in the long run. For this, the dynamic naming would > be fine. I'd just be careful to make it a habit for everything. > > > Jason Merrill > > Bank of America Global Learning > Learning & Performance Solutions > > Join the Bank of America Flash Platform Community and visit our > Instructional Technology Design Blog > (note: these are for Bank of America employees only) > > > > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
