3 ms·
Those two flags only enable local file access via XHR, you still have to know the exact path to the file and you can't write anything. It would be less tricky a
by jarek-foksa 14y ago
Those two flags only enable local file access via XHR, you still have to know the exact path to the file and you can't write anything. It would be less tricky and more secure to just handle file i/o with native code.
- zoobert 14y ago@feronull @jarek-foksa. Ok thanks for the info. I agree with jarek-foksa it is still a bit tricksy and I would prefer to access the file i/o with native code. What does it means ? Do I need to build my own "file i/o" lib in c to interface with it ? Does it exist somewhere ? Would you have an example ? Many thanks
- jarek-foksa 14y agoYou have to implement a bridge between JavaScript and native environment that will allow you for passing messages between them. This is already done in Brackets, you could just copy/paste the code from https://github.com/adobe/brackets-app/blob/master/src/win/cefclient/brackets_extensions.cpp https://github.com/adobe/brackets-app/blob/master/src/win/ce... and https://github.com/adobe/brackets-app/blob/master/src/win/cefclient/res/brackets_extensions.js https://github.com/adobe/brackets-app/blob/master/src/win/ce... as it's under MIT license. With the bridge in place you can access files from JavaScript as follows: brackets.fs.readFile('path/to/file.txt', 'utf-8', function(file) { console.log(file); }); There are also corresponding methods for writing files, deleting files and reading whole directories.