Create read-only output discovery library #27

New issue

Open

opened 2026-02-10 23:51:25 +01:00 by JoshStrobl · 0 comments

JoshStrobl commented

2026-02-10 23:51:25 +01:00

Owner

Split out the logic for discovering and reading display output information from Wayland protocols (wl_output, wlr_output_management, etc.) into a standalone library.

This library should provide a unified API for getting all outputs, output properties (name, make, model, resolution, refresh rate, position, scale, etc.), and all modes regardless of which protocol is available.

Write operations (applying configurations) are out of scope and will remain in budgie-desktop-services itself, so we must be able to get the underlying heads e.g. ::zwlr_output_head_v1 to perform these ops (e.g. creating a zwlr_output_configuration_head_v1)

This will reside in its own repository.

Depends on #26

Split out the logic for discovering and reading display output information from Wayland protocols (wl_output, wlr_output_management, etc.) into a standalone library. This library should provide a unified API for getting all outputs, output properties (name, make, model, resolution, refresh rate, position, scale, etc.), and all modes regardless of which protocol is available. Write operations (applying configurations) are out of scope and will remain in budgie-desktop-services itself, so we must be able to get the underlying heads e.g. `::zwlr_output_head_v1` to perform these ops (e.g. creating a `zwlr_output_configuration_head_v1`) This will reside in its own repository. Depends on #26