Tween code cleanup

[thaaks]

Tween and Tweener and involved classes like Ease and *Motion need code cleanup.
Tween and Tweener should not need to know about Entity and should not require an entity as a method parameter. Instead they need to have a proper startingPosition set. That's it.

Method apply() should be renamed to update() and also get the delta value as parameter.

Tweens should be modified to allow usage of delta instead of tick based counting. Also duration should be a value in ticks OR in milliseconds, similar to the solution in my Alarm class. Pretty simple.

I'm wondering if start() and pause() and so on should only affect the current Tween or simply all of them. If they affect only one tween I want to pass the Tween as parameter maybe. And not just rely on the internal variable current...

[Gornova]

I'm falling in love with Flashpunk NumTween :D It's an easy way to change a numeric value (for example for fade out to black or fade in when level starts).. maybe we can work on this side too?

[thaaks]

NumTween is just a special case of your Motion Tween stuff - you only change one value instead of two. But yes, while we are at it we should also add something like NumTween ;-)

[thaaks]

Just had a look at the Flashpunk tween stuff - got the idea. Having different tween implementations in Marte needs a bit of a rewrite. Not very complicated but affects some changes in the interface. Will deal with it.

[Gornova]

What kind of changes?

[thaaks]

In Flashpunk Motion is a subclass of Tween (which makes sense IMHO). In your implementation a Tween has an instance var of class Motion and requires a Motion as a constructor parameter.
I modified the code in my devtommy repository (will push later this week) to change that back to Flashpunk style.
So now the inheritance is Tween <- Motion <- LinearMotion and Tween <- NumTween.
Have a look after the push and tell me what you think. I am sure Motion and LinearMotion can have some more convenience constructors but that's no big deal ;-)

I also didn't understand your Tweener code. In Flashpunk the Tweener starts all Tweens simultaneously whereas your implementation seems to behave like a stack?! Did you have any reason or intention or purpose for this?

[Gornova]

tip: watch Gemserk's Animation4j here https://github.com/gemserk/animation4j seem to be interesting !!

[thaaks]

Good hint! The TimelineAnimationBuilder looks interesting to create sequences of tweens and a nice way to create something like "multi value" tweens.
As usual their tool chain with Guice and Maven and their (sometimes unnecessary) high level of abstraction makes things look complicated.
But we can definitely borrow some ideas or inspiration for further enhancements of our simple tween stuff.
For now I think our existing functionality is sufficient.

[Gornova]

move it to 0.4 for now, keep looking on animation4j, we must done some example with it!

Blog introduction (and video, here http://blog.gemserk.com/2011/03/17/animation4j-project-introduction/ ) is pretty cool! :D