[x3d-public] HudPrototype.json in updated .zip; converting url file extensions from .x3d to to .x3dv .json etc.

Roy Walmsley roy.walmsley at ntlworld.com
Sun Jul 3 02:08:36 PDT 2016


Hi Don and John,

 

As far as I know my own code (in development) is the only one that can load both JSON and XML encodings, albeit with only partial node implementations, which currently approximates “Immersive” profile.

 

Roy

 

From: x3d-public [mailto:x3d-public-bounces at web3d.org] On Behalf Of John Carlson
Sent: 03 July 2016 02:10
To: Don Brutzman
Cc: X3D Graphics public mailing list
Subject: Re: [x3d-public] HudPrototype.json in updated .zip; converting url file extensions from .x3d to to .x3dv .json etc.

 

On Jul 2, 2016 8:25 PM, "Don Brutzman" <brutzman at nps.edu> wrote:

>> Mentioned here (I rewrite URLs to use .json) for the ExternProtoDeclare stuff:

> By that, I assume that you mean, should url file-extension values be converted from .x3d to .json?

Not necessary, I would like to not have to regen JSON files every time I do a fresh install.

> Am always hesitant to change the original content provided by an author in a scene.

I think it's okay to leave as is, as long as it's okay for me to change it in the  short term.

> Conceivably we might add changeUrlExtensionsFromX3dToX3dv and changeUrlExtensionsFromX3dToJson parameters in the XSLT conversion stylesheets.
>
> Is it preferable to have that as a default for all of the .x3dv and .x3db and .json conversions of the X3D Example Archives?

It would provide an extra check to that complete JSON example files are there.
I'm not aware of any browser that does both XML and JSON yet.  Roy?  Right now, following a JSON link in the browser leads to a text page with JSON on it, so you may not want to change Anchors.

John

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


More information about the x3d-public mailing list