On 21-May-09, at 12:51 PM, Nick Baum wrote: > Re:standardizing APIs, we're relying on HTML5 as much as possible. > For example, we'll provide HTML5 LocalStorage and Databases instead > of rolling our own storage API. The
That's good to know, and yeah, I assumed we'd leverage as much web- standard stuff as we could. However, there's no real HTML or w3c webapps stuff around adding bookmarks, adding notifications to status areas, etc, is there? (There's actually no HTML5 Databases spec at the moment, either, as that was broken out of the HTML5 document and put to its own proposal) > same goes for notifications once those are implemented for web apps. > Our first question when designing an extension API is "could this > just be part of HTML?". Agreed, and again, while I don't speak for the JetPack team (project lead there is a combination of Aza and Atul) I believe that's their desire, as well. > As for the browser-specific APIs (bookmarks, downloads, etc.), I'd > love to see them converge. This might take some time though, as our > asynchronous API design is very heavily shaped by our multi-process > architecture. We'll accept your patches to help Mozilla towards a more multi-process architecture in support of synchronizing those APIs! ;) cheers, mike --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
