On 08/29/2010 09:14 PM, Dianne Hackborn wrote:
On Sun, Aug 29, 2010 at 6:46 AM, Jonas Petersson <[email protected]
<mailto:[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.
Excellent!
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?
Oh, sorry - let me clarify with an example: In one of my apps
(Inventory), each item may have an owner. For 2.x, I obviously want to
present the new cool QuickContact badge, I have stashed the contact URI
(and hopefully DISPLAY_NAME - see above) from the selection (long ago),
but ideally, my app shouldn't need access to summarize stuff in Contacts
for this URI, just hand over the URI in question along with a suitable
View and let the system access Contacts for what is needed. My point is
that my app really doesn't need to read anything from Contacts, the
badge is just for the user's convenience. I'm fairly sure this
separation can be tricky to safely implement, but still...
Best / Jonas
--
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
