CloudNebulaProject/wayray
1
0
Fork 0
mirror of https://github.com/CloudNebulaProject/wayray.git synced 2026-04-10 13:10:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
wayray/Cargo.toml

31 lines
871 B
TOML
Raw Normal View History

Set up Cargo workspace with four crates Workspace: wrsrvd, wrclient, wayray-protocol, wradm under crates/. Smithay configured with default-features=false, portable features only. Implements ADR-007 project structure.
2026-04-04 18:16:53 +02:00
[workspace]
resolver = "3"
members = [
"crates/wayray-protocol",
Implement pluggable window management protocol (Phase 2.5) Add a custom Wayland protocol (wayray_wm_v1) that allows external window manager processes to control layout, focus, and keybindings in the WayRay compositor, inspired by River's two-phase transaction model. New crates: - wayray-wm-protocol: Wayland protocol XML + generated server/client bindings via wayland-scanner for four interfaces (manager, window, seat, workspace) - wr-wm-tiling: Reference BSP tiling WM demonstrating the protocol Compositor changes: - WindowManager trait + WmState coordinator abstracts WM behavior - Built-in floating WM (centered windows, click-to-focus, z-ordering) - Protocol server with GlobalDispatch/Dispatch for all interfaces - Hot-swap (replaced event) and crash resilience (fallback to built-in) - new_toplevel delegates to WM instead of hardcoding 800x600 at (0,0) - WM render phase integrated into headless frame pipeline
2026-04-07 22:29:19 +02:00
"crates/wayray-wm-protocol",
Set up Cargo workspace with four crates Workspace: wrsrvd, wrclient, wayray-protocol, wradm under crates/. Smithay configured with default-features=false, portable features only. Implements ADR-007 project structure.
2026-04-04 18:16:53 +02:00
"crates/wrsrvd",
"crates/wrclient",
"crates/wradm",
Implement pluggable window management protocol (Phase 2.5) Add a custom Wayland protocol (wayray_wm_v1) that allows external window manager processes to control layout, focus, and keybindings in the WayRay compositor, inspired by River's two-phase transaction model. New crates: - wayray-wm-protocol: Wayland protocol XML + generated server/client bindings via wayland-scanner for four interfaces (manager, window, seat, workspace) - wr-wm-tiling: Reference BSP tiling WM demonstrating the protocol Compositor changes: - WindowManager trait + WmState coordinator abstracts WM behavior - Built-in floating WM (centered windows, click-to-focus, z-ordering) - Protocol server with GlobalDispatch/Dispatch for all interfaces - Hot-swap (replaced event) and crash resilience (fallback to built-in) - new_toplevel delegates to WM instead of hardcoding 800x600 at (0,0) - WM render phase integrated into headless frame pipeline
2026-04-07 22:29:19 +02:00
"crates/wr-wm-tiling",
Set up Cargo workspace with four crates Workspace: wrsrvd, wrclient, wayray-protocol, wradm under crates/. Smithay configured with default-features=false, portable features only. Implements ADR-007 project structure.
2026-04-04 18:16:53 +02:00
]
[workspace.package]
Initial commit Signed-off-by: Till Wegmueller <toasterson@gmail.com>
2026-03-28 18:53:00 +01:00
edition = "2024"
Set up Cargo workspace with four crates Workspace: wrsrvd, wrclient, wayray-protocol, wradm under crates/. Smithay configured with default-features=false, portable features only. Implements ADR-007 project structure.
2026-04-04 18:16:53 +02:00
version = "0.1.0"
license = "MPL-2.0"
Initial commit Signed-off-by: Till Wegmueller <toasterson@gmail.com>
2026-03-28 18:53:00 +01:00
Set up Cargo workspace with four crates Workspace: wrsrvd, wrclient, wayray-protocol, wradm under crates/. Smithay configured with default-features=false, portable features only. Implements ADR-007 project structure.
2026-04-04 18:16:53 +02:00
[workspace.dependencies]
wayray-protocol = { path = "crates/wayray-protocol" }
Implement pluggable window management protocol (Phase 2.5) Add a custom Wayland protocol (wayray_wm_v1) that allows external window manager processes to control layout, focus, and keybindings in the WayRay compositor, inspired by River's two-phase transaction model. New crates: - wayray-wm-protocol: Wayland protocol XML + generated server/client bindings via wayland-scanner for four interfaces (manager, window, seat, workspace) - wr-wm-tiling: Reference BSP tiling WM demonstrating the protocol Compositor changes: - WindowManager trait + WmState coordinator abstracts WM behavior - Built-in floating WM (centered windows, click-to-focus, z-ordering) - Protocol server with GlobalDispatch/Dispatch for all interfaces - Hot-swap (replaced event) and crash resilience (fallback to built-in) - new_toplevel delegates to WM instead of hardcoding 800x600 at (0,0) - WM render phase integrated into headless frame pipeline
2026-04-07 22:29:19 +02:00
wayray-wm-protocol = { path = "crates/wayray-wm-protocol" }
Set up Cargo workspace with four crates Workspace: wrsrvd, wrclient, wayray-protocol, wradm under crates/. Smithay configured with default-features=false, portable features only. Implements ADR-007 project structure.
2026-04-04 18:16:53 +02:00
tracing = "0.1"
tracing-subscriber = { version = "0.3", features = ["env-filter"] }
miette = { version = "7", features = ["fancy"] }
thiserror = "2"
Implement wire protocol messages and codec in wayray-protocol Message types for control, display, and input channels with serde derives. Length-prefixed postcard codec with encode/decode/framing. Seven round-trip tests covering all message types and edge cases.
2026-04-07 15:35:48 +02:00
serde = { version = "1", features = ["derive"] }
postcard = { version = "1", features = ["alloc"] }
zstd = "0.13"
Add QUIC transport layer with quinn for server and client Implement QUIC networking for wrsrvd (server) and wrclient (client) using quinn over rustls with self-signed certificates. Three logical channels: control (bidirectional), display (server->client unidirectional), and input (client->server unidirectional). Server runs tokio in a background thread, communicating with the compositor via std::sync::mpsc channels. Client exposes an async connect() API that returns a ServerConnection with methods for sending input and receiving frames. Key design note: quinn streams are lazily materialized -- accept_bi/ accept_uni on the peer won't resolve until data is written. The handshake protocol accounts for this by having each side write immediately after opening streams.
2026-04-07 16:54:01 +02:00
quinn = "0.11"
rustls = { version = "0.23", default-features = false, features = ["ring", "std"] }
rcgen = "0.13"
tokio = { version = "1", features = ["rt-multi-thread", "macros", "net", "sync"] }
Reference in a new issue Copy permalink