On 1/31/14 10:21 AM, ext Arthur Barstow wrote:
* Do we want to continue both efforts (and thus reflect this in the
charter update)?
Given the feedback on this thread, I don't think there is consensus to
only focus on one API so I added the Mozilla FileSystem API spec to the
set of File
On Tue, 04 Feb 2014 20:48:30 +0400, Arun Ranganathan a...@mozilla.com
wrote:
On Feb 4, 2014, at 6:15 AM, Charles McCathie Nevile wrote:
On Mon, 03 Feb 2014 19:09:53 +0400, Arthur Barstow
art.bars...@nokia.com wrote:
On 1/31/14 10:44 AM, ext Ian Clelland wrote:
Hi Art,
For what it's
The great thing about Cordova is that it doesn't have to be a single
platform -- every developer has the power to choose the APIs that they want
to use, and every published app is essentially running on its own custom
web platform.
I wasn't presenting the Cordova data point as we're doing this
Hi,
In which case, what Cordova does (and more to the point what developers do
with it) seems relevant information to consider as we try to find a consensus.
For what it’s worth, we’re currently building a mobile app for use with both
Cordova and Web browsers.
The main use case of our app
On Feb 5, 2014, at 7:03 AM, Charles McCathie Nevile wrote:
Similarly the issue here is not whether we can make a specification for
one or the other approach that *could* be a standard, since it seems we
can, but whether one or the other is a clear candidate to be a real
standard - i.e. what
On Feb 5, 2014, at 11:12 AM, Ian Clelland wrote:
The great thing about Cordova is that it doesn't have to be a single platform
-- every developer has the power to choose the APIs that they want to use,
and every published app is essentially running on its own custom web platform.
I wasn't
On Feb 5, 2014, at 6:51 AM, Sebastian Kippe wrote:
For what it’s worth, we’re currently building a mobile app for use with both
Cordova and Web browsers.
The main use case of our app is caching large video files and playing them
back directly from the filesystem. So filesystem URLs are a
On Feb 4, 2014, at 6:15 AM, Charles McCathie Nevile wrote:
On Mon, 03 Feb 2014 19:09:53 +0400, Arthur Barstow art.bars...@nokia.com
wrote:
On 1/31/14 10:44 AM, ext Ian Clelland wrote:
Hi Art,
For what it's worth, theFile API: Directories and System is also
implemented (and supported)
On 2/4/14 11:48 AM, Arun Ranganathan wrote:
A web page using the FileSystem API in JavaScript and working in two separate
browser implementations seems like a good measure of interoperability
A good measure of interop is a test suite that actually tests edge cases
(something that a web page
On 1/31/14 10:44 AM, ext Ian Clelland wrote:
Hi Art,
For what it's worth, theFile API: Directories and System is also
implemented (and supported) by Apache Cordova[1]. The implementation
is essentially complete for mobile applications on Android, iOS and
FireOS, with nearly-complete support
Hi Eric, Arun, Jonas, All,
During the review of the first draft of WebApps' proposed charter
extension, Marcos raised (indirectly) a question [1] about the plan for
WebApps' various file system APIs and I agreed to followup.
We have the two specs that Eric edits:
* File API: Writer
On Jan 31, 2014, at 10:21 AM, Arthur Barstow wrote:
Hi Eric, Arun, Jonas, All,
We also have this spec from Arun and Jonas:
* FileSystem API http://w3c.github.io/filesystem-api/Overview.html. The
last update of the ED was 2-Oct-2013 and this spec has not been published as
a TR.
My
Hi Art,
For what it's worth, the File API: Directories and System is also
implemented (and supported) by Apache Cordova[1]. The implementation is
essentially complete for mobile applications on Android, iOS and FireOS,
with nearly-complete support on Blackberry and Windows Phone.
While our
Hi,
Art wrote:
My understanding is the only implementation of Eric's APIs is Chrome. I
do not know the implementation status of Mozilla's spec. If anyone has
additional information about the implementation status or plans of
either effort, please let us know.
With the usual disclaimer that
14 matches
Mail list logo
