Feature Request: Add QML support for C++/QML applications
Summary
It would be useful to add support for QML in projects where C++ and QML work together. Many Qt applications use C++ for backend logic and QML for the user interface, so better QML awareness would improve development, navigation, analysis, and tooling support for these projects.
Problem
Currently, C++ and QML parts of an application are often treated separately. This makes it harder to understand how QML components interact with C++ classes, properties, signals, slots, and registered types.
For example, in a typical Qt application:
- C++ classes are exposed to QML using
qmlRegisterType, qmlRegisterSingletonType, context properties, or QML modules.
- QML files access C++ properties, methods, enums, signals, and slots.
- Application behavior is split between C++ backend code and QML UI logic.
Without QML support, it becomes difficult to follow references, detect usage, analyze dependencies, or understand the full application structure.
Requested Behavior
Please add support for QML files and C++/QML integration, including:
- Recognition of
.qml files
- Understanding QML imports, components, properties, signals, and bindings
- Linking QML usage to C++ classes exposed to QML
- Support for C++ types registered with Qt/QML APIs
- Better navigation between C++ backend code and QML frontend code
- Ability to analyze applications where C++ and QML work together
Example Use Case
A Qt application may define a C++ class such as BackendController, expose it to QML, and then use it inside QML files:
qmlRegisterType<BackendController>("App.Backend", 1, 0, "BackendController");
import App.Backend 1.0
BackendController {
onStatusChanged: {
console.log(status)
}
}
In this case, it would be helpful if the tool could understand that the QML component refers to the C++ class and provide correct analysis or navigation between them.
Why This Matters
Qt applications commonly rely on both C++ and QML. Supporting only the C++ side gives an incomplete view of the project. Adding QML support would make the tool much more useful for real-world Qt/C++ applications.
Feature Request: Add QML support for C++/QML applications
Summary
It would be useful to add support for QML in projects where C++ and QML work together. Many Qt applications use C++ for backend logic and QML for the user interface, so better QML awareness would improve development, navigation, analysis, and tooling support for these projects.
Problem
Currently, C++ and QML parts of an application are often treated separately. This makes it harder to understand how QML components interact with C++ classes, properties, signals, slots, and registered types.
For example, in a typical Qt application:
qmlRegisterType,qmlRegisterSingletonType, context properties, or QML modules.Without QML support, it becomes difficult to follow references, detect usage, analyze dependencies, or understand the full application structure.
Requested Behavior
Please add support for QML files and C++/QML integration, including:
.qmlfilesExample Use Case
A Qt application may define a C++ class such as
BackendController, expose it to QML, and then use it inside QML files:In this case, it would be helpful if the tool could understand that the QML component refers to the C++ class and provide correct analysis or navigation between them.
Why This Matters
Qt applications commonly rely on both C++ and QML. Supporting only the C++ side gives an incomplete view of the project. Adding QML support would make the tool much more useful for real-world Qt/C++ applications.