Difference between revisions of "X3D version 3.4 Development"
From Web3D.org
(editorial) |
m |
||
| Line 7: | Line 7: | ||
* Audio and sound: free formats, aural spatialization | * Audio and sound: free formats, aural spatialization | ||
* CAD Interactive Profile | * CAD Interactive Profile | ||
| − | * | + | * ECMAScript (Javascript) specification revision: confirm compatibility with X3D scripting |
* H-Anim new work items | * H-Anim new work items | ||
* Medical improvements | * Medical improvements | ||
| Line 13: | Line 13: | ||
* [[X3D Multitexture]] is undergoing review for correctness, completeness and conformance of rendering example scenes | * [[X3D Multitexture]] is undergoing review for correctness, completeness and conformance of rendering example scenes | ||
* Rendering: bump maps, projective texture mapping (PTM), shadows | * Rendering: bump maps, projective texture mapping (PTM), shadows | ||
| − | * Other | + | * Other components may be added by Web3D Consortium members |
'''Notes''' | '''Notes''' | ||
Revision as of 01:11, 20 June 2013
X3D version 3.4 Development efforts are evolutionary improvements to the proven X3D Graphics architecture.
Working groups are currently defining goals and requirements.
We expect to add a lot of links and details during this summer's Web3D 2013 and SIGGRAPH 2013 conference meetings.
- Audio and sound: free formats, aural spatialization
- CAD Interactive Profile
- ECMAScript (Javascript) specification revision: confirm compatibility with X3D scripting
- H-Anim new work items
- Medical improvements
- Mobile Profile
- X3D Multitexture is undergoing review for correctness, completeness and conformance of rendering example scenes
- Rendering: bump maps, projective texture mapping (PTM), shadows
- Other components may be added by Web3D Consortium members
Notes
X3D version 4.0 Development efforts are focused on HTML5/Declarative 3D/X3DOM and Augmented Reality Continuum (ARC) technologies, which may require architectural changes. Some new technologies may get pushed from 4.0 to 3.4 (or back again) after careful consideration.
As with all other X3D components, all work is defined in the abstract specification has corresponding file encodings (.x3d .x3dv .x3db) and language bindings (ECMAScript and Java).
