Expand description
Application state and TUI event loop.
The App struct owns long-lived state (config, HTTP client, cache,
downloads, and the currently active AppScreen). It drives a simple
state machine:
- render the current screen,
- wait for input,
- dispatch the key to a small handler per screen.
This is intentionally separated from the drawing code in screens/
so that alternative frontends can reuse the same "backend" services.
Structs§
- App
- Root application object for the TUI.
Enums§
- AppScreen
- All possible high-level screens in the TUI.