Yeah, I've brought this up a couple of times before. There have been two competing specs for file system access, and the one which Cordova implements has officially "lost" now. It was only ever implemented on the desktop by Chrome; Mozilla had some serious reservations about it.
Practically, I think that this means that we should maintain the current API -- it is one of the most-used plugins out there, with almost 100,000 downloads from the plugin registry alone. Bug fixes at this point are at our discretion, and I'm sure we can stay within the "spirit" of the spec, even though it's deprecated. On the upside, we're free to extend it now, in whatever way makes sense for mobile devices :) Regarding the new spec -- it does look good: not "callbacks all the way down" like what we're used to. :) At the last f2f hangout, someone brought up the idea that we should implement the new spec, and publish that as a new plugin. Once it's out, we could refactor org.apache.cordova.file to be a thin wrapper around it. Then there would be one place to handle most of the tricky bits of file handling, apps written for the old plugin would still work, and we'd have the new API to move forward with. On Thu, Apr 24, 2014 at 4:19 PM, Andrew Grieve <agri...@chromium.org> wrote: > And thus continues the pattern of all Cordova APIs being based on > defunct specs :P. > > Do love the new Promise-based API though. > > On Thu, Apr 24, 2014 at 4:05 PM, venkata kiran surapaneni > <svkir...@gmail.com> wrote: > > Thanks for clarifying. > > > > > > On Fri, Apr 25, 2014 at 1:26 AM, Shazron <shaz...@gmail.com> wrote: > > > >> Based on this page: > >> http://www.w3.org/Mobile/mobile-web-app-state/#Data_storage > >> I think this is the new draft: > >> http://w3c.github.io/filesystem-api/Overview.html > >> (has Promises in there) > >> > >> File API seems unchanged. > >> > >> > >> On Thu, Apr 24, 2014 at 12:37 PM, Shazron <shaz...@gmail.com> wrote: > >> > >> > http://www.w3.org/TR/file-system-api/ > >> > > >> > "*Work on this document has been discontinued and it should not be > >> > referenced or used as a basis for implementation."* > >> > > >> > > >> > > >> > > > > > > > > -- > > Thanks & Regards, > > -Kiran >
