I wanted to make a small poll on the changes i'm about to make with both android orx port.
1) drop android-native port
android-native port require to runs on Android 2.3+ and use the NativeActivty to implement orx main loop.
Since it allow ones to write a complete android application in c/c++, I was expecting to have better performance than with a more traditional jni binding Activity.
Well, the various test i made proved me wrong. There is no measurable performance differences between both orx ports.
That was for the "pro" for android-native.
For the cons, I have one major, the impossibility to use the orx view in a layout (say you want to show an Admob banner, on top of orx). That is just not possible by design.
So, since there is no obvious advantages of using this port, I'm about to drop support for this (code will probably stay in the repo for a while in the repository, but I won't update it / maintain it anymore)
supporting two ports is a bit too much of works for me alone, so the non-native port will become the one and only orx port.
2) raise min API level for the non-native android port to 2.3
the non-native port of orx allowed me to lower the min API level down to 2.1 (not without some issues)
today, android 2.1 + android 2.2 is about 10% of the android landscape see Android Dashboard
thoses are mainly low-end devices old of about 2 years, and wont fit for orx games because of the low specs anyway.
raising the min API level to 2.3 will allow me to implement a better Sound plugin by using OpenSL ES, simplify file I/O and some other stuffs.
So I'd like to hear you opinion / question on theses changes before doing anything...