Now QT does not look at the cross-platform, QT also has the ability to compete with native applications.
You can go directly to the QT website to see how he works with those vendors. In comparison with Java, the framework does not seem practical to compare with Java.
If it is a C + + and Java comparison, there are many articles on the Web, you can browse by themselves, do not look at the C + + and Java comparison, black C + +, holding Python and PHP. What about Java? On one side.
On Android, there may be a lot of problems now, but with the QT update, the overall solution is 7788. Qt on Android for the original QT developers and enthusiasts is a good choice, although in Qt can do most of the Android's corresponding function, can do not knock Java code, but QT official intention is to let the program ape less Knock Java code, so provide Android extra module. (for Android 3.0 may not be perfect, but for example, a variety of sensors, cameras, localization, etc. support is perfect, webview problem seems to be solved in Qt5.5, if not the Java and C + + mixed, mixed difficult? A person is really difficult, but for the team, this kind of thing is very good to solve.
Then, QT in the final analysis, or cross-platform interface library, so for the mainstream system support will become increasingly perfect.
In addition, due to the characteristics of C + + itself, it is suitable to combine with scripting language to complete static language and dynamic language. So I'm Amway.
QML~
Qyvlik
Links: http://www.zhihu.com/question/32282261/answer/57381061
Source: Know
Copyright belongs to the author, please contact the author for authorization. In addition to the size is a little big, the native SDK pedigree pure,
No other big fault.
NetEase Battle Network client is QT Quick writes--------------------------------------------------------------------------------------------------concrete pits: http://www.zhihu.com/question/37331229------------------------------------------------------------------------ --------------------------
Not optimistic about QT for Android. Hereinafter referred to as QFA.
1. Cross-platform only has the advantage on the PC, has no advantage on the mobile device. The overall application style of the mobile device needs to be consistent, and you can add a UI that is consistent with the platform. How do you maintain this consistency of use with the native UI.
2. In the development of ease of use, the Android (Java) API has done very well, including events, broadcasts, services and so on QT some of the basic Android API has been done very well, from the QT developer to Java developers are also easy. If you want to write QFA applications, developers need not only to understand QT, but also to avoid writing Java code.
3. If you want to write and communicate with other apps, Qfa's disaster comes. If it is the upper level almost as full as the Android API to do it again. In addition to some of the device-related calls (Gps/telephony), etc., QFA of the workload suddenly came up, at this time you also expect QML?
4. What about performance? The QFA request for the graphics render area is also requested in the Java interface, and is not going to go around a big bend again.
5. Software volume. The end user wants to use the QT app, must first install a Qt lib, or in your app in the static release.
Before there are a lot of good qfa apps, people are not happy to install a big software for a good app, but will be willing to choose a native software replacement.
6. Official support. How many people are currently on the QT development team? But how many platforms are they currently supporting? Linux/windows/mac/vxworks/qnx/android. If there is not a big business level software in use QFA, the official can do is to let the software on the Android platform can compile, run, solve some obvious bugs.
7. The best chance for Qt to do Mobile is to be seen by a big spender. She has also been spotted (Nokia and Intel). But it was elop killed. I hate him!!!!!!!!!!!!!!!!!!!!!!
QT is a great development kit, I love her. Zhu Gaping
Links: http://www.zhihu.com/question/19689965/answer/22507712
Source: Know
Copyright belongs to the author, please contact the author for authorization. -------------------------------------------The Android graphics system is really good, but some of this concludes that Qt for Android has no future or is unnecessarily arbitrary.
Qt for Android still has his advantage:
1. QT Main advantage is the cross-platform, Qt5.2 has been able to support Android and iOS more complete, currently from the cross-platform in terms of QT is one of the best none.
2. After nearly 20 years of tempering,
QT has accumulated a wealth of practical, network, 2D graphics, 3D graphics and UI library, and so on, if it can be reused on Android is a good thing
3. Java is not as efficient as C + + in many complex operations, although there are ndk, but it is still a little cumbersome to use, Qt for Android in this area is much easier
4. For some C + + loyalty, but also need to develop Android applications, but do not want to learn Java Android development of the people QT provides a quick start of a good choice
5.
Qml+js can quickly and easily develop high-end atmosphere of the UI, while the efficiency is nearly 5 times times higher than the HTML5 (online assessment)
Therefore, there is no future with what technology does not have much to do with, it is important that you use it to do what application.
Leo Lei
Links: http://www.zhihu.com/question/19689965/answer/22313952
Source: Know
Copyright belongs to the author, please contact the author for authorization.
Qt for Android Evaluation (very comprehensive, basically no problem, NetEase War network client is QT Quick write), can reuse QT accumulation 20 years RTL is good, qml efficiency is HTML5 5 times times
