3 ms·
Over the last few days, I was looking at building an IDE as a Chrome Packaged App, but went with node-webkit due to the file I/O limitations of Chrome. However,
by pedalpete 13y ago
Over the last few days, I was looking at building an IDE as a Chrome Packaged App, but went with node-webkit due to the file I/O limitations of Chrome. However, for many apps, the combination of ease of building a Chrome Packaged App and the automatic cross-platform capabilities (anything that runs Chrome) will further strengthen the Chromebook market.
The one thing I think is missing is more drool-worthy mid-priced machines. There are some very nice Windows 8 devices in the sub-$1000, and it seems Chromebooks jump from $400 right to the Pixel $1200+, which is a large gap in the market.
- skybrian 13y agoCould you say more about file I/O?
- pedalpete 13y agoSure, I wanted to allow the user to select a folder, and for the app to read all the sub-folders and files. Unfortunately, from my experiments, I can open a file, but opening a folder using webkitdirectory hides the path to the folder, so I can't read the folder and it's sub-directories. As I understand it, I could copy the files to the sandboxed filesystem API, but there are a few issues with working in an IDE environment which would break that usability, for example, grunt creating new files, etc. etc. Please correct me if I'm wrong. Happy to take this question to SA if that is a better venue where people would more likely look for the answer as well, if you've got a better solution. As I said, I'm keen to do this as a Chrome Packaged App, though there are a few things like Grunt that I'll want to be running within the app, so node-webkit isn't a bad solution for the prototype.