<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=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></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><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.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</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:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Tuesday, May 22, 2018 5:30 PM<br><b>To: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a>; <a href="mailto:andreasplesch@gmail.com">Andreas Plesch</a>; <a href="mailto:holger.seelig@yahoo.de">holger.seelig@yahoo.de</a>; <a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a>; <a href="mailto:x3dom-users@lists.sourceforge.net">x3dom mlist</a><br><b>Subject: </b>RE: Bad rendering of JSON SimpleShader in X_ITE -- Also Bug in X3DOMProtoExpander.</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">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">John Carlson</a><br><b>Sent: </b>Tuesday, May 22, 2018 4:51 PM<br><b>To: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a>; <a href="mailto:andreasplesch@gmail.com">Andreas Plesch</a>; <a href="mailto:holger.seelig@yahoo.de">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">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">John Carlson</a><br><b>Sent: </b>Tuesday, May 22, 2018 4:36 PM<br><b>To: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a>; <a href="mailto:andreasplesch@gmail.com">Andreas Plesch</a>; <a href="mailto:holger.seelig@yahoo.de">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">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">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">holger.seelig@yahoo.de</a>; <a href="mailto:andreasplesch@gmail.com">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">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">John Carlson</a><br><b>Sent: </b>Tuesday, May 22, 2018 3:59 PM<br><b>To: </b><a href="mailto:andreasplesch@gmail.com">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">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:19.2pt'>Thanks, the screenshot came through.<o:p></o:p></p><div><p class=MsoNormal style='margin-left:19.2pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:19.2pt'>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:19.2pt'><o:p> </o:p></p></div></div><div><p class=MsoNormal style='margin-left:19.2pt'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:19.2pt'>On Tue, May 22, 2018 at 3:25 PM, John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">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:38.4pt'>Hopefully this BS contact example makes it.<o:p></o:p></p></div><p class=MsoNormal style='margin-left:38.4pt'><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-left:38.4pt'>---------- Forwarded message ---------<br>From: John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">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">reply+000ac4f78369c959aaa1022cea58689148651aac125ae7a492cf00000001171b6f7792a169ce1351f190@reply.github.com</a>>, x3dom/x3dom <<a href="mailto:x3dom@noreply.github.com" target="_blank">x3dom@noreply.github.com</a>><br>Cc: Author <<a href="mailto:author@noreply.github.com" target="_blank">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:38.4pt'><o:p> </o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:38.4pt'>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:38.4pt'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:38.4pt'>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986" target="_blank">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:38.4pt'> <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:38.4pt'><b>From: </b><a href="mailto:notifications@github.com" target="_blank">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">x3dom/x3dom</a><br><b>Cc: </b><a href="mailto:yottzumm@gmail.com" target="_blank">John Carlson</a>; <a href="mailto:author@noreply.github.com" target="_blank">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:38.4pt'> <o:p></o:p></p><p><a href="https://rawgit.com/andreasplesch/x3dom/inlineShader/doc/x3doc/base/tutorials/lighting/customShader/example.html" target="_blank">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">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">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AArE9_8Wd-sJSolp23LMBxXHsigHw-Weks5t06T3gaJpZM4UDkKu" target="_blank">mute the thread</a>.</span><span style='font-size:12.0pt;color:#666666'><img border=0 width=1 height=1 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"></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:38.4pt'> <o:p></o:p></p></div></div></div></blockquote></div><p class=MsoNormal style='margin-left:19.2pt'><br><br clear=all><o:p></o:p></p><div><p class=MsoNormal style='margin-left:19.2pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:19.2pt'>-- <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></div></body></html>