Comments on: Tweening by code comes to WPF http://zehfernando.com/2007/tweening-by-code-comes-to-wpf/ Tue, 07 Sep 2010 01:37:13 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Jesse Graupmann http://zehfernando.com/2007/tweening-by-code-comes-to-wpf/comment-page-1/#comment-2320 Jesse Graupmann Sun, 04 Apr 2010 22:54:05 +0000 http://labs.zeh.com.br/blog/?p=105#comment-2320 Inspired by Tweener and the PennerDouble Animation, I’ve created my own engine for both Silverlight and WPF called the Artefact Animator. It actually uses the same class files to produce each version – so there are no surprises jumping back and forth between WPF and Silverlight. I’d encourage you to check it out over at http://artefactanimator.codeplex.com/. There are a couple of other main differences inspired by Tweener. It doesn’t use storyboards and instead relies on getter/setters registered to the Type of value being animated, the DependencyProperty registered, or a string used as a shortcut – like “x” for Canvas.LeftProperty. Some other big ones include; animating multiple properties, more callbacks, and generally more access to animation information. Cheers, Jesse Inspired by Tweener and the PennerDouble Animation, I’ve created my own engine for both Silverlight and WPF called the Artefact Animator. It actually uses the same class files to produce each version – so there are no surprises jumping back and forth between WPF and Silverlight. I’d encourage you to check it out over at http://artefactanimator.codeplex.com/.

There are a couple of other main differences inspired by Tweener. It doesn’t use storyboards and instead relies on getter/setters registered to the Type of value being animated, the DependencyProperty registered, or a string used as a shortcut – like “x” for Canvas.LeftProperty. Some other big ones include; animating multiple properties, more callbacks, and generally more access to animation information.

Cheers,
Jesse

]]>