On Sat, Feb 28, 2009 at 6:54 PM, Romain Guy <romain...@google.com> wrote: > >> 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? > > Only if the app is recompiled for that build. ie, Source compatibility is guaranteed, which makes sense, I think.
Ideally, the Android-market app should not be referring to com.android.internal.R (except if it has used that specific old SDK, or hacked itself through) Is there a validation for market place apps, so such impure apps would be filtered out, or carry some sort of warning? > Either: > - You are writing an OEM app meant only for your device or other OEM, > and you use private resources (which means the app has to be compiled > for each build it's meant to run on) > - You keep using the current public resources > - You put the resources in your app > - You submit patches to add public resources to the Android platform Good summary, Romain. For the first case, OEMs add private resources to the framework and build apps meant to be run only on their device. However, those other impure android-market place apps, at runtime, when installed on their device, would fail without any meaningful messages? I guess, it comes down to: Is there some sort of validation for marketplace apps? Does adding private resources demand new versioning mechanism to be enforced? -Jey --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
