<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>Andreas,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Many thanks for the follow up details you provided. I have now added these to the <a href="http://www.web3d.org/wiki/index.php/X3D/HTML_Implementations">X3D/HTML Implementation</a> wiki page. I have also added material from our discussions last week, which covered a couple of additional items for X3DOM, and then moved on to X_ITE. If you have any additions or corrections, please feel free to let me know, and I will update the wiki page.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>All the best,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Roy<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><span lang=EN-US style='mso-fareast-language:EN-GB'>-----Original Message-----<br>From: x3d-public [mailto:x3d-public-bounces@web3d.org] On Behalf Of Andreas Plesch<br>Sent: 13 December 2017 20:57<br>To: X3D Graphics public mailing list <x3d-public@web3d.org><br>Subject: Re: [x3d-public] review of various X3D statement implementations for X3DOM</span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Thanks for sharing these wiki updates. These are great x3dom summaries.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><a href="http://www.web3d.org/wiki/index.php/X3D/HTML_Implementations#X3DOM_specific_event_handlers"><span style='color:windowtext;text-decoration:none'>http://www.web3d.org/wiki/index.php/X3D/HTML_Implementations#X3DOM_specific_event_handlers</span></a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>In addition to onoutputchanged there is also a very useful but not officially documented onviewpointchanged event. See these github<o:p></o:p></p><p class=MsoPlainText>issues:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><a href="https://github.com/x3dom/x3dom/search?q=viewpointchanged&type=Issues&utf8=%E2%9C%93"><span style='color:windowtext;text-decoration:none'>https://github.com/x3dom/x3dom/search?q=viewpointchanged&type=Issues&utf8=%E2%9C%93</span></a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><a href="http://www.web3d.org/wiki/index.php/X3D/HTML_Implementations#X3D_Nodes_with_additional_or_missing_fields"><span style='color:windowtext;text-decoration:none'>http://www.web3d.org/wiki/index.php/X3D/HTML_Implementations#X3D_Nodes_with_additional_or_missing_fields</span></a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>crossOrigin does relate to CORS which prohibits fetching from remote resources unless explicitly allowed. crossOrigin = "anonymous" can be very useful if remote host allows it.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><a href="http://www.web3d.org/wiki/index.php/X3D/HTML_Implementations#Additional_nodes_not_in_X3D"><span style='color:windowtext;text-decoration:none'>http://www.web3d.org/wiki/index.php/X3D/HTML_Implementations#Additional_nodes_not_in_X3D</span></a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Since I just came across it there is also RenderedTexture<o:p></o:p></p><p class=MsoPlainText>(<a href="https://github.com/x3dom/x3dom/blob/master/src/nodes/Texturing/RenderedTexture.js"><span style='color:windowtext;text-decoration:none'>https://github.com/x3dom/x3dom/blob/master/src/nodes/Texturing/RenderedTexture.js</span></a>)<o:p></o:p></p><p class=MsoPlainText>which is documented as X3D native because it sounds like it should but in fact is not in the standard as far as I can see.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><a href="http://www.web3d.org/wiki/index.php/X3D/HTML_Implementations#CSS"><span style='color:windowtext;text-decoration:none'>http://www.web3d.org/wiki/index.php/X3D/HTML_Implementations#CSS</span></a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>x3dom does respond to some CSS:<o:p></o:p></p><p class=MsoPlainText><a href="https://examples.x3dom.org/example/x3dom_cssTrans.html"><span style='color:windowtext;text-decoration:none'>https://examples.x3dom.org/example/x3dom_cssTrans.html</span></a><o:p></o:p></p><p class=MsoPlainText>But I think it is restricted to 3D transformations and animations, and only a Transform (and perhaps other grouping) nodes can be styled in that way.<o:p></o:p></p><p class=MsoPlainText>The X3D element can be styled as well. Dynamic changes to the style may have to be applied to the generated Canvas element.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>X-ITE has an accurate list of supported nodes:<o:p></o:p></p><p class=MsoPlainText><a href="http://create3000.de/x_ite/supported-nodes/#supported-components"><span style='color:windowtext;text-decoration:none'>http://create3000.de/x_ite/supported-nodes/#supported-components</span></a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>It sticks very closely to the X3D spec. I am not aware of missing or additional fields for supported nodes. In itself it does not expose any X3D specific events to the DOM and the X3D nodes are not part of the DOM. They still can be accessed via the SAI programmatically after getting a browser reference. There is my X_ITE_dom extension which adds the X3D nodes to the DOM, and generates X3D specific events. In fact, with X_ITE_dom all X3D out events become custom X3D specific DOM events with names derived from the X3D event name.<o:p></o:p></p><p class=MsoPlainText>The X3D element probably can be styled. Dynamic changes to the style may have to be applied to the generated Canvas element.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Glad to help answer any questions which may arise,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-Andreas<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On Wed, Dec 13, 2017 at 3:00 PM, <<a href="mailto:x3d-public-request@web3d.org"><span style='color:windowtext;text-decoration:none'>x3d-public-request@web3d.org</span></a>> wrote:<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Message: 1<o:p></o:p></p><p class=MsoPlainText>> Date: Wed, 13 Dec 2017 09:39:31 -0800<o:p></o:p></p><p class=MsoPlainText>> From: Don Brutzman <<a href="mailto:brutzman@nps.edu"><span style='color:windowtext;text-decoration:none'>brutzman@nps.edu</span></a>><o:p></o:p></p><p class=MsoPlainText>> To: Roy Walmsley <<a href="mailto:roy.walmsley@ntlworld.com"><span style='color:windowtext;text-decoration:none'>roy.walmsley@ntlworld.com</span></a>><o:p></o:p></p><p class=MsoPlainText>> Cc: <<a href="mailto:x3d@web3d.org"><span style='color:windowtext;text-decoration:none'>x3d@web3d.org</span></a>>, X3D Graphics public mailing list<o:p></o:p></p><p class=MsoPlainText>> <<a href="mailto:x3d-public@web3d.org"><span style='color:windowtext;text-decoration:none'>x3d-public@web3d.org</span></a>><o:p></o:p></p><p class=MsoPlainText>> Subject: Re: [x3d-public] [x3d] Agenda for X3D WG Meeting Wednesday<o:p></o:p></p><p class=MsoPlainText>> 13th December 2017<o:p></o:p></p><p class=MsoPlainText>> Message-ID: <<a href="mailto:8c586ea5-bf61-ba0b-c95f-5173ecf2d3c2@nps.edu"><span style='color:windowtext;text-decoration:none'>8c586ea5-bf61-ba0b-c95f-5173ecf2d3c2@nps.edu</span></a>><o:p></o:p></p><p class=MsoPlainText>> Content-Type: text/plain; charset="windows-1252"; format=flowed<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Today's X3D Working Group discussion is including review of various X3D statement implementations for X3DOM and X_ITE.<o:p></o:p></p><p class=MsoPlainText>> <a href="http://www.web3d.org/wiki/index.php/X3D/HTML_Implementations"><span style='color:windowtext;text-decoration:none'>http://www.web3d.org/wiki/index.php/X3D/HTML_Implementations</span></a><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Related work from a few years ago: conjecture that associated shared SAI methods providing values of broad authoring utility, that perhaps might be exposed to authors via direct ROUTE connections.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> <a href="http://www.web3d.org/x3d/content/examples/Basic/development/SceneNodeP"><span style='color:windowtext;text-decoration:none'>http://www.web3d.org/x3d/content/examples/Basic/development/SceneNodeP</span></a><o:p></o:p></p><p class=MsoPlainText>> rototypeIndex.html <o:p></o:p></p><p class=MsoPlainText>> <a href="http://www.web3d.org/x3d/content/examples/Basic/development/SceneNodeP"><span style='color:windowtext;text-decoration:none'>http://www.web3d.org/x3d/content/examples/Basic/development/SceneNodeP</span></a><o:p></o:p></p><p class=MsoPlainText>> rototype.html <o:p></o:p></p><p class=MsoPlainText>> <a href="http://www.web3d.org/x3d/content/examples/Basic/development/SceneNodeP"><span style='color:windowtext;text-decoration:none'>http://www.web3d.org/x3d/content/examples/Basic/development/SceneNodeP</span></a><o:p></o:p></p><p class=MsoPlainText>> rototype.x3d<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> ==================================================<o:p></o:p></p><p class=MsoPlainText>> <meta name='title' content='SceneNodePrototype.x3d'/><o:p></o:p></p><p class=MsoPlainText>> <meta name='created' content='19 December 2000'/> <meta <o:p></o:p></p><p class=MsoPlainText>> name='modified' content='14 November 2015'/> <meta name='description' <o:p></o:p></p><p class=MsoPlainText>> content='Expose functionality of Browser class in Java/ECMAscript <o:p></o:p></p><p class=MsoPlainText>> annexes of VRML 97 specification. Consider promotion to a native node <o:p></o:p></p><p class=MsoPlainText>> in X3D/VRML 200x scenes.'/><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> <ProtoDeclare name='Scene'><o:p></o:p></p><p class=MsoPlainText>> <ProtoInterface><o:p></o:p></p><p class=MsoPlainText>> <!-- Standard browser attributes exposed via VRML 97 Script annexes --><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='createVrmlFromString' type='SFString'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='createVrmlFromURL' type='SFString'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='createdVrmlNodes' type='MFNode'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='currentFrameRate' type='SFFloat'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='currentSpeed' type='SFFloat'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='description' type='SFString'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='evaluate' type='SFBool'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='loadUrl' type='SFString'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='loadUrlParameter' type='SFString'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='name' type='SFString'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='replaceWorld' type='MFNode'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='version' type='SFString'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='worldUrl' type='SFString'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='addRoute' type='SFBool'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='deleteRoute' type='SFBool'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='fromNode' type='SFNode'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='fromEventOut' type='SFString'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='toNode' type='SFNode'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOnly' name='toEventIn' type='SFString'/><o:p></o:p></p><p class=MsoPlainText>> <!-- Candidate additions --><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='boundBackground' type='SFNode'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='boundFog' type='SFNode'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='boundGeoViewpoint' type='SFNode'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='boundNavigationInfo' type='SFNode'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='boundViewpoint' type='SFNode'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='outputOnly' name='response' type='MFString'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOutput' name='dashboardVisible' type='SFBool' value='true'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOutput' name='pixelWidth' type='SFInt32' value='-1'/><o:p></o:p></p><p class=MsoPlainText>> <field accessType='inputOutput' name='pixelHeight' type='SFInt32' value='-1'/><o:p></o:p></p><p class=MsoPlainText>> </ProtoInterface><o:p></o:p></p><p class=MsoPlainText>> ==================================================<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Feedback welcome, thanks for considering the possibilities.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> all the best, Don<o:p></o:p></p><p class=MsoPlainText>> --<o:p></o:p></p><p class=MsoPlainText>> Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu"><span style='color:windowtext;text-decoration:none'>brutzman@nps.edu</span></a><o:p></o:p></p><p class=MsoPlainText>> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<o:p></o:p></p><p class=MsoPlainText>> X3D graphics, virtual worlds, navy robotics <o:p></o:p></p><p class=MsoPlainText>> <a href="http://faculty.nps.edu/brutzman"><span style='color:windowtext;text-decoration:none'>http://faculty.nps.edu/brutzman</span></a><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> ------------------------------<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Subject: Digest Footer<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> _______________________________________________<o:p></o:p></p><p class=MsoPlainText>> x3d-public mailing list<o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:x3d-public@web3d.org"><span style='color:windowtext;text-decoration:none'>x3d-public@web3d.org</span></a><o:p></o:p></p><p class=MsoPlainText>> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"><span style='color:windowtext;text-decoration:none'>http://web3d.org/mailman/listinfo/x3d-public_web3d.org</span></a><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> ------------------------------<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> End of x3d-public Digest, Vol 105, Issue 33<o:p></o:p></p><p class=MsoPlainText>> *******************************************<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>--<o:p></o:p></p><p class=MsoPlainText>Andreas Plesch<o:p></o:p></p><p class=MsoPlainText>Waltham, MA 02453<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>_______________________________________________<o:p></o:p></p><p class=MsoPlainText>x3d-public mailing list<o:p></o:p></p><p class=MsoPlainText><a href="mailto:x3d-public@web3d.org"><span style='color:windowtext;text-decoration:none'>x3d-public@web3d.org</span></a><o:p></o:p></p><p class=MsoPlainText><a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"><span style='color:windowtext;text-decoration:none'>http://web3d.org/mailman/listinfo/x3d-public_web3d.org</span></a><o:p></o:p></p></div></body></html>