Files
pipelines/android/app
alan 0b373d0c65 Make Android pane navigation adaptive with a fixed peek budget
Replace the per-level peek with a fixed total peek budget on wide windows
and drop the stack entirely on narrow ones, so a folded phone loses no
width to dead peek space and a deep stack never reserves more than the
budget.

- SlidingPaneStack gains a `wide` parameter (the callers pass the existing
  isWideLayout value). On a narrow window the budget is 0dp, so every
  pane's open offset is 0 and each opened pane is a full-window screen
  that springs in over the last; Back, the gesture and the pane's own back
  control pop one level and nothing is left on the left.
- On a wide window peekBudgetDp (PEEK_BUDGET_DP, 224dp) is the fixed total
  space shared between the covered panes, independent of depth, so the
  active pane's left edge is always exactly the budget and its width
  (hostWidth - budget) stays constant as levels are added. paneOpenOffsetsDp
  widens the leftmost strip first so it stays tappable after the start
  inset (min of PEEK_WIDTH_DP and the platform minimum interactive size),
  then splits the rest evenly. peekBudgetDp clamps so the active pane never
  collapses below MIN_ACTIVE_PANE_WIDTH_DP and paneWidthDp is never
  negative. All geometry is derived from the named tokens, the measured
  host width and the system insets - no new literals.
- The peek-strip hit targets now come from the shared offsets, and panes
  remain opaque, inset inside the safe area, hidden from accessibility when
  covered, and opening/closing stay exact mirrors through the same
  animators. PaneState documents the narrow (no peek) rule.
- SlidingPaneStackTest is rewritten around the pure budget geometry (narrow
  spends no peek, the wide active pane is constant width, four levels share
  one budget with every strip tappable, the budget clamps, tiny hosts never
  go negative), and android/README.md records the pass, its evidence and
  what was not verified.
2026-10-15 23:49:10 +01:00
..