Introduce target-specific display templates without coupling presentation to WFB transport.
Target behavior
Viture: FPV template, video priority, compact flight OSD
MIPI/touch: operator template, later expanded telemetry, map, and optional video widget
First implementation
Define a display target abstraction and one Viture/X11 target. Do not require MIPI hardware for this issue. Keep UI state separate from renderer/physical display.
Acceptance
A target can be selected from configuration and the display process receives a target-specific layout definition. Existing Viture kiosk behavior remains working.
## Goal
Introduce target-specific display templates without coupling presentation to WFB transport.
## Target behavior
```text
Viture: FPV template, video priority, compact flight OSD
MIPI/touch: operator template, later expanded telemetry, map, and optional video widget
```
## First implementation
Define a display target abstraction and one Viture/X11 target. Do not require MIPI hardware for this issue. Keep UI state separate from renderer/physical display.
## Acceptance
A target can be selected from configuration and the display process receives a target-specific layout definition. Existing Viture kiosk behavior remains working.
Deferred by #20. Preserve the multi-display/touchscreen architecture, but do not implement UI before OSD telemetry and adaptive-link core.
Deferred by https://git.piksar.eu/piotr/groundstation/issues/20. Preserve the multi-display/touchscreen architecture, but do not implement UI before OSD telemetry and adaptive-link core.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
Introduce target-specific display templates without coupling presentation to WFB transport.
Target behavior
First implementation
Define a display target abstraction and one Viture/X11 target. Do not require MIPI hardware for this issue. Keep UI state separate from renderer/physical display.
Acceptance
A target can be selected from configuration and the display process receives a target-specific layout definition. Existing Viture kiosk behavior remains working.
Deferred by #20. Preserve the multi-display/touchscreen architecture, but do not implement UI before OSD telemetry and adaptive-link core.