mikkeli
4cf7a786d6
The shell (shell.dart): a drawer from the left edge or each page's menu button. Dash, Signals, Captures; Tools (Camera, Link test, Orin power options), the rarely used ones, after pirate-station-aide; Settings (gateway address, dark/bright, build-time theme and landing). Landing view at build time: YUKART_HOME=dash|signals, signals for now. Dash, Signals and Captures stay alive while hidden; Captures has its own navigator, so a run survives switching views. Back goes inside Captures, then to the landing view, then out. The mock banner sits over every page. main.dart is startup only; the old home screen is pages/signals.dart; dialogs and sheets moved to actions/; the protocol client, USB binding and Reading to link/. lib/README.md catalogues it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DDwfd6Ki8UfG4hK6W5YpJz
type
| type |
|---|
| reference |
Flutter display client
Part of Project Yukart, making an old 2008 Mitsubishi Z27AG a bit smarter with modern technologies.
This file serves as the minimalist portal to other docs
What this repo is about
The in-car display. Renders vehicle telemetry and a moving map, and runs on a tablet connected to the Orin over USB or WiFi.
Flutter rather than native Android so the display unit stays swappable — the display is deliberately a separate unit from the compute, and nothing here should assume it will always be an Android tablet.
It is a bus subscriber like any other display: it talks to the message bus and to svc-gw, never to hardware.
flutter test
flutter run --dart-define=YUKART_GW=ws://<host>:7700/ # default: the car Orin, ws://192.168.55.1:7700/
- For debugging the app in the car (ADB over the Orin link), refer to ADB in the car;
- For implementation practice guidelines, refer to the guidelines;
- For implementation plans and history, refer to them;