Highest Rated Comments
saurik1 karma
I am pretty certain you could just copy NativeActivity and compile it outside; that way your code on the other side would be targeting a standard interface, and would have access to all of the features of NativeActivity (your stub seems to just have onCreate: it seems like at least dealing with saved states would have been important... maybe that comes later?); developers targeting 2.3+ could then end up without the extra stub (or maybe they do; not really important). It just seemed like an interesting choice: I would have anticipated prototyping with NativeActivity to remove variables, and then compiling NativeActivity to 2.2 to achieve portability.
saurik3 karma
As all this seems to do is stub over Activity into native code, why not use the existing NativeActivity?
View HistoryShare Link