[x3d-public] Priorities

[John Carlson]

https://github.com/coderextreme/x3dom

Look up both master and Script branches for changes to support
Script/X3DScript node.

I don't see that it's hard to support Script/X3DScript if you call it a
x3dom nodeType.  So I'm going to support both branches until I hit a show
stopper.  I have added fields to Script.

I am currently testing:

http://localhost:8000/test/functional/ScriptEventsX3dom.xhtml
http://localhost:8000/test/functional/MaterialModulatorX3dom.xhtml

Major problems appear to be lack of input from sensors.  Suggestions?  Fix
routes in X3DOM????

Gears demo has been put off until SFRotation implemented or converted.

Please join me in testing/debugging.  You'll need to start a web server at
x3dom level (contains test folder).

So all this ballyhoo about HTML versus XML scripts seemed just to need to
declare Script as a x3dom node.  Someone could make sure I did it the right
way.

John


On Thu, Oct 15, 2020 at 1:44 AM Don Brutzman <brutzman at nps.edu> wrote:

> John please don't worry about SAI completeness.  You didn't hear me
> mention that.
>
> Most Scripts take simple input events, compute a change, and send the
> result back out to the scene graph. Rudimentary functionality with strict
> typing.
>
> X_ITE indeed supports Script nodes and prototypes, and has done so capably
> for a long time.  Many examples:
>
> * https://x3dgraphics.com/examples/X3dForWebAuthors/
>
> https://x3dgraphics.com/examples/X3dForWebAuthors/Chapter09EventUtilitiesScripting/
>
> https://x3dgraphics.com/examples/X3dForWebAuthors/Chapter09EventUtilitiesScripting/ScriptEventsIndex.html
>
> * https://x3dgraphics.com/examples/X3dForWebAuthors/Chapter14Prototypes/
>
> https://x3dgraphics.com/examples/X3dForWebAuthors/Chapter14Prototypes/MaterialModulatorIndex.html
>
> Focusing on one test case at a time is a good way to isolate potential
> problems and resolve them - again, one test case at a time.
>
> Good luck out there!
>
>
> On 10/14/2020 7:44 PM, John Carlson 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
> <mailto: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
> <mailto: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
> <mailto: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 <mailto: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
> >
>
> 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/20201016/ad6293f8/attachment.html>