- led-simulator: the rig runs the C++ led-driver as WebAssembly (sim-driver/), one single-threaded worker per bar, no cross-origin isolation needed. Rooms (one JSON per room) with an on-page editor, and a pattern gallery. The Python server, Pyodide boot and ring buffer are removed. - sim-controller sim_rig.c: serves /sim/ from an embedded pack, the page's WebSocket and the rooms/flash API. The desktop build embeds it too. - bridge.c: a "browser" bridge kind that carries ESP-NOW frames to the page; devices announced through it are marked sim. - UI: Simulator in the Menu, split view with resize and pop-out, swipe between controller and rig on phones; SIM/REAL badges in Devices. - Fades: preset pushes and Wi-Fi driver bodies always carry fade and beat_time, so "off" no longer inherits an earlier fade. - Also the sequences-v2 work in progress: desktop port, bridge firmware, serial bridge, Wi-Fi drivers, sequence timeline, audio and API changes. - led-driver: ESP-NOW link, beat sync, control messages, sim hooks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
14 lines
558 B
C
14 lines
558 B
C
/*
|
|
* The simulated rig, served by the host build (desktop and sim-controller): the page at /sim/, where every
|
|
* LED bar is the C++ led-driver built to WebAssembly (sim-driver/), and the "browser" bridge that carries the
|
|
* controller's ESP-NOW frames to those drivers over the page's WebSocket. Rooms and each bar's flash are kept
|
|
* under <db>/sim/.
|
|
*/
|
|
#pragma once
|
|
|
|
#include "esp_err.h"
|
|
#include "esp_http_server.h"
|
|
|
|
// Register /sim, /sim/ws, /sim/api/* and /sim/* (call before any catch-all handler)
|
|
esp_err_t sim_rig_register(httpd_handle_t server);
|