yes, by native I was referring to .so inclusion. From my understanding it was necessary for parts of the Java libraries to be re-coded from Java to native to achieve the desired performance. So I would imagine this would be a requirement for CPU intensive applications like games, but also useful for situations with missing/ partial library support, in this case BT and wireless, or even some of the other non phone platforms in the pipeline.
Still I also understand that the Google team would like to keep some control, it's just a matter of how open is open I guess. On the other hand it's nice that there will be the some control over the core, otherwise the whole thing would get very fragmented much like linux. I guess we'll know more in a couple of weeks. Anyway I look forward to the announcements, and thanks for your response! Cheers Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
