3 ms·

Can anyone comment on specifically how Kivy is better than the other options available (e.g., QT?). How have other peoples' experiences been? Some comments say

by asafira 10y ago

Can anyone comment on specifically how Kivy is better than the other options available (e.g., QT?). How have other peoples' experiences been? Some comments say small community, but that seems like it could be a large drawback honestly. Does that mean, for example, there are few(er) stack overflow posts about it, and you are likely to run into some painful issues along the way? How well does it integrate with matplotlib? How easy is it to tweak its internal widgets to your liking?

allan_s 10y ago
We were building a interface for a multi-touch table (9 meter per 1.2m) , so basically a device on which you could look on a lot of different angle, for which most GUI framework are not suitable as they have a strong opinion on what is "top" and what is "bottom" , while kivy easily permitted us to have different widget rotated
shadowmint 10y ago
QT is in every way a better choice, except for the license. Kivy is great, fun to use, but it suffers for the same thing that many python applications do: package management is a pain, packing is difficult (especially dependencies with c libraries), applications are slow, there are no threads (any action locks the UI), the bridge to native code is quite troublesome (especially on IOS), it uses a custom DSL for UI layout and the 'non native' widgets can be clunky. Don't get me wrong; it's a fun platform, but really have a good play with it before you decide to use it for anything serious, especially for mobile targets. (QT isn't perfect either; but its a rock solid platform for building real applications in. Ultimately though, you should really suck it up and write native UI for each platform and only share underlying application logic; if you don't you're just going down the road of various different levels of clunkiness on every platform).
- mixmastamyk 10y ago
  Why do you think packaging is a pain? It is possible to do things in a background thread, it may not use all cpus, but it won't block: http://stackoverflow.com/questions/37502084/download-file-with-kivy-app-without-locking-event-loop http://stackoverflow.com/questions/37502084/download-file-wi... https://github.com/kivy/kivy/wiki/Working-with-Python-threads-inside-a-Kivy-application https://github.com/kivy/kivy/wiki/Working-with-Python-thread...

by asafira 10y ago

allan_s 10y ago

We were building a interface for a multi-touch table (9 meter per 1.2m) , so basically a device on which you could look on a lot of different angle, for which most GUI framework are not suitable as they have a strong opinion on what is "top" and what is "bottom" , while kivy easily permitted us to have different widget rotated

shadowmint 10y ago

QT is in every way a better choice, except for the license. Kivy is great, fun to use, but it suffers for the same thing that many python applications do: package management is a pain, packing is difficult (especially dependencies with c libraries), applications are slow, there are no threads (any action locks the UI), the bridge to native code is quite troublesome (especially on IOS), it uses a custom DSL for UI layout and the 'non native' widgets can be clunky. Don't get me wrong; it's a fun platform, but really have a good play with it before you decide to use it for anything serious, especially for mobile targets. (QT isn't perfect either; but its a rock solid platform for building real applications in. Ultimately though, you should really suck it up and write native UI for each platform and only share underlying application logic; if you don't you're just going down the road of various different levels of clunkiness on every platform).

mixmastamyk 10y ago
Why do you think packaging is a pain? It is possible to do things in a background thread, it may not use all cpus, but it won't block: http://stackoverflow.com/questions/37502084/download-file-with-kivy-app-without-locking-event-loop http://stackoverflow.com/questions/37502084/download-file-wi... https://github.com/kivy/kivy/wiki/Working-with-Python-threads-inside-a-Kivy-application https://github.com/kivy/kivy/wiki/Working-with-Python-thread...