<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.pl-en
{mso-style-name:pl-en;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Leonard writes:<o:p></o:p></p><p class=MsoNormal>>X3D in all public releases of the standard is not DOM integrated. There are no public documents that explicitly show how a future generation of X3D would be DOM integrated. That may happen in the future, but that has been worked on without public results for over three years. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have some questions. What are the requirements for being DOM integrated? Which DOM do you refer to? Isn’t DOM more of a language or library feature rather than a potential X3D feature? Is it merely that X3D Scripts support DOM? I have loaded DOM into both Cobweb and X3DOM, without the need for many complex extensions, just a DOM producer and JQuery or interfaces to the browser (<span class=pl-en><span style='font-size:9.0pt;font-family:Consolas;color:#6F42C1;background:white'>$</span></span><span style='font-size:9.0pt;font-family:Consolas;color:#24292E;background:white'>(selector).</span>append () line 405 of <a href="https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/node/loaderJQuery.js">https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/node/loaderJQuery.js</a> for X3DOM, importDocument() line 205 of <a href="https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/node/loaderJQuery.js">https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/node/loaderJQuery.js</a> for Cobweb).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>By using DOM, you can get DOM events, however, I think what you are saying is that Cobweb and X3DOM scenegraphs are not DOM event integrated. I can see that.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If we want the X3D scenegraph integrated with the DOM events, that will likely take a lot of work, which I believe Leonard is the only brave soul doing—I have been off generating events from JavaScript. However, I would warn him that it’s likely that the THREE.js scenegraph isn’t DOM integrated either, but likely he knows the answer to this better than I do.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Will we ever see a scenegraph integrated with the DOM events? Isn’t that the goal?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Perhaps the best approach to DOM integration is to try it OUTSIDE the web environment first.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<br><br><o:p></o:p></p><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div></body></html>