[x3d-public] [X3D-Ecosystem] X3DOM/X_ITE/Castle Content Preview in RawKee X3D Exporter for Maya

Wed Feb 19 12:29:33 PST 2025

The aim is cross-x3d browser scene loading and possibly modification.
Which API is best currently.

John

On Wed, Feb 19, 2025 at 2:15 PM Joe D Williams <joedwil at earthlink.net>
wrote:

> > standard set of functions, perhaps DOM
>
>
>
> The DOM and its interfaces continue to evolve to make it more 'alive' and
> competent for realtime interactive simulations.
>
> Like the X3D SAI the DOM has enough power to implement a realtime fully validating
> authoring system.
>
> Both the DOM and SAI can coexist beside or embedded in one another.
>
> The DOM is represented as a tree; X3D is presented as a DAG with multiple
> roots and hierarchy of namespaces.
>
> Just that the X3D SAI has certain runtime advantages.
>
> These are mainly derived from the idea that SAI is conceived as a
> realtime/anytime, internally/externally scriptable, prototypable,
>
> validatable process with both declarative and imperative aspects presented
> human-readable form.
>
> In addition, X3D runtime is both time and internal/external event-driven
> and fully documents frame-by-frame event flows as the scene progresses.
>
> X3D is basically the xmlized version of VRML but can be produced in most
> any language, including ecmascript, java, json, etc.
>
>
>
> So all is great. The X3D scenegraph can be represented as inline code
> interspersed with the html and use mainly DOM runtime, or
>
> run directly using SAI contained by Canvas, or
>
> run independently directly in the OS as a 3D web browser.
>
> As real 3D interactive support improves in current WWW browsers and
> evolves toward metaversal experiences, the value and versatility of X3D
> will increase.
>
>
>
> > Qt WebChannel
>
>
>
> Look around, maybe a way to do HUDs and control panels, but lots of
> licensing involved?
>
>
>
> Thanks,
>
> Joe
>
>
>
>
>
>
>
> -----Original Message-----
>
> From: X3D Ecosystem public discussion <x3d-ecosystem at web3d.org>
> Sent: Feb 19, 2025 9:25 AM
> To: Bergstrom, Aaron <aaron.bergstrom at und.edu>
> Cc: John Carlson <yottzumm at gmail.com>, X3D Ecosystem public discussion <
> x3d-ecosystem at web3d.org>
> Subject: Re: [X3D-Ecosystem] X3DOM/X_ITE/Castle Content Preview in RawKee
> X3D Exporter for Maya
>
>
> To understand where I’m coming from, read the link, which includes:
>
> “
> Qt WebChannel enables peer-to-peer communication between a server
> (QML/Python application) and a client (HTML/JavaScript or QML application).
> It is supported out of the box by Qt WebEngine . In addition it can work
> on all browsers that support WebSockets , enabling Qt WebChannel clients
> to run in any JavaScript environment (including QML). This requires the
> implementation of a custom transport based on Qt WebSockets.
> “
> So I see client/server and websockets and I think JSONverse and socket.io.
>
> AFAIK,  there’s no X3D standard which includes websockets.
>
> But it seems like you’re more about a standard set of functions, perhaps
> DOM, which is common across all JS browsers.
>
> I don’t know if there’s an X3D DOM standard, but I suspect the best place
> to look is the XML encoding.
>
> John
>
>
> On Tue, Feb 18, 2025 at 2:48 PM Bergstrom, Aaron <aaron.bergstrom at und.edu>
> wrote:
>
>> John,
>>
>>
>>
>> I think we are talking about two different things. What you’ve described
>> sounds very complex and is not what I had in mind.
>>
>>
>>
>> So I apologize if I gave the impression that I was looking to recreate
>> the DIS, EAI.
>>
>>
>>
>> I am thinking just a handful of Javacript functions that would be called
>> in the same for each viewer, and allow me access the scenegraph in each of
>> viewers.
>>
>>
>>
>> The programming work, I was planning to go myself. I was looking more for
>> feedback, and guidance. And I was planning on using the QWebChannel object
>> built into Qt for accessing the webpage already loaded into the Qt objects
>> that display the webpage.
>>
>>
>>
>> This wouldn’t be communicating with external browsers or other websites.
>>
>>
>>
>>
>>
>> Aaron
>>
>>
>>
>> *From:* John Carlson <yottzumm at gmail.com>
>> *Sent:* Tuesday, February 18, 2025 2:14 PM
>> *To:* X3D Ecosystem public discussion <x3d-ecosystem at web3d.org>
>> *Cc:* Bergstrom, Aaron <aaron.bergstrom at und.edu>
>> *Subject:* Re: [X3D-Ecosystem] X3DOM/X_ITE/Castle Content Preview in
>> RawKee X3D Exporter for Maya
>>
>>
>>
>> Aaron,
>>
>>
>>
>> There is prior work on this, primarily DIS, EAI, which got folded into
>> SAI, and socket.io work I did on my JSONverse project. Office Towers has
>> full multiuser avatars.
>>
>>
>>
>> I would suggest creating an extension to x3d.py project which will do SAI
>> across the network, possibly using the EAI underneath SAI.  If you want to
>> move objects around the scene, DIS or HLA may be indicated.  There’s an
>> X3DOM pull request for DIS.  X_ITE doesn’t support DIS.  JSONverse is
>> written with X_ITE.  Since JSONverse uses X3D script
>>
>>
>>
>> You probably won’t see leadership supporting anything else, unless it’s
>> in the Metaverse Standards Forum.  Web3D is a member.  I believe the
>> Webiverse may be a proposal using existing standards.
>>
>>
>>
>> I am more interested in what goes across the network, which events, etc.
>> WebSockets has good backing,  but people are working on WebTransport now.
>>
>>
>>
>> Might I suggest we discuss what you want to communicate before we discuss
>> standards?
>>
>>
>>
>> On Tue, Feb 18, 2025 at 11:59 AM Bergstrom, Aaron wrote:
>>
>>
>>
>> What I’m hoping for is to collaborate with the X3D Ecosystem community
>> and X3D viewer developers to standardize Maya/RawKee/QtWebChannel
>> communication across the various viewers.
>>
>>
>>
>> You can learn a bit more about this here:
>>
>> https://doc.qt.io/qtforpython-6/PySide6/QtWebChannel/index.html
>>
>>
>>
>> And by doing a Google search based on these search request:
>>
>> ‘communicate with QtWebEngine using javascript via PySide6’
>>
>>
>>
>> Thoughts?
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Aaron
>>
>> --
>> X3D-Ecosystem mailing list
>> X3D-Ecosystem at web3d.org
>> http://web3d.org/mailman/listinfo/x3d-ecosystem_web3d.org
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250219/f4aec24c/attachment-0001.html>