Chrome app: read file in hard drive

[Stefano Corradi]

What is the best way to read (and use) files (json/audio/video) stored on the local hard disk (not in the application folder es file:///myFolder/myVideo.mp4) with a chrome app?

thank you!

[Victor Khimenko]

On Tue, May 12, 2015 at 8:05 PM, Stefano Corradi <stefano...@gmail.com> wrote:

What is the best way to read (and use) files (json/audio/video) stored on the local hard disk (not in the application folder es file:///myFolder/myVideo.mp4) with a chrome app?

Uhm... "Best" is kind of wague. Perhaps you could explain why tutorial ( https://developer.chrome.com/apps/app_storage ) haven't helped you to make a decision?

[Stefano Corradi]

the problem is that the files are not stored nell'app_storage but in different locations on the hard disk. These paths are dynamically passed through an external json

thank!

[David Brodbeck]

I don't think you can do that with the current API.  There's the chrome.fileSystem API, but it requires the user to choose a file directly from a dialog; you can't pass in an arbitrary path.  You *can*, however, retain a user-selected entry and use it again without having to prompt the user a second time.

--
You received this message because you are subscribed to the Google Groups "Chromium Apps" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-app...@chromium.org.
To post to this group, send email to chromi...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-apps/.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

--

GPG Key Fingerprint: 0DB7 4B50 8910 DBC5 B510 79C4 3970 2BC3 2078 D875

[Matt Giuca]

David is correct.

You cannot open an arbitrary path in the user's file system, for security reasons. Otherwise a Chrome App could take full control over a user's machine.

All file access abilities in Chrome Apps are either sandboxed, or require that the user grants permission to access the specific files or folders.

[Stefano Corradi]

Thanks for your answer!

Do you think that would be possible with a chromebook?

[David Brodbeck]

As far as I know, no.  Chromebooks don't get any fileSystem APIs that aren't available on other platforms.

[Matt Giuca]

Again, David is correct. The whole point of a Chromebook is that all apps are sandboxed and the user's files are safe.

(Besides, ChromeOS doesn't really *have* a file system, just a Downloads folder.)

[Dato Da]

A related question: Can I use the File System API supported by Chrome (described here http://www.html5rocks.com/en/tutorials/file/filesystem/) in a Chrome app? I tried to use it in a Chrome app, like this:

  navigator.webkitPersistentStorage.requestQuota (

    requestedBytes, 

function(grantedBytes) {  

        window.webkitRequestFileSystem(PERSISTENT, grantedBytes, onInitFs, errorHandler); 

    }, 

    function(e) { 

      console.log('Error', e); 

    }

  );

yet the call seems to be a no-op, neither the success handler nor the failure handler was called. Any insight on this behavior would be appreciated. Thanks.