Difference between Qt and Android APIs
-
Hi all, I want to start the topic that, what's the differences between Qt and Android development ,and specially, the APIs.
I think Qt has well-designed interfaces, but sometimes, when someone ask me, which API Qt has but Android dosen't, i just confused. Sometimes it seems that, Android has a more convenient one for the developers.
What's your opinion ?
The first one i want to highlight is the radius setting in QML: The same radius is used by all 4 corners; there is currently no way to specify different radii for different corners. And in Android APIs, it support.
I just thinking about, if the different radii for different corners, will spend more time on clicking detection or something else, so QML remove this feature.
Waiting for your opinions :)
-
[quote author="Chuck.Gao" date="1305686590"]what's the differences between Qt and Android development
[/quote]In my opinion there are too different to compare. Android is OS for mobile devices and Java is used for application development while Qt is C++ framework compatible to different OS (including Android :) )
-
[quote author="situ117" date="1305756456"]I don't think any API can beat Qt's signal/slot mechanism. Try to compare the way how events are handled in Android API.[/quote]
I have no idea about how event are handled in Android, but i think it's event driven also.
-
[quote author="leon.anavi" date="1305761086"]
In my opinion there are too different to compare. Android is OS for mobile devices and Java is used for application development while Qt is C++ framework compatible to different OS (including Android :) )
[/quote]Yes, it's true. And how about think it from APIs point of view? Just the interfaces, do you find some limits in Qt ?
-
Well, there are two major points in using Qt as I see it.
Platform independent. You can write code for multiple platforms using the same code base. It's not dependent on having a specific OS installed. Android code can only execute in a dalvik/android-environment.
Language independent. This is even better than the first point, at least for me. You can choose to develop in many different languages such as Python, Java, C#, Ruby and C++ (and there sure more options). Android is basically Java-only. I'm sure their scripting supports are actually executing by the dalvikvm.
Then I would also add that the Qt-api:s feels more generic and Android is more tailored for specific situation where you need to embedded contact manager, calendars etc in your application.
-
http://code.google.com/p/qt4dotnet/
http://techbase.kde.org/Development/Languages/QyotoI'm not sure of the status because I'm not using C# but it seems to be a rather small community behind the C# bindings.
I think the python bindings has the best support
-
[quote author="mario" date="1305786992"]Well, there are two major points in using Qt as I see it.
Platform independent. You can write code for multiple platforms using the same code base. It's not dependent on having a specific OS installed. Android code can only execute in a dalvik/android-environment.
Language independent. This is even better than the first point, at least for me. You can choose to develop in many different languages such as Python, Java, C#, Ruby and C++ (and there sure more options). Android is basically Java-only. I'm sure their scripting supports are actually executing by the dalvikvm.
Then I would also add that the Qt-api:s feels more generic and Android is more tailored for specific situation where you need to embedded contact manager, calendars etc in your application.[/quote]
Yes, a lot of language bindings. And as you says, Qt is more generic, you can use it create more beatiful things, while Android, i think maybe it's a little bit tailored. But, anyway, it depends.