I want to get your thoughts on overhauling the current animation code. It seems to me that you have to include an awful lot of code to do something as simple as a slide or a wipe on a layer. Looking at the way the current animation extensions are created shows that apart from the run methods they are all pretty similar - would we not be better with a new animation class ?
that way our animation code could inherit methods such as stopAnimation(), setLoops() etc etc... leaving us with just a bit of setup in whatever.PlayAnimation() and then the actual run(). Also a few of the 'core' animations are still missing - wipe, grow and glide for instance. I have seen a few variations of each pass through the list - should we not choose one of each and add it to the main distribution? Anyone coming from another API such as DynAPI1 would consider them standard, and I imagine Dan will be adding them to his new API. If we add the code from richard's site for wipe/glide then they can be maintained/tested/improved along with everything else and we gain a pretty complete animation system. I'm planning to spend tomorrow experimenting with the latest stable release to see what I can come up with. I'm open to your opinions/rocks :) _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[email protected]/
