Comments on: KitchenSync, I Can Stop Using Tweener Now!

By: Joe Wheeler

Joe Wheeler — Wed, 04 Feb 2009 00:00:22 +0000

I still use Tweener for complex 3d stuff and used to use TweenLite for my day-to-day work horse. I’ve now switched to GTween. It’s awesome. The best bits are progress points and the proxy object. The most useful tweening class yet IMHO

By: ToddJ

ToddJ — Mon, 15 Sep 2008 19:56:45 +0000

Looks good but will still use tweener, …Lite, & …Max for my projects.

By: Tyler Egeto

Tyler Egeto — Tue, 12 Aug 2008 16:16:21 +0000

Cool, I will have to give it a try.

By: Brettf

Brettf — Sun, 10 Aug 2008 07:30:00 +0000

@Matt: Thanks I will have to check that out.

@ Vorg: Your right, Tweener can do pretty much the same thing. I am just not a huge fan of using delays to sequence things. It makes it a bit more complicated to repeat your groups. I actually find KS easy and faster then Tweener so I guess it’s really a matter of personal preference.

By: Matt Przybylski

Matt Przybylski — Sat, 09 Aug 2008 17:08:50 +0000

You should give TweenMax a try. It’s got all the stuff you listed for KitchenSync but is faster and has a smaller filesize. :P

http://www.tweenmax.com

By: vorg

vorg — Sat, 09 Aug 2008 16:34:03 +0000

Are you saying that Tweener documentation isn’t good? There is good ‘getting started’ section and description of all parameters with examples. What more is needed? Maybe there isn’t so much docs like in KitchenSync because Tweener is simpler. Much more simpler. I don’t need “animation framework” to do the job. Is it creating new KSTween for each animated property really that good? Parallel animations, sequences? It could be done using Tweener too (using delay parameter). So what is the killer feature of KitchenSync? I would vote for Object Oriented architecture but only for those who like to write a lot of code and ‘do things right’ instead of doing things fast and easy.