[x3d-public] Continuing discussions on ProtoExpander

[John Carlson]

What I can try to do is write up documentation for the JSON based expander,
and then we can see how to convert it to more bindings.

John

On Fri, May 22, 2020 at 11:35 AM John Carlson <yottzumm at gmail.com> wrote:

> I would target the python environment first, imho.   Everyone seems
> excited about it.   I’m also open to doing it in the es6 environment, I
> just need some prototype examples written or translated.
>
> X3dToES6.xslt or a serializer is becoming critical path.
>
> I think we need to sit down and design the abstract specification for
> protoexpansion?  Or do we work on code first?
>
> John
>
>
> On Fri, May 22, 2020 at 11:19 AM John Carlson <yottzumm at gmail.com> wrote:
>
>> Maybe we can add expanding to all X3D*SAIL and x3d.* packages.
>>
>> Something to think about, something to drink about!
>>
>> John
>>
>> On Fri, May 22, 2020 at 11:06 AM John Carlson <yottzumm at gmail.com> wrote:
>>
>>> Don,  I’m thinking the best platform for creating  a ProtoExpander may
>>> be Java, then use jni or JSweet or hand porting to get it to other
>>> languages.   What do you think?   I should be able to help with the port to
>>> Java,  I just need an excellent namespace/scoping/context library written
>>> or found.
>>>
>>> On Fri, May 22, 2020 at 1:06 AM John Carlson <yottzumm at gmail.com> wrote:
>>>
>>>> Design considerations.  Create one or more dispatch tables to classes
>>>> like ProtoDeclare, ProtoInterface, ProtoBody, ProtoInstance, ROUTE,
>>>> Script,etc.   Add handle method to each class.
>>>>
>>>> Reconsider what constitutes a scope.   Does a scope have a symbol table?
>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200522/66c75d1e/attachment-0001.html>