The new Tweener seems to be a better implementation (now uses Classes and no longer uses MovieClip.prototype, etc..), but I haven't
tried it out yet.
Proper documentation seems to be missing however:
http://code.google.com/p/tweener/wiki/Documentation
Not even half of the methods are documented.
The download does not include any documentation, just the class files.
A few things I was looking for:
support for adding/removing event handlers --> addEventListener(event, handler)
support for custom easing rather than the predefined ones (robert penner's).
support for parallel and sequence tweening
Just as a small addendum, and to make things a bit more clear:
I agree documentation is a must. The current Tweener documentation
sucks. It's being rewritten so it can be a real downloadable+IDE
documentation; using the wiki for documentation was a mistake I realized
later. The html docs available through subversion (which are the same
documentation that will be available as a normal download) already
feature more content than the wiki, although it's still missing stuff.
Feature wise:
Event handling is done on a tweening basis and not on object/instances
-- meaning they're added with addTween() but you can't assign once the
tween is done. There are no tweening instances. It's actually one of the
main points of Tweener: being simple. This means you won't be creating
instances of everything, then adding a bunch of events or callbacks
later -- just one line per tweening. You can create the object on
several different lines if you wish, but it's not usually the point.
Custom easing is done by creating and using any function you'd wish and
it follows the 'classic' function parameter order as defined by Penner's
own functions (and other easing equation builders available out there).
You're right in the sense that it accepts string parameters (built-in,
default functions) or function reference themselves.
Tweening is parallel by default and sequence tweening is done by using
delays, which may be a positive or a negative feature depending on your
point of view (like most of the points above actually).
As a final thought... there are moments where you require one entire
ecosystem of OOP patterns just for one single tweening to take place.
But that's not what Tweener is trying to do. That's why it has a focus
in being simple (you don't create instances for everything), modular
(you can attach property modifiers and other transitions to the engine)
and flexible (loose syntax by way of anynoymous objects) that won't be
the best for everyone.
That's also why I believe tweening options are more bound to personal
preference and personal needs than anything; one can't do it all and
still keep syntax consistency. I'm a firm believer that a solution that
fits all will be a solution that fits none, or several different
solutions inside itself that are very different from each other. Hence
why it's a great thing to have these many more options in tweening
extensions/classes for as2, as3 and beyond.
Zeh
_______________________________________________
[email protected]
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
