[x3d-public] taste of X3D-BabylonJS converter/viewer

[John Carlson]

Okay, after viewing it on the desktop, I was able to get it to work on 
the iPhone, but got a bit lost.  I will continue on the desktop until I 
get a chance to look at it on the iPad.

John

On 12/14/21 00:46, John Carlson wrote:
> Interesting, but I couldn’t see much beyond the hierarchy on iPhone.  
> I will probably try the iPad tomorrow.
>
> Is there a spec or schema for their JSON, or did you base your work on 
> examples?
>
> I think the challenge these days is making everything work on a 
> variety of devices.   Ultimately there will be another Windows.   They 
> need a kind of TIOBE index for TypeScript software.
>
> If Babylon has a json schema, I could probably enhance my fuzz 
> generation for schema 2020-12
>
> John
>
> On Mon, Dec 13, 2021 at 11:54 PM Andreas Plesch 
> <andreasplesch at gmail.com> wrote:
>
>     I am interested in using BabylonJS, similar to ThreeJS, as a simple
>     web based X3D viewer since it has all the latest rendering features,
>     and a well supported code base and community.
>
>     First, I am just looking at Shapes, no events or anything dynamic.
>     Here is a first impression:
>
>     https://observablehq.com/@andreasplesch/x3d-babylon-viewer/2
>
>     Checkout out the node inspector. It is nice and could also provide
>     some inspiration.
>
>     Basic geometry and ITS as well as IFS work, as well as basic material
>     and diffuse image texture. Background, Viewpoint, headlight and a few
>     light types are also working. DEF/USE is also somewhat supported but
>     has to be tweaked for node types since Babylon has various kinds of
>     instancing for shapes, but other objects have to be shared by
>     referencing on a JS level. The converter works by constructing a BJS
>     scene, as intended, and then serializing to their JSON format which
>     supports most features. There will need to be some postprocessing
>     after importing back to reestablish some DEF/USE object references in
>     memory.
>
>     I think after adding Extrusion and ElevationGrid, this could already
>     be useful for static uses. Not sure about Inline as it will require
>     namescopes and invoking the parser from itself which ObservableHQs
>     reactive dataflow may not like. One idea which came up in BJS forum
>     was to hand code dynamic features around the imported Shapes (Meshes).
>
>     I am using ObservableHQ for rapid development/testing for now.
>     BabylonJS itself is TypeScript which will be an  interesting option.
>
>
>
>     -- 
>     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/20211214/7f14ddcb/attachment.html>