On 16 June 2015 at 00:59, Jonas Sicking <[email protected]> wrote: > We will definitely need a FirefoxOS-specific API which tracks the list > of URLs that have been bookmarked, and which maybe caches manifest > information as needed. Likely this API would also need to send > notifications when pins are added/removed. >
I think this API is now the biggest unknown platform dependency for the Pin the Web features for 2.5. I've been thinking about what this API might look like, and I've been struggling to think of many ways in which it is different to the existing Apps API in terms of its interface. We might say that the biggest difference is that a site no longer requires a manifest in order to be pinned/installed. But all of the features we've talked about which require Gecko to know about a pinned site actually require a manifest anyway. How will this API be substantially different than the existing Apps API? How much of this could we achieve with the existing API for "pinned apps" (i.e. sites with a manifest) and a DataStore for "pinned sites" (i.e. sites without a manifest), then just amalgamate them together in the system app like we already do for apps and bookmarks, but hide the differences from users? Should we be focusing on removing separate data jars rather than re-implementing the Apps API? Ben
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
