[x3d-public] [x3dom-users] vrml conversions

Andreas Plesch andreasplesch at gmail.com
Tue Aug 15 05:26:36 PDT 2023


Hi Don,

Thank you for the kind words and support. These conversions are driven by
the beauty of the geometry and as an experiment to discover if and how
X3DOM may be used for such content.

Let me clarify that while X3DOM can use scripting and the scripts can be
very similar to X3D scripts in their style and functionality, it cannot
quite digest X3D script nodes directly. Rather it relies on standard DOM
based web scripting. This has disadvantages for compatibility but also
advantages such as improved security and allowing any style of programming
or external library. In this respect it is more similar to Castle than
X_ITE. Please note that X_ITE can also be scripted by standard DOM scripts.

I noticed that glTF may have plans to adopt more complex behaviors than
fixed animations. It may turn into X3D :)

Andreas

On Tue, Aug 15, 2023, 3:09 AM Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
wrote:

> Andreas, just have to say that your superlative progress on X3DOM support
> for both X3D Prototypes and X3D Script nodes powerfully shows how
> Extensible an X3D model can be.
>
>
>
> Thanks for getting X3DOM improved to approach X_ITE on the road to model
> parity, with view3dscene and freewrl coming right along too.  Wow.
>
>
>
> This larger dynamic has many influential possibilities which we might
> barely be able to notice in terms of diffusion of innovation and adoption.
> Perhaps most important is the primary focus for everyone becomes the
> interactive 3D itself, wherever it is used, rather than various annoying
> incompatibility/configuration blockers.  The playing field is changing.
>
>
>
> Recent emphasis by you and several others on VRML has also helped a lot.
> Using magnificent models created by Vladimir Bulatov remains quite
> inspiring, even after decades - what a feat.
>
>
>
> Standing ovation!!  Have fun with Extensible 3D!  8)
>
>
>
> 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
> https://faculty.nps.edu/brutzman
>
>
>
> -----Original Message-----
> From: Andreas Plesch <andreasplesch at gmail.com>
> Sent: Monday, August 14, 2023 12:57 PM
> To: x3dom mlist <x3dom-users at lists.sourceforge.net>
> Cc: X3D Graphics public mailing list <x3d-public at web3d.org>
> Subject: Re: [x3dom-users] vrml conversions
>
>
>
>
> https://andreasplesch.github.io/Library/Viewer/index.html?url=https://gist.githubusercontent.com/andreasplesch/df593e4f82b3fbd99148583ecb235edd/raw/d21237d4ee23a419eb28853ca9cd8fd96e1f5e0b/hyper_6_4_2.x3d
>
>
>
> is another conversion from http://bulatov.org/vrml a hyperbolic
> kaleidoscope with some minor changes.
>
>
>
> In addition to the use of Protos it shows how to use shared initialization
> and variable scope across multiple script output functions/fields as the
> original vrml script does the same, in a single script node.
>
>
>
> Cheers, Andreas
>
>
>
> On Sat, Aug 12, 2023 at 12:07 AM Andreas Plesch <andreasplesch at gmail.com>
> wrote:
>
> >
>
> [...]
>
> > A few interesting x3dom related aspects here are:
>
> >
>
> > - Protos work pretty well in x3dom, even if complicated
>
> > - For IS protofields it is sometimes necessary to provide appropriate
>
> > default values also in the Protobody (not just in the ProtoInterface)
>
> > in case the x3d default values cause problems. This happened here
>
> > because the TextureCoordinate node does not have point coordinates by
>
> > default. x3dom probably should ignore TextureCoordinate nodes with an
>
> > empty point field and treat that as if there is no TextureCoordinate
>
> > node.
>
> > - X3D scripts can be converted to DOM javascripts almost 1:1. ROUTEs
>
> > become the onoutputchange attribute with a function to call for the
>
> > fromNode, and the script itself finds the toNode in directOutput
>
> > style. The conversion shows a more complicated example which includes
>
> > use of wrapper function to avoid global (page wide) variables.
>
> > - HTML weirdness: Script DOM nodes generated 'from scratch' and then
>
> > appended to the page document execute when this happens. However,
>
> > Script DOM nodes generated with the builtin DOMParser or with
>
> > outer/innerHTML parsing are marked and do not execute when appended to
>
> > the page document. There is another, more obscure parsing method which
>
> > does generate executable Script nodes. This is what the editor now
>
> > uses.
>
> >
>
> > Andreas
>
> >
>
> > On Sat, Aug 5, 2023 at 4:44 PM Andreas Plesch <andreasplesch at gmail.com>
> wrote:
>
> > >[...]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230815/e88fa78a/attachment.html>


More information about the x3d-public mailing list