Add Qt Bigscreen (QML/CMake), remove Tauri

Add a native Qt "Bigscreen" shell: CMakeLists, C++ entry (main.cpp, InputRouter), QML module (Theme, ShellWindow, views and components) and a Bigscreen/.gitignore; update top-level .gitignore and README with Qt build/run instructions. Remove the legacy Tauri/web prototype files (package.json, package-lock.json, src-tauri and many web assets) as part of the migration to the Qt/CMake-based shell.
This commit is contained in:
2026-05-23 21:19:24 +12:00
parent 627c52a5b7
commit f8632e40e7
102 changed files with 1123 additions and 17645 deletions
+38 -6
View File
@@ -304,15 +304,47 @@ The repo still contains an early **Tauri/HTML v0 prototype** under `Bigscreen/`
## Run
### Qt shell (target)
### Qt shell
Build and run instructions will be added when the Qt project lands in `Bigscreen/`. Expect a standard CMake workflow, for example:
From `Bigscreen/` (Qt 6.5+ with Quick modules installed):
```bash
cmake -S Bigscreen -B build/bigscreen -DCMAKE_BUILD_TYPE=Debug
cmake --build build/bigscreen
cmake -S . -B build -DCMAKE_BUILD_TYPE=Debug
cmake --build build --config Debug
```
On Windows, the build runs `windeployqt` automatically so Qt DLLs sit next to the executable. If you see missing `Qt6*.dll` errors, rebuild once from `Bigscreen/`:
```powershell
cmake --build build --config Debug
```
From the repo root instead:
```bash
cmake -S Bigscreen -B Bigscreen/build -DCMAKE_BUILD_TYPE=Debug
cmake --build Bigscreen/build --config Debug
```
Run the binary:
```bash
# Linux (from Bigscreen/)
./build/nebula-bigscreen
# Windows (from Bigscreen/)
build\Debug\nebula-bigscreen.exe
```
To run without redeploying, you can instead put Qt on `PATH` for that session (adjust the kit path if needed):
```powershell
$env:PATH = "C:\Qt\6.10.2\msvc2022_64\bin;" + $env:PATH
.\build\Debug\nebula-bigscreen.exe
```
**Controls (v0):** arrow keys to navigate, Enter to accept, Escape/Backspace for back, Menu key (or Start when mapped later) for the power overlay. Gamepad mapping is planned next.
### Legacy Tauri prototype
To run the existing v0 web prototype while migration is in progress, from `Bigscreen/`:
@@ -326,9 +358,9 @@ npm run dev
## Build
### Qt shell (target)
### Qt shell
Release builds will use the Qt/CMake project once it is in the tree.
Same CMake workflow as above with `-DCMAKE_BUILD_TYPE=Release`.
### Legacy Tauri prototype