Undolog.com

Adobe announced some time some new features (Hydra filters for advanced graphics and better management of the text) that will be present in the next release of Flash. In particular has attracted interest the introduction of 3D (Z axis), then the ability of Flash to manipulate objects in a three-dimensional world. The same Adobe states that this 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 introns z axis, but despite this, the symbol remains flat in three dimensional space! Un po '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 variety of features (camera, scenes, textures, etc ...) absent "nell'Astro unborn." In essence Adobe wants absolutely no overlap in projects 3D third-party but only provide a native layer to improve performance of existing 3D libraries.

Anyway the important thing is that Adobe seems geared to introduce these three-dimensional features a high level, not at all helping libraries complete and complex as Paparevision3D. For some time, in fact, we use two techniques to expand the capabilities of Flash: API low-level and high-level API.

The low-level API are normally written in C / C + + and are part of the core of Flash, then fill in the Player. This method while guaranteeing greater speed of execution, the other increases the size of Flash Player.

The high-level API are written in Actionscript and does not belong to the core native. In other words are just like a library that we could write us, with the difference that is provided directly from Adobe. As with the release of Flash 5, the first introduction of XML was built entirely in Actionscript, creating many problems of performance!
The advantage is that such libraries are filled only when necessary and then discharged within the SWF file. As happens today with the subject Tween (see fl.motion .* or fl.transition .*) written entirely in Actionscript (including this parallel projects were born as Tweener (caurina.transitions.Tweener) or TweenerMax.
Precisely for this reason the community Papervision is not entirely happy for the choice of using high-level API, in practice the same "level" of Papervision3D. This, in fact, it may not affect future performance 3D library.

However will end, the important thing is that Papervision3D did not die, indeed!

Related Post

• Web2.0: Adobe is trying to Apollo? (2)
• Umapa Flash Component (Beta v0.6) (0)
• PicLens in Flash with Papervision3D 2.0: Part II (13)
• Piclens to Flash with Papervision3D 2.0 (2)
• Papervision3D: how to handle Bitmap in FIVe3D (0)