[x3d-public] Priorities

[John Carlson]

Now client JavaScript isn't working, it appears (caught in new Function()
code).

http://localhost:8000/test/functional/Gears/

I suspect I will have to add JS declarations for all fields in the
X3DScript.  While I've done this before, I'm wondering if there's some
better juju to use.   We should discuss use of var, let and const in such
code.

Thanks,

John

Uncaught ReferenceError: innerRadius is not defined
    at eventsProcessed (eval at nodeChanged (x3dom-full.debug.js:45126),
<anonymous>:88:16)
    at initialize (eval at nodeChanged (x3dom-full.debug.js:45126),
<anonymous>:73:2)
    at eval (eval at nodeChanged (x3dom-full.debug.js:45126),
<anonymous>:286:41)
    at x3dom.registerNodeType.defineClass.nodeChanged.nodeChanged
(x3dom-full.debug.js:45190)
    at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:11796)
    at x3dom.registerNodeType.defineClass.nodeChanged.nodeChanged
(x3dom-full.debug.js:33648)
    at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:11796)
    at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:11789)
    at NodeList.forEach (<anonymous>)
    at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:11787)

On Wed, Oct 14, 2020 at 10:52 PM John Carlson <yottzumm at gmail.com> wrote:

> I've added the following test to x3dom (coderextreme's master branch).
> There are some pretty basic things such that it doesn't work,
> below--MFInt32 not defined.   Do I need to define all field Types?  Can do,
> I've done it before!  I probably need to do it in the same scope as
> initialize?
>
> I will pursue adding field types for now. Wish me luck!
>
> Thanks.
>
> x3dom-full.debug.js:45007 Adding fields
> x3dom.registerNodeType.defineClass.nodeChanged @ x3dom-full.debug.js:45007
> x3dom-full.debug.js:45034 Number of fields 6
> VM46:31 Uncaught ReferenceError: MFInt32 is not defined
>     at eventsProcessed (eval at nodeChanged (x3dom-full.debug.js:45126),
> <anonymous>:31:16)
>     at initialize (eval at nodeChanged (x3dom-full.debug.js:45126),
> <anonymous>:24:2)
>     at eval (eval at nodeChanged (x3dom-full.debug.js:45126),
> <anonymous>:236:41)
>     at x3dom.registerNodeType.defineClass.nodeChanged.nodeChanged
> (x3dom-full.debug.js:45139)
>     at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:11796)
>     at x3dom.registerNodeType.defineClass.nodeChanged.nodeChanged
> (x3dom-full.debug.js:33648)
>     at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:11796)
>     at x3dom.NodeNameSpace.<anonymous> (x3dom-full.debug.js:11789)
>     at NodeList.forEach (<anonymous>)
>     at x3dom.NodeNameSpace.setupTree (x3dom-full.debug.js:11787)
> x3dom-full.debug.js:45007 Adding fields
> x3dom.registerNodeType.defineClass.nodeChanged @ x3dom-full.debug.js:45007
> x3dom-full.debug.js:45034 Number of fields 5
> x3dom-full.debug.js:45007 Adding fields
> x3dom.registerNodeType.defineClass.nodeChanged @ x3dom-full.debug.js:45007
> x3dom-full.debug.js:45034 Number of fields 5
> x3dom-full.debug.js:45007 Adding fields
> x3dom.registerNodeType.defineClass.nodeChanged @ x3dom-full.debug.js:45007
>
>  create mode 100644 test/functional/Gears/Rotor.x3d
>  create mode 100644 test/functional/Gears/gears.x3d
>  create mode 100644 test/functional/Gears/index.html
>
> http://localhost:8000/test/functional/Gears/
>
> Thanks,
>
> John
>
> ---------- Forwarded message ---------
> From: John Carlson <yottzumm at gmail.com>
> Date: Wed, Oct 14, 2020 at 9:54 PM
> Subject: Re: [x3d-public] Priorities
> To: Don Brutzman <brutzman at nps.edu>
> Cc: X3D Graphics public mailing list <x3d-public at web3d.org>
>
>
> I will be pursuing getting X3DScript working entirely within x3dom this
> evening.
>
> John
>
> On Wed, Oct 14, 2020 at 9:44 PM John Carlson <yottzumm at gmail.com> wrote:
>
>> X3DJSONLD only has limited functionality for X3DScript.   I stripped it
>> because X_ITE did not have support, so none of my X3DScripts were working.
>>   I hope we can get X3DScript added to XMLSchema, X3DUOM etc
>>
>> Thanks, Don
>>
>>  John
>>
>> On Wed, Oct 14, 2020 at 9:33 PM John Carlson <yottzumm at gmail.com> wrote:
>>
>>> If I recall correctly, full support for SAI will require a Browser
>>> implementation.   I suggest someone scope out the work for that, if any.
>>> That is, much of the functionality may be there.  It’s important to
>>> distinguish X_ITE’s Browser from X3DOM’s in any case.
>>>
>>> John
>>>
>>> On Wed, Oct 14, 2020 at 9:22 PM John Carlson <yottzumm at gmail.com> wrote:
>>>
>>>> Andreas, can you share any info about why field routing may not be
>>>> working for X3DScripts in X3DOM?  See coderextreme repository.
>>>>
>>>> When I get a chance, I will peek at proto declare/interface fields, but
>>>> my understanding is those go away!
>>>>
>>>> Note that I’m not currently working on SAI for X3DOM, but I do have
>>>> some preliminary steps for declaring field types.
>>>>
>>>> John
>>>>
>>>> On Wed, Oct 14, 2020 at 6:45 PM Don Brutzman <brutzman at nps.edu> wrote:
>>>>
>>>>> On 10/13/2020 8:26 PM, John Carlson wrote:
>>>>> >
>>>>> > Here’s may be possible:  X3DScript node for X3DOM and  X_ITE.
>>>>> PROTOs with scripts
>>>>>
>>>>> Script node support is is always topmost deficient.  X3DOM without
>>>>> scripts is not compliant X3D or VRML.
>>>>>
>>>>> Prototypes are tied for importance, as in Really Really Important for
>>>>> X extensibility.
>>>>>
>>>>> Please continue sharing information with Andreas so that this might
>>>>> all land and work.  Thanks John.
>>>>>
>>>>> all the best, Don
>>>>> --
>>>>> Don Brutzman  Naval Postgraduate School, Code USW/Br
>>>>> brutzman at nps.edu
>>>>> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA
>>>>>  +1.831.656.2149
>>>>> X3D graphics, virtual worlds, navy robotics
>>>>> http://faculty.nps.edu/brutzman
>>>>>
>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20201014/d8fcf2ec/attachment-0001.html>