Expose Android bindings #42
Description
I started looking into adopting accesskit for the GTK Android backend. It seems like the obvious choice, given that GTK is already using accesskit for some of the other backends.
This isn't possible right now, as accesskit-c does not provide bindings for the accesskit android platform. I haven't really understood how you are supposed to use lower-level, but the injecting adapter seems like it should be possible to use in theory. I'd rather not use the embdeded-dex stuff, but due to the way the gtk android backend works, (*env)->FindClass (env, "dev/accesskit/android/Delegate") is not going to work, as it'll only look for classes using the system class loader (GTK is run in a separate thread, without any JVM frames on the callstack). I'll somehow need a mechanism to tell accesskit the classloader its supposed to look for the class with.