tburchfield / cursello Goto Github PK

We need to implement some sort of mechanism for opening a new board/switching to a saved board. Of course, this depends on #2, persistence. Once this is implemented, there should be command to switch to a new board.

If the current board hasn't been saved in it's most current state, prompt the user.

If the board they attempt to open does not exist, open it as a blank or scaffold board (perhaps with one empty list). It it does exist, open it.

This is probably a pretty small issue, if someone wants to look at it.

The cursor is being displayed to the right of the title bottom item of the rightmost list. This is not intended, the cursor should not be displayed.

This shows the issue. The cursor is displayed to the right of "test".

I tried doing with this with a stdscr.clear() at the top of the refresh_lists function, but this prevents some other things from being printed.

There's probably a better way of refactoring this functionality.

demo: https://asciinema.org/a/5KLOxND6HtJbGULdITr2QSVP6

Too long a list currently crashes cursello.
Let's make the lists have the ability to scroll, and thus have information off screen.

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.

Currently there exists no way to delete lists or items.

This is a much needed feature. "d" could delete an item, while "D" might delete the list, unless you have a suggestion for something you think works better.

BarInput fails if the user tries to write something beyond the screen size. Some sort of scrolling input would be helpful here.

In modules/cursello_io.py, the BarInput function works well, but could use some updates.

• Currently it is impossible to backspace. This is problematic from a UI perspective. Make sure to do bounds checking here.

• Some parts of BarInput are a little obfuscated. (ie while i != 10 waits until i is the ascii value that represents enter, but this isn't clear).

• Currently the prompt is erased when the user starts entering text. To me, perhaps clearer UI would be to have the user input appear following the prompt, not on top of where it was. Thoughts?

• Since #12 was resolved, the cursor is never displayed at at all. We should probably bring the cursor back when doing user input.

Some sort of command, (maybe 'a') to create a new list.