After hundreds of development hours, countless caffine-fueled late nights, and a level of preoccupation with tweening that borders on obsessive-compulsive, version 11 is born. This is no minor update. It is by far the most significant (and extensive) upgrade ever.
Last Call for v11 Input
Before officially releasing v11 of the GreenSock tweening platform, I wanted to solicit feedback from the community one last time, particularly on TimelineLite/Max because after the API is locked down, it’s pretty tough to change. Here are the specific questions I’d like feedback on (please feel free to offer feedback/suggestions about topics that aren’t on this list too):
- 1) TimelineLite & TimelineMax – how does the API “feel”? – Does it give you the power and flexibility you need without being bloated? Have you found yourself needing some kind of functionality that’s missing? Is everything intuitive?
- 2) Should ALL plugins be activated in TweenMax by default? – I haven’t done so because I’m afraid it may be seen as “bloated” with the extra kb. On the other hand, it’s not terribly difficult to open the class file and prevent activation of certain plugins if you need to conserve file size, and activating all plugins would prevent some potential confusion for newbies. Keep in mind that there will likely be more and more plugins over time that offer added functionality, so if they’re all activated, TweenMax may hit 30kb at some point in the distant future.
- 3) Should I eliminate the default plugin activations in TweenLite? – This would cut the default file size by around 40%. When I asked this question in v10, I got a fair amount of feedback saying backwards compatibility was much more important than small file size, especially because end users could delete the activation code inside the class file if they needed smaller file size. Then again, TweenLite is supposed to prioritize small file size and a lot of end users are either scared to or don’t understand how to delete the activation code in the class file.
- 4) Are there any important features missing? – I’m trying to prevent bloat while at the same time provide tremendous flexibility, power, and speed. It’s a balancing act. Let me know if you were really hoping a particular feature would make its way into one of the classes.
- 5) What is your favorite feature (or features) that absolutely, positively shouldn’t get cut? – I’m not fishing for compliments here – it’s just helpful to know what the community values so that those features don’t end up on the cutting room floor (so to speak).
- 6) Should “repeat” be renamed “cycles”? – “repeat” seems more common, but some have suggested that “cycles” is more intuitive. If it gets changed to “cycles”, what would you name “repeatDelay”?
- 7) Should append() and prepend() be eliminated from the timeline classes? – One developer suggested eliminating append() and prepend() because they’re not absolutely necessary. For example, append() could be accomplished with myTimeline.insert(myTween, myTimeline.duration). prepend() is more difficult, though. Personally, I find them very intuitive for building sequences and they don’t cost much kb.
If you haven’t tried v11 yet, especially the TimelineLite and TimelineMax classes, I’d highly recommend it.
gTween and TweenLite/Max Unite?
Grant Skinner is one of the most well-respected Flash developers in the world. His inspiring work and generous contributions to the Flash community have earned him a stellar reputation and countless fans. So it is with great excitement that I announce our collaboration on the upcoming release of TweenLite and TweenMax. Grant’s recent Beta offerings of his gTween engine showed great promise and as we talked, it became obvious that we have similar objectives. We figured it made a lot of sense to put our heads together and build on TweenLite and TweenMax, creating a unified platform that’s better, faster, and more flexible than ever. Grant has a proven track record of looking for ways to benefit the overall Flash community, and this is just one more example. It is truly an honor to have his valuable input.
While we’re confident that the collaboration will bear good fruit, there is always a chance that we’ll hit an impasse. Thus far, however, we seem to share remarkably similar goals, convictions, and…most importantly…initials – “Grant Skinner” and “GreenSock”. Coincidence or fate?
Accompanying this announcement is v11 Beta 1 of the GreenSock Tweening Platform. It’s a work-in-progress, and we welcome your input. Get the details and code here.