This is the first of a multi-part post that examines the issues preventing easy integration of X3D into DOM. This post lists the specific issues and provides some background. It links to other posts that discuss the issue in more detail and in some cases provide possible solutions.
This is part of a multi-part post that explores some ideas for integrating X3D into HTML5 DOM. It explores various options and their implications. The primary post is "Integrating X3D into DOM - Issues".
Main post that lists the major issues for integration.
The previous post ("Integrating X3D Into DOM - Inline") developed a solution for namescoped nodes, specifically Inline. This post looks at implications of that solution.
This is part of a multi-part post that explores some ideas for integrating X3D into HTML5 DOM. It explores various options and their implications. The primary post is "Integrating X3D into DOM - Issues".
X3D is the ISO standard for the display of 3D graphics on the Web (ISO/IEC 19775). Until the last year, it was necessary to have use a plug-in or specialized application to display and interact with 3D objects. In late 2014, the browser builders released versions of their browsers that provided a JavaScript interface to the underyling graphics system of your computer. This interface is called WebGL and is part of most HTML5 implementations. There are several different libraries that provide a simplier interface to the graphics.