[x3d-public] announce: X3D4 updates

[John Carlson]

<x3dscript> offered for experimental purposes by Don (you'll have to search
for x3dscript):

http://web3d.org/pipermail/x3d-public_web3d.org/2020-June/012829.html

Please find W3C text that allows "field" and "IS" under script/Script.

Suggestions on how to proceed with fields under HTML5 script welcome.
 Does x_ite_dom do this?

Or:  script is not an X3DOM node, and cannot be instantiated within the
X3DOM scenegraph.

Andreas has already shown how to disable a script node by adding a
non-processed type.  Perhaps we can use that here.

I will proceed more today with additional testing.  I do not think it will
be an issue to change X3DScript to Script if that's possible.

John

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

> The only way I know how to get Scripts working is with X_ITE. That means
> using Inline at the top level.  That's currently how I'm getting X3DScript
> working (but I'm fairly sure i can get it working otherwise, not sure.  I
> think that restricting Scripts to Inlines will be a breaking change for
> X3DOM.
>
> Please show me a way to get script (Script) working with fields, if you
> think it will be possible.  Thanks! I'm going to go search back in email to
> find out where you said X3DScript would be acceptable.
>
> I assume you got Script working with fields in 1997.  I don't like
> anecdotal things.  If we have a 1997 example, let's have it.
>
> Plus, there have been many years of HTML and JS development since 1997.
>
> John
>
> On Thu, Oct 15, 2020 at 1:51 AM Don Brutzman <brutzman at nps.edu> wrote:
>
>> "X3DScript" is non standard and will not be included in the X3D
>> specification.
>>
>> It may be a useful hack to get X3DOM to coexist in a well-behaved way
>> with HTML.  Should simply debugging a lot, eliminating ambiguity to get
>> things working.
>>
>> Once it is working, we can then address how to let X3DOM be in charge of
>> all Script nodes within an X3D scene.
>>
>> If no one can get X3DOM to handle it, it simply remains a curious
>> noncompliant deviation from X3D.
>>
>> p.s. Gee we got Script working in 1997, didn't seem so hard then.
>> Hopefully you can get X3DScript working now, that is most of the work.
>>
>> On 10/14/2020 7:47 PM, John Carlson wrote:
>> >
>> > Don’t forget to add X3DScript as previously mentioned.  Note I don’t
>> expect X3DOM to support Script node for backwards compatibility.
>> >
>> > John
>> >
>> >
>> > On Wed, Oct 14, 2020 at 7:03 PM Don Brutzman <brutzman at nps.edu <mailto:
>> brutzman at nps.edu>> wrote:
>> >
>> >     I have updated X3D4 nodes and fields and documentation to support
>> all changes for Physically Based Rendering (PBR) and glTF, plus most
>> changes for Projective Texture Mapping (PTM).
>> >
>> >     a. X3D XML Schema and DOCTYPE
>> >     b. X3D Unified Object Model (X3DUOM)
>> >     https://www.web3d.org/specifications/
>> >
>> >     c. X3DJSAIL: X3D Java Scene Access Interface Library
>> >     http://www.web3d.org/specifications/java/X3DJSAIL.html
>> >
>> >     d. X3DPSAIL (Python X3D Package)
>> >     https://pypi.org/project/x3d/
>> >     https://www.web3d.org/x3d/stylesheets/python/python.html
>> >
>> >     e. X3D Ontology (Turtle)
>> >     https://www.web3d.org/x3d/content/semantics/semantics.html
>> >
>> >     f. X3D JSON
>> >     https://www.web3d.org/x3d/stylesheets/X3dToJson.html
>> >
>> >     g. X3D Tooltips
>> >     https://www.web3d.org/x3d/content/X3dTooltips.html
>> >
>> >     h. X3D Validator
>> >     https://savage.nps.edu/X3dValidator/
>> >
>> >     i. X3D Specification (github), editorial smoothing continues
>> >     https://github.com/Web3DConsortium
>> >
>> >     Needless to say, it takes a lot of cross-checking to get all this
>> to hang together.  That is good, high reliability.
>> >
>> >     Everything is published and checked into version control, along
>> with build output logs for comparison.
>> >
>> >     Next, I expect one more X3D4 update prior to Web3D 2020 Conference:
>> >
>> >     - Sound component updates for W3C Audio API,
>> >     - A few more hanges to PTM (texture transform, X3DLightingNode)
>> resolution planned for this friday
>> >     - shadowIntensity, in or out?
>> >
>> >     At that point we will have the entire infrastructure needed to
>> support all X3D4 implementation capabilities.  No really.
>> >
>> >     All feedback and testing welcome.  Have fun with X3D4!  8)
>> >
>> >     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
>> >
>> >     _______________________________________________
>> >     x3d-public mailing list
>> >     x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>> >     http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>> >
>>
>> 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/c1d85d49/attachment.html>