<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>I am considering deleting portions of X3DJSONLD, particularly X3DJSONLD/src/main/node/Script.js, and the portions of X3DJSONLD/src/main/node/loaderJQuery.js which use Script.js to convert X3D ECMAScripts to HTML Scripts for X3DOM—This only partially worked anyway, on several of my scripts. I suggest looking towards how X3DOM already handles scripting, or perhaps using X_ITE. I do not like eval’ing externally provided script code—it makes me dang nervous—and pushing a CDATA section into a X3D XML Script element is preferable to me (handing off the issue I guess), thus I will try to continue to support X_ITE. This likely means we will never see Protos fully implemented in X3DOM (Is anyone crying?). Thus we will have an X3DJSONLD based X3DOM ProtoExpander without X3D ECMAScripts fully implemented.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Any feedback on this? I fully support Declarative Graphics, and suggest we get someway to generate pseudorandom numbers declaratively. They are useful in my scripts, and I don’t know how to do it outside a script yet. I am pretty much limited to X_ITE for Protos and Scripts on the web. Now that X_ITE implements shaders, I have less use for X3DOM, but subdividing a surface like a sphere in various ways (ala Blender) would be useful in the X3D standard to me. I would use it as a shortcut to defining an IFS which estimates a sphere. Which I probably need to do to unify my shader code. I don’t really want to store the IFS in code. Thanks.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>