<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">John,<br>
<br>
It shouldn't. There was a spec change and your browser may be
caught between versions. If you insert an existing DOM node into
another portion of the tree, it will first be removed from its
existing location before it appears in the new location. A clone
should create a completely separate copy; however, there may be
some issues with data structures inserted into the DOM that are
intended to be single-existence.<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
</div>
<blockquote type="cite"
cite="mid:5b06319a.1c69fb81.fe454.79e5@mx.google.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<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>
<div class="WordSection1">
<p class="MsoNormal">child.cloneNode(true); seems to destroy
child somehow, and child is no longer visable. I am not quite
sure what is going on. Requires more investigation.</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"
moz-do-not-send="true">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:yottzumm@gmail.com"
moz-do-not-send="true">John Carlson</a><br>
<b>Sent: </b>Wednesday, May 23, 2018 10:53 PM<br>
<b>To: </b><a href="mailto:brutzman@nps.edu"
moz-do-not-send="true">Don Brutzman</a>; <a
href="mailto:andreasplesch@gmail.com"
moz-do-not-send="true">Andreas Plesch</a>; <a
href="mailto:holger.seelig@yahoo.de"
moz-do-not-send="true">holger.seelig@yahoo.de</a>; <a
href="mailto:x3d-public@web3d.org" moz-do-not-send="true">X3D
Graphics public mailing list</a>; <a
href="mailto:x3dom-users@lists.sourceforge.net"
moz-do-not-send="true">x3dom mlist</a><br>
<b>Subject: </b>RE: Bad rendering of JSON SimpleShader in
X_ITE</p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Okay, I tested importDocument, and it
works, so that points to X_ITE importJS being the problem. If
someone can get me a way to build x_ite from scratch, I will
start work getting JSONParser and the CDATA stuff up to date
in X_ITE. If that doesn’t solve the problem I will have to dig
deeper.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Does anyone know how to deep clone a DOM?
I’d like to render both X_ITE and X3DOM from similar DOM trees
without having to retranslate the JSON to DOM (adding another
output to X3DJSONLD).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></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"
moz-do-not-send="true">Mail</a> for Windows 10<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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" moz-do-not-send="true">John
Carlson</a><br>
<b>Sent: </b>Wednesday, May 23, 2018 4:30 AM<br>
<b>To: </b><a href="mailto:brutzman@nps.edu"
moz-do-not-send="true">Don Brutzman</a>; <a
href="mailto:andreasplesch@gmail.com"
moz-do-not-send="true">Andreas Plesch</a>; <a
href="mailto:holger.seelig@yahoo.de"
moz-do-not-send="true">holger.seelig@yahoo.de</a>; <a
href="mailto:x3d-public@web3d.org" moz-do-not-send="true">X3D
Graphics public mailing list</a>; <a
href="mailto:x3dom-users@lists.sourceforge.net"
moz-do-not-send="true">x3dom mlist</a><br>
<b>Subject: </b>RE: Bad rendering of JSON SimpleShader in
X_ITE<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Okay, I’ve narrowed another part of it down
to:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">"#sourceText": [<o:p></o:p></p>
<p class="MsoNormal">
<a class="moz-txt-link-rfc2396E" href="data:text/plain;charset=utf-8,">"data:text/plain;charset=utf-8,"</a>,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Produces correct X_ITE *<b>XML</b>*
renderings in X3DJSONLD, translating from JSON to XML.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">"#sourceText": [<o:p></o:p></p>
<p class="MsoNormal">
"",<o:p></o:p></p>
<p class="MsoNormal">
" data:text/plain;charset=utf-8,",<o:p></o:p></p>
<p class="MsoNormal">
"",<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Generated by X3dToJson.xslt, does not
produce correct XML rendering in X3DJSONLD. And neither does:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">"#sourceText": [<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I will trim() strings in X3DJSONLD CDATA
sections—I have fixed this in X_ITE as well, but I’ve been
unable to build, but may want to rely on X3dToJson.xslt to do
the right thing in the future.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This does not fix the X_ITE JSON rendering
in either X_ITE or X3DJSONLD (X_ITE JSON rendering in
X3DJSONLD *<b>is</b>* X_ITE 4.1.5). There *appears* to be the
desire to load ShaderPart CDATA sections (if they are in fact
CDATA sections…I have not confirmed this) as URLs.
Currently, in X_ITE, I convert all #sourceText as a CDATA
section using Andreas’ method for creating a CDATA section
with DOMParser, which I replaced in X3DJSONLD, due to issues
with Edge.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So how do we solve the problem of rendering
JSON in X_ITE? I am getting the following:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Failed to load
<a class="moz-txt-link-freetext" href="data:text/plain;charset=utf-8,precision">data:text/plain;charset=utf-8,precision</a> mediump float;uniform
mat4 x3d_ProjectionMatrix;uniform mat4
x3d_ModelViewMatrix;uniform mat3 x3d_NormalMatrix;attribute
vec4 x3d_Vertex;attribute vec3 x3d_Normal;varying vec3
normal;void main(){normal = x3d_NormalMatrix *
x3d_Normal;gl_Position = x3d_ProjectionMatrix *
x3d_ModelViewMatrix * x3d_Vertex;} ?_=1527054157284: Invalid
response. Origin '<a class="moz-txt-link-freetext" href="http://localhost:3000">http://localhost:3000</a>' is therefore not
allowed access.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There are “network loads” (appear under
Network tab in developer tools on Chrome) which don’t appear
with the XML version. The above is one of them. Apparently
the XML version does something different than the JSON
version, even though the JSON is translated to DOM in X_ITE.
It is possible that I didn’t actually create a CDATA section
with the JSON version, that needs to be checked, if nothing
else has been fixed or comes to mind. This has been a
problem with serializing DOM to XML with Edge (CDATA tag
disappeared), but I haven’t seen it otherwise.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Attached are the tested versions of
SimpleShader.json and SimpleShader.x3d, minus non-x_ite
shaders.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I need help building x_ite from scratch (I
removed my copy), see issue on GitHub. Make all fails.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Note: I have not tested importDocument,
just createX3DFromString and importJS and specifying urls on
X3DCanvas.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Sorry I didn’t get to testing embedded
Shaders sooner with X3DOM and X_ITE, it slipped my mind, and I
didn’t realize the Examples folder didn’t cover embedded
ShaderPart’s. The Shaders tests are under Components…<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">People can comment on my
CDATACreateFunction and fixXML sections of JSONParser
(X3DJSONLD.js). They likely need work.<o:p></o:p></p>
<p class="MsoNormal">Patches are welcome too! But please run
“sh local.sh” in src/main/shell and peruse the diffs (yes, I
know they are horrible). At a minimum, run “sh quotetest.sh”
(I just checked, those diffs are horrible too!). Sigh! I’m
not sure what’s holding this ball of wax together.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Does anyone want to do a massive conversion
of x_ite’s test Library to X3D JSON?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Also help with ProtoExpander on below would
be welcome.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think I can finally send this email.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">John<o:p></o:p></p>
<p class="MsoNormal">Sent from <a
href="https://go.microsoft.com/fwlink/?LinkId=550986"
moz-do-not-send="true">Mail</a> for Windows 10<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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" moz-do-not-send="true">John
Carlson</a><br>
<b>Sent: </b>Tuesday, May 22, 2018 5:57 PM<br>
<b>To: </b><a href="mailto:brutzman@nps.edu"
moz-do-not-send="true">Don Brutzman</a>; <a
href="mailto:andreasplesch@gmail.com"
moz-do-not-send="true">Andreas Plesch</a>; <a
href="mailto:holger.seelig@yahoo.de"
moz-do-not-send="true">holger.seelig@yahoo.de</a>; <a
href="mailto:x3d-public@web3d.org" moz-do-not-send="true">X3D
Graphics public mailing list</a>; <a
href="mailto:x3dom-users@lists.sourceforge.net"
moz-do-not-send="true">x3dom mlist</a><br>
<b>Subject: </b>RE: Bad rendering of JSON SimpleShader in
X_ITE -- Also Bug inX3DOMProtoExpander.<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">When I got rid of the space leading into
data:text/string in the Cobweb shaders, the XML rendered
properly. So it’s the leading space generate either by the
XML -> JSON translation (DOM2JSONSerializer.js) or the JSON
-> DOM -> XML which is preventing the XML from
rendering. I will switch to X3dToJson.xslt and see if that
fixes it.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">John<o:p></o:p></p>
<p class="MsoNormal">Sent from <a
href="https://go.microsoft.com/fwlink/?LinkId=550986"
moz-do-not-send="true">Mail</a> for Windows 10<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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" moz-do-not-send="true">John
Carlson</a><br>
<b>Sent: </b>Tuesday, May 22, 2018 5:30 PM<br>
<b>To: </b><a href="mailto:brutzman@nps.edu"
moz-do-not-send="true">Don Brutzman</a>; <a
href="mailto:andreasplesch@gmail.com"
moz-do-not-send="true">Andreas Plesch</a>; <a
href="mailto:holger.seelig@yahoo.de"
moz-do-not-send="true">holger.seelig@yahoo.de</a>; <a
href="mailto:x3d-public@web3d.org" moz-do-not-send="true">X3D
Graphics public mailing list</a>; <a
href="mailto:x3dom-users@lists.sourceforge.net"
moz-do-not-send="true">x3dom mlist</a><br>
<b>Subject: </b>RE: Bad rendering of JSON SimpleShader in
X_ITE -- Also Bug in X3DOMProtoExpander.<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Probably it’s not passing schema in
X3DJSONLD because of the ProtoExpander. The ProtoExpander
does not exist in X_ITE to my knowledge (but it may have it’s
own version).<o:p></o:p></p>
<p class="MsoNormal"><br>
When I turn off the proto expander in X3DJSONLD, and the
schema does not report an error. The shader only takes affect
in XML when I load XML. When I turn off the proto expander in
X3DJSONLD, the JSON still does not render properly in X_ITE
(as evidenced by the previous collection of files I
submitted).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The online validator reports no error with
the non-proto expanded JSON.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Attached is the expanded JSON and schema
errors.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The schema error seems to surround:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> "@decis": [<o:p></o:p></p>
<p class="MsoNormal"> 0.95,<o:p></o:p></p>
<p class="MsoNormal"> 0.44,<o:p></o:p></p>
<p class="MsoNormal"> 0.22<o:p></o:p></p>
<p class="MsoNormal"> ],<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Which should be an @value on the field, so
the schema error is definitely an issue with the
ProtoExpander. This may affect and likely does affect X3DOM.<o:p></o:p></p>
<p class="MsoNormal"><br>
I doubt if this will shed light on the X_ITE bug, except to
indicate the error is NOT in the XML parser, to my knowledge.<o:p></o:p></p>
<p class="MsoNormal"><br>
I still don’t know why the non-proto expanded JSON does not
render properly in X_ITE. I have just figured out another
bug.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I believe the ProtoExpander error stems
from IS and wanting to fill in an attribute somewhere, but I’m
not really sure yet. I will have to check to see if the
target (proto?) field is an attribute or a field, I think.
Hmm.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is probably why I had to get rid of
the Proto in X3DOM, the first version of the shader I released
for X3DOM.<o:p></o:p></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"
moz-do-not-send="true">Mail</a> for Windows 10<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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" moz-do-not-send="true">John
Carlson</a><br>
<b>Sent: </b>Tuesday, May 22, 2018 4:51 PM<br>
<b>To: </b><a href="mailto:brutzman@nps.edu"
moz-do-not-send="true">Don Brutzman</a>; <a
href="mailto:andreasplesch@gmail.com"
moz-do-not-send="true">Andreas Plesch</a>; <a
href="mailto:holger.seelig@yahoo.de"
moz-do-not-send="true">holger.seelig@yahoo.de</a><br>
<b>Subject: </b>RE: Bad rendering of JSON SimpleShader in
X_ITE<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Note that SimpleShader.json does not pass
schema with X3DJSONLD, but does pass schema with my other
tools. Hmm.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You may want to try to validate against
your own schema. I will try against my online validator.<o:p></o:p></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"
moz-do-not-send="true">Mail</a> for Windows 10<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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" moz-do-not-send="true">John
Carlson</a><br>
<b>Sent: </b>Tuesday, May 22, 2018 4:36 PM<br>
<b>To: </b><a href="mailto:brutzman@nps.edu"
moz-do-not-send="true">Don Brutzman</a>; <a
href="mailto:andreasplesch@gmail.com"
moz-do-not-send="true">Andreas Plesch</a>; <a
href="mailto:holger.seelig@yahoo.de"
moz-do-not-send="true">holger.seelig@yahoo.de</a><br>
<b>Subject: </b>Bad rendering of JSON SimpleShader in X_ITE<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Don, I’m not sure if this is a translation
issue or an X_ITE issue that the JSON displays just as
Material, and doesn’t use the shader. I thought you would
like to be informed. I tried bringing the “data:text/plain;”
to be start of the source text without any change to the
rendering, but you may have better luck.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You’ll need to remove ../data/ twice in the
xhtml.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This should be the original
SimpleShader.x3d from sourceforge.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It might be with data:text/plain, we have
to put the entire CDATA section inside a single string in
JSON? I don’t know yet.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Or maybe just remove the data:text/plain.
I will try that next.<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"
moz-do-not-send="true">Mail</a> for Windows 10<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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" moz-do-not-send="true">John
Carlson</a><br>
<b>Sent: </b>Tuesday, May 22, 2018 4:20 PM<br>
<b>To: </b><a href="mailto:holger.seelig@yahoo.de"
moz-do-not-send="true">holger.seelig@yahoo.de</a>; <a
href="mailto:andreasplesch@gmail.com"
moz-do-not-send="true">Andreas Plesch</a><br>
<b>Subject: </b>RE: [x3dom/x3dom] Full patch from
coderextreme/x3dom.IncludesJSONloading, protoexpander,
inline changes, and field changes (#844)<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Okay, it looks like there’s an issue with
the JSONParser and X_ITE and X3DJSONLD, possibly. See
attached x_itesimpleshader.xhtml for differences between JSON
and XML versions. I haven’t done any debugging yet, there’s
probably something on the console, like parsing a data URL
(the shader).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Here is the original X3D and converted
JSON.<o:p></o:p></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"
moz-do-not-send="true">Mail</a> for Windows 10<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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" moz-do-not-send="true">John
Carlson</a><br>
<b>Sent: </b>Tuesday, May 22, 2018 3:59 PM<br>
<b>To: </b><a href="mailto:andreasplesch@gmail.com"
moz-do-not-send="true">Andreas Plesch</a><br>
<b>Subject: </b>Re: [x3dom/x3dom] Full patch from
coderextreme/x3dom. IncludesJSONloading, protoexpander,
inline changes, and field changes (#844)<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Oh, okay.
I guess x_ite was falling back to material in some cases
with X3DJSONLD. Before I started mucking with the Proto
from the original.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, May 22, 2018, 3:53 PM
Andreas Plesch <<a
href="mailto:andreasplesch@gmail.com"
target="_blank" moz-do-not-send="true">andreasplesch@gmail.com</a>>
wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-left:48.0pt">Thanks,
the screenshot came through.<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:48.0pt"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:48.0pt">But
it looks like BSContact does not understand or use
the ComposedShader at all. It just falls back to
the Material. I think it has a console ?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:48.0pt"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:48.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:48.0pt">On
Tue, May 22, 2018 at 3:25 PM, John Carlson <<a
href="mailto:yottzumm@gmail.com" target="_blank"
moz-do-not-send="true">yottzumm@gmail.com</a>>
wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid
#CCCCCC 1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-left:96.0pt">Hopefully
this BS contact example makes it.<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:96.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"
style="margin-left:96.0pt">----------
Forwarded message ---------<br>
From: John Carlson <<a
href="mailto:yottzumm@gmail.com"
target="_blank" moz-do-not-send="true">yottzumm@gmail.com</a>><br>
Date: Tue, May 22, 2018, 10:13 AM<br>
Subject: RE: [x3dom/x3dom] Full patch from
coderextreme/x3dom. Includes JSONloading,
protoexpander, inline changes, and field
changes (#844)<br>
To: x3dom/x3dom <<a
href="mailto:reply%2B000ac4f78369c959aaa1022cea58689148651aac125ae7a492cf00000001171b6f7792a169ce1351f190@reply.github.com"
target="_blank" moz-do-not-send="true">reply+000ac4f78369c959aaa1022cea58689148651aac125ae7a492cf00000001171b6f7792a169ce1351f190@reply.github.com</a>>,
x3dom/x3dom <<a
href="mailto:x3dom@noreply.github.com"
target="_blank" moz-do-not-send="true">x3dom@noreply.github.com</a>><br>
Cc: Author <<a
href="mailto:author@noreply.github.com"
target="_blank" moz-do-not-send="true">author@noreply.github.com</a>><o:p></o:p></p>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:96.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:96.0pt">Here
it is in BS Contact: <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:96.0pt"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:96.0pt">Sent
from <a
href="https://go.microsoft.com/fwlink/?LinkId=550986"
target="_blank" moz-do-not-send="true">Mail</a>
for Windows 10<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:96.0pt"> <o:p></o:p></p>
<div style="border:none;border-top:solid
#E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:96.0pt"><b>From:
</b><a
href="mailto:notifications@github.com"
target="_blank" moz-do-not-send="true">Andreas
Plesch</a><br>
<b>Sent: </b>Tuesday, May 22, 2018 1:41
AM<br>
<b>To: </b><a
href="mailto:x3dom@noreply.github.com"
target="_blank" moz-do-not-send="true">x3dom/x3dom</a><br>
<b>Cc: </b><a
href="mailto:yottzumm@gmail.com"
target="_blank" moz-do-not-send="true">John
Carlson</a>; <a
href="mailto:author@noreply.github.com"
target="_blank" moz-do-not-send="true">Author</a><br>
<b>Subject: </b>Re: [x3dom/x3dom] Full
patch from coderextreme/x3dom. Includes
JSONloading, protoexpander, inline
changes, and field changes (#844)<o:p></o:p></p>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:96.0pt"> <o:p></o:p></p>
<p><a
href="https://rawgit.com/andreasplesch/x3dom/inlineShader/doc/x3doc/base/tutorials/lighting/customShader/example.html"
target="_blank" moz-do-not-send="true">https://rawgit.com/andreasplesch/x3dom/inlineShader/doc/x3doc/base/tutorials/lighting/customShader/example.html</a><br>
is the tutorial example.</p>
<p>Here is the simpleShader.x3d for x3dom:<br>
<a
href="https://rawgit.com/andreasplesch/x3dom/inlineShader/test/regression-suite/test/cases/composedShader/inlineShader.xhtml"
target="_blank" moz-do-not-send="true">https://rawgit.com/andreasplesch/x3dom/inlineShader/test/regression-suite/test/cases/composedShader/inlineShader.xhtml</a><br>
Do you know how it is supposed to look
like ? light0 is probably the headlight.</p>
<p><span
style="font-size:12.0pt;color:#666666">—<br>
You are receiving this because you
authored the thread.<br>
Reply to this email directly, <a
href="https://github.com/x3dom/x3dom/pull/844#issuecomment-390869376"
target="_blank" moz-do-not-send="true">view
it on GitHub</a>, or <a
href="https://github.com/notifications/unsubscribe-auth/AArE9_8Wd-sJSolp23LMBxXHsigHw-Weks5t06T3gaJpZM4UDkKu"
target="_blank" moz-do-not-send="true">mute
the thread</a>.</span><span
style="font-size:12.0pt;color:#666666"><img
style="width:.0104in;height:.0104in"
id="_x0000_i1025"
src="https://ci4.googleusercontent.com/proxy/KktpRTcHHAIH5QXL5qHKSgPwK4oTQlUjm8ONUZWIeGiGEyNQgohbrhd76yyVPzgbO7KhHQ3gL4R4ocL5mqz9F8kz4PM978991YwadxOf_SiLDhEhUa_rY4q0JDMhXDMSi2ZdsZ9xHVg9hkxGYnTHS-bsfWky0A=s0-d-e1-ft#https://github.com/notifications/beacon/AArE9"
alt="https://github.com/notifications/beacon/AArE9183osU_x9UEKTouaAfUXwpLR2Mlks5t06T3gaJpZM4UDkKu.gif"
moz-do-not-send="true" height="1"
width="1" border="0"></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:96.0pt"> <o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:48.0pt"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:48.0pt"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:48.0pt">-- <o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-left:4.8pt">Andreas Plesch<br>
Waltham, MA 02453<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! <a class="moz-txt-link-freetext" href="http://sdm.link/slashdot">http://sdm.link/slashdot</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
X3dom-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:X3dom-users@lists.sourceforge.net">X3dom-users@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/x3dom-users">https://lists.sourceforge.net/lists/listinfo/x3dom-users</a>
</pre>
</blockquote>
<p><br>
</p>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
LA ACM SIGGRAPH Past Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>