1/ It would be cool to see relative coordinates with special cast :
eaze(target).to({ x:”100″ })

It would say something like “x += 100″, helping games or other interactive projects.

2/ I just started to understand what linkedlist are, and how powerfull they can be. As you write eaze tweens like “chaining” function calls, i thought you could have built eaze with linkedlist ; so i started to think about accessing to “previous” and “next” nodes and finally thought i’d love something like this :

eaze(target).forward(2).to({ x:”100″ }).backward(2);

Those “forward” and “backward” utility functions would be able to control the way the tween goes, with counting how many time they’ve been called. This tween would shake the target 2 times from left to right with increment of 100 (which could be relative too). Also, without parameter it could be endless

In extension you could do an other utility function :
eaze(target).to({ x:100 }).repeat(2, true); with .repeat(times:int, reverse:Boolean);

I started to write some eaze tweens with and without those features :

Before :
eaze(target).to({ x:target.x + 100 }).to({ x:target.x – 50 }).to({ x:target.x + 100 }).to({ x:target.x – 50 }).to({ x:target.x + 100 }).to({ x:target.x – 50 });

After:
eaze(target).forward(4).to({ x:”100″ }).to({ x:”-50″ }).backward(3)

Well i’m tired now. Hope u’ll like this idea. I just wanted to help

Do you have kind of killTweensOf / killChildrensTweensOf ?

Is it possible to have an “allTo” with a “stagger” property to easily chain tweens with an internal delay (anyway this could be done with a loop but if it’s in the box, i feel better ) ?

Thanks a lot !

I can do mouse follow stuff, too, man. And It’s not the actual problem anyway…
I know i can add an Event.Enter_FRAME, then within the handler, just set
mc.x += (stage.mouseX-mc.x)/10;
mc.y += (stage.mouseY-mc.y)/10;
and for this case we don’t need a tween engine

Let’s consider another sample. You have a container, when user click on that container the content changes with tween (the old content move out, the new content move in). What if the user click too fast ? with eaze the images just stuck there or moving slowly / abruptly until they stop click…

Of couse we can disable mouse until the tweening is fully completed, of course there are other ways to get this kind of thing done but it’s not the easiest/simplest way…