You must not add public resources because it would change the public API and thus make your Android phone/device potentially incompatible with other Android devices.
Private resources can be accessed through com.android.internal.R, or with a special syntax from XML. On Sat, Feb 28, 2009 at 4:51 AM, jingcheng <trustc...@gmail.com> wrote: > > why? > what prevents it in the framework code? > The OEM sometime must add some resources or hardware into it. > > On Feb 28, 4:02 am, Dianne Hackborn <hack...@android.com> wrote: >> Correct. Sorry. >> >> On Fri, Feb 27, 2009 at 5:47 AM, cht <caoht...@gmail.com> wrote: >> >> > for the OEM, if want to add some public resources, they can not do >> > that? >> > waht they added must be private? can not be accessed for the >> > android.R ? >> >> -- >> 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. All such questions should be posted on public >> forums, where I and others can see and answer them. > > > -- Romain Guy Android framework engineer romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. 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 -~----------~----~----~----~------~----~------~--~---
