On Wed, Jan 26, 2011 at 4:05 PM, Hari Edo <[email protected]> wrote: > > On Jan 26, 2:53 pm, Mark Murphy <[email protected]> wrote: >> I would recommend that developers depend as little as possible on >> explicitly using firmware-defined resources. If you need them, copy >> their values into your project. Or, at least have a value that you use >> as a fallback in case a firmware-defined resource is not available. > > While I understand that sentiment, it's not practical. Widgets > like Button constantly use built-in firmware-defined resources.
I wrote: "I would recommend that developers depend as little as possible on explicitly using firmware-defined resources." The key word there being "explicitly". As in "you type in android.R.color.foo or @android:drawable/bar". Button will take care of itself with respect to firmware-defined resources. While a device manufacturer can change the definitions of certain resources (and even get rid of them, apparently), they can't break compatibility so bad that Button fails to work. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in London: http://bit.ly/smand1 and http://bit.ly/smand2 -- 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
