Among other changes, all actions now use the initials ‘KS’ instead of ‘Synchronized’.

Classes have also been moved to multiple packages.

• org.as3lib.kitchensync - Contains the new KitchenSync class and the KitchenSyncDefaults. These are global classes that control the entire system.
• org.as3lib.kitchensync.easing - Contains all the easing function classes.
• org.as3lib.kitchensync.action - Contains all Actions
• org.as3lib.kitchensync.action.tweenable - Contains classes that represent properties that can be tweened.
• org.as3lib.kitchensync.core - Contains the internal workings of the system
• org.as3lib.kitchensync.util - Contains helper classes.

The changes to the names of classes are listed here: Naming Changes

The changes to the package structure are listed here: Package Structure

Help with converting older code is here: Legacy help

The new naming convention went up yesterday in version 1.2. I fixed everything with the refactor command in FB and with find and replace so there’s a good chance that there are a couple of bugs, although, my demos are still running correctly. Please let me know if there are any problems with the wiki or the library.

1. The most glaring thing I learned from the survey is that NOBODY’S USING IT! Come on people!

Aside from myself, only 5 people reported that they have actually used KitchenSync, of them, only one has used it for a real project. The good news? That person is none other than Aral Balkan and that project is GAE SWF, so it could be worse.

2. People love Tweener and TweenLite.

People listed Tweener as one they’ve tried but TweenLite came up more as a favorite. Not surprisingly, people loved TweenLite because of it’s incredible small size and speed.

Two people voted for KitchenSync as their favorite. Hey, that’s the same number as the people who have used it for a project. Coincidence?

3. People think KitchenSync is okay (even though most haven’t used it) but to make it better will require matching the features of the other leading tween engines.

People want performance above all else which would explain why TweenLite, currently the fastest of the competitors, is the favorite of the group.

Here is how people prioritized individual features.

4. In the tools department, Flash and FlexBuilder came in at a tie. For those of you who do your coding in Flash and have never used FlexBuilder, I suggest you give it a shot. Flash is miserable as a programming tool (but that’s a topic for another post). Also, despite the cries of distaste from the FlashDevelop crowd, people apparently love TextMate.

In conclusion, I think KitchenSync has a lot to offer. It’s a unique with a sophisticated architecture and some advanced features. However, these tests are proof that to be taken seriously, KS will need to add the basic, missing features that are found in other systems. So the big aim of version 2.0 will be to patch the holes and optimize for speed. I guess that’s what I was planning to do in the first place but it was great to get everyone’s input on the project.

That’s it! Thank you so much for taking the survey! Stay tuned for updates to the project over the summer.

GAE SWF

• Tweener
• TweenLite (and flavours)
• Boostworthy Animation System
• FuseKit
• Go
• and KitchenSync 1.1

Note: After some helpful feedback from readers (THANK YOU!) I added TweenLite to the list of libraries I reviewed. I should add here that these are fairly superficial observations about how things work and don’t go into incredible detail. If I steal any features, I’ll look closer ;-D

Keep the comments coming!

Tween Engine Comparisons (updated)

Changes in 1.1:

• ADDED jumpToTime() method to Tween (this may be moved to AbstractSynchronizedAction in a later release)
• ADDED getTimestampFromFrames() and getTimestampFromMilliseconds() to TimestampUtil
• ADDED Timecode to TimeStringParser. Now “:ss”, “mm:ss;ff”, and “dd:hh:mm:ss;ff” are supported.
• ADDED ActionDefaults class for storing default initialization values.
• ADDED easeOutIn() to most of the easing functions (buggy. seems to overshoot target in some cases)
• ADDED version check in Synchronizer.initialize()
• CHANGED type of Numbers within Timestamp to int.
• REFACTORED all actions to contain super() in the constructor.
• REMOVED errors that are thrown when pause() and start() are called at the wrong times.

Hey KS Fans,

KitchenSync version 1.0.1 was released last week. This version is just a patch that fixes a few minor issues. Here’s the change log for this version.

===== v1.0.1 (2008.02.04) ======
Fixed Cubic.easeOut bug.
Made getters for Tween's toValue and fromValue.
Added source code to main download.
Added metadata for events.
Updated docs and added summaries to all wiki pages.

I received some feedback from people who were having trouble setting up KitchenSync for use with Flash CS3. I didn’t know this before but you cannot use .swc files compiled with the Flex SDK in a .fla file (WTF, Adobe!) Also, some people were confused by having to use SVN to get the source. To help solve these problems, I’ve added the latest source code as its own download.

I’ve also written EVEN MORE documentation including help for downloading and setting up the source code.

Finally, if you’re using KS, drop me a line or post to the mailing list. I’d love to hear any feedback you may have!

Subscribe to KitchenSyncLib for AS3

Visit this group

KitchenSync is more than an animation library

KitchenSync is more than an animation library. Tweens are a major part of KitchenSync but that is not the end. It also allows you to sequence sounds, functions, and event dispatches among other actions. The framework is open-ended allowing you to come up with new ways to work with the virtual timeline.

KitchenSync was designed with developers in mind

KitchenSync was designed for developers who want a smart way to handle animation or other time-based functionality with code. Written from the ground up in ActionScript 3.0, KitchenSync relies on smart object-oriented architecture rather than complicated shorthand. It includes a number of features and shortcuts, such as the clone() method, that save effort for developers. KitchenSync makes extensive use of events and informative runtime errors and is quite flexible when it comes to extending the functionality.

KitchenSync aims to…

• offer a well-architected, extensible framework for working with time-based animations and events.
• take advantage of the power of ActionScript 3.0 while using OOP best practices and design patterns and without requiring the Flex framework.
• respond to the needs of developers with a rich set of features.
• be a full-featured library for animation and timeline based actions.

Links

• Getting started
• Types of synchronized actions
• Units of time, parsing time strings, and sync mode
• API Reference