On Sun, Aug 29, 2010 at 2:59 PM, Jonas Petersson <jonas.peters...@xms.se>wrote:
> 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... > Ah, good point. Yes that is certainly something that should be supported... actually, the only significant issue I can think of is that in order to resolve an intent the caller queries the content resolver for the MIME type of its URI before finishing the call to the system process. So if you explicitly set the MIME type as well as the URI, it may just work. That said, there is no reason to need a permission to get the MIME type, so we should look at making that smoother. -- 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, 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 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
