Porting to Kivy

[xloem]

Hi,

I've been working on making a kivy library that has the same interface as your python library, and I have what I've implemented running on android. The insides of the functions make java calls; see https://github.com/xloem/kivy-gattlib/tree/master/recipes/gattlib/src/gattlib .

Would you like this work integrated into your tree? Do you have any requests on what that would look like?

I don't expect to finish porting the entire library, but I have already finished enough that others could find it very useful.

[xloem]

When I began this work, I wasn't really aware of how gattlib and kivy worked under the hood.

It would make way more sense to port this as C rather than python, since kivy also uses C under the hood, on android.

Unfortunately, I've found that gattlib is missing some features important for me, and I am more likely to find and port a different library, when I get to the point that switching to C would be relevant.

gattlib upsides:

• design would support adding pluggable backends
• backends can be written bare metal
• compatible with older and newer systems

gattlib downsides (these mostly look pretty reasonable to patch):

• presently cannot find devices that are already connected #130
• object oriented python interface doesn't provide access to device alias string for users to recognise
• presently very slow to connect to devices (possibly because I am calling connect during discovery)
• i ended up getting pretty frustrated by strange segfaults in desktop gattlib from python, dereferencing null pointers. seems to relate to the mainloop situation.