SL4A integration: SL4A's extensive API can be used before a total pyjnius port

[SL4A](https://github.com/damonkohler/sl4a/) had already implemented [lots of Android APIs](http://code.google.com/p/android-scripting/wiki/ApiReference) to be used for script languages, and [most](http://code.google.com/p/android-scripting/wiki/Tutorials) of the [examples](https://github.com/damonkohler/sl4a/tree/master/python/ase/scripts) are wrote in Python, including a [native UI subframework]
(http://code.google.com/p/python-for-android/wiki/fullscreenwrapper2) with [samples](http://code.google.com/p/python-for-android/wiki/fullscreenwrapper2#Download).

No doubt that [pyjnius](http://pyjnius.readthedocs.org/) can do [amazing](http://python-for-android.readthedocs.org/en/latest/android/#module-android.broadcast) [things](https://github.com/kivy/python-for-android/blob/master/recipes/android/src/android/broadcast.py) in a cleaner and faster (perfomant) way than [this one](http://code.google.com/p/python-for-android/source/browse/sl4atools/fullscreenwrapper2/fullscreenwrapper2.py#398), but SL4A can already provide most the API that we need without spending the time to port to pyjnius right now.

Lets accept SL4A for now and than plan on converting the whole API to pyjnius?