Context Navigation

Changes between Version 63 and Version 64 of AndroidPort

v63	v64
105	105
106	106	= Implementation =
107		The [http://en.wikipedia.org/wiki/Dalvik_(software) Android VM] allows applications to call methods implemented in native code through [http://docs.oracle.com/javase/7/docs/technotes/guides/jni/index.html JNI]. This means we have to produce a native shared library which implements the core game functions as a set of methods that can be called from a "shell" application. The library and application can then be packaged and distributed together.
	107	The [http://en.wikipedia.org/wiki/Dalvik_(software) Android VM] allows applications to call methods implemented in native code through [http://docs.oracle.com/javase/7/docs/technotes/guides/jni/index.html JNI]. This means we have to produce a native shared library which implements the core game functions as a set of methods that can be called from a "shell" application running in the standard Android VM. The library and application can then be packaged and distributed together.
108	108
109	109	In the native library, we will include all the functionality that will be shared between the original game and the Android port, such as the Pyrogenesis engine and the gameplay logics. In the shell application, we will include all the functionality that will be specific to the Android port, such as the redesigned touch interface and handlers for Android system events.