<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Would people be terribly upset if I made this a node.js or nashorn process instead (ECMAScript) or even VRMLScript? How closely are we planning on wedding the JSON -> XML converter to the browser? With all the different XML and JSON libraries, it would seem to be difficult to match up these libraries for all vendors.</p><p class=MsoNormal>I agree C++ is faster.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Monday, March 5, 2018 11:59 AM<br><b>To: </b><a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>; <a href="mailto:gpugroup@gmail.com">GPU Group</a><br><b>Subject: </b>First Alpha version of C++ X3DJSONLD...for early adopters</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="https://github.com/coderextreme/X3DJSONLD/tree/master/src/main/cplusplus">https://github.com/coderextreme/X3DJSONLD/tree/master/src/main/cplusplus</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Converts X3D JSON to X3D XML in a C++ process environment.<o:p></o:p></p><p class=MsoNormal><br>Works on 50% of JSON files tested, 1 out of 2.<o:p></o:p></p><p class=MsoNormal><br>Works with Gason JSON library and Xerces XML.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Executable appears as x3djsonld.exe in cplusplus/src. Build instructions in INSTALL. Need to copy xerces library to cplusplus/src.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Designed for autoconf, but cmake might work as well. Has compiled with Visual Studio 14 2015 (nmake). Has not compiled with VS 2017 nmake.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Initial deployment target: Windows 10, Cygwin.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Main file is X3DJSONLD.cpp.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Contributions welcome!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>