On Sun, Aug 29, 2010 at 6:46 AM, Jonas Petersson <[email protected]>wrote:
> I've been pondering this too for my apps, what I'd like to see is something > that just could call "pick contact" and the result would be JUST the data > related to that particular contact (for most cases, the DISPLAY_NAME would > be enough). Sort of like Intent.ACTION_INSERT_OR_EDIT but in reverse. > Yes this is absolutely the kind of thing that we need and will be introducing. Most of the infrastructure is in place -- via Intent.FLAG_GRANT_URI_READ_PERMISSION -- but I don't think the Contacts app has implemented this yet. > I'd also like to see an API to which I can just hand over handling a > "badge" to. My app in itself has no need for all the user data as long as I > can just hand over a contact URI. > I'm not sure what you mean by this. Could you explain? > And while I'm at it: last I checked, Intent.ACTION_INSERT_OR_EDIT didn't > quite support all the (to me) obvious values for putExtras() - one of my > apps would be reasonably happy without being able to write to Contacts as > long as I could trust this intent to store all the provided data. (This was > a while ago, might have been fixed for 2.2) > I suspect it hasn't been changed in 2.2, but this is the kind of thing that we should extend and if we aren't doing it fast enough would most likely accept patches for. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. 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 [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
