[x3d-public] X3D minutes, 17 JAN 2020: X3Dv4 progress, rename hidden as visible, name types, Mantis issue resolution

[Joseph D Williams]

➢ Ecmascript Scene Programming Interface.

Otherwise known as ECMAScript language bindings for our X3D scene authoring interface (SAI).
Thanks for All,
Joe 



From: Andreas Plesch
Sent: Friday, January 17, 2020 12:16 PM
To: X3D Graphics public mailing list
Subject: Re: [x3d-public] X3D minutes, 17 JAN 2020: X3Dv4 progress,rename hidden as visible, name types, Mantis issue resolution

A short response:

> Date: Fri, 17 Jan 2020 09:34:32 -0800
> From: Don Brutzman <brutzman at nps.edu>
> To: X3D Graphics public mailing list <x3d-public at web3d.org>
> Subject: [x3d-public] X3D minutes, 17 JAN 2020: X3Dv4 progress, rename
>         hidden as visible, name types, Mantis issue resolution

...
>         [x3d-public] TypeScript SAI (and ECMAScript API implementation)
>         https://web3d.org/pipermail/x3d-public_web3d.org/2020-January/011666.html
>
> Primary motivation: additional implementation of X3Dv4 in native JavaScript, usable in node.js (for example).
>
> No need to dwell on TypeScript from perspective of X3Dv4 standardization, though possible motivator for Microsoft engagement with Web3D Consortium as well as ISO.

Note that TypeScript may still be helpful in implementing a Ecmascript
Scene Programming Interface.

...
> 4.a. Mantis 1271: add hidden field to Shape
>       https://www.web3d.org/member-only/mantis/view.php?id=1271
>
> Discussion:  see email thread from last week's minutes and the Mantis issue itself.
>
> Pending today: rename to "visible"?  Note change to CADAssembly.  Also need example scene.
>
> TODO: example models for testing implementations.
>
> Related: whether this has impact on X3DPickableNode.  Our immediate reaction is to confirm that we have formal prose that non-visible geometry is not pickable.

Similar prose may be needed for collision detection, for example in walk mode.

>
> We agreed to proceed in this manner.  Once accomplished, this bug is left open that final implementation/evaluation in 2 browsers is needed.
>
> ------
>
> 5.b. Environment node for gamma correction - comments on mailing list, more to follow.  Nicholas tracking... looking at X3DOM capabilities that need to be elevated to X3Dv4 and multiple implementations.  Review by Michalis (wrt PBR), Andreas and Holger (X3DOM-X_ITE), Doug Sanden (FreeWrl) et al. is welcome.  Note overlap with web browser functionality, perhaps utility methods should be exposed in A3D SAI Browser class.
>
>     https://www.web3d.org/mailman/private/x3d_web3d.org/2020-January/007790.html

https://doc.x3dom.org/tutorials/lighting/gamma/index.html may be
already referenced. Wondering what the overlap with web browser
functionality may be ? Operating systems may have color management for
monitor output control.

x3dom now also has tone mapping
(https://en.wikipedia.org/wiki/Tone_mapping), implemented in simple
color mapping shaders:

https://github.com/x3dom/x3dom/blob/b27bda43ee1662bb7cf3488d16051477a99d7601/src/shader/ShaderParts.js#L614

Not sure though if there really is a standard set of such tone mapping
operators.

Andreas
-- 
Andreas Plesch
Waltham, MA 02453

_______________________________________________
x3d-public mailing list
x3d-public at web3d.org
http://web3d.org/mailman/listinfo/x3d-public_web3d.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200118/07a2fc6e/attachment.html>