Well, after a month or 2 of getting it going, after discovering that I need to have a java “EditBox” widget overlaid on the screen, I have now switched back to the java version. I’ll used the cmake file that has been discussed here for a while, and have patched it so that it works with Android. I’ll post the patch back to the CMake thread. But unfortunately, unless someone wants to take over, the native activity stuff is going to be laid to rest :-(. It was an interesting learning experience.
Yeah, that is a something that many developers overlook when trying to use
native activities in Android.
The Java API is still the main one to use, and the NDK is only supposed to
be used for code hotspots, at least
in Google’s opinion.–
Paulo
On Tue, Sep 11, 2012 at 5:12 AM, foufee <matthew.huck at ur.co.nz> wrote:
**
Well, after a month or 2 of getting it going, after discovering that I
need to have a java “EditBox” widget overlaid on the screen, I have now
switched back to the java version. I’ll used the cmake file that has been
discussed here for a while, and have patched it so that it works with
Android. I’ll post the patch back to the CMake thread. But unfortunately,
unless someone wants to take over, the native activity stuff is going to be
laid to rest [image: Sad]. It was an interesting learning experience.
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
Using the Java API isn’t really an option as we’re porting a commercial application that is already in C++ and is in the 100K’s of SLOC (an in house programming language, but we have apps already written using it). Having Java in the source tree wasn’t something I really wanted (already have C++, Python, C, Obj-C, CMake in the mix, didn’t really want to add another, oh well).
If anything though, have a much deeper understanding of Native Android development now 