dreamerBoy wrote: >> You could putter through the source code to see how the in-call >> application handles it. Again, whatever technique it uses is probably >> not for public consumption, your mileage may vary, do not taunt Happy >> Fun Android, etc. > > I thought that Android was supposed to be about empowering developers > to create new breeds of applications.
It is. However, Android is an open source project, and those who busted their asses to build the system get to call the shots at the outset -- not you, and not me. Just as Android's feature set will never ever ever meet everyone's needs, the decisions of those with commit authority will never ever ever meet everyone's needs. That's no different than any other open source project, whether started by 1 developer or 100. At least with Android, there's a sign that non-OHA developers might get such authority: http://source.android.com/project -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training on the Ranch! -- Mar 16-20, 2009 http://www.bignerdranch.com/schedule.shtml --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
