<div dir="ltr">I always understood "external" as something like RMI or RPC. I don't distinguish external as a separate process, so it should just "work"?</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 1, 2020 at 8:19 PM Joseph D Williams <<a href="mailto:joedwil@earthlink.net">joedwil@earthlink.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><div class="gmail-m_-6368013714104836568WordSection1"><ul style="margin-top:0in" type="disc"><li class="gmail-m_-6368013714104836568MsoListParagraph" style="margin-left:0in">Perhaps it would be best to keep my SAI on the server side?<u></u><u></u></li></ul><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">One symmetry I hope you will see is that the ‘same’ x3d SAI works internal or external.<u></u><u></u></p><p class="MsoNormal">That is, it looks the same from the inside or the outside, internal or external. <u></u><u></u></p><p class="MsoNormal">So, the script processing you develop using an ‘internal’ script can simply be moved outside and imported, or even executed externally under control of the ‘internal’ and even executed ‘externally’ under complete control of the update process with the same effect. If this is not true, please show me. <u></u><u></u></p><p class="MsoNormal">Thanks, <u></u><u></u></p><p class="MsoNormal">Joe<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in"><p class="MsoNormal" style="border:none;padding:0in"><b>From: </b><a href="mailto:yottzumm@gmail.com" target="_blank">John Carlson</a><br><b>Sent: </b>Friday, May 1, 2020 2:48 PM<br><b>To: </b><a href="mailto:x3d-public@web3d.org" target="_blank">X3D Graphics public mailing list</a><br><b>Subject: </b>[x3d-public] ES6 -> ES5 converter help for ES6 SAI</p></div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">Can someone help me set up an ES6 -> ES5 conversion for older browsers (X3D standalone and less modern web browsers)? I am targeting my SAI at ES6 (Node.js) at the moment. I am really liking ES6 on the serverside (and in jupyter) right now. Perhaps it would be best to keep my SAI on the server side?</p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Maybe we can do a zoom meeting?</p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">I am currently welcoming feature requests for a ES6 SAI. One possible request might be doing ROUTEs with Proxy classes.</p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Current features:</p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">1. Flexible constructor parameters using an object.</p></div><div><p class="MsoNormal">2. XML output (needs additional testing).</p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Current development environment is in this zip:</p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal"><a href="https://coderextreme.net/es6.zip" target="_blank">https://coderextreme.net/es6.zip</a></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div></div><p class="MsoNormal">John</p><p class="MsoNormal"><u></u> <u></u></p></div></div></blockquote></div>