[x3d-public] including ProtoInterface keys in the JSON encoding

[Don Brutzman]

On 12/4/2015 8:55 PM, John Carlson wrote:
> I was able to get my scripts working loading from either X3D XML -> Cobweb or X3D XML -> JSON -> Cobweb by inlining them.  My scripts don’t use ProtoInterface, so the lack of that didn’t cause an issue.  So the good news is, we have Prototypes and Scripts partially working with X3D JSON and the X3D JSON loader, albeit via XML for now until we can get native tool support.  We do need ProtoInterfaces for a complete tool, but I’m hoping that will come without many more additional changes to my X3D JSON Loader (Don, can you change X3dToJson.xslt to output ProtoInterface keys?  If you like I can be an alias for field Thank you.)

Previously we omitted ProtoInterface keys for terseness.

However it does make more sense to include them, for symmetry with XML encoding and also since author scripts might be adding class attributes or HTML callbacks etc. to elements in the DOM tree.

Added to Issues list of TODO action items, will work on it.

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

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