[x3d-public] Stuck on Inlining JSON--Question for JSON Loader customers

[Leonard Daly]

John,

I am not sure I have a full understanding of what you are asking. I am 
going to restate and provide my view.

Are you asking if people will use an X3D JSON loader using data stored 
in an HTML file rather than GETting it from a server? The data would be 
stored as a JavaScript variable (object) inside of a (HTML) script element.

It seems to me that including data in code in a file that is meant for 
display is not good practice. The data is content, but it needs to be 
processed before it is viewable as content. I see JSON as far more 
useful as downloaded data. This doesn't decrease the need for a 
XML->-JSON->XML converter chain. Does your JSON loader load the scene 
into an X3DOM environment? If not, what runtime do you use for display 
of the 3D content?

If it does load it into an X3DOM run-time, perhaps it is better written 
as the download callback routine for X3DOM's Inline.

Leonard Daly




> Do people want to Inline JSON files in my X3D JSON Loader?  I think they do, but I’m pretty sure I want to separate the code out into my prototype expander.  How do people feel about this?  Ultimately, I think that X3DOM and Cobweb will fully support JSON, but until they do, can we develop a stopgap measure?
>
> I don’t want to put Inline JSON in my X3D JSON Loader, because it introduces a dependency on AJAX/JQuery, and changes the DOM/XML so I can’t do roundtrip comparisons with the original X3D.
>
> Who is using the X3D JSON Loader at this time and what are the requirements?  The loader is moving towards a support role for verifying the JSON encoding, and unless my customers speak up, it will continue to move that way.
>
> John
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org


-- 
*Leonard Daly*
3D Systems & Cloud Consultant
X3D Co-Chair on Sabbatical
LA ACM SIGGRAPH Chair
President, Daly Realism - /Creating the Future/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160329/467facbe/attachment.html>