Make Bigscreen a Qt shell; move login to OS

Update documentation to treat the Tauri/HTML prototype as legacy and define Bigscreen as a native Qt/QML/C++ shell. Remove in-shell PIN/login as a target feature and clarify that account selection, sign-in, and session choice are handled by a controller-friendly OS login (SDDM) implemented under Desktop Mode. Add phased plan, build/run notes for Qt vs legacy Tauri prototype, and clarify session/login workflow and responsibilities across Bigscreen/, Desktop/, and the top-level README.
This commit is contained in:
2026-05-23 17:33:12 +12:00
parent 8bea372b98
commit 627c52a5b7
3 changed files with 167 additions and 80 deletions
+41 -38
View File
@@ -58,11 +58,11 @@ It is designed for:
* Profiles
* Media-focused workflows
Bigscreen Mode is built as a fullscreen Nebula shell using Tauri, HTML, CSS, JavaScript, and a controller-first navigation system.
Bigscreen Mode is becoming a native Qt shell; the repo still contains a Tauri/HTML v0 prototype for early UI work. Sign-in and session choice happen at the OS login screen, not inside Bigscreen.
Current v0 features include:
* Lock screen with controller and keyboard PIN keypad
* Lock screen with PIN keypad in the Tauri prototype only (OS login replaces this in the target design)
* Home dashboard tile grid
* Library screen
* Settings screen
@@ -169,11 +169,13 @@ NebulaOS
│ ├── Nebula Library
│ ├── Controller Settings
│ ├── Power Menu
│ └── Profile / Lock Screen
│ └── Profile status (signed-in user; no OS login)
├── Desktop Mode
│ ├── KDE Plasma
│ ├── Nebula desktop theme
│ ├── Controller-friendly SDDM login
│ ├── Session entries (Bigscreen / Desktop)
│ ├── Desktop apps
│ └── Advanced system tools
@@ -244,7 +246,7 @@ Current features include:
* Tauri frontend shell
* Controller and keyboard input mapping
* Lock screen
* Tauri prototype lock screen (superseded by planned OS login)
* Home dashboard
* Library stub
* Settings stub
@@ -254,7 +256,7 @@ Current features include:
* Windows-first development setup
* Linux build pathway
The project is currently focused on building the Bigscreen shell first, while planning Desktop Mode as the second major pillar of the OS.
The project is building **Bigscreen Mode** (Qt shell) and **Desktop Mode** (KDE Plasma customization) in parallel. A controller-friendly **OS login** (SDDM + sessions) is part of Desktop/system work so Bigscreen does not handle account creation or sign-in.
---
@@ -397,7 +399,7 @@ Used for:
* UI development
* Controller navigation
* Lock screen work
* Bigscreen UI prototyping (legacy Tauri lock screen is not target architecture)
* Library UI
* Settings UI
* Frontend architecture
@@ -424,49 +426,50 @@ Test OS-level behavior in Linux.
## Roadmap
### Phase 1: Bigscreen Shell
### Phase 1: Desktop Mode and OS login (in progress)
Goal: Build a polished controller-first shell.
Goal: Build the KDE-based desktop layer and a controller-friendly login experience.
Deliverables:
* Lock screen
* Home dashboard
* Library screen
* Settings screen
* Power menu
* Controller navigation
* Fullscreen mode
* Basic app launching
---
### Phase 2: Desktop Mode Foundation
Goal: Create the NebulaOS desktop environment experience.
Deliverables:
* KDE Plasma setup
* Nebula theme
* SDDM login configuration
* Bigscreen and Desktop session entries
* Desktop-to-Bigscreen switching
* KDE Plasma Nebula theme and look-and-feel
* Controller-friendly SDDM login (account picker, sign-in)
* Nebula Bigscreen and Nebula Desktop session entries
* First-run / account setup at the OS layer (not inside Bigscreen)
* Desktop-to-Bigscreen and Bigscreen-to-Desktop switching
* Basic Nebula desktop tools
---
### Phase 3: Session Integration
### Phase 2: Bigscreen Qt shell
Goal: Make NebulaOS feel like a real OS experience.
Goal: Build a polished controller-first game shell that starts after OS login.
Deliverables:
* Bigscreen session selectable from login
* Desktop session selectable from login
* Bigscreen launches fullscreen
* Exit to desktop or login
* Controller works reliably in Bigscreen Mode
* Native Qt/QML Bigscreen app
* Home dashboard
* Library screen
* Settings screen
* Power menu (including log out to OS login)
* Controller navigation
* Fullscreen mode
* Basic app launching
Bigscreen does **not** deliver in-shell login, PIN lock, or account creation.
---
### Phase 3: Session polish
Goal: Make NebulaOS feel like a real OS from boot to shell.
Deliverables:
* Reliable gamepad support on SDDM and in Bigscreen
* Bigscreen launches fullscreen into the signed-in session
* Exit to desktop or return to login
* Consistent Nebula visual identity across login, Bigscreen, and Desktop
---
@@ -508,7 +511,7 @@ NebulaOS v0 is successful when:
* Bigscreen Mode can be launched fullscreen
* The entire shell is controller navigable
* The lock screen works
* OS login works with controller and keyboard (SDDM; not an in-Bigscreen lock screen)
* The Home dashboard works
* The Library can display and launch local entries
* Settings has a usable controller-first structure