Details
-
User Story
-
Resolution: Out of scope
-
Not Evaluated
-
None
-
None
Description
I (as Java/Scala/C++ programmer) wants to benefit from QML component composition, layout (or delegate that to a UI-designer) but still ensure proper separation of concerns.
After instantiating the QML View from a given ".qml" file:
- I should be able to register on the QML events my "C++/Java/Scala" (UI-)Controller event handler.
- I should be able to add/remove QML elements using "C++/Java/Scala" programatically.
- I should be able to bind the QML properties (i.e. like a Label's text or Icon's image) to "C+/Java/Scala" (ui-)data model. Or allow to define in QML a UI-data model that could be use to generate "C+/Java/Scala" (ui-)data model.
Given above description, in he perspective of MVC, I can use QML as a View specification and still use "C++/Java/Scala" for implementing the controller or/and the ui model.