Hi Aldo,
>- flex does address some issues that are the main reason behind many lib efforts (AnimationPackage for instance). It would not be advisable to use a tweening engine other than the one included in Flex for the sake of simplicity and mantainability. Not to mention the work done by layout manager As far as I know AnimationPackage does use the same tween engine like Flex does. (for time based tweening, it's mx.effects.Tween) Anyway, if you have some ideas how to improve AP, let me/us know. Best, Alex http://www.alex-uhlmann.de/flash/animationpackage/unstable/index.htm
