{"id":95,"date":"2007-03-13T13:11:41","date_gmt":"2007-03-13T20:11:41","guid":{"rendered":"http:\/\/labs.zeh.com.br\/blog\/?p=95"},"modified":"2007-10-09T08:12:03","modified_gmt":"2007-10-09T15:12:03","slug":"papervision3d-tweener","status":"publish","type":"post","link":"https:\/\/labs.zeh.com.br\/blog\/?p=95","title":{"rendered":"Papervision3D + Tweener = Cones"},"content":{"rendered":"

From the very start, one of the main aspects I wanted to focus on with Tweener<\/a> was forgetting about the whole Actionscript\/Flash API, forgetting there were “MovieClips” and “TextFields” and similar visual class instances. Instead, I wanted Tweener to be an engine focused on tweening any property of any object of any class, as long as it was numeric; it was too often with MC Tween that I had to create “wrap arounds” for new classes I created, when I simply wanted to tween a property of it – say, the .cameraX property of a Stage camera object. Hence why Tweener works by being a separate class that tweens properties of any object, regardless of its type; it’s meant to work seamlessly with whatever numeric properties you want to tween. So a few days ago I decided to put that flexibility into test with Papervision3D<\/a>, the Actionscript 3d renderer that many people are talking about.<\/p>\n

<\/p>\n

Now here’s the fun part: since Papervision3D’s renderer engine uses some simple objects, each with its own numeric properties, it was pretty easy to create something to test — with no code adaptation whatsoever to the way Tweener works. Check this example out:<\/p>\n