Skip to content

Support Wayland? #20

@onli

Description

@onli

I'm not sure supporting Wayland should be a goal, but I wanted to have this issue to document it.

Fact is, regardless of whether Wayland finally replaces X or not in a to me relevant way, there are interesting Wayland window managers like niri. And in contrast to how Wayland was initially planned out, it is possible to run a dock with them, as niri-wm/niri#1638 shows. At least on some Wayland WMs the relevant protocols seem to be there. Also, wxWidgets does support Wayland now, though I'm not sure how well.

So:

  • Check how good the available Wayland docks are. https://github.com/dangvd/crystal-dock in particular looks like it might make a Wayland version of Simdock unnecessary, depends probably on how well it cycles through windows.
  • If the existing docks fall short, decide on a wayland environment where simdock could dock onto (pun intended). Again, Niri might be a good choice, the concept is nice, it's popular and the link above shows the technical feasibility.
  • Implementing wayland support would mean at the very least abstracting the wnck usage in https://github.com/onli/simdock/blob/master/src/tasks.cc away, so that on wayland it uses whatever is needed there (to my understanding right now, wlr-foreign-toplevel-management is the keyword) while the X11 path stays as it is. https://github.com/onli/simdock/blob/master/src/background.cc also uses Xlib directly, but replacing that on wayland might be quite easy since grabbing the background should be unnecessary there, as compositing would be set. Follow-up tasks for the Makefile. Probably more to do.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions