Rituals views: wishes (list row, card, detail, timeline, compose) #180
Labels
No labels
build-dist
priority
P1
priority
P2
priority
P3
priority
P4
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Toilville/toilville-design#180
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #177. Revised: this was "wish compose wizard". It is now the pilot for the view-per-entity approach.
What it's for: the house-style views for a wish, rendered from the wish entity plus its event history. Every client uses these unless the person has a lens of their own.
Views to design
wish.created,status_changed,context_patched,activated,priority_set,dependency_declared,session_started,session_closed,progress_updatedandclosed.createcommand form (#181/#178), with the "guessed from your title" preview and a quick-capture variant.Today
macOS
WishWizard.swifthas 7 steps and Flutterwish_entry_screen.darthas 14. The macOS inbox can only mark a wish done.ritual wish browseis a terminal list.Acceptance criteria
Rituals pattern: wish compose and hydrate (the 7 questions)to Rituals views: wishes (list row, card, detail, timeline, compose)