[X3D-Public] [x3dom-developers] initial X3D JSON conversion support using X3dToJson.xslt

[Jung, Yvonne]

Hi,
just wrote a very small test that instead dumps a given scene as JSON to the Browser console (ignore __proto__, this is always there in JS, should be skipped when serializing). Here is the example (click the “dump” button and see the result in the console): http://www.x3dom.org/x3dom/test/functional/flipper.html
This is because I think, it might be easier to start the other way round: the X3DOM runtime already has all information for creating some test JSONs. The export could then be refined/optimized based on some tests and from that, a first and easy to integrate draft could be derived. What do you think?
Best, Yvonne


Von: Clayton Cottingham [mailto:drfrog666 at gmail.com]
Gesendet: Samstag, 18. Oktober 2014 19:14
An: Don Brutzman; Behr, Johannes; Kristian Sons; Cecile Muller; Jung, Yvonne
Cc: x3d-public mlist; x3dom-developer mlist
Betreff: Re: [x3dom-developers] [X3D-Public] initial X3D JSON conversion support using X3dToJson.xslt

Ive been looking into this but stumbling on how to re-initialize the x3dom runtime after updating the x3don scene
On 16 October, 2014 10:50:10 PM PDT, Don Brutzman <brutzman at nps.edu<mailto:brutzman at nps.edu>> wrote:

abject pleading follows   8)

On 10/13/2014 12:47 PM, Don Brutzman wrote:

 [...]
 d. still not seeing an X3DOM example of JSON.parse() and .json scene (though have asked several times).

 as before, if X3DOM has an internal X3D model with corresponding parsable JSON, that will be very helpful.

 is anything online, hopefully showing loading and parsing?

 if not, OK.  even draft-y or different-ish examples will likely aid understanding.

 i think that the current HelloWorld.json example seems perfectly parsable already, and it would be good to see how much close the result is to how X3DOM works.

It would be great if someone experienced could uncover or spin together some kind of JSON.parse() conversion code that loads the attached .json syntax into X3DOM.

This will get some good visibility at the VR Hackathon this weekend, all contributions welcome and will be fully credited.

Of course am willing to vary the encoding pattern if that helps simplify the loading - that is the whole goal, find the right balance.

Not sure our Javascript skills are up to the task, but we will struggle with it.   :0

Thanks for any help.

all the best, Don

--
Sent from my Android
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20141018/fd5df6ce/attachment.html>