[fsp] Add documentation for the File System Provider API.

[fsp] Add documentation for the File System Provider API.

This patch adds basic documentation, which is mostly auto generated.

TEST=Tested manually with a testing server.
BUG=248427
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=279959

[mtomasz, 2014-06-24 04:54:08]

@kalman: PTAL. Thanks.

Preview:
https://chrome-apps-doc.appspot.com/_patch/356463002/apps/fileSystemProvider

[not at google - send to devlin, 2014-06-24 14:25:42]

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
File chrome/common/extensions/docs/templates/intros/fileSystemProvider.html
(right):

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/templates/intros/fileSystemProvider.html:21: Most
obvious use cases are decompressing archives, or accessing files in a cloud
"Most obvious use cases" -> "Canonical use cases" or even just "Uses cases
include".

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/templates/intros/fileSystemProvider.html:29:
instead.
I don't think this paragraph is necessary and might be a bit confusing, for
example some cloud providers provide access via APIs which hide the details of
whether it's XHR or WebSockets.

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/templates/intros/fileSystemProvider.html:40: case
is decompressing archives.
I don't understand the context of this section on "File handlers". How do they
relate? This is a bit general/vague.

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/templates/intros/fileSystemProvider.html:47: file
system is <a href="method-mount">mounted</a> by a providing extension, it
"Hence, it can be assumed, that once a file system is..." -> "Hence, once a file
system is..."

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
File chrome/common/extensions/docs/templates/public/apps/fileSystemProvider.html
(right):

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/templates/public/apps/fileSystemProvider.html:1:
{{+partials.standard_apps_api api:apis.fileSystemProvider
intro:intros.fileSystemProvider/}}
please add an extension entry as well

[mtomasz, 2014-06-25 05:38:14]

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
File chrome/common/extensions/docs/templates/intros/fileSystemProvider.html
(right):

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/templates/intros/fileSystemProvider.html:21: Most
obvious use cases are decompressing archives, or accessing files in a cloud
On 2014/06/24 14:25:42, kalman wrote:
> "Most obvious use cases" -> "Canonical use cases" or even just "Uses cases
> include".

Done.

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/templates/intros/fileSystemProvider.html:29:
instead.
On 2014/06/24 14:25:42, kalman wrote:
> I don't think this paragraph is necessary and might be a bit confusing, for
> example some cloud providers provide access via APIs which hide the details of
> whether it's XHR or WebSockets.

Removed. Done.

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/templates/intros/fileSystemProvider.html:40: case
is decompressing archives.
On 2014/06/24 14:25:42, kalman wrote:
> I don't understand the context of this section on "File handlers". How do they
> relate? This is a bit general/vague.

Basically to write an extension showing contents of archives as virtual file
systems (JS replacement for FUSE), we need the input file (Entry). I clarified
the text a little. WDYT?

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/templates/intros/fileSystemProvider.html:47: file
system is <a href="method-mount">mounted</a> by a providing extension, it
On 2014/06/24 14:25:42, kalman wrote:
> "Hence, it can be assumed, that once a file system is..." -> "Hence, once a
file
> system is..."

Done.

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
File chrome/common/extensions/docs/templates/public/apps/fileSystemProvider.html
(right):

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/templates/public/apps/fileSystemProvider.html:1:
{{+partials.standard_apps_api api:apis.fileSystemProvider
intro:intros.fileSystemProvider/}}
On 2014/06/24 14:25:42, kalman wrote:
> please add an extension entry as well

Done.

[not at google - send to devlin, 2014-06-25 14:03:31]

lgtm

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
File chrome/common/extensions/docs/templates/intros/fileSystemProvider.html
(right):

https://codereview.chromium.org/356463002/diff/20001/chrome/common/extensions...
chrome/common/extensions/docs/templates/intros/fileSystemProvider.html:40: case
is decompressing archives.
On 2014/06/25 05:38:13, mtomasz wrote:
> On 2014/06/24 14:25:42, kalman wrote:
> > I don't understand the context of this section on "File handlers". How do
they
> > relate? This is a bit general/vague.
> 
> Basically to write an extension showing contents of archives as virtual file
> systems (JS replacement for FUSE), we need the input file (Entry). I clarified
> the text a little. WDYT?

lgtm

https://codereview.chromium.org/356463002/diff/40001/chrome/common/extensions...
File chrome/common/extensions/docs/templates/intros/fileSystemProvider.html
(right):

https://codereview.chromium.org/356463002/diff/40001/chrome/common/extensions...
chrome/common/extensions/docs/templates/intros/fileSystemProvider.html:19: File
System Provider API allows to write extensions providing support for
s/to write extensions providing support for/extensions to support/

[mtomasz, 2014-06-26 02:19:43]

Done. I removed the doc for extensions, since the API is currently not enabled
for extensions, but packaged apps only.

https://codereview.chromium.org/356463002/diff/40001/chrome/common/extensions...
File chrome/common/extensions/docs/templates/intros/fileSystemProvider.html
(right):

https://codereview.chromium.org/356463002/diff/40001/chrome/common/extensions...
chrome/common/extensions/docs/templates/intros/fileSystemProvider.html:19: File
System Provider API allows to write extensions providing support for
On 2014/06/25 14:03:30, kalman wrote:
> s/to write extensions providing support for/extensions to support/

Done.

[mtomasz, 2014-06-26 05:37:47]

The CQ bit was checked by mtomasz@chromium.org

[commit-bot: I haz the power, 2014-06-26 05:38:45]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/mtomasz@chromium.org/356463002/60001

[commit-bot: I haz the power, 2014-06-26 06:25:34]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)

[commit-bot: I haz the power, 2014-06-26 08:14:25]

Change committed as 279959

[not at google - send to devlin, 2014-06-26 14:38:56]

On 2014/06/26 02:19:43, mtomasz wrote:
> Done. I removed the doc for extensions, since the API is currently not enabled
> for extensions, but packaged apps only.
> 

Oh. I thought the plan was to support this for extensions, what happened?

[mtomasz, 2014-06-26 23:00:34]

On 2014/06/26 14:38:56, kalman wrote:
> On 2014/06/26 02:19:43, mtomasz wrote:
> > Done. I removed the doc for extensions, since the API is currently not
enabled
> > for extensions, but packaged apps only.
> > 
> 
> Oh. I thought the plan was to support this for extensions, what happened?

We can. Let's enable it first, then add a documentation.