[x3d-public] gltf tooling

[Joe D Williams]

> can run Script node functions immediately, without needing to wait for end-of-frame processing.   
  
The x3d Script node can be part of a cascade that sends node and field events when the script completes all having the same time stamp as the input event. 
  
If directOut, then Script should execute and output event immediately without initiating a new cascade or being part of any existing cascade.  
    
The THIS is the DEF string of the Script node. 

> Ultimately, the scenegraph *should* be built into the browser or OS. 
    
The html browser uses DOM for runtime. x3d uses SAI, In a sense runtime is built into the html  browser using javascript gl interfaces that produce the runtime where the SAI and DOM can talk to each other using Canvas. Other tools are standalone with whatever SAI they can conjure. 
  
Thanks and Best,
Joe






-----Original Message-----
From: Extensible 3D (X3D) Graphics public discussion <x3d-public at web3d.org>
Sent: Jul 15, 2024 11:46 AM
To: Extensible 3D (X3D) Graphics public discussion <x3d-public at web3d.org>
Cc: GPU Group <gpugroup at gmail.com>
Subject: Re: [x3d-public] gltf tooling

"question of extensibility" "build in an extension mechanism"
One thought experiment: how to build a web3d browser completely from PROTOs - no nodes pre-defined, just load a scene with proto defs for all node types at top of scene.
There are some limitations: hardware / operating system / browser environment dependent --like sound, opengl graphics and shaders, mouse and keyboard input-- so cheating on this ideal with some built in nodes and Browser functions exposed to Scripting would help. But even then, the current web3d PROTO system comes up short.
Cortona - a vrml browser from parallelgraphics- used MS Windows-based COM objects for one path to advanced protos. And IIRC had some initialize, draw, finalize type functions.
Octaga browser has an unusual trait: it can run Script node functions immediately, without needing to wait for end-of-frame processing. 
https://freewrl.sourceforge.io/tests/29_Scripting/script_call_script.x3dv
https://freewrl.sourceforge.io/tests/29_Scripting/script_call_proto.x3dv
Octaga answer = Hello
(other browsers tested can't do this)
This would allow the following design: a set of inputOutput fields on a Proto are the input parameters, an input_only field operates as the function to run, and another set of inputOutput or outputOnly proto fields would represent the function outputs. 
(output1, output2, output3) = run( input1, input2, input3 ..)
And the outputs would happen immediately. This allows Parent-Child arrangement of Protos which can recurse deep, allowing protos to emulate many of the node type functionally that are currently opaque due to parent-child immediate-run needs.
-Doug
 
 





On Mon, Jul 15, 2024 at 11:53 AM John Carlson via x3d-public <x3d-public at web3d.org (mailto:x3d-public at web3d.org)> wrote:
Ultimately, the scenegraph *should* be built into the browser or OS.   Then there’s the question of extensibility, where X3D steps right in!
 
Instead of arguing about which extensions to support, build in an extension mechanism!
 
Now, how do we do that for XML Schema and X3DUOM so we can validate X_ITE materials?
 
I’m maybe halfway there, parsing X_ITE documentation into X3DUOM.  I’ve converted glTF examples to X3D (JSON, IIRC) using Holger’s x3d-tidy, now to actually validate the examples with X3D JSON schema!
 
In the middle of this, I get a whole new system.
 
Sigh!
 
John

On Mon, Jul 15, 2024 at 10:06 AM Joe D Williams via x3d-public <x3d-public at web3d.org (mailto:x3d-public at web3d.org)> wrote:
https://www.youtube.com/watch?v=Z-WTelO-IgU


Anyone looking at this?
Thanks, 
Joe

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

_______________________________________________
x3d-public mailing list
x3d-public at web3d.org (mailto: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/20240715/bc5e1be6/attachment-0001.html>