Should we have integrate a tweening library by default?

[gsynuh]

People have their preferences etc, so I can see how people can disagree. I just replied to something about camera shaking. If CE had an integrated tweening library, then it would be done straight away and we would have camera.shake(time,intensity) for example.

because this means either "reinventing the wheel" and tweening with our own equations and delay calling to create the shake effect with one function call easily etc... or grab something like TweenLite to handle tweening/delayed calls etc. unfortunately though, TweenLite for example has its own enterframe listener which means pausing CitrusEngine won't pause it - even though if its integrated then you can actually make that happen easily by pausing each instances that are running.

anyway it's a question, I think if there's any kind of state transition to have, this would also help to know.

[alamboley]

I agree that we don't have to create our own Tween Engine, and we can't use Starling one due to its dependency.

Then we have caurina (no more supported I think), Eaze (http://code.google.com/p/eaze-tween/ made by Flash Develop guy) but not as much as popular as Greensock/TweenMax which has a final end user licence a bit restrictive for mobile...

[gsynuh]

I should've thought about it before posting it, in my mind TweenLite was the small license free version of TweenMax but it has a license in fact, and I always forget about it... If we need one, even if its less popular, developers will have to deal with it and so will we because we have no choice... And this wouldn't mean they can't use their own tweening libraries right? I'm just talking about things that need tweening inside CE, so things people will not have to touch - but would be able to use if such library is already included so a kind of hidden bonus I guess.

took a look at eaze, I vote for it, perfect for everything we need right now - camera, sound, state transition

[alamboley]

No sure if eaze is anymore supported, but ok let's go for it even if it has a JS syntax. I've added it.

We should a benchmark: http://www.greensock.com/tweening-speed-test/

[FrancescoMaisto]

I meant to chip in the conversation earlier to suggest to actually include a tweening engine in CE, if nothing else as an extension, but I see you guys are already one step ahead :) good decision btw

[ofabricio]

For internal CE use or either for users access? for internal use should be ok, since once you need to change the tweening engine, users do not are affected, whereas - if users have access - if you change from engine to engine users will get crazy.

[gsynuh]

Well @ofabricio , users do have access to it but I don't see the problem because you are not forced to use it : you can tween with starling, other open source libraries or the libraries with commercial licenses!

With CE here, for internal use, this means we are independent from starling (which is perfect for people using CE with 'flash only') so we don't have to include the starling package just to tween stuff, and its not a commercial library so it fits in with CE's license

We worried about the license, otherwise we would've included the most popular tweening library and we'd be fine if it wasn't a commercial product.