Ride detail: three manual pages for totals, elevation and sensors

[timohueser]

Goal

The device ride detail shows a ride's totals, elevation and sensor data on pages that the rider turns by hand. Today two pages cycle on a 5 s timer, the units follow no single rule, and there is no room for the ride's energy or HR/power history.

Decisions

• Manual pages. Up/down turns the page, and there is no auto-cycle. Because the rider can go back and forth, more than two pages is fine. The title bar shows a page counter ("1/3") at the right, as the menus do.
• Delete ride is selected by default on every page, and a hold deletes the ride as today.
• One unit rule. A total carries its unit (17.8 km, 1:00 h, ▲120 m). An average row names the metric in the caption with the riding tiles' vocabulary (AVG KPH, AVG HR, AVG RPM, AVG PWR), and the value is a bare number.

Pages

1. Totals. The date line, and the map with the ridden track. The map band is 26 px shorter than today. Two totals lines follow: distance at the left and moving time at the right, then average speed (17.8 km/h) at the left. The right slot of the second line stays empty.
2. Elevation. The ride's elevation profile takes exactly page 1's map band. On page 1's first totals line, ▲ climb sits at the left and ▼ descent at the right, the same layout as the route detail's profile page.
3. Sensors. This page shows only when the ride has HR, cadence or power data.
   • HR and power each use the number + graph field from Effort display: zone gauge on the map, tinted HR/power tiles, kJ and 5-minute graphs #2138, with the block widened to 96 px so AVG PWR fits:
     • the block shows AVG HR or AVG PWR and the ride average, tinted in that average's zone;
     • the graph shows the whole ride in 60 buckets, each bar coloured by its zone;
     • captions use the short power word (AVG PWR, Ø W, MOY W, MED POT) and are cut to fit;
     • the zone colours come from the rider's current max HR and FTP; without a limit the field is tan with olive bars, as on the stats screen.
   • Below the graphs are the ledger rows AVG RPM and KJ, with bare numbers.
   • There is no cadence graph.

A ride without sensor data has two pages ("1/2").

Needs

• The ride's total descent. It is added to the v5 ride footer in Ride summary: descent and total kJ in the ride footer (OBRF v5) #2148.
• The whole-ride HR and power series, derived from the ride's samples when the detail opens, as the elevation profile is today. The live 5-minute history is not reused.

Mocks: real simulator renders at 240×320 (a sensor ride, a ride with HR only, and page 3 in de/fr/es).

Requirements: none