Sorry I saw a reply 2 days ago on this thread and apparently hadn't read
your old reply so thought it was new.

On Sat, Nov 27, 2010 at 2:55 AM, Jonas Petersson <[email protected]>wrote:

> Hi Dianne,
>
> I'm not really sure why you brought this up again almost a year after I
> asked, but I guess it confirms that this will hardly be in 2.3 (eagerly
> waiting...), but I'll still keep hoping for something along these lines at
> some later stage.
>
> The recent browser security hole sort of hints that this would be a good
> idea for experienced/paranoid users - I don't really see why the browser
> needs read access to my SD card (unless it is for caching which probably
> could be safely wrapped to a sandbox in some way)
>
>                Just my few eurocents / Jonas
>
>
>
> On 11/27/2010 02:22 AM, Dianne Hackborn wrote:
>
>> No, no android:optional on <uses-permission>.  Semantically that is
>> totally different than what am talking about here, which means to still
>> allow being installed even if the device doesn't support the library (or
>> feature since you can do the same <uses-feature>).
>>
>> On Tue, Jan 19, 2010 at 1:43 AM, Jonas Petersson <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>    Hi Dianne,
>>
>>
>>    Dianne Hackborn wrote:
>>
>>        As of 2.0 I believe there is an additional attribute on
>>        uses-library that lets you specify that it is optional.
>>
>>
>>    This sounds like a really good step. However, I failed to find it
>>    mentioned in the docs (maybe I'm just looking in the wrong place).
>>
>>    When this works, could we expect it to also work for
>>    uses-permission, as outlined over a year ago? That would be a really
>>    good thing too, IMHO.
>>
>>                    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]
>>    <mailto:[email protected]>
>>
>>    To unsubscribe from this group, send email to
>>    
>> [email protected]<android-developers%[email protected]>
>>    
>> <mailto:android-developers%[email protected]<android-developers%[email protected]>
>> >
>>
>>    For more options, visit this group at
>>    http://groups.google.com/group/android-developers?hl=en
>>
>>
>>
>>
>> --
>> Dianne Hackborn
>> Android framework engineer
>> [email protected] <mailto:[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]<android-developers%[email protected]>
>> For more options, visit this group at
>> http://groups.google.com/group/android-developers?hl=en
>>
>
> --
> 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]<android-developers%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>



-- 
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

Reply via email to