Adobe has announced some new features for some time (Hydra filters for advanced graphics and a better text handling) that will be present in the next release of Flash. In particular has attracted the attention of the introduction of 3D (Z axis), then the ability of Flash to manipulate objects in a three-dimensional world. Adobe says that the same is actually a 2.5D, as is often stated, a kind of "simulation" of a real three-dimensional world. In fact you can rotate a symbol Flash flow around the z axis, but despite this, the symbol remains flat in the three-dimensional space! A little 'what happens when you distort a bitmap in Photoshop! This, then, has nothing to do with projects like Papervision3D , Away3D , Sandy and many others, which contain a number of features (camera, scenes, textures, etc ...) absent "emerging in the abstraction." In essence, Adobe does not want to completely overlap with 3D designs of third parties, but only provide a native layer to improve the performance of existing 3D libraries.
Anyway, the important thing is that Adobe seems geared to introduce these features to a higher dimensional level, not helping at all libraries complete and complex as Paparevision3D. For some time, in fact, we use two basic techniques to expand the functionality of Flash: low-level APIs and high-level API.
The low-level APIs are generally written in C / C + + and Flash are part of the core, then fill in the player. This method, while it ensures a higher execution speed, the other increases The size of the Flash Player.
The high-level APIs are written in Actionscript and are not native to the core. In other words are very similar to the libraries that we could write to us, with the difference that is provided directly from Adobe. As with the release of Flash 5, the first introduction of the XML object was completely in Actionscript, creating many performance problems!
The advantage is that these libraries are compiled only when necessary and then discharged into the SWF file. As is the case today with the Tween object (see fl.motion fl.transition .* or .*) entirely written in Actionscript (also parallel projects like this are born Tweener (caurina.transitions.Tweener) or TweenerMax .
For this reason, the Papervision community is not entirely happy with the choice of using high-level API, in practice the same "level" of Papervision3D. This, in fact, may not affect the future performance of 3D libraries.
However it will end, the important thing is that Papervision3D is not dead, indeed!
There are no comments for this post
Leave a comment