"Is it okay to build some animations using the timeline?"
Surely it's as 'okay' to build timeline animations as it is to build scripted animations! The decision is simply based on what best suits the requirement in terms of efficiency to build, the production values of the finished animation, how extensible and maintainable it needs to be e.t.c. For example, I'm currently working on a small Flash campaign microsite (my role is purely ActionScript development). It has a short intro animation (aaarrrggghh!) where the camera flys through a 3D keyline landscape into which an illustrator has dropped hand-drawn and photographic assets. Then a navigation animates in and from there we have transitions between the various pages. The content of the site may change in the future, more pages may be added and all the textual content needs to be translated. the intro animation will be identical across all versions of the site. Given the 'requirements' for the various parts of this site, it makes complete sense to build the intro animation on the timeline (it would take a very gifted coder to code it!) and build all the navigational animations and page transitions through code. Marcelo, I completely understand why you're asking the question but just remember that just because you *can*, doesn't necessarily mean you *should*. Do whatever seems to work best for your project after you've considered all the requirements. Also, i'll echo Adam's advice to keep things neat, organised and well labelled - it is one of my pet hates to open someone elses project only to find it looks like it was produced by a lunatic on acid! Happy keyframing - I'm off to script some tweens! Adrian P. On 6/28/06, Adam Pasztory <[EMAIL PROTECTED]> wrote:
I am an "OOP supporter", but I'll be the first one to tell you that there's nothing wrong with using timeline-based animations in your project. In fact, I encourage it. You're being true to the spirit of Flash. *However* if you want the timeline-based animations to integrate well with your OOP Application, you should be careful to follow good practices, including: 1. Use consistent naming conventions for all instances. 2. Put all your code on the first frame, on the top level. 3. Keep your layers well organized. 4. Keep your library well organized. In my experience, the greatest benefit of OOP is not extensibility, but maintainability. I have more comments on these issues here: http://www.pasz.com/blog/2006/03/oop-just-one-reason-why.html http://www.pasz.com/blog/2006/04/flash-dev-gotchas-9-dont-over-engineer.html -Adam _______________________________________________ Flashcoders@chattyfig.figleaf.com 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
_______________________________________________ Flashcoders@chattyfig.figleaf.com 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
