<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Catching up...<br>
<br>
<br>
</div>
<blockquote
cite="mid:CAGC3UEkBo3O1jia6Uzi7uVCi6+1qsq8MASxSy1JQ9CHJu2DSzQ@mail.gmail.com"
type="cite">
<p dir="ltr">Well I totally messed that up. I'll add another pass
that handles Inline. Does anyone know the semantics of Inlines
and the best way to splice/graft it into the main scenegraph
body in DOM? Obviously, it's about time to integrate a JSON
loader into X3DOM and other Web tools. An alternative for
X3DOM is to use css selectors to patch in the inline....will
that even work naively?</p>
</blockquote>
<br>
I am familiar with the way X3DOM handles Inline files. X3DOM makes
an HTTP GET request then runs the result back through the node
parser. The node parser inserts the contents into the scene graph
and DOM if nameSpaceName is defined. <br>
<br>
I could see something like one of the following:<br>
1) Provide a JSON parser as X3DOM code that performs the correct
calls to add the node content. This would duplicate the current
parser and would lead to multiple code paths for populating the 3D
scene graph<br>
2) Provide a JSON -> X3D converter that transforms the returned
JSON file to an X3D file, then feed that to the X3DOM parser. This
has the advantage of being simpler but slower. Inline is not run
frequently nor many times, so this may not be such a bad way to
start.<br>
<br>
X3DOM is not really set up for plugin code, especially for parsing.
Jumping to (1) may involve a lot of code maintenance if X3DOM
undergoes a lot of changes.<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
<blockquote
cite="mid:CAGC3UEkBo3O1jia6Uzi7uVCi6+1qsq8MASxSy1JQ9CHJu2DSzQ@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Mar 30, 2016 12:05 AM, "John Carlson"
<<a moz-do-not-send="true" href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Let me be more clear. Do people want to use
"Inline" as a key to an object containing a JSON @url in a
file received unto my X3D JSON Loader? I am thinking of
adding a separate pass exclusively for doing Inline
downloading and substitution in the scenegraph. I may do
Inlines before protos so I can create protos from inlines
(or vica versa if someone has a good feel for which comes
first.) If no one is using the Inline tag to Inline JSON
(they should be able to use Protos or ExternProtoDeclare
with my server prototype expander).</p>
<p dir="ltr">The X3D JSON loader already has mechanisms for
loading JavaScript objects, and a currently adjunct library
for loading JSON URIs called loaderJQuery.js.</p>
<div class="gmail_quote">On Mar 29, 2016 11:50 PM, "Leonard
Daly" <<a moz-do-not-send="true"
href="mailto:Leonard.Daly@realism.com" target="_blank">Leonard.Daly@realism.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>John,<br>
<br>
I am not sure I have a full understanding of what you
are asking. I am going to restate and provide my view.<br>
<br>
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.<br>
<br>
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? <br>
<br>
If it does load it into an X3DOM run-time, perhaps it
is better written as the download callback routine for
X3DOM's Inline.<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
</div>
<blockquote type="cite">
<pre>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
<a moz-do-not-send="true" href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>
<a moz-do-not-send="true" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>
</pre>
</blockquote>
<br>
<br>
<div>-- <br>
<font color="#333366"> <font size="+1"><b>Leonard
Daly</b></font><br>
3D Systems & Cloud Consultant<br>
X3D Co-Chair on Sabbatical<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</div>
<br>
_______________________________________________<br>
x3d-public mailing list<br>
<a moz-do-not-send="true"
href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<a moz-do-not-send="true"
href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"
rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
<br>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
<br>
<br>
<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>
X3D Co-Chair on Sabbatical<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>