On Friday, 22 November 2013 at 07:48:34 UTC, eles wrote:
On Friday, 22 November 2013 at 05:30:00 UTC, Paulo Pinto wrote:
Am 22.11.2013 00:52, schrieb John J:
On 11/21/2013 05:02 PM, Paulo Pinto wrote:
Am 21.11.2013 21:25, schrieb inout:
On Thursday, 21 November 2013 at 07:35:01 UTC, Volcz wrote:
On Sunday, 17 November 2013 at 05:49:43 UTC, John J wrote:
On 11/15/2013 02:13 AM, Jeremy DeHaan wrote:
If it should survive as an alternative, Jave should have
Not to mention that Google leaves to the developers the effort
of creating the JNI wrappers themselves, instead of providing
a nice C++ API for them.
That is a Java class full of native methods for calling into
native code from Dalvik.
Now lets say you are doing a game, so NDK already provides the
necessary C, C++, OpenGL libraries.
Do you want to use Renderscript for GPGPU code? Well if targeting
Android versions lower than 4.4, you need to write the JNI
Do you want to allow the players to share their games
achievements via Google Play Game Services?
Then you need to write the JNI bindings yourself. But fear not,
Google has made a video about it,
http://www.youtube.com/watch?v=dxI5bReatJw. Lets see if part 2
ever comes up.
If you need more than graphics, sound or sensors manipulation,
then you need JNI.