File functionality is confusing

[auroranil]

Current functionality

You can only store one file at a time in local storage. Opening a file from a link or opening an example will cause the current file to be replaced, with some of the actions not prompting user whether they want to continue performing this action.

Download and upload functionality works fine. Google Drive integration is broken due to missing OAuth client (see #295).

Proposed functionality

A non-hierarchical file system will be created for https://marie.js.org domain, where the files will be stored in local storage. Users should be able to (re)name their file in their browser. Naming conflicts should prompt user if they want to replace this file.

Autosave functionality should still be present to ease burden of user when saving files, but it should be more immediate rather than having a 10 seconds of inactivity. If user is typing into editor then for some reason leaves that page before autosave finishes, then a prompt should be made to prevent the user from losing latest changes to their file. Users should still be able to disable autosave functionality, in which case they would need to save their file manually.

Downloading functionality should substitute in name in the OS File Save dialog from the name specified by user in the browser beforehand.

Picking file from Google Drive and saving to Google Drive should work after user logins to verified application.

Upload functionality pulls file name from chosen file, then stores it in browser. If there is a naming conflict, then prompts user whether they want to replace the current file or rename this one.

• File dropdown menu from menu bar
  • New
  • Open
    • File within browser
    • Example
  • Save
  • Import
    • Load file from your file system
    • Load file from link
    • Pick file from Google Drive
  • Export
    • Save file to your file system
    • Copy file as link
    • Save file to Google Drive

[auroranil]

Closing this issue due to it being stale.