MCU-related improvements 2025

MCU-related improvements 2025

We should use this EPIC to manage and triage the issues we are fixing and to plan and prioritize new features.

Simple features/gaps

Some of them are already WIP.

• https://bugreports.qt.io/browse/QDS-12105 (cannot create sub-module in QDS WIP )
• https://bugreports.qt.io/browse/QDS-12175 (QDS does not support list type - Not directly MCU related. Does not look like low-hanging fruits)
• https://bugreports.qt.io/browse/QDS-9674 (Fonts are not copied from QtDS to qmlproject and fonts folder)
• https://bugreports.qt.io/browse/QDS-12946 (QDS does not support Image.transform - Not directly MCU related. Does not look like low-hanging fruits)

Suggested features

• Proper qmlprojectexporter integration (https://bugreports.qt.io/browse/QDS-14871)
• Fix UX for kit management (https://bugreports.qt.io/browse/QDS-14872)
• Checking unreferenced assets/qml files (https://bugreports.qt.io/browse/QDS-14873)
• Improved MCU-related wizards (https://bugreports.qt.io/browse/QDS-14874)
• Implement qmlproject editor (https://bugreports.qt.io/browse/QDS-14875)

Ongoing

Constantly review the workflow from Fgima to Qt Design Studio to target hardware. There should always be one Demo done.

Laundry demo for Qt Design Studio 4.8.

Update Mai 2025:

1. Qt Design Studio Project Must Compile Without Issues (In Progress)

• Ongoing effort to ensure compatibility and successful compilation.
• Requires continuous identification of differences between MCU and MPU targets.
• The qmlproject` exporter should be improved to perform more thorough checks during export. See: https://bugreports.qt.io/browse/QDS-14871

2. Flat QML Structure

• All QML files are placed in the root folder without categorization by default.
• Qt Design Studio does not support a submodule or directory-based structure for organizing QML files without manual steps.
• Structuring QML projects should be natively supported by Qt Design Studio.

3. Manual `qmldir` Management (In Progress)

• No built-in support for module management in QDS.
• Requires manual creation and maintenance of the `qmldir` file.
• It should be simple to create new modules and move components into them.
• This is already under active development. See: https://bugreports.qt.io/browse/QDS-12105

4. Unused Assets

• Projects often contain unused QML and image files, increasing project size and reducing maintainability.
• Tooling is needed to detect unused or oversized assets.
• Initial step: assess current asset sizes and compare them with a hardware template.
• If asset sizes exceed template limits, users should be warned.

5. Inconsistent Path Handling (In Prgress)

• Path systems differ between QUL and QDS:
    - QUL supports root QRC absolute paths.
    - QDS supports only relative paths.
• Needs urgent resolution. Suggested solution:
    - Add QRC support to QDS.
    - Allow certain folders to be assigned a QRC URL in the `qmlproject` file.
    - Adjust lookup in qml2puppet (for both preview and puppet) using `QAbstractFileEngineHandler`.
• https://bugreports.qt.io/browse/QDS-15386, https://bugreports.qt.io/browse/QDS-15385

6. Incompatible Project File Syntax (Priority)

• The `qmlproject` syntax differs between QUL and Qt Design Studio.
• These inconsistencies cause friction when switching between tools.
• Differences must be {}identified and resolved to ensure smooth interoperability.