Wayland compositor In design

Phosphor

Phosphor is a standalone Wayland compositor with window placement at its core. It runs the same snapping, tiling and scrolling engines as PlasmaZones, inside the compositor instead of beside it, and Lambent draws on top.

In design. The compositor has a full technical design and a phased plan, and nothing you can run yet. Today the placement engines run inside KWin through PlasmaZones, and the phosphor-compositor library defines the bridge both hosts implement.

Approach

The plan

Ten phases, each with its own design document. The first four build a compositor that can drive a screen and take input. The rest connect placement, the shell, decorations, XWayland and plugins.

  1. 0

    Skeleton

    Build setup, a headless backend and the event loop.

  2. 1

    Core protocols

    Core Wayland protocols, the scene graph and the surface state machine.

  3. 2

    DRM and sessions

    Kernel mode setting, session management and output lifecycle.

  4. 3

    Rendering

    The Qt RHI and Vulkan pipeline, textures and damage tracking.

  5. 4

    Input

    The input pipeline, seats, focus and the cursor.

  6. 5

    Placement bridge

    The policy engine, the D-Bus service and session restore.

  7. 6

    Shell protocols

    Layer shell, session lock, clipboard and supporting protocols.

  8. 7

    Decorations

    Server-side decorations, window tabbing, shading and the effects pipeline.

  9. 8

    XWayland

    The XWayland bridge and PipeWire screen sharing.

  10. 9

    Plugins

    A tiered plugin system in Luau, QML and C++.

Today

Until the compositor exists, PlasmaZones brings the placement engines to KDE Plasma through a KWin effect and a daemon. That path stays after the compositor ships, so Plasma users keep it.

Try PlasmaZones on Plasma