[Android-development] Anatomy of a Qt 5 for Android application
bog_dan_ro at yahoo.com
Wed Jan 27 19:32:31 CET 2016
Yes, every Qt on Android application has (at least) two threads. First one is the Android UI thread where the main android event loop leaves and the Qt one where the main Qt even loop runs (if you want to understand how it works, here http://www.kdab.com/qt-android-episode-7/ you have more info about how we do calls from one world to the other).And yes, *every* single Android application needs a Java part, even those so called "Native" Android Apps they are using a small Java part (NativeActivity) which is "hidden" in Android (Java) SDK.
On Wednesday, January 27, 2016 6:25 PM, Fabrice Salvaire <fabrice.salvaire at orange.fr> wrote:
I read the blog post of Eskil Abrahamsen Blomfeldt
and I am not sure to understand this sentence
"At this point, your application takes over and can run in its thread
with no regard to the origin of the input events it is getting."
Does it mean a Qt application on Android is made of two threads where
the Java thread forwards all events (like touch events) to the Qt
thread? In other words, an application on Android must run in a Java
container and we have an overhead due to this architecture: Kernel C >
Java VM > Java Thread / Native Thread.
I found any discussion on the Qt doc on the architecture impact on
Android-development mailing list
Android-development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Android-development