<div dir="auto">To understand where I’m coming from, read the link, which includes: </div><div dir="auto"><br></div><div dir="auto">“</div><div dir="auto"><div><span style="color:rgb(0,0,0);font-family:'titillium web',sans-serif;font-size:medium;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration:none;display:inline!important;float:none">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 </span><span style="color:rgb(0,0,0);font-family:'titillium web',sans-serif;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">Qt WebEngine</span><span style="color:rgb(0,0,0);font-family:'titillium web',sans-serif;font-size:medium;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration:none;display:inline!important;float:none"> . In addition it can work on all browsers that support </span><span style="color:rgb(0,0,0);font-family:'titillium web',sans-serif;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">WebSockets</span><span style="color:rgb(0,0,0);font-family:'titillium web',sans-serif;font-size:medium;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration:none;display:inline!important;float:none"> , enabling Qt WebChannel clients to run in any JavaScript environment (including QML). This requires the implementation of a custom transport based on Qt WebSockets.</span></div>“</div><div dir="auto">So I see client/server and websockets and I think JSONverse and <a href="http://socket.io">socket.io</a>.</div><div dir="auto"><br></div><div dir="auto">AFAIK, there’s no X3D standard which includes websockets.</div><div dir="auto"><br></div><div dir="auto">But it seems like you’re more about a standard set of functions, perhaps DOM, which is common across all JS browsers.</div><div dir="auto"><br></div><div dir="auto">I don’t know if there’s an X3D DOM standard, but I suspect the best place to look is the XML encoding.</div><div dir="auto"><br></div><div dir="auto">John</div><div dir="auto"><br></div><div dir="auto"><br><div class="gmail_quote gmail_quote_container" dir="auto"><div dir="ltr" class="gmail_attr">On Tue, Feb 18, 2025 at 2:48 PM Bergstrom, Aaron <<a href="mailto:aaron.bergstrom@und.edu">aaron.bergstrom@und.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="m_-5175435957974849803WordSection1">
<p class="MsoNormal">John,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I think we are talking about two different things. What you’ve described sounds very complex and is not what I had in mind.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">So I apologize if I gave the impression that I was looking to recreate the DIS, EAI.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">This wouldn’t be communicating with external browsers or other websites.</p></div></div><div lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word"><div class="m_-5175435957974849803WordSection1"><p class="MsoNormal"><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Aaron<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> <br>
<b>Sent:</b> Tuesday, February 18, 2025 2:14 PM<br>
<b>To:</b> X3D Ecosystem public discussion <<a href="mailto:x3d-ecosystem@web3d.org" target="_blank">x3d-ecosystem@web3d.org</a>><br>
<b>Cc:</b> Bergstrom, Aaron <<a href="mailto:aaron.bergstrom@und.edu" target="_blank">aaron.bergstrom@und.edu</a>><br>
<b>Subject:</b> Re: [X3D-Ecosystem] X3DOM/X_ITE/Castle Content Preview in RawKee X3D Exporter for Maya<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Aaron,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">There is prior work on this, primarily DIS, EAI, which got folded into SAI, and
<a href="http://socket.io" target="_blank">socket.io</a> work I did on my JSONverse project. Office Towers has full multiuser avatars.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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 <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I am more interested in what goes across the network, which events, etc. WebSockets has good backing, but people are working on WebTransport now.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Might I suggest we discuss what you want to communicate before we discuss standards?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Tue, Feb 18, 2025 at 11:59 AM Bergstrom, Aaron wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">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.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">You can learn a bit more about this here:<u></u><u></u></p>
<p class="MsoNormal"><a href="https://doc.qt.io/qtforpython-6/PySide6/QtWebChannel/index.html" target="_blank">https://doc.qt.io/qtforpython-6/PySide6/QtWebChannel/index.html</a><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">And by doing a Google search based on these search request:<u></u><u></u></p>
<p class="MsoNormal">‘communicate with QtWebEngine using javascript via PySide6’<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Thoughts?<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Aaron<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal">-- <br>
X3D-Ecosystem mailing list<br>
<a href="mailto:X3D-Ecosystem@web3d.org" target="_blank">X3D-Ecosystem@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-ecosystem_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-ecosystem_web3d.org</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote></div></div>