W dniu środa, 17 października 2012 00:27:27 UTC+2 użytkownik Kristopher Micinski napisał: > > The NDK is for *pieces* of an app. Typically very high performance > pieces, but not the actual app itself. >
Not really, since 2.3 there are two legitimate scenarios for NDK use: 1) as you mention "high performance pieces" 2) games (or more generally full screen) In second scenario one will use NativeActivity with native event loop implementation + OpenSL for sound/music and OpenGL for graphics. Cross platform development for iOS/Android is actually quite easy because this OSes shares bunch of APIs: pthread for threading (abstracting threading is usually pain in the ass) and opengl for graphics. This means that a lot of code can be shared and with just thin abstraction layer for events, sound and resource access. -- Bart > > kris > > On Tue, Oct 16, 2012 at 6:23 PM, Kristopher Micinski > <[email protected] <javascript:>> wrote: > > On Tue, Oct 16, 2012 at 6:12 PM, Bob S <[email protected] <javascript:>> > wrote: > >>> (for the Android side, ever heard of NDK?). > >> > >> > >> Yes, that is my question! Did you read my original post? NDK would > seem to > >> be what I want, yet there are all these disclaimers when you download > it > >> that warn you away from it. They pretty much say "you do not want to > use > >> this", and I am asking why, or is there an alternative where C/C++ is > >> concerned? > >> > > > > Because you can't actually program the majority of the app in the NDK. > > Just try to use the GUI, for example, or any of the other major > > components of Android apps. > > > > kris > -- 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
