First version of WebIDE supported filehandling for local files. There are a lot of restrictions inside chrome because of security. One of them is you have to select files manually. There is no way to store or load a file without manually selecting this file in selectbox. Nothing like "file://C:..." works.
In a later version projects plugin was added. In this a local sandbox needs to be assigned. Chrome supports handling of files and directorys in a sandbox much better compared to ordinary files.
One example is searching for modules. In source window the command require("modulname") is used to search inside local sandbox for this module. Open a file by name without manual interaction is impossible. If you know a way, please let me know. I would be very interested.
Another example is the projects tab. You get a list of existing js-projects and load this into your editor. The plugin remembers this name and once you open the project-folder again, there is a save button for this project. SaveAs is supported by typing a new name into the textbox at the bottom of the list and click the save button.
Both options follow a different philosophy and have their pros and cons, take the one, which fits best for you.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
First version of WebIDE supported filehandling for local files. There are a lot of restrictions inside chrome because of security. One of them is you have to select files manually. There is no way to store or load a file without manually selecting this file in selectbox. Nothing like "file://C:..." works.
In a later version projects plugin was added. In this a local sandbox needs to be assigned. Chrome supports handling of files and directorys in a sandbox much better compared to ordinary files.
One example is searching for modules. In source window the command require("modulname") is used to search inside local sandbox for this module. Open a file by name without manual interaction is impossible. If you know a way, please let me know. I would be very interested.
Another example is the projects tab. You get a list of existing js-projects and load this into your editor. The plugin remembers this name and once you open the project-folder again, there is a save button for this project. SaveAs is supported by typing a new name into the textbox at the bottom of the list and click the save button.
Both options follow a different philosophy and have their pros and cons, take the one, which fits best for you.