I'm actually glad that you're finding the workflow similar - because it's actually a rather massive two-cycling change behind the scenes, and we typically hear something a bit different. Here are some of the changes and benfits between old and new:
- you cannot break a new motion tween - no more “dashed arrows”
- as such, new tweens are easier to use: you directly manipulate objects on the Stage without needing to always think about keyframes. You don’t even need to add keyframes - just manipulate the object and the keyframes are inserted for you.
- granular control over each part of a tween.
- motion paths are shown right on the Stage for all tweens. Highly visual, and directly editable.
- you can use the new Motion Editor with new tweens
- as such, the Motion Editor means tweens are more powerful in general: each property and keyframe on each property is accessible and editable independently. You can tween alpha separately from rotation separately from scale (etc).
- in that Motion Editor you can edit individual properties on a graph
- you can use the new 3D model with new tweens
- you can give your tween an instance name and then give other instances that same tween at runtime
- new tweens are easy to stretch by just dragging the span in the timeline
- new tweens have new eases, which have advanced (and very cool, better, enhanced) eases
- you can create/apply custom eases that do not need to end at 100%
- you can save a tween as a preset and reuse it in that or other documents
- new tweens are easy to move now - either on the timeline (drag the tween span around), or on the stage by selecting the motion path and just moving it on the Stage (lets just say it is WAY easier than edit multiple frames).
- motion paths in general are easier, and you no longer need motion guides. The motion path for a tween is attached right to the tween.
- you can apply a new instance to an existing tween by just pasting it onto a tween to swap it out, drag a new instance from the Library, or use Swap Symbol. you can even have a tween without an instance applied to it, and all properties of that tween will be saved until you apply an instance to it.
You may want to check out the Motion Migration guide here: http://www.adobe.com/devnet/flash/articles/motion_migration_guide.html -- this article outlines the changes between the two models.
Some of the bigger new features to check out are: Motion Presets (pre-made and custom), the Motion Editor (it ain't small...), preset eases (these made a radical difference in how quickly I could do certain animations), and tween instances (tons of new capabilities here, and reductions in amt of scripted code you have to write). Here are some blog posts on them:
- http://flashthusiast.com/2008/12/10/flash-cs4-example-spray-brush-tween-instance-new-motio n-as3-fancy-jsfl-profit/
- http://flashthusiast.com/2008/10/12/new-motion-and-tween-instances-flash-cs4-presentation- flashcamp/
Motion editor and custom eases:
- http://flashthusiast.com/2008/11/20/flash-cs4-modifying-and-applying-a-custom-ease-in-the- motion-editor/
You may also want to adapt how you use F6 with tweens:
Entire Animation guide:
Let me know if you have any questions,