On 17 Feb 2015, at 3:26 am, Benjamin Francis <[email protected]> wrote:
> On 16 February 2015 at 11:07, Marcos Caceres <[email protected]> wrote: > > - deviceStorage:* > > Maybe the Quota Management API? I've not evaluated it, but worth having a > look: > https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html > > I don't think this is particularly related. The underlying need of the Device > Storage API is a cross-origin offline file store for things like images, > audio and video which multiple apps would like to access. Is there a more > webby way fo fulfil these use cases? How should a gallery web app display the > photos taken by a camera web app for example? > > > > - contacts > > There have been various attempts to do contacts - but they got caught up on > the whole web intents thing. I think we should redo contacts, and do it > right. In particular, something that allows something as simple as: > > <input type="contact"> > > I'm not convinced we need a full contacts API like the one we use in Gaia. If > we have a dedicated storage API for contacts should we have one for calendars > and todo list items as well? As Paul explains below, the underlying need here > is a cross-origin offline database like DataStore. Can we find a web-friendly > way to share indexedDB databases between origins? Or is there another way of > fulfilling these use cases? How can a messaging web app display names next to > messages for contacts whose names are stored in a contacts web app for > example? How can an alternative homescreen web app access a list of a user's > bookmarks? How can an alternative search app search the user's browsing > history? > > Web Activities/web intents seem the right kind of solution to the contacts > picker use case. It would be great if we could make some progress > standardising that. > > > CORS enables SystemXHR-like capabilities on the Web. That's already a solved > problem. > > I hear a lot of people saying otherwise, but I don't have a productive > suggestion here. > > How is basic support for things like?: > <input type="file" accept="image/*;capture=camera"> > > Heh. I'm chuckling because that's exactly what the first commit to the camera > app [1] looked like when I wrote it in 2011. This is a world away from what > is needed to build apps like our camera app and third party apps like > Instagram. You should talk to the team who work on the camera app to gather > some use cases of what is needed above getUserMedia, David Flanagan would be > a good person to start with. Will do. I also noticed this thread around the design of the original camera control API which has a lot of detail: https://groups.google.com/forum/#!topic/mozilla.dev.webapi/_3zX2G4HCYE > > 1. > https://github.com/mozilla-b2g/gaia/commit/2c57d29a9f8823d82364a59dd7b1917ee2b77a2d > >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
