bbafe66ee7
QEMU-Linux boards used three competing file surfaces (workspace group with a meaningless sketch.ino/libraries.json, the VFS panel with its Upload button, and the Pi workspace's own editor). Now they behave like every other board: - the editor file group defaults to script.py for ANY Pi-family kind (kind-based check via isPiBoardKind, not the old raspberry-pi- string) - the libraries.json manifest row is hidden for Pi boards - EditorPage always renders Monaco; the RaspberryPiWorkspace swap is gone - the bottom serial panel renders the interactive xterm (PiTerminal, now seeded with session history) for running Pi boards - example vfsFiles load into the editor group (single source of truth); the run path uploads the group into the guest home - Run on a booted guest re-runs without the 45 s reboot (Ctrl-C + re-upload + run); starting a Pi board pops the terminal open - piSyncAndRunScript/piRerunScript exported from the store; auto-run now applies to the whole family (guestHome/autoRun overridable) |
||
|---|---|---|
| .. | ||
| AboutPage.css | ||
| AboutPage.tsx | ||
| ArduinoEmulatorPage.tsx | ||
| ArduinoMegaSimulatorPage.tsx | ||
| ArduinoSimulatorPage.tsx | ||
| AtmegaSimulatorPage.tsx | ||
| Attiny85SimulatorPage.tsx | ||
| CircuitSimulatorPage.tsx | ||
| CustomChipSimulatorPage.tsx | ||
| DocsPage.css | ||
| DocsPage.tsx | ||
| EditorPage.tsx | ||
| ElectronicsSimulatorPage.tsx | ||
| Esp32C3SimulatorPage.tsx | ||
| Esp32S3SimulatorPage.tsx | ||
| Esp32SimulatorPage.tsx | ||
| ExampleDetailPage.tsx | ||
| ExampleEditorPage.tsx | ||
| ExampleLoaderPage.tsx | ||
| ExamplesPage.tsx | ||
| LandingPage.css | ||
| LandingPage.tsx | ||
| PricingPlaceholder.tsx | ||
| ProjectByIdPage.tsx | ||
| RaspberryPiPicoSimulatorPage.tsx | ||
| RaspberryPiSimulatorPage.tsx | ||
| SEOPage.css | ||
| SpiceSimulatorPage.tsx | ||
| Velxio2Page.css | ||
| Velxio2Page.tsx | ||
| Velxio3Page.tsx | ||
| Velxio25Page.tsx | ||