Remove TODO-fit-to-screen-layout.md: implemented by the notes grid

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
Krzysztof Rudnicki 2026-11-02 09:28:27 +01:00
parent f7ea0ffb3d
commit 9e18821c7b
2 changed files with 1 additions and 28 deletions

View File

@ -1,27 +0,0 @@
# Fit every main screen on one phone screen
## what
Todo's main screen is the notes list (ListView.separated). Convert it to a dense note-tile grid that fits the screen, paged by swipe.
## where
/home/kuhy/src/todo; screens to convert:
- lib/ui/notes_list_screen.dart: Notes — ListView.separated of notes -> 2-column title tiles with priority/status color, filter chips, paged; body/meta in long-press sheet (note_actions_sheet.dart)
Exempt: note editor and capture form (free-text editor), settings, GitHub mirror and cloud-image settings (settings)
## must
- no vertical scrolling on converted screens at 1080x2400 with status bar + nav inset
- secondary metadata/actions behind long-press or a tap sheet, not dropped
- must not: change data/sync/storage code
- optional: reuse `FitGrid` from ~/src/utils/design_system (first tag after design_system-v0.2.1); bump the app's design_system pin to that tag
## done
A widget test per converted screen at Pixel 6a geometry (`physicalSize = Size(1080, 2400)`, `devicePixelRatio = 2.625`, `padding = FakeViewPadding(top: 132, bottom: 63)`, real nav bar + mini-player/bottom chrome pumped) asserts no vertical Scrollable has maxScrollExtent > 0 and the primary actions are hit-testable; `flutter test --reporter=compact` exits 0.
## verify
Pixel 6a 23181JEGR08034, release build via ~/.claude/scripts/phone_deploy.sh, screenshot from phone_vd.sh per converted screen.
## read first
- ~/.claude/skills/build-mobile-app/SKILL.md (R7)
- ~/src/tunedeck Home tab implementation (reference pattern)
REMOVE ME AFTER FINISH

View File

@ -16,7 +16,7 @@ publish_to: 'none' # Remove this line if you wish to publish to pub.dev
# https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
# In Windows, build-name is used as the major, minor, and patch parts
# of the product and file versions while build-number is used as the build suffix.
version: 1.0.49+1
version: 1.0.50+1
environment:
sdk: ^3.12.2