autosave feature
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.1k
- Forks
- 129
- Avg merge
- 19h 7m
- Merged PRs (30d)
- 48
Description
Regularly, let's say every 50 commands or every five minutes (configurable ?), the scenario should be backed-up in some user folder (not in a temp directory since they are wiped on reboot, hence not useful in case of power failure).
To do
- This should certainly go in
iscore::DocumentBackupManager. Currently, the command stack is saved at each command (this should really be optimized at some point to only save the changes on each command / undo / redo), but the document is never saved. - Should the actual document be saved, or a copy of it ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with iscore::DocumentBackupManager and inspect how the command stack is currently saved after each command. Before implementation, resolve whether to save the document or a copy, then define the configurable command/time cadence and user-folder backup behavior; done means the document is backed up rather than only the command stack.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100