Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W wayland-protocols
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 103
    • Issues 103
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 54
    • Merge requests 54
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • waylandwayland
  • wayland-protocols
  • Merge requests
  • !40

Add ext-workspace-unstable

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Ilia Bozhinov requested to merge ammen99/wayland-protocols:master into main Aug 04, 2020
  • Overview 58
  • Commits 18
  • Pipelines 12
  • Changes 3

This is an updated version of the wlr-workspace-unstable-v1 protocol. Original work here: https://github.com/swaywm/wlr-protocols/pull/35

Pending PRs for implementation in compositors (wlroots, Wayfire, Sway): https://github.com/swaywm/wlroots/pull/2357 https://github.com/WayfireWM/wayfire/pull/647 https://github.com/swaywm/sway/pull/5597

There is also a person who is starting/has started to implement this protocol in Waybar: https://github.com/Alexays/Waybar/issues/762, I will update this MR with a link to it as soon as it is ready.

Note that the protocol inside is still in the zwlr namespace, which I will obviously rename to ext if the protocol is approved.

The intention of the protocol is to expose information about workspaces in the compositor and associate them with outputs:

  • A compositor exposes one or more workspace groups
  • Each workspace group is comprised of several workspaces
  • Each workspace group is "visible" on a few outputs

For example, in Wayfire, there is one workspace group per output, because the workspaces on each output are independent.

In GNOME, one would probably also have a workspace group per output, and all of them except the primary output's workspace group will have just one workspace.

Clients would be able to use this protocol to implement workspace switching widgets in panels, command line tools used to focus a workspace and similar. This would also make it possible to modify the wlr-foreign-toplevel-management protocol understand on which workspace(s) toplevels are visible.

Edited Oct 13, 2020 by Ilia Bozhinov
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: master