Might be better to send him an email. The comment might be missed?
On Sat, Mar 21, 2009 at 3:57 AM, Mariano Kamp <mariano.k...@gmail.com>wrote: > Sorry if I wasn't clear, but I am not the author. Having said that I'll > post a comment on his blog with a reference to this thread. > > > On Fri, Mar 20, 2009 at 9:52 PM, Dianne Hackborn <hack...@android.com>wrote: > >> Thanks for the pointer, that's nice! Might be useful to contribute to >> ApiDemos or DevTools. >> >> >> On Fri, Mar 20, 2009 at 1:01 PM, Mariano Kamp <mariano.k...@gmail.com>wrote: >> >>> http://mgmblog.com/2008/12/12/listing-androids-drawable-resources/ >>> In the code referenced above the author's code iterates over >>> android.R.drawable and puts the result in a list. It is a bit more >>> illustrative as you can actually see the icons. >>> >>> Also when looking for what's what and how should you use it, I consider >>> the API demos and the packaged apps (http://android.git.kernel.org/ -> >>> packages) quite valuable. >>> >>> 2009/3/20 Dianne Hackborn <hack...@android.com> >>> >>>> As with other resources, the official list of public resources is here: >>>> >>>> http://developer.android.com/reference/android/R.drawable.html >>>> >>>> Note that a lot of these are actually things like state list drawable >>>> XML files, which map to some set of multiple underlying images that you can >>>> not directly access. >>>> >>>> On Fri, Mar 20, 2009 at 7:42 AM, Mark Murphy >>>> <mmur...@commonsware.com>wrote: >>>> >>>>> >>>>> >> That list is... very questionable. It contains lots and lots of >>>>> >> resources >>>>> >> that are not in the public SDK, and which you should not be using. >>>>> > >>>>> > Then how about pointing us to a list that isn't questionable? Or at >>>>> least >>>>> > show us where to find said information and we'll draw up a list. >>>>> >>>>> Agreed. For example, one would hope we are encouraging people to use >>>>> the >>>>> stock option menu icons wherever possible, for consistency between >>>>> applications. However, that implies that developers know how to >>>>> reference >>>>> the stock option menu icons, which implies the existence of some sort >>>>> of >>>>> documentation. >>>>> >>>>> We do not necessarily need the core Android team to develop the >>>>> documentation, but we do need the algorithm for deducing if a resource >>>>> is >>>>> deemed "in the public SDK" or not. >>>>> >>>>> -- >>>>> Mark Murphy (a Commons Guy) >>>>> http://commonsware.com >>>>> _The Busy Coder's Guide to Android Development_ Version 2.0 Available! >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> 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. >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> -- >> 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. >> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
