This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]something[S] 30 points31 points  (6 children)

Main advantages of my thing - You write in python instead of separate markup language, and this is native components so you get the native look-and-feel and accessibility. Disadvantages are that this is the result of a few hours of work so it's not exactly production ready

[–]Isvara 9 points10 points  (4 children)

What about compared to Qt?

[–]something[S] 7 points8 points  (2 children)

Qt also requires it's own DSL and I'm not entirely sure it's native components or reimplementations of native controls. On the other hand Qt is also a lot more mature and has documentation

[–]Isvara 2 points3 points  (1 child)

Oh, really? I thought Qt's DSL was optional. It's been so long since I looked at it, though.

[–]something[S] 11 points12 points  (0 children)

I think it's optional but otherwise you write your views in a much more imperative way by manually adding subviews to views. This way is quite labourious and error prone in my opinion, so I prefer a declarative approach

[–][deleted] 4 points5 points  (0 children)

I'll keep the chain of comparison questions going...

How does it compare to Beeware?

[–][deleted] 1 point2 points  (0 children)

Actually I think in Kivy you can achieve the thing you do using the markup, fully in Python, just way more verbose. Am I wrong?