[x3d-public] X3D JSON - comments preceding and following the X3D Element/Object

John Carlson yottzumm at gmail.com
Mon Jan 11 07:12:21 PST 2016


Try a trailing comment after </X3D> <!— here —> and see if you apply the stylesheet then JSON.parse() it (or use one of the JSON parsing webpages on the output) whether the result will be parseable or not.  No, jslint doesn’t count.

John
> On Jan 11, 2016, at 9:50 AM, Don Brutzman <brutzman at nps.edu> wrote:
> 
> Comments and ROUTE statements all appear under "-children" key, interspersed with other children nodes in order of appearance.
> 
> This occurs even if a node (e.g. Appearance Material etc.) doesn't have "-children" nodes of it's own.
> 
> All examples, stylesheet, X3D-Edit and the description page updated to match.
> 
> 	http://www.web3d.org/x3d/stylesheets/X3dToJson.html
> 
> Update message with some discussion sent
> 
> 	http://web3d.org/pipermail/x3d-public_web3d.org/2016-January/004083.html
> 
> On 1/11/2016 6:11 AM, John Carlson wrote:
>> Don, how are we handling comments which precede and follow the X3D Element/Object?
>> 
>> Thanks,
>> 
>> John
> 
> Thanks for asking, further questions welcome.
> 
> 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




More information about the x3d-public mailing list