[x3d-public] ES6 -> ES5 converter help for ES6 SAI

John Carlson yottzumm at gmail.com
Sun May 3 20:15:58 PDT 2020


I always understood "external" as something like RMI or RPC. I don't
distinguish external as a separate process, so it should just "work"?

On Fri, May 1, 2020 at 8:19 PM Joseph D Williams <joedwil at earthlink.net>
wrote:

>
>    - Perhaps it would be best to keep my SAI on the server side?
>
>
>
> One symmetry I hope you will see is that the ‘same’ x3d SAI works internal
> or external.
>
> That is, it looks the same from the inside or the outside, internal or
> external.
>
> 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.
>
> Thanks,
>
> Joe
>
>
>
>
>
> *From: *John Carlson <yottzumm at gmail.com>
> *Sent: *Friday, May 1, 2020 2:48 PM
> *To: *X3D Graphics public mailing list <x3d-public at web3d.org>
> *Subject: *[x3d-public] ES6 -> ES5 converter help for ES6 SAI
>
>
>
> 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?
>
>
>
> Maybe we can do a zoom meeting?
>
>
>
> I am currently welcoming feature requests for  a ES6 SAI.  One possible
> request might be doing ROUTEs with Proxy classes.
>
>
>
> Current features:
>
>
>
> 1. Flexible constructor parameters using an object.
>
> 2. XML output (needs additional testing).
>
>
>
> Current development environment is in this zip:
>
>
>
> https://coderextreme.net/es6.zip
>
>
>
> John
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200503/87c04f87/attachment.html>


More information about the x3d-public mailing list