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

Persistence #2

Closed
TBurchfield opened this issue Dec 17, 2017 · 4 comments
Closed

Persistence #2

TBurchfield opened this issue Dec 17, 2017 · 4 comments

Comments

@TBurchfield
Copy link
Owner

TBurchfield commented Dec 17, 2017

Cursello needs to have persistence. This largely involves

  • Some sort of write command to write out the state to some sort of file. I would prefer to use pickle, unless you have a different suggestion.
  • Some sort of "Are you sure you want to quit without saving?" prompt if the state has changed it was last written out.
  • Most importantly, loading this information on start.
@TBurchfield
Copy link
Owner Author

Upon consideration, something like yaml might work better, so that it's human readable.

@dsmith47
Copy link
Contributor

YAML is the easiest to parse on the command line with shell tools as well.

@dsmith47
Copy link
Contributor

I'd propose a YAML module that stores a dictionary mapping List Names to lists of items (similar to how the runtime stores things) and checking for file at startup before using a default configuration (from a defaults file) and adding a trap to dump current state of cursello board on exit.

I would start storing list files in ~/.cursello/

Can start on this now if no one else wants it.

@dsmith47 dsmith47 mentioned this issue Jan 3, 2018
@TBurchfield
Copy link
Owner Author

Resolved by @dsmith47 's 91a4792

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