Are Nokia qt-components available in Qt 5.1 Android?
-
That's fantastic...so now I can compile my code that use nokia qt-components on android without any worry about that!?
I have a Qt mobile app (written using Symbian/MeeGo qt-components)...what I need to convert to Android/Blackberry?!
-
[quote author="AlterX" date="1371638832"]That's fantastic...so now I can compile my code that use nokia qt-components on android without any worry about that!?[/quote]I'm not sure. There has been many changes to the code -- you will likely have to make a few adjustments at least. Use the "porting guide":http://doc-snapshot.qt-project.org/qt5-stable/qtdoc/portingguide.html to help you port your old code to Qt 5.1 (pay attention to the links "C++ API Changes" and "Porting ______ Applications to Qt 5", and post your questions in this forum if you need help :)
[quote]I have a Qt mobile app (written using Symbian/MeeGo qt-components)...what I need to convert to Android/Blackberry?![/quote]I think it would depend on what features you're using. Why don't you download the "Qt 5.1 release candidate":http://download.qt-project.org/development_releases/qt/5.1/5.1.0-rc1/ and try it out? It might be easier to make it compile on the PC first (comment out your mobile-specific parts), then try to deploy it to Android.
What kind of app is it?
-
Actually I'm just using qt components for navigation among forms and phonon backend.
I was trying necessitas and I had problem with qt components integration even someone used that.This is my app: "softair real-time cooperative team":http://www.softairrealfight.net
-
By "navigation", I assume you mean buttons, menus, etc.? Those should already work for Android. Qt 5 no longer uses Phonon however; I'm not sure what needs to be done to convert your code to use Qt Multimedia.
By the way, please be aware that Android and iOS support is only at "Technical Preview" stage now -- it is not yet complete. Full support will come in Qt 5.2. See the list of "known issues":http://qt-project.org/wiki/Qt_for_Android_known_issues.
Necessitas is for Qt 4 -- Android support is integrated into Qt 5.1, so you shouldn't use the separate Necessitas package anymore. See the "documentation":http://doc-snapshot.qt-project.org/qt5-stable/qtdoc/android-support.html. for details on how to deploy Android apps.
-
[quote author="JKSH" date="1371645461"]By "navigation", I assume you mean buttons, menus, etc.? Those should already work for Android. Qt 5 no longer uses Phonon however; I'm not sure what needs to be done to convert your code to use Qt Multimedia.
[/quote]Not buttons or menu...just PageStack and so on...
[quote author="JKSH" date="1371645461"]
By the way, please be aware that Android and iOS support is only at "Technical Preview" stage now -- it is not yet complete. Full support will come in Qt 5.2. See the list of "known issues":http://qt-project.org/wiki/Qt_for_Android_known_issues.Necessitas is for Qt 4 -- Android support is integrated into Qt 5.1, so you shouldn't use the separate Necessitas package anymore. See the "documentation":http://doc-snapshot.qt-project.org/qt5-stable/qtdoc/android-support.html. for details on how to deploy Android apps.[/quote]
I know necessitas is the base of Qt 5.1 and I know it's in tech preview. But using necessitas I've just had problem with PageStack and similar and of course audio that wasn't implemented yet.
The rest of my code has worked... -
PageStack has been renamed as "StackView":http://doc-snapshot.qt-project.org/qt5-stable/qtquickcontrols/qml-qtquick-controls1-stackview.html
See "here":http://doc-snapshot.qt-project.org/qt5-stable/qtquickcontrols/qmlmodule-qtquick-controls1-qtquick-controls-1-0.html for a list of all available components, and "here":http://doc-snapshot.qt-project.org/qt5-stable/qtdoc/modules-qml.html for a list of all QML modules
-
So I have just to change these and "navigation" will be working?
-
Try it :) I don't know your code, so I can't know the answer.
-
Ok, but I think they didn't have to change Nokia qt-components interface...I mean, I know symbian and Meego are almost dead, but in this manner they can be definitively dead since there is no compatibility!
-
[quote author="AlterX" date="1371652199"]Ok, but I think they didn't have to change Nokia qt-components interface...I mean, I know symbian and Meego are almost dead, but in this manner they can be definitively dead since there is no compatibility![/quote]
Qt5 had all Symbian code removed. Nokia does not care to update it's SDKs. As far as Qt is concerned, that platform is dead, IMO.
And Meego lives as Sailfish now, and is doing quite fine :)
-
[quote author="AlterX" date="1371652199"]Ok, but I think they didn't have to change Nokia qt-components interface...I mean, I know symbian and Meego are almost dead, but in this manner they can be definitively dead since there is no compatibility![/quote]That change was to improve the API and make it consistent across the whole of Qt. It's not just qt-components -- even the core C++ API had some changes (see the porting guide I posted above)
Qt has been good with compatibility overall, IMHO -- it only changed interfaces when it was necessary, to make it easy to port old programs to Qt 5. And, it provided detailed documentation to help developers to port.