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

John Carlson yottzumm at gmail.com
Sat Apr 2 13:57:20 PDT 2016


That works for a single Inline, so I assume it will work for multiple.  One problem.  When I serialize to XML, the Document
Fragment is nowhere to be found, thus, only the JSON to DOM rendering has the Inline, not the XML to X3DOM or the XML to Firefox (I didn’t really expect them to work anyway).

John
> On Mar 30, 2016, at 5:18 AM, Roy Walmsley <roy.walmsley at ntlworld.com> wrote:
> 
> John,
>  
> I’m thinking that you would manage Inlines roughly as follows:
>  
> 1)      You load an HTML page with X3D content as normal, i.e. a DOM Document
> 2)      When you come across an Inline load it as a DOM DocumentFragment.
> 3)      Then add the DocumentFragment as a child of the Inline.
> 4)      Repeat steps 2 and 3 until the whole HTML page has been  loaded.
>  
> Regards,
>  
> Roy
>  
> From: x3d-public [mailto:x3d-public-bounces at web3d.org] On Behalf Of John Carlson
> Sent: 30 March 2016 05:33
> To: Leonard Daly
> Cc: X3D Graphics public mailing list
> Subject: Re: [x3d-public] Stuck on Inlining JSON--Question for JSON Loader customers
>  
> Hmm I guess I have to consider JSON file urls containing JSON file urls ...
> 
> I am beginning to see why protos and inlines are so painful to implement.
> 
> John 
> 
> On Mar 30, 2016 12:26 AM, "John Carlson" <yottzumm at gmail.com <mailto:yottzumm at gmail.com>> wrote:
> 
> On Mar 29, 2016 11:50 PM, "Leonard Daly" <Leonard.Daly at realism.com <mailto:Leonard.Daly at realism.com>> wrote:
> >Does your JSON loader load the scene into an X3DOM environment? If not, what runtime do you use for display of the 3D content? 
> 
> It loads it in DOM for display with X3DOM and converts the DOM to XML for display with cobweb (thanks Andreas!) and X3DOM, for a total of 2+ runtimes...one runtime is used two different ways.
> 

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


More information about the x3d-public mailing list