Attention: you're visiting an archived version of this post on my old website. Click here to view this same post on my new website.
In 2003, I was pretty pissed with the tweening extensions available at the time. I found them to be too clumsy and overly complex, requiring a lot of code just to create a single transition. I didn’t want to use 3+ lines just to change the way a button looked like when it was rolled over. After giving up on the task to find a simple extension based on Robert Penner’s equations, I decided to create such an extension for my own use. Called MC Tween, it was very straightforward; it didn’t create instances, didn’t allow you to rewind anything, nor did it allow you to create then fire animations separately. And in fact, it didn’t intend to; it just created a simple tweening, played it on the specified time, and called it a day.
To my surprise, it quickly got bigger than I expected when everybody started using it at my workplace, and then when it became the most popular prototype on good old proto.layer51.com with no “marketing” whatsoever. It didn’t even have any documentation, all I used to say was “look at the source code, the methods are there”. MC Tween evolved a lot on the following years, getting a small website of its own (one with proper documentation!), and getting really popular with some folks. I still receive email about it almost everyday, and I like to believe it was the first of its kind – using simple code to create tweenings in a fast and straightforward way, inspiring designers and programmers alike to stop using the timeline and adopting code-based tweening almost exclusively.
With that said, well, I have something to confess…: I haven’t been using MC Tween for more than one year, including on all my commercial work.
The reason is, I’ve been slowing developing a new tweening thing. Now, instead of a collection of prototypes that extend the existing classes by way of AS1 code and AS2 hacks, it’s a real static class, working the same way on both AS2 and AS3. And while it still follows the concept of simple, one-line tweenings, it’s has a slightly different syntax. It’s called caurina.transitions.Tweener, or just Tweener.
Now, to be honest, there’s still a bit left to go for Tweener to have as many features as MC Tween has. For example, Tweener doesn’t have native filter tweening, as we’re still deciding on the best syntax approach. However, at the same time, there’s a lot of positive things about Tweener, and because of this, I feel it’s about time Tweener is publicly announced. So there it is. I don’t work with MC Tween anymore, and I won’t change it anymore. It was a good extension, and it still is, but I have thought a lot about code-based tweening for the past 4 years and I have reached the conclusion that there’s a slightly better approach; that’s what I think Tweener is.
Did you notice I said “we’re still deciding on the best approach” above? Yeah, it’s because Tweener is more like a group affort, differently from MC Tween, which was mostly a one-man job, taking suggestions from here and there. Currently, Tweener is being helped by Nate Chatellier, who wrote the original AS3 version and has been providing valuable input on both versions, and Arthur Debert, which has helped with submitting bugs and fixes as well as suggestions on how stuff should work.
Anyhow, there’s a lot I could say here but I would probably just be repeating myself. So if you’re interested, Tweener is available for anyone who wants to test it. Its official page is hosted at Google Code. You can download the stable version, or download the latest versions, available from Subversion, or from the web version of the repository. You can also check the changelog. And if you want to see it in action, there’s a few examples available; this time, I’m trying to make examples as distinct as possible, covering as many different development setups as possible. Right now, there are examples available for AS2 under Flash 8 and MTASC, AS3 under Flash 9, and Flash Lite 2 under Flash 8, but I expect to add more as time allows.
The documentation is still being written but there’s plenty of content already. If you’re a MC Tween (or similar) user, you can check the differences between MC Tween and Tweener – it explains the new class in depth and also has a few bits on the rationale behind most of the changes.
And finally, there’s a discussion list for generic Tweener discussion (in english).
Wew. It feels good to finally get that off my chest. So there.