W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2009

Re: Use Cases and Requirements for Saving Files Securely

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 10 Nov 2009 23:34:30 -0800
Message-ID: <63df84f0911102334j3d64eaf6h63209a5a132eac94@mail.gmail.com>
To: Maciej Stachowiak <mjs@apple.com>
Cc: Ian Hickson <ian@hixie.ch>, Dominique Hazael-Massieux <dom@w3.org>, "public-webapps@w3.org" <public-webapps@w3.org>, public-device-apis@w3.org
On Tue, Nov 10, 2009 at 5:53 PM, Maciej Stachowiak <mjs@apple.com> wrote:
>
> On Nov 10, 2009, at 12:36 PM, Ian Hickson wrote:
>
>> On Tue, 10 Nov 2009, Dominique Hazael-Massieux wrote:
>>>
>>> Le lundi 09 novembre 2009 à 20:08 +0000, Ian Hickson a écrit :
>>>>
>>>> Some use cases:
>>>> […]
>>>> * Ability to write a Web-based photo management application that handles
>>>>  the user's photos on the user's computer
>>>> * Ability to expose audio files to native media players
>>>> * Ability to write a Web-based media player that indexes the user's
>>>> media
>>>
>>> Note that these three use cases would be potentially better addressed by
>>> the potential Media/Gallery API the group is supposed to work on
>>> (“Gallery API, an API to manage the local media file storage” in our
>>> charter [1]).
>>
>> Wouldn't such an API be over-specialisation?
>
> Many modern platforms (well, at least iPhone and Mac OS X) have APIs to
> manipulate a system notion of media gallery. We have considered exposing the
> ability to choose from the user's media collection via <input type="file">,
> possibly keying off of accept="image/*" or "audio/*" or "video/*".

It would be awesome if you exposed it that way. That's exactly what we
have in mind too at mozilla. Won't happen in the Firefox 3.6 release,
but hopefully not long after that.

/ Jonas
Received on Wednesday, 11 November 2009 07:35:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:01 GMT