On Jul 25, 4:25 pm, Indicator Veritatis <[email protected]> wrote: > Although I think there is a way of making this work, I have to > question why you would want to do this. It is the Java interface > (including JSR-239)that is well tested in Android.
> Recall,http://developer.android.com/sdk/ndk/index.html#overviewsays: > > "The NDK will not benefit most applications. ... Typical good > candidates for the NDK are self-contained, CPU-intensive operations > that don't allocate much memory, such as signal processing, physics > simulation, and so on." I am processing large amounts of data and generating complex graphics from it. Most of the work can be self contained in C, but it is useful to add some non-computationally-intensive stuff in Java. Believe me, I wouldn't go to NDK if I didn't have to - I made my living as a C programmer before I made it as a Java programmer, and I far prefer Java. I have run performance tests and C is *dramatically* faster for my app - in the compute-intensive areas. BTW... I did an experiment since posting the question and the C and Java co-existed quite well. I suspect the GL object handed to the GLSurfaceView callback is just a handle to the OpenGL library, with no context associated with it. If that's true, the answer to my question is: YES. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
