[x3d-public] Priorities

[John Carlson]

Perhaps we should try to integrate X3DOM, X3DPSAIL and brython, such that
we can write X3DOM scripts with brython (plus field tags), using standard
script tags, modified for brython.

I am open to this.

Once we have brython example, we can move to JavaScript (or whatever you
want to call JavaScript with fields).

Thanks,

John

On Thu, Oct 15, 2020 at 9:34 AM John Carlson <yottzumm at gmail.com> wrote:

> X3DOM has field types, but they're under the x3dom namespace, so either
> need to change script code, or provide aliases for x3dom's field types.
> Ah, thank's Andreas!
>
> I would like to get the Gears example working, because it has both script
> and Protos.  Plus it's the canonical GL example, AFAIK.
>
> I think the problem I am seeing is JavaScript knows little about what the
> fields are, in the example, field name="innerRadius."
>
> I am not particularly having an issue with script/Script/X3DScript.  I am
> having problems with fields, which AFAIK, are not allowed in HTML5 script.
> Using X3DScript, I am allowed to have field children.
>
> 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/20201015/6e46907d/attachment.html>