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

[John Carlson]

See, when you say chrome 108, it sounds separate, but of course, it doesn’t
have to be.

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-ecosystem_web3d.org/attachments/20250218/f744d66a/attachment.html>