[x3d-public] X3D JSON encoding: refactoring, simplifying handling of #comment and #ROUTE

[Don Brutzman]

John, thanks for the phone discussion today and confirming that you successfully modified your loader for the simplified handling of #comment and ROUTE.

The X3dToJson.xslt stylesheet now reports if comments are encountered outside of the X3D document, and does not convert/move them into the JSON object.

I have graduated this issue as completed work.

	http://www.web3d.org/x3d/stylesheets/X3dToJson.html#Issues

Good luck with your continuing efforts on prototypes!

On 1/6/2016 12:45 PM, Don Brutzman wrote:
> OK.  The suggested changes have been implemented and deployed: #comment and ROUTE statements.
>
> Since ROUTE is a well-defined statement and being handled similar to other nodes, it no longer seems necessary to include the # symbol.
>
> ========================================
> The description page prose and examples have been updated to show the new syntax.
>
>      X3D to JSON Stylesheet Converter
>      http://www.web3d.org/x3d/stylesheets/X3dToJson.html
>
>      Design Patterns
>      http://www.web3d.org/x3d/stylesheets/X3dToJson.html#DesignPatterns
>
>      Examples
>      http://www.web3d.org/x3d/stylesheets/X3dToJson.html#Examples
>
>      http://www.web3d.org/x3d/stylesheets/X3dToJson.html#HelloWorld.json
>      http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.json
>
>      http://www.web3d.org/x3d/stylesheets/X3dToJson.html#TestJsonEncoding
>      http://www.web3d.org/x3d/content/examples/Basic/development/TestJsonEncoding.json
>
>      http://www.web3d.org/x3d/stylesheets/X3dToJson.html#OrigamiCranes
>      http://x3dgraphics.com/examples/X3dForAdvancedModeling/Animation/OrigamiCranes.json
>
> ========================================
> Updated example archives and X3D-Edit integration have been deployed.
>
>      X3D Resources: Examples
>      http://www.web3d.org/x3d/content/examples/X3dResources.html#Examples
>
>      Special testing distribution. A comprehensive collection of all JSON example scenes
>      is available at
>      http://www.web3d.org/x3d/content/examples/X3dExampleArchivesJsonScenes.zip
>      http://www.web3d.org/x3d/content/examples/X3dExampleArchivesJsonScenes.zip.MD5
>
>      plus current output from the X3D JSON build process at
>      http://www.web3d.org/x3d/content/examples/build.json.out
>
>      X3D-Edit Authoring Tool for Extensible 3D (X3D) Graphics
>      https://savage.nps.edu/X3D-Edit
>      https://savage.nps.edu/X3D-Edit/images/X3D-EditToolbarButtons3.png
> ========================================
>
> Review and discussion welcome.
>
> Our remaining list of unfinished encoding issues is getting pretty short:  IMPORT/EXPORT for Inline, and null nodes within an MFNode array.
>
>      http://www.web3d.org/x3d/stylesheets/X3dToJson.html#Issues
>
> On 1/4/2016 5:30 AM, John Carlson wrote:
>> I can report that the new JSON format is better at maintaining order in the roundtrip :) We just need to work on the first leg.
> [...]
>
> Baton of implementation/evaluation now handed back to you and others John. Have fun with X3D JSON!   8)
>
> all the best, Don


all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman