[x3d-public] problems loading JSON CDATA embedded shader data urls, X_ITE 4.2.1

[John Carlson]

I believe there is a difference between the JSON and the XML documents and/or URL loading which is preventing the JSON file from displaying the shader in X_ITE 4.2.1

http://coderextreme.net/X3DJSONLD/src/main/html/x_itesimpleshader.xhtml

why are we loading URLs with data in CDATA sections (as it appears).

Help would be appreciated.

Likely this applies to all JSON files with data urls in CDATA sections.

XML works fine, in many cases.

If you monitor the network developer tools tab, you will see the difference in URL loading (do each browser found in the XHTML file separately), which seems to be the difference between JSON and XML.

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Tuesday, May 22, 2018 4:20 PM
To: holger.seelig at yahoo.de; Andreas Plesch
Subject: RE: [x3dom/x3dom] Full patch from coderextreme/x3dom.IncludesJSONloading, protoexpander, inline changes, and field changes (#844)

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).

Here is the original X3D and converted JSON.

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Tuesday, May 22, 2018 3:59 PM
To: Andreas Plesch
Subject: Re: [x3dom/x3dom] Full patch from coderextreme/x3dom. IncludesJSONloading, protoexpander, inline changes, and field changes (#844)

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.
On Tue, May 22, 2018, 3:53 PM Andreas Plesch <andreasplesch at gmail.com> wrote:
Thanks, the screenshot came through.

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 ?


On Tue, May 22, 2018 at 3:25 PM, John Carlson <yottzumm at gmail.com> wrote:
Hopefully this BS contact example makes it.

---------- Forwarded message ---------
From: John Carlson <yottzumm at gmail.com>
Date: Tue, May 22, 2018, 10:13 AM
Subject: RE: [x3dom/x3dom] Full patch from coderextreme/x3dom. Includes JSONloading, protoexpander, inline changes, and field changes (#844)
To: x3dom/x3dom <reply+000ac4f78369c959aaa1022cea58689148651aac125ae7a492cf00000001171b6f7792a169ce1351f190 at reply.github.com>, x3dom/x3dom <x3dom at noreply.github.com>
Cc: Author <author at noreply.github.com>

Here it is in BS Contact:  
 
Sent from Mail for Windows 10
 
From: Andreas Plesch
Sent: Tuesday, May 22, 2018 1:41 AM
To: x3dom/x3dom
Cc: John Carlson; Author
Subject: Re: [x3dom/x3dom] Full patch from coderextreme/x3dom. Includes JSONloading, protoexpander, inline changes, and field changes (#844)
 
https://rawgit.com/andreasplesch/x3dom/inlineShader/doc/x3doc/base/tutorials/lighting/customShader/example.html
is the tutorial example.
Here is the simpleShader.x3d for x3dom:
https://rawgit.com/andreasplesch/x3dom/inlineShader/test/regression-suite/test/cases/composedShader/inlineShader.xhtml
Do you know how it is supposed to look like ? light0 is probably the headlight.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
 




-- 
Andreas Plesch
Waltham, MA 02453


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180619/f5e9201b/attachment.html>