Save editor content with a possibility to recover in case of crash
Closed, ResolvedPublic

Description

In order to trust the editor the editor must never lose data.
The easiest and most reliable way for this is to save the content in regular intervals to disk.
In case such a backup file is found when starting kube we should provide a possibility to recover the content.

I'd prefer just saving it to drafts in regular intervals

hmm... I though about it as well.

The drawbacks are:

  • Saving as draft will always be more expensive than a local file as it will trigger a writeback to the server etc.
  • We can't save as draft unless we have an account selected.
  • We have to deal with new drafts that are just temporary (and thus shouldn't result in notifications or anything like that).

The benefits are:

  • One system instead of two.

Perhaps the additional complexity of a save to file + recovery dialog is worth it if we really keep it to a minimum...

cmollekopf moved this task from Backlog to 0.2 on the Kube board.Nov 15 2016, 4:53 PM
cmollekopf edited projects, added Kube (0.2); removed Kube.
cmollekopf moved this task from 0.2 to Backlog on the Kube board.Feb 21 2017, 12:42 PM
cmollekopf edited projects, added Kube; removed Kube (0.2).
cmollekopf lowered the priority of this task from Normal to Wishlist.
cmollekopf closed this task as Resolved.Jul 31 2018, 4:16 PM
cmollekopf claimed this task.

For now we just save drafts and try to avoid crashing.