Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QtWebEngine
  4. Javascript Support QtWebEngine in Autodesk Maya 2025
QtWS25 Last Chance

Javascript Support QtWebEngine in Autodesk Maya 2025

Scheduled Pinned Locked Moved Unsolved QtWebEngine
2 Posts 1 Posters 248 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    RawKeeX3D
    wrote on last edited by RawKeeX3D
    #1

    Qt Community,

    Is it possible for a user to update the javascript implementation for an existing QtWebEngine implementation to a more recent version javascript? Or does anyone have a suggestion for a workaround based on the explanation of my problem below?

    I'm porting an Autodesk Maya plugin from C++ to one based on the Maya Python 2.0 API for the purpose of exporting Maya content to the X3D file format (Web3D.org). The Python port is based on C++ code found here (links shown below to prove that the code exists):

    • Previous 2008 C++ Release - https://rawkee.sourceforge.net
    • Updated 2024 C++ Release - https://github.com/und-dream-lab/rawkee/

    In the C++ version I implemented a GUI that allowed users to prep the scene for X3D animation, HAnim, and other X3D interactivity, which I called the Interaction Editor (IE). However, much progress has been made with cross-platform X3D scene editing since I originally created the X3D exporter for Maya. Specifically, there is a web-based product called X_ITE/Sunrize that would make the IE obsolete if I could implement it within Maya using Qt WebEngine.

    • X_ITE - https://create3000.github.io/x_ite/
    • Sunrize - https://create3000.github.io/sunrize/

    However, it appears that Maya 2025's implementation of Qt via PySide 6 seems to be Qt 6.5.3, which I think uses Chrome 108 for the Qt WebEngine web browser. Unfortunately, X_ITE appears to be developed using Javascript functions [ specifically toSplice(), but probably others as well ] that requires ECMA 2023 functionality, which Chrome 108 doesn't support.

    Anyone have any ideas how I can work around this issue?

    Thanks,

    Aaron

    1 Reply Last reply
    0
    • R Offline
      R Offline
      RawKeeX3D
      wrote on last edited by
      #2

      UPDATE: After blowing up Maya 2025 by doing a pip update on mayapy for Pyside6 and all of it's subcomponents (don't do that), I communicated with the X_ITE developers. They were able to release a version of X_ITE for me that removed the ECMAScript 2023 functions, and now uses javascript that is compatible with Chrome 108 and the version of PySide6/Qt6 compatible with QWebEngine in Maya 2025.

      1 Reply Last reply
      1

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved