<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>Frankly, this seems like a very bad idea. Never mind.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></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><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></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:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Sunday, July 3, 2016 5:49 AM<br><b>To: </b><a href="mailto:roy.walmsley@ntlworld.com">Roy Walmsley</a>; <a href="mailto:brutzman@nps.edu">Don Brutzman</a>; <a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a>; <a href="mailto:x3dom-developers@lists.sourceforge.net">X3DOM Developers</a>; <a href="mailto:x3dom-users@lists.sourceforge.net">x3dom-users@lists.sourceforge.net</a><br><b>Subject: </b>Starter Script.js for X3DOM JSON Script development. Your effortrequested.</p></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><p class=MsoNormal>Here’s my Script.js if you want to start working on a Script node in the X3D JSON Encoding for X3DOM! It generates two logs, one for the JavaScript classes code, and one for “Route code” which copies values around (in and out of the scripts). The package may be initially undefined. If we could get it to the point where it uses X3DOM routing for Scripts, that would be an accomplishment!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>processScripts(JSON object, LOG classes, Script package, LOG routecode) is the main entry point.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I suggest using a different tag if you’re going to put the scripts in DOM. Perhaps <vrmlscript>, <ECMAScript> or <javascript>. You can change the “Script” to something that X3DOM will recognize (that is, program a script extension for X3DOM).</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Or you can start with a different implementation and the X3D JSON encoding standard! One thing we’re working on is making Scripts independent of Protos, so the Script.js developer won’t have to worry about Protos. The prototype expander should hopefully take care of all the proto dependent stuff. You will however, be expected to deal with similar Script that come out of multiple instances of a proto body—each should have a different DEF (if you want to collaborate, we can discuss—however, I’m trying to build tools which plug and play together well, so we can leave out proto expansion or scripting if we don’t need it—hopefully, we don’t have to bundle them together, but I’m willing to discuss a common core if you have some ideas).</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><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Sunday, July 3, 2016 5:02 AM<br><b>To: </b><a href="mailto:roy.walmsley@ntlworld.com">Roy Walmsley</a>; <a href="mailto:brutzman@nps.edu">Don Brutzman</a>; <a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>prototype expanded gears.json works in Cobweb with X3D JSON Loader<o:p></o:p></p></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><p class=MsoNormal>Attached! Still needs work on Script node for X3DOM, I guess. Could be the CDATA issue or some such.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If someone could independently work in JavaScript on processing JSON Script nodes from my Prototype Expanded files to get them working in X3DOM, that would be cool. I can get you started, but it still needs a lot of work! I have several prototype expanded test files with scripts I could pass your way! I am currently using Cobweb for many of my tests, but I don’t have Inline JSON working with Cobweb yet. You probably don’t even need my expanded files, just start working with my X3D JSON Loader and JSON files with Script objects in them!</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><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>