I wonder if you have any other good and modern tweening libraries in haxe to suggest, have you seen or used anything comparable/reliable?

For you Tweener users out there, I think you’ll find migrating to TweenLite/Max to be relatively painless because the syntax is very similar. http://www.TweenMax.com

And for the record, Zeh has an open invitation to help shape the future of the GreenSock platform with any advice from his years of experience. It would be an honor.

You’re an inspiration, Zeh, and I hope you’ll keep sharing. Best wishes in the next season of your career.

I think many of the decisions that maybe cause it to have some date is the hooks to AS2 style development and the transition. It was perfect for the time and is still used quite frequently by many flash devs I know including myself.

Thanks for your hard work and support of a really great tool. Hopefully Tweener gave back to you as much as it gave to the flash community. Onward!

I can’t give a very deep take about other engines since I don’t use them, but my opinion is - specially with TweenMax - that they’re doing everything right, syntax wise. One of the reasons why I had no problem saying Tweener is sort of stalled from now on is because there’s great alternatives out there. Specially with the way TweenMax/TweenLite treat sequences, maybe - I really dig the syntax and if I had to implement something like this today, it’d probably be too similar to that. So personally I like it. I’m speaking for myself only though.

I haven’t looked at Desuade, sorry.

Go is a nice project in essence. But I guess in the end we all still suffer of the “not-invented-here” syndrome. There’s always a lot of redundancy in libraries for any language. I’m not sure this is a bad thing.

Thank you again for all your work - people really do appreciate it.

So now what about the future. You mention some new engines. So what are your takes on say, TweenMax(http://blog.greensock.com/tweenmaxas3/) or even something like the Desuade Motion Package (http://desuade.com/dmp)?

I know Moses attempted to unify things, but that didn’t seem to happen

Cheers!

I’d like to thank you very much for Tweener. At Gringo, we’ve been using it extensively for years. Tweener is just a workhorse.
Of course, it does have it’s short comings, but tweener has been **the** reliable code infrastructure for us. Never ever we hit a bug with it. This is, to me, the golden standard of code: something you can rely on. All things equal, I’ll take rock solid code to performance any day.

Also, the way you’ve handled Tweener publicly has always been an example. Always replying with great details on the mailing list, and never getting tangled on flamewars, even on blog posts that were really critical of Tweener (some were pretty inaccurate, by the way).

As a side note, a small anedocte that I remember fondly. Once I had a project that when unloading swfs, I needed to “reset” Tweener, remove all tweens. So I asked Zeh over IM if a removeAll would be useful. He replyed “Yes, I guess… wait a minute”. Two minutes latter he came back in IM and asked me to svn up Tweener. There it was, the removeAll feature. Five minutes from the suggestion to working code in trunk. That was sweet.

By the way, the most under appreciated feature in Tweener is it’s tagline: “because there’s infinity between 0 and 1″ .

Thanks for all the hard work, and good luck on your new tweening endeavors.
Cheers
Arthur Debert

Ok, initially the tweening extension used my old package name - zeh.easing.* - and when Nate Chatellier joined the team, and it was about to go public, I didn’t want it to have my name on the package, it’d sound like a solo man thing. I wanted to pick something a bit more abstract so I picked part of my own company’s name.

My own company was called “Caurinauebi”. It only existed on paper, because it was needed for local legal purposes (so I could work for other companies as a freelancer), and it was never advertised. The name was too long so I just picked “caurina”. Since people still had to write imports all the time back in the day, at least when using it inside the Flash IDE, I really wanted something simple and short.

The name “Caurinauebi” is a sort of a personal joke. If you try reading the name in brazilian portuguese, it sounds as “Caught in a web”, which is a music from Dream Theater and, I thought, a good name for a company that did web stuff.

In retrospect the name was a mistake. It’s not abstract enough, it’s just strange. Some people call Tweener “the caurina”. Some people think it’s a girl’s name. Stuff like that.

Nowadays I’ve gave up on trying not to respect the normal package naming conventions and I just use “com.zehfernando.*” for everything (ie, classes at my public svn server). A simpler package name is actually one of the main reasons why I picked this new domain (zehfernando.com) instead of keep using the old one (zeh.com.br).

So here’s an addendum to the post-mortem article: always use a package name that makes sense or you’ll regret it later.

Feels like it was yesterday when I was teaching Actionscript to my workmates and they were laughing at the name of “MC Tween”. You know.. the hip hop stuff… MC Hammer and so on…