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.
The initial version of Basx3DTM 3D the HTML Way has been released. This version is pre-alpha and is released to assist in the development of the next release of X3D V4. Basx3DTM is a 3D scene builder using declarative 3D nodes.
Documentation and examples for ThreeJS.org are complete. There are a lot of contributors who are always adding material. In the world of simple-VR, there is the StereoEffects for rendering. This is an effects that renders the scene into left/right eye split-screen.
This set of examples will use the first scene. It is real simple (in terms of elements), but it is sufficient to illustrate the projection issues. For the purposes of this discussion assume that the display screen is sufficiently large to show everything that is desired to be displayed. Also assume that the rendering software does not enlarge the displayed scene to fit the screen.
For the last nine months I have been working on a declarative language for VR/AR/MR to display 3D content in a browser. I have called the language XSeen.