I am a bit concerned about the native activity used in dev branch of 3.0. Maybe it is because I don’t understand native activity completely, or maybe the decision to move to native activity needs more thought.
- How to integrate AdMob? Java activity could use a XML layout for AdMob with OpenGL/Cocos2dx using rest of the space, how to do this with native activity? On a similar note, how to integrate Google Analytics SDK?
- How to handle orientation change? Java activity could handle the onSurfaceChanged event? How to do this with native activity?
- How to send intents and receive intents? Java activity could do startActivityForResult and receive intents in onCreate bundle, how to do this from native activity?
A few quick google searches didn’t give much useful information which makes me wonder if it was a good decision to use native activity after all. I have been using JNI a lot with cocos2dx 2.1.4, but native activity adds a whole level of complexity for seemingly simple tasks.
Is all this even possible using native activity, or should cocos2d go back to Java activity?