Eel VS kivy

In a previous post, we explore Eel, which is a cool python library that allow us to create web based GUI's for our python scripts.

Then if it grows unwieldy etc I replace that with a Builder.load_string('simplewidget.kv') .. In Kivy core you will find that everything is put in a single file data/style.kv, it avoids the overhead of loading multiple files on application startup (but I don't find this necessary for my own code so far)

When I look up EventDispatcher, it's not clear what that's contributing. https://github.com/kivy/kivy/blob/master/kivy/event.py

Kivy's event logic is written mostly in cython and can be seen here. There's a fair bit to it though as the code handles a lot of different specifics. The core idea is much simpler than it might look, essentially the event handler is storing a reference to your function and calling it later with an argument.

After some thinking, I realized a mobile/desktop app is more suitable for my task. After a little googling and comparison, I decided to go with Kivy.

See Contribute - unit tests, plus there are tools and examples for this in kivy.tests directory of core distribution - for example GraphicUnitTest class

I haven't used transitions enough to notice a problem, nor am I up to date on anything rpi.. But what's your window provider? In the old days at least, the best performance for rpi was using the egl window provider. If you are using SDL2 or X or something else, that could maybe be the reason

I haven't tested, and it doesn't really say much about the touch hardware on the product page... but on Linux almost certainly usable via kivy's mtdev input provider (using libmtdev) - doc link. If you get inverted x/y axis or other issues you can add an entry to [input] section of kivy.ini to manually configure the device

Label is special in this regard, see documentation. Now I don't mean to be rude or anything, you say you've read it, but do read the "text alignment and wrapping" again. Also play a bit with the label sizing example

Ping /u/inclemnet - I see you were involved in this for Android via kivy #4665. Could you maybe clarify if this is supposed to work on desktop platforms, or if that's a complicated thing to do?