dispatchEvent

Roger Braunstein + Mims Wright = this blog



Woo! KitchenSync v1.1 is out! It now supports timecode, default values, new easing functions and juping to a specific time in a tween. Go check it out!

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.

kitchenSync

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!


If you’ve used Flex, you’ve no doubt (er, hopefully) been using View States (AKA <mx:State>) to change the look of your RIA as it progresses through different situations of use. While this is immeasurably useful, it does not necessarily qualify as an implementation of the State Design Pattern which allows you to change not only how a component looks but how it functions as well.
(for more on design patterns, read my favorite book Head first design patterns).
Continue reading The State pattern in Flex - combining view states with logical states…

« Previous PageNext Page »