robert/PedalPebble
Watch
1
0
Fork
You've already forked PedalPebble
 0
Code Issues 43 Pull requests Projects Releases 1 Packages Wiki Activity Actions

Watchapp skeleton: window stack, view switching, button handling #8

New issue
Closed
opened 2026-08-31 17:14:36 +02:00 by robert · 1 comment
robert commented 2026-08-31 17:14:36 +02:00 (Migrated from git.butzei.de)
Copy link

Goal

Set up the app shell that the three views plug into.

Acceptance criteria

  • main.c handles app lifecycle and owns the AppMessage inbox
  • Window stack with three views: ride, navigation, map
  • Up/Down cycle views; Back leaves the app with a confirmation while a ride is running
  • AppMessage opened with app_message_open(app_message_inbox_size_maximum(), app_message_outbox_size_maximum())
  • heap_bytes_free() logged at each view transition
  • Builds and runs on emery, and degrades to a usable layout on basalt (144x168)

Files

  • watchapp/src/c/main.c
  • watchapp/src/c/view_ride.c
  • watchapp/src/c/view_nav.c
  • watchapp/src/c/view_map.c

Notes

Max-size AppMessage buffers cost roughly 16 KB of heap - measure before assuming it fits.

Update — 2026-08-31: view stack becomes a page carousel

The three-view stack is replaced by a flat page ring — data pages, navigation and map all as pages of
the same carousel. Button handling moved to its own issue; see docs/DESIGN.md section 5.

This issue keeps app lifecycle, the AppMessage inbox, heap_bytes_free() logging at page transitions,
and the basalt degradation check.

## Goal Set up the app shell that the three views plug into. ## Acceptance criteria - [ ] `main.c` handles app lifecycle and owns the AppMessage inbox - [ ] Window stack with three views: ride, navigation, map - [ ] Up/Down cycle views; Back leaves the app with a confirmation while a ride is running - [ ] AppMessage opened with `app_message_open(app_message_inbox_size_maximum(), app_message_outbox_size_maximum())` - [ ] `heap_bytes_free()` logged at each view transition - [ ] Builds and runs on `emery`, and degrades to a usable layout on `basalt` (144x168) ## Files - `watchapp/src/c/main.c` - `watchapp/src/c/view_ride.c` - `watchapp/src/c/view_nav.c` - `watchapp/src/c/view_map.c` ## Notes Max-size AppMessage buffers cost roughly 16 KB of heap - measure before assuming it fits. ## Update — 2026-08-31: view stack becomes a page carousel The three-view stack is replaced by a flat page ring — data pages, navigation and map all as pages of the same carousel. Button handling moved to its own issue; see `docs/DESIGN.md` section 5. This issue keeps app lifecycle, the AppMessage inbox, `heap_bytes_free()` logging at page transitions, and the `basalt` degradation check.
robert commented 2026-09-04 09:05:48 +02:00
Owner
Copy link

Closed by PR #83 (merged): main.c app lifecycle, AppMessage inbox opened at max buffer size, and a minimal page_view.c placeholder (Select cycles the three #58 default pages, heap logged at each transition) so the heap-logging criterion has something to transition between — full carousel behaviour (Up/Down, skip-empty-page, long-press jumps) stays #60's job, not built here. Verified live in the emulator on all three targets (screenshots, real button presses), not just compiled.\n\nWorth flagging for whoever picks up #59/#60/#62 next: measured AppMessage-open heap cost is a flat 16500 bytes on every platform (8200 inbox + 8200 outbox + ~100 bookkeeping) since inbox/outbox size maximum() is platform-independent here. On basalt that leaves 44952 bytes free out of 61452 before opening (a ~27% cut, not the ~73% the PR description misstated) — still the tightest of the three targets by a wide margin, and every future feature (map polylines, sensor buffers, more AppMessage decoding) draws from that same shrunken basalt pool. Not blocking this issue, but a real number worth checking against DESIGN.md/REQUIREMENTS.md's basalt heap assumptions before #59/#62's round/template work leans on it.

Closed by PR #83 (merged): main.c app lifecycle, AppMessage inbox opened at max buffer size, and a minimal page_view.c placeholder (Select cycles the three #58 default pages, heap logged at each transition) so the heap-logging criterion has something to transition between — full carousel behaviour (Up/Down, skip-empty-page, long-press jumps) stays #60's job, not built here. Verified live in the emulator on all three targets (screenshots, real button presses), not just compiled.\n\n**Worth flagging for whoever picks up #59/#60/#62 next**: measured AppMessage-open heap cost is a flat 16500 bytes on every platform (8200 inbox + 8200 outbox + ~100 bookkeeping) since inbox/outbox size maximum() is platform-independent here. On `basalt` that leaves **44952 bytes free** out of 61452 before opening (a ~27% cut, not the ~73% the PR description misstated) — still the tightest of the three targets by a wide margin, and every future feature (map polylines, sensor buffers, more AppMessage decoding) draws from that same shrunken basalt pool. Not blocking this issue, but a real number worth checking against DESIGN.md/REQUIREMENTS.md's basalt heap assumptions before #59/#62's round/template work leans on it.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
area/gpx-cue-enricher-d59
area/round-display-support
area/rejoin-point-selection
area/digit-height-content-aware
area/geometry-enricher
area/page-template-hero1-grid6
area/nav-engine
area/cue-sheet-review
area/map-viewport-geometry
area/navigation-snapping-test-audit
area/lap-function
area/navigation-snapping
area/ble-power-meter
area/gpx-export
area/gpx-recording
area/pkjs-speed-feed
tooling/watchapp-distribution
area/csc-cadence
area/about-screen
area/backlight-policy
tooling/gpx-replay
area/derived-metrics
area/speed-pipeline-coverage-audit
area/speed-source-arbitration
area/speed-pipeline
area/stop-detector
area/ble-csc-sensor
area/persist-ride-state
area/foreground-location-service
area/protocol-version-handshake
area/real-komoot-fixture
tooling/message-keys-codegen
tooling/fix-android-platform-doc
area/settings-screen
tooling/first-real-android-build
tooling/fix-runner-label
area/cue-sheet-cache
area/route-library
area/page-template-renderer
area/colour-palette
area/page-carousel
area/ride-state-machine
area/watchapp-skeleton
tooling/host-test-harness
area/field-store-page-descriptors
tooling/ci-pipeline
area/cue-sheet-enricher-interface
area/gpx-share-import
process/security-persona
area/android-companion-skeleton
tooling/pebble-sdk-emulators
process/team-and-pipeline
dev-latest
v0.5.0
Labels
Clear labels   
area:companion
Android companion app

  
area:docs
Documentation

  
area:shared
Message contract shared by both sides

  
area:tooling
Build tooling, SDK, dev scripts

  
area:watchapp
Pebble C watchapp

  
blocker
Blocks a large part of the project until resolved

  
kind:chore
Setup, scaffolding, maintenance

  
kind:feature
New functionality

  
kind:spike
Time-boxed investigation to de-risk a decision

  
kind:test
Tests and fixtures

No labels
area:companion
area:docs
area:shared
area:tooling
area:watchapp
blocker
kind:chore
kind:feature
kind:spike
kind:test
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#10 HRM integration with sample-period lifecycle
robert/PedalPebble
#11 Ride state machine: idle / running / paused / stopped
robert/PedalPebble
#42 view_map polyline renderer
robert/PedalPebble
#45 Backlight policy for night riding
robert/PedalPebble
#60 Page carousel navigation with long-press jumps
robert/PedalPebble
Depends on
#2 Install Pebble SDK toolchain, build and run on the emery and gabbro emulators
robert/PedalPebble
Reference
robert/PedalPebble#8
No description provided.