presentation should be cached in localStorage about strut

[tantaman]

How often were you thinking it should be cached? On every update or every 30 seconds or so?
Doing the latter would be simple. Doing the former, and keeping it performant, may take some time.

[jancborchardt]

I’d say on every 10 seconds (30 is a bit long) and catching the window close event and saving before that – is a great start. It can always be improved step by step.

[tantaman]

When should auto saves (for presentations that were never saved before) be removed?

Remove auto saves from the previous session when ending a new session?

[jancborchardt]

Saves should never removed until the user deletes it from the file list – or do you mean something else? For auto save, I think about just the current state of the slides being saved. There is not full-on versioning, is there?

Basically the thing is: The »save« and »save as« functions should be deprecated, everything should be autosaved. Automatic saving is the only form of saving. Ideally, when someone uses Ctrl+s, that should force a save (and suppress the default function that a system file saving dialog pops up).
It should be replaced by just a presentation list: all the presentations, plus a function to add a new one. (Like the simple document list on Litewrite [you have to hover the top left].)

[tantaman]

I like Litetwrite's auto save. That makes a lot more sense than what I was thinking of and gets rid of the concerns I had in my previous question.

No, there is no versioning.

[jancborchardt]

Yeah, versioning should probably also be a thing that gets handled by remoteStorage.js eventually.