Re:Qt for Android better than ever before
by kuschku on Thursday October 10, 2019 @11:29AM
(#21215631)
Even with native Java/Kotlin on Android it's pretty hard to reliably run background service, if not to say impossible (most manufacturers make it impossible, and even on Google devices it's impossible on Marshmallow).
Re:Qt for Android better than ever before
by oever on Thursday October 10, 2019 @11:34AM
(#21215717)
Qt6 will have faster and lower footprint QML because JavaScript will be optional.
Also QML will gain type checking.
Re:Qt for Android better than ever before
by dkersten on Thursday October 10, 2019 @12:02PM
(#21216056)
Is there a timeline or target release date for Qt6 yet?
Re:Qt for Android better than ever before
by jcelerier on Thursday October 10, 2019 @12:25PM
(#21216357)
https://www.qt.io/blog/2019/08/07/technical-vision-qt-6
TL;DR : "we’re aiming to have Qt 6.0 ready for a first release by the end of 2020."
Re:Qt for Android better than ever before
by dkersten on Thursday October 10, 2019 @02:27PM
(#21217664)
Thank you! I read that page, but I guess I didn't read it properly.
Re:Qt for Android better than ever before
by cjslep on Thursday October 10, 2019 @11:37AM
(#21215757)
I had to create a Qt JNI app... That was entirely run as a background service. It was quite the wizardry, and did require a little bit of Cyanogen kernel hacking from a coworker.
Re:Qt for Android better than ever before
by yellow_lead on Thursday October 10, 2019 @12:48PM
(#21216662)
If you want a background service you currently have to create the code for it in Java, and call that code with the JNI. You can register callbacks for communicating the other direction (towards native code). A pain, but possible.
Re:Qt for Android better than ever before
by The_rationalist on Thursday October 10, 2019 @02:38PM
(#21217761)
Could you do a comparison of why using QT js instead of electron/ionic?
Re:Qt for Android better than ever before
by allenskd on Thursday October 10, 2019 @07:15PM
(#21220172)
It's not a comparison I can do. I haven't used ionic extensively enough to put out a well-thought out comparison that can expose the layers of complexities and the pros and cons of how we can benefit from each technology.
I have yet to use electron tho... I haven't done a personal project in a long time to play with it.
Qt is amazing and so is QML. I still found QML JavaScript engine utilizing a lot of memory back then as well and I don't know if it has been fine-tuned these days.