[x3d-public] X3DOM X3DScript examples.

[John Carlson]

I am reverting to an older x3dom so I can stay synced with x3dom/master. I
will integrate changes from x3dom/master into my local x3dom, build, and
deploy x3dom to x3domx3dscripting/node/.

I believe this means no XML protos.  I think that JSON protos will work but
I'm unsure if they'll work with X3DScripts (good test).

The x3domx3dscripting codebase is intended in the long run to
develop/convert ECMAScript SAI compatible code for X3DOM. Our first attempt
will be for compatibility, then we'll work towards functionality.

Thanks,

John

On Tue, Jun 30, 2020 at 8:28 PM John Carlson <yottzumm at gmail.com> wrote:

> I think that I must make is creating a Function to link X3DScript state
> (field values) to.  Also a scope (possibly namescope) to differentiate
> different X3DScript function names.
>
> Code modification suggestions should be done in a pull request.
>
> I would expect most changes to be to this file:
>
> x3dom/src/nodes/Scripting/X3DScript.js
>
> Please make your own branch of x3dom from x3dom's master.   I will be
> creating a new master of x3dom of my soon.
>
> On Tue, Jun 30, 2020 at 7:33 PM John Carlson <yottzumm at gmail.com> wrote:
>
>> I am working on an "X3DScript" extension to X3DOM.
>>
>> My repository is here:
>>
>> https://github.com/coderextreme/x3domx3dscripting
>>
>> Please do pull requests for .x3d/.json files you'd like me to test.
>>
>> Please test your own X3DScripts!  If you find a bug in x3dom, let me
>> know! Just replace Script begin/end tags in your X3D code with "X3DScript"
>>
>> There are many shader errors in my examples, if anyone wants to help fix
>> them.  I think the errors may stem from bad paths. I am not sure at this
>> time.
>>
>> Thanks,
>>
>> John
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200630/a0c0e233/attachment-0001.html>