Details
-
User Story
-
Resolution: Unresolved
-
P2: Important
-
None
-
None
Description
Why?
Cause - i.e why is it needed?
- I want to be able to call QML functions from Android, either to provide data to the QML view, or to trigger special behaviors, without having to toggle a property to trigger a QML property change listener.
Customer - i.e. who needs it?
- Qt Quick for Android users i.e. Android developers bringing Qt Quick 3D rendering engine to their applications
Cruft - i.e. why it is not needed (counter arguments)?
What?
Definition - i.e what is it?
- Direct QML function calls can be called/invoked from Java or Kotlin code
Demarcation - i.e. it is not?
- TODO
Dependencies - i.e. it needs?
- TODO
How?
Effort - i.e how easy or hard does it feel?
- Extend the QtQuickViewContent java class to provide a java -> native function chain to call a function with N arguments.
- Extend the qandroidquickviewembedding native code to support above, and then call the QML function.
- Extend the code generation in ADQT to also generate Java functions that will call the native functions that call QML functions.
- Chain these together, add a test suite.
Estimate - i.e. how big is the amount of work (in calendar time)?
Essential - i.e the add on value it brings? High
When?
Flex i.e. time-bound (like platform or feature freeze) or not is it?
- Qt 6.11 FF in early December
- Force i.e. labor (do we have enough people working on it) capacity?
Fit i.e. does it fit in (like Qt release)?
- Qt 6.11?