cutepig123 / npapi-file-io Goto Github PK

What steps will reproduce the problem?
1. I tried to save a large file (8 Mg) and this function takes 50 seconds.
2.
3.

What is the expected output? What do you see instead?
The time to obtain from the server the file is 60ms. I thing the copy maked 
with *byteArrayFromNpVariant is very slowly. 

What version of the product are you using? On what operating system?
Windows

Please provide any additional information below.

Regards

Isidro

Windows 7, Chrome 17.0.963.46.


Assumes getBinaryFile, getTextFile work

NPAPI File IO test [FAILED]
/C:/Users/Nikita/Desktop/npapi-file-io/test/tests/passing/save-text-file.html
7 of 7 tests run in 66ms.
0 passed, 7 failed.
9 ms/test. 8 files loaded.
.
17:05:25.842  Start
17:05:25.844  
testSaveTextSavesNewLinesWithCarriageReturnsOnWindowsAndWithoutOnLinux : FAILED 
(run individually)
17:05:25.844  ERROR in 
testSaveTextSavesNewLinesWithCarriageReturnsOnWindowsAndWithoutOnLinux
Error calling method on NPObject.
> (unknown)
> testSaveTextSavesNewLinesWithCarriageReturnsOnWindowsAndWithoutOnLinux at 
file:///C:/Users/Nikita/Desktop/npapi-file-io/test/tests/passing/save-text-file.
html:47:12
17:05:25.860  testSavesBasicText : FAILED (run individually)
17:05:25.860  ERROR in testSavesBasicText
Error calling method on NPObject.
...

It's a nice local file I/O solution for chrome extension; I can't wait to see 
the "write" method comes out.

Probably some security issues here, as well as functionality...

npapi-file-io doesn’t seem to work on Mac. Would be nice to support Mac 
platform same way it supports Windows and Linux.

I haven’t found any docs at all.

I came here from 
http://groups.google.com/a/chromium.org/group/chromium-extensions/browse_frm/thr
ead/0372dfd06d94f55a/63a422b834ccb36a#63a422b834ccb36a. I wonder, does it 
provide JS API such as the following or not?

<embed type="application/x-my-extension" id="fs"> 
<script> 
  var fs = document.getElementById("fs"); 
  fs.writeFile("/Users/nv/dummy.txt", "bla-blah", function(err) { 
    if (!err) console.log("Hooray!"); 
  }); 
</script>

The headers in this project appear to be a snapshot of Chromium's NPAPI 
headers. Instead, it should use the authoritative source, which is:
http://code.google.com/p/npapi-sdk/
Using a specific browser's copy means picking up various local modifications 
that are generally only there for legacy reason, and add confusion.

When trying to listFiles on a directory containing symlinks, the plugin 
crashes. (linux)