- Created
- 5 days ago
- Modified
- 1 day ago
- Author
~clover
- Status
- Todo
- Labels
#128plan a "reader mode" for mobile notes
basically, an optional mode that would only do vertical scroll, no zoom. this is particularly tricky to get right but we could at least make it always work if one text object exists, but making it work with more objects would be cool too. maybe if we could split every note into "main text" and "annotations" idk
the use of this is you can treat it like a text editor for basic stuff like starting lyrics but as you annotate more the it becomes useful to have the full canvas
Reader work exists at f68c9103fa67 and remains default-off in f48a5c1bf572. Native simulator checks and seven diagnostic cases confirm it is read-only, permits zoom/sideways movement, discards Undo/selection on a round trip, and collapses displayed stanza breaks; canonical notebook bytes stayed identical. The current plan starts with an editable empty/single-body column retaining the canonical editor, source/UTF-16 identities, blank paragraphs, IME, history and source anchors. Mixed-object ordering/roles remain your choice; no Android defaults were selected. Light, dark, landscape, scope. Keeping #128 Todo: this is the measured baseline and proposal.
Assisted-by: gpt-6.1-sol
Landed and pushed 76298065bb1d6758c3bce206ebf9a981c49759ed. Reading View now keeps the canonical editor editable while reflowing, locks the Reader viewport to its column, and preserves source geometry, selection, composition and original undo/redo history through round trips and local save completion. It remains opt-in/default-off; Android remains off. Exact-revision full CI passed all 11 available lanes and 106 distinct test parts. Eight actual iPhone 16e/iOS 26.3.1 scenarios passed, including independent views, four injected composition/save cuts, native keyboard/menu interaction and portrait-landscape-portrait reversible edits. Each captured actual Section.written completion and matched the entire ordered ID/author/edit queue after cold reopening the original SQLite replica. Screenshots and raw evidence stay private. Keeping this issue open for broader mixed-object Reader behavior. This does not accept #136 custody recovery. A separately reproduced landscape Done contrast defect is tracked in #143; actual Done dismissal and refocus passed.
Assisted-by: gpt-6.1-sol
~ai-clover-claude-opus-5.5 added label human · 1 day ago
Clover, 2026-10-15, for pages with several objects: "Flow them all, in reading order". Every text box goes top to bottom, left column first, wrapped to the phone and editable where it is. "Pictures shrink in, ink stays out": pictures appear in reading order at column width; ink and drawings are left out, with a small note saying the page has them. "Yes, on for real": Reading View loses its developer switch. In progress, aiming for her phone by 2026-10-16 09:00.
Assisted-by: claude-opus-5.5
On main (486eeeb2) and on Clover's iPhone since 2026-10-15. Reading View now flows every text box on a page in reading order, top to bottom and left column first, each wrapped to the phone and editable where it is. Pictures appear in order at column width, never scaled up. Drawings are left out, and a grey line at the end says the page has them. The developer switch is gone. Pages that are mostly ink or overlapping boxes, and pages with tables, math or files inside text, still aren't offered: 814 of the corpus's 966 distinct pages are. Two clean-room reviews checked that nothing in the column can pick, move or delete a drawing or picture, and that edits land in the right box. Keystroke cost is about 1 ms on a 75-paragraph page. Leaving this open for Clover's feedback.
Assisted-by: claude-opus-5.5
