Files

JFly02 a37a3c5cbe Der nächste Layer ist jetzt als echte gemeinsame Außenkante umgesetzt. Das neue API-Crate in [server.rs](</C:/Users/janni/Documents/RFP/Infinity_Vis _Rust/crates/infinity_host_api/src/server.rs>), [dto.rs](</C:/Users/janni/Documents/RFP/Infinity_Vis _Rust/crates/infinity_host_api/src/dto.rs>) und [main.rs](</C:/Users/janni/Documents/RFP/Infinity_Vis _Rust/crates/infinity_host_api/src/main.rs>) stellt die geforderten versionierten Endpunkte bereit: GET /api/v1/snapshot, GET /api/v1/catalog, GET /api/v1/presets, GET /api/v1/groups, POST /api/v1/command und WS /api/v1/stream. Die API trennt jetzt sauber zwischen Command-, State-, Preview- und Event-Modell, inklusive stabiler Außen-Enums und dokumentierten Fehlerobjekten statt eines unreflektierten 1:1-Core-Leaks.

Darauf sitzt die erste Web-UI V1 direkt gegen diese API in [index.html](</C:/Users/janni/Documents/RFP/Infinity_Vis _Rust/web/v1/index.html>), [app.js](</C:/Users/janni/Documents/RFP/Infinity_Vis _Rust/web/v1/app.js>) und [styles.css](</C:/Users/janni/Documents/RFP/Infinity_Vis _Rust/web/v1/styles.css>). Sie enthält Pattern-/Preset-Auswahl, globale Regler, Gruppenauswahl, Übergänge, Preview, Snapshot-Anzeige und Event-Feed. Die technische Desktop-GUI bleibt bewusst die Engineering-/Diagnoseoberfläche; die kreative Web-UI baut nicht an einer Parallelarchitektur vorbei.

Contract-Tests liegen in [contract.rs](</C:/Users/janni/Documents/RFP/Infinity_Vis _Rust/crates/infinity_host_api/tests/contract.rs>), und die API ist mit Beispiel-Responses in [docs/host_api.md](</C:/Users/janni/Documents/RFP/Infinity_Vis _Rust/docs/host_api.md>) dokumentiert. Zusätzlich habe ich [README.md](</C:/Users/janni/Documents/RFP/Infinity_Vis _Rust/README.md>), [docs/build_and_deploy.md](</C:/Users/janni/Documents/RFP/Infinity_Vis _Rust/docs/build_and_deploy.md>) und [docs/architecture.md](</C:/Users/janni/Documents/RFP/Infinity_Vis _Rust/docs/architecture.md>) auf den neuen Stand gebracht.

Verifiziert habe ich:
- `cargo check -p infinity_host_api`
- `cargo test -p infinity_host_api`
- `cargo test -q`

Nicht verifiziert habe ich eine separate JS-Syntaxprüfung mit `node --check`, weil `node` in dieser Umgebung nicht installiert ist.

2026-04-17 11:58:07 +02:00

2.4 KiB

Raw Blame History

Infinity Vis Rust

Production-oriented greenfield architecture for a low-latency LED control system that targets:

6 ESP32-N16R8 nodes
3 physical LED outputs per node
106 LEDs per output
18 logical panels and 1908 LEDs total

The repository is intentionally structured around hard separation of concerns:

crates/infinity_config: versioned project configuration and validation
crates/infinity_protocol: shared control and realtime protocol model
crates/infinity_host: host-side core library, simulation engine, scene/preset API, and CLI
crates/infinity_host_ui: native Rust desktop engineering GUI for mapping, diagnostics, and admin
firmware/esp32_node: ESP-IDF firmware skeleton with explicit driver abstraction
docs/: architecture, protocol, validation, deployment, testing, and acceptance artifacts
config/: example configuration files

Current software priority:

stable host-core first
shared host API for every surface
simulation and mock-first creative workflow
web UI as the primary creative surface
engineering GUI for technical operation
grandMA planned later as an external show-control adapter, not as the system core

The current baseline is intentionally strict about unresolved hardware facts. UART 6, UART 5, and UART 4 are treated as unvalidated labels until the real electrical meaning is confirmed.

Quick Start

Install a current Rust toolchain.
Review the open validation checklist in docs/validation_open_points.md.
Start from config/project.example.toml.
Inspect the software-first host snapshot with cargo run -p infinity_host -- snapshot --config config/project.example.toml.
Start the versioned host API plus creative web UI with cargo run -p infinity_host_api -- --config config/project.example.toml --bind 127.0.0.1:9001.
Open http://127.0.0.1:9001/ for the creative surface.
Start the engineering GUI with cargo run -p infinity_host_ui.
Use the host CLI to validate the project config before attempting activation.

2.4 KiB Raw Blame History

Infinity Vis Rust

Quick Start

Docs

2.4 KiB

Raw Blame History