Yeah, regarding the BetweenAS3 demo, they tweened Sprites with TweenMax but
Points with BetweenAS3. Sprites use 12.6 times more memory and require about
2.2 times more processing power to update x and y properties! Very
misleading.
As for the comment about GTween being stricter and more object oriented,
that's a common misperception due to the fact that many folks like to use
the static to() and from() methods in TweenLite/Max to avoid gc chores.
TweenLite/Max are equally object oriented, though - you can use this syntax:
var myTween:TweenLite = new TweenLite(mc, 1, {x:100, y:200});
myTween.play();
myTween.currentTime = 0.5;
myTween.reverse();
...etc.
Speed tests are available at http://www.greensock.com/tweening-speed-test/
or do your own.
But like Steven said, for most use cases speed won't be the biggest factor.
Other things should be considered like syntax, documentation, support,
reliability, file size, architecture, and features.
Happy tweening.
Jack
-----Original Message-----
From: Steven Sacks [mailto:flash...@stevensacks.net]
Sent: Thursday, June 24, 2010 3:37 PM
To: Flash Coders List
Subject: Re: [Flashcoders] Tweener still in development
If I recall correctly, one of his points was that they used Vectors in 10
for
theirs and Arrays in 9 for Greensock's for their comparison, which is
obviously
biased.
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
