Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve loading/saving interface #23

Open
manics opened this issue Dec 7, 2019 · 1 comment
Open

Improve loading/saving interface #23

manics opened this issue Dec 7, 2019 · 1 comment

Comments

@manics
Copy link
Owner

manics commented Dec 7, 2019

Follow-up from #18

I think replacing the button to store the notebook with a periodic task (every 30s or so) that saves the current state to IndexedDB would be nice. My hunch would be that people will only remember to press the "save state" button when they try and restore the notebook (aka when it is too late).

This will require a bit of UI work so that we don't overwrite an existing stored copy without checking. A related idea is to proactively offer to load a notebook from storage when a user opens a notebook in a reloaded repository.

@betatim
Copy link
Collaborator

betatim commented Dec 8, 2019

Good point with the over-writing :-/ I hadn't thought it through that far.

Maybe an alternative way to think about this is that "save/restore from cloud" is an "expert option". In the sense that you have to think about it for a second to understand what is happening and that it requires an explicit action from the user. To help those who only remember to save stuff after it is too late maybe we could display a popup/modal after the kernel connection is gone that says "click here to download the notebook before you close the tab!!".

Needs some pondering about what is easier UI wise maybe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants