<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;}
/* 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;}
.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>Yeah, I was relaxing most of the day yesterday. I may have posted incorrect information. But I still believe x3dom fields are not handled at all for scripts, based on prior research, and up-to-date investigation in the chrome browser (fields and related attributes are black for scripts). . They are handled for ComposedShader, and we might use that as an example for handling Script fields.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Good luck, it’s up to someone else besides me. It should be fairly simple to activate script fields I hope. I am not sure you want them in HTML scripts anyway.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:brutzman@nps.edu">Brutzman, Donald (Don) (CIV)</a><br><b>Sent: </b>Friday, March 1, 2019 6:11 PM<br><b>To: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Cc: </b><a href="mailto:x3d@web3d.org">X3D Graphics Working Group</a>; <a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: [x3d] X3D meeting minutes 22 FEB 2019: X3D v4 Development statuscategories</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for these observations John.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think this points us at the importance of syntax for sending events to destinations, either (X3D -> HTML) or (HTML -> X3D).</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There are several links in today's minutes of relevance: event descriptions and diagrams for both X3D and HTML.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The X3Dv4 spec defines functionality - this will tell authors how to construct what they need, and tell implementers what syntax/semantics to support. In other words, interoperable content. It does not mandate how an implementation gets coded.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Building examples and comparing X3DOM and X_ITE together should get us on path to convergence.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It would be good to get Roy Walmsley's original HTML+SVG+X3D+Javascript demo of "bouncing ball" back on center stage and refreshed. Anyone know where it is? Valuable role here for someone...</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 3/1/2019 2:19 PM, John Carlson wrote:</p><p class=MsoNormal>> In other words, to prevent script source code from appearing on the rendered page, I had to remove the text or CDATA node. I am fairly sure I removed the field nodes as well for X3DOM in X3DJSONLD, favoring my own implementation.</p><p class=MsoNormal>> </p><p class=MsoNormal>> I believe that text nodes are incompatible with execution, but it might be worth seeing how something like jsfiddle does it, if they keep a shadow script or what.</p><p class=MsoNormal>> </p><p class=MsoNormal>> I believe you can keep the fields in DOM (I didn’t) if you have an X3DOM implementation of them.</p><p class=MsoNormal>> </p><p class=MsoNormal>> On Fri, Mar 1, 2019 at 4:03 PM John Carlson <yottzumm@gmail.com <mailto:yottzumm@gmail.com>> wrote:</p><p class=MsoNormal>> </p><p class=MsoNormal>> In other words, scripts (really script fields) do not appear in DOM and do not receive or generate DOM events.</p><p class=MsoNormal>> </p><p class=MsoNormal>> John</p><p class=MsoNormal>> </p><p class=MsoNormal>> On Fri, Mar 1, 2019 at 3:46 PM John Carlson <yottzumm@gmail.com <mailto:yottzumm@gmail.com>> wrote:</p><p class=MsoNormal>> </p><p class=MsoNormal>> As far as I know there is no Script “class” or source file in X3DOM, thus no place to hang fields, thus nowhere to hook up routes. I did write one at one time, it didn’t seem that difficult, but I’m not presently on board to rewrite it. I suggest looking at other implementations of fields.</p><p class=MsoNormal>[...]</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>all the best, Don</p><p class=MsoNormal>-- </p><p class=MsoNormal>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu</p><p class=MsoNormal>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</p><p class=MsoNormal>X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>