Details
-
User Story
-
Resolution: Fixed
-
P2: Important
-
6.7.0 FF
-
-
2023wk34FOQtforAndroid, 2023wk36FOQtforAndroid, 2023wk38FOQtforAndroid, 2023wk40FOQtforAndroid, 2023wk42FOQtforAndroid, 2023wk44FOQtforAndroid, 2023wk46FOQtforAndroid, 2023wk48FOQtforAndroid, 2023wk50FOQtforAndroid
-
90b3b1754 (dev), d1760bc81 (dev), 4102db752 (dev), d9845e2ac (dev), 1da7acd93 (dev), 3b6d288e3 (dev), ac8c27bb1 (dev), ac7f22ed0 (dev), 820cf7fbc (dev), 17ef5be08 (dev), 1957e850e (dev), f6ad69506 (dev), 2f706df65 (dev)
Description
The current Qt for Android Java bindings have few issues that might affect the stability and performance of Qt apps
- The public bindings are too complex and big with no real user to users.
- Some parts of the bindings should be internal, yet we have them public (Loader parts).
- The architecture and relation is convoluted between the Loader, Delegate and the facing Activity class.
- Heavy use of reflection which is a bit slow and hard to maintain.
As part of this work, we want to simplify the architecture, improve the responsibilities of each part, i.e. the public bindings shouldn't do much of the internal logic, and complex relations should be broken down to simpler ones.
As part of this work, it's expected to get rid of the multiple code duplications in the Java bindings and internal codes.
Attachments
Issue Links
- covers
-
QTBUG-114075 PrivateApi in QtActivityLoader
- Closed
-
QTBUG-114074 DiscouragedApi of QtLoader.java
- Closed
- is required for
-
QTBUG-86048 Be able to have multiple activities running within the same process (on Android)
- Open
-
QTBUG-116884 Redesign Android QPA
- Closed