Checklists
Target Users: Justin
This started as a User Story, but it's really a Use Case.
I've hit multiple times where what I really want is simply a proper Checklist Type. For example, in Querki's Design Notes, I really wanted a checklist for App Implementation. It could be hacked at the user level, but needs some enhancements under the hood to really sing.
Conceptually, a basic checklist is just a Model Type with ExactlyOne YesNo and ExactlyOne Text, which is easy. But there are two features that are currently impossible:
- When I click the checkbox, it should strike through the corresponding text.
- The text should be easily editable: I should be able to just click on the text and edit it.
Both of these are really lower-level features, and both might happen, in which case this story is really a Use Case. That first feature becomes possible when we have a websocket connection and a "live" relationship between fields. (Indeed, it's a great example of that sort of data binding.) The second becomes possible with the _editable command that I've pondered from time to time.
This is also probably a precondition for Abby's Task List Use Case.
Open Stories
Completed Stories
