Skip to content

Migration to Qt 6 / PySide 6 #1406

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 14 commits into from
Closed

Migration to Qt 6 / PySide 6 #1406

wants to merge 14 commits into from

Conversation

gregoire-dl
Copy link
Member

@gregoire-dl gregoire-dl commented May 4, 2021

Description

Meshroom migration to Qt 6 / PySide 6.

Features list

Missing modules for migration

  • QtCharts → Wait for Qt 6.1, now released
  • QtPositioning → Wait for Qt 6.2 now released, qt6 changes
  • QtLocation → Wait for Qt 6.5 blog post, wip 6.5 release, qt6 changes
  • QtQuick.Dialogs → Remove dependencies (Use Qt.labs.platform)
  • QtQuick.Controls 1.x → Remove dependencies (Use QtQuick.Controls 2.x)
  • QtGraphicalEffects (QML) → Remove usage

Missing features of the current branch

  • 3D Viewer (3D Graphics backend, Shader Management)
  • Node Statistics
  • Image Metadata (2D Viewer)
  • Meshroom Plugins migration

Implementation remarks

XMLHttpRequest

Using GET on a local file with XMLHttpRequest is disabled by default in Qt6.
For now, environmental variable QML_XHR_ALLOW_FILE_READ must be set to 1 to enable this feature.
Local files access might need to be rewritten in Python.

Qt Issues

https://doc-snapshots.qt.io/qt6-dev/whatsnew60.html
https://doc-snapshots.qt.io/qt6-dev/whatsnew61.html
https://doc-snapshots.qt.io/qt6-dev/whatsnew62.html
https://doc-snapshots.qt.io/qt6-dev/whatsnew63.html
https://doc-snapshots.qt.io/qt6-dev/whatsnew64.html
https://doc-snapshots.qt.io/qt6-dev/whatsnew65.html

https://doc.qt.io/qt-6/modulechanges.html

@stale
Copy link

stale bot commented Jul 31, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale for issues that becomes stale (no solution) label Jul 31, 2022
@simogasp simogasp removed the stale for issues that becomes stale (no solution) label Jul 31, 2022
@simogasp simogasp added the do not close issue that should stay open (avoid automatically close because stale) label Jul 31, 2022
@cbentejac
Copy link
Contributor

Replaced by #2599.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in progress wip work in progress
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants