QtDesignStudio/QMLProjectFileFormat: Difference between revisions
No edit summary |
No edit summary |
||
Line 14: | Line 14: | ||
=== Adjusting the project strucuture for legacy projects: === | === Adjusting the project strucuture for legacy projects: === | ||
Move the project module from "./import/ProjectName" to "./ProjectName". The same applies to any other module in imports. | Move the project module from "./import/ProjectName" to "./ProjectName". The same applies to any other module in imports. | ||
The URI is not affected by this. | |||
Move all modules from "./assets_imports" to "./Generated". Unfortly this also requires adjusting the import URIs throughout the project. | Move all modules from "./assets_imports" to "./Generated". Unfortly this also requires adjusting the import URIs throughout the project. |
Revision as of 13:53, 11 November 2024
With Qt Design Studio 4.5 the project structure did change.
With Qt Design Studio 4.5 we changed the project structue. The goal was to have only a single import path (./) at the root of the project. This is better in line with the QML compiler and QML tooling. (https://doc.qt.io/qt-6/qtqml-qtquick-compiler-tech.html)
The default import path is now "./" the root folder of the project, since this better matches with the requirements of the QML compiler and tooling around QML.
Before there were usually two import "imports" and "assets_imports". Also relative URIs between modules are now the same in QDS and in the compiled C++ application.
The default project module is now in ./ProjectName instead of imports/ProjectName.
Assets are now imported to "Generated" instaed of "assets_imports". QtQuick3D assets are now in Generated/QtQuick3D and Generated.Effects instead of e.g. assets_imports/QtQuick3DAssets.
Adjusting the project strucuture for legacy projects:
Move the project module from "./import/ProjectName" to "./ProjectName". The same applies to any other module in imports. The URI is not affected by this.
Move all modules from "./assets_imports" to "./Generated". Unfortly this also requires adjusting the import URIs throughout the project.