On Feb 28, 10:37 am, Romain Guy <romain...@google.com> wrote:
> 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.
I thought adding private resources (inside the framework) would also
jumble the hex values generated into R.java file.
>From what you are saying, an Android-market app referring to
com.android.internal.R would work okay on another OEMs device that has
some new additional private resources inside its framework?
In other words, you are saying that binary compatibility of apks are
guaranteed across devices, even if one of the frameworks has new
private resources. Correct?
thanks,
-vi
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
