The permission documentation is auto-generated from the declarations in the code; don't count on that to tell you anything about what APIs are actually available. You should use it the other way around -- find the official API you want, and we try to have the documentation for those link back to the permission that is needed to call it.
On Mon, Jul 6, 2009 at 4:36 PM, Chris <chris.l.elf...@intel.com> wrote: > > Thanks Diane, this is helpful and lets us cross a scenario off of our > list. > > Diane writes: > > ... > > There should be no ambiguities -- the symbols in the android jar you link > > your apps with (and corresponding the symbols in the SDK documentation) > are > > the only ones that are public. > > ... > > The source of our confusion is at > > http://developer.android.com/reference/android/Manifest.permission.html#CHANGE_CONFIGURATION > which states "Allows an application to modify the current > configuration, such as locale." Now CHANGE_CONFIGURATION is a > permission that developer applications can effectively have. For > example, the weather channel application seems to have the > CHANGE_CONFIGURATION permission. > > So the API documentation suggests that the locale is one of the things > that can be changed if the developer uses the CHANGE_CONFIGURATION > permission and we see real applications out there that are installed > with this permission so we assume that the permission actually does > have a developer visible use. So the documentation mentions as an > example of what can be done something that cannot actually be done > with that permission. In fact, the API documentation is quite vague > what exactly CAN be done with this permission. > > Diane writes: > > ... > > There are numerous permissions for things that > > applications can't do, so the APIs for them don't appear in the SDK. > > ... > > Yes, we are definately noticing this. It would be helpful for the > documentation to call out permissions that are reserved for use by the > system only and are not supported for consumption by application > developers. For these, I would imagine that the system should enforce > not allowing user installation of applications that request those > permissions. > > Thanks, > Chris > > On Jul 2, 1:59 pm, Dianne Hackborn <hack...@android.com> wrote: > > On Thu, Jul 2, 2009 at 6:31 AM, Zhao, Bingqi <bingqi.z...@intel.com> > wrote: > > > Is there intended to be a public API that allows application developers > to > > > create applications that set system locale? > > > > Not at this point. > > > > > We are trying to resolve ambiguities in the API specifications > regarding > > > what APIs are intended to be visible to application developers. > > > > There should be no ambiguities -- the symbols in the android jar you link > > your apps with (and corresponding the symbols in the SDK documentation) > are > > the only ones that are public. > > > > > So I am wondering that is there way to invoke an > > > IActivityManager.updateConfiguration() using public API of SDK? (I > think > > > there is not a way in the cupcake API ). > > > > No. > > > > > Does AOSP plan to have a public API that allows application developers > to > > > set System Locale? If no, what is the purpose of the comment > regarding > > > (user.permission.write_setting) that says that it allows setting > locale. > > > > No plans at this point. There are numerous permissions for things that > > applications can't do, so the APIs for them don't appear in the SDK. > > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see > and > > answer them. > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---