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.
Description
Description
Comment Actions
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...