Gnome-shell Hackfest 2019 – Day 2

Well, we are starting the 3rd and last day of this hackfest… I’ll write about yesterday, which probably means tomorrow I’ll blog about today :).

Some highlights of what I was able to participate/witness:

  • Roman Gilg of KDE fame came to the hackfest, it was a nice opportunity to discuss mixed DPI densities for X11/Xwayland clients. We first thought about having one server per pixel density, but later on we realized we might not be that far from actually isolating all X11 clients from each other, so why stop there.
  • The conversation drifted into other topics relevant to desktop interoperation. We did discuss about window activation and focus stealing prevention, this is a topic “fixed” in Gnome but in a private protocol. I had already a protocol draft around which was sent today to wayland-devel ML.
  • A plan was devised for what is left of Xwayland-on-demand, and an implementation is in progress.
  • The designers have been doing some exploration and research on how we interact with windows, the overview and the applications menu, and thinking about alternatives. At the end of the day they’ve demoed to us the direction they think we should take.

    I am very much not a designer and I don’t want to spoil their fine work here, so stay tuned for updates from them :).

  • As the social event, we had a very nice BBQ with some hackerspace members. Again kindly organized by Revspace.

3 thoughts on “Gnome-shell Hackfest 2019 – Day 2”

  1. Does the window focus protocol allow applications to _lower_ their windows? For me that’s the only remaining major Wayland regression: middle-click on the titlebar to lower the window works for legacy X11 applications but not for native Wayland applications that use client-side decorations. I (used to) use it to switch between maximized applications with a single click.

  2. @gn0mish Thanks! There are no plans for such from the ground up redesign, we are looking into addressing all those problem areas in a way that fits the current design.

    @Marius it doesn’t… the protocol addresses the activation of foreign surfaces, and the inter-client interactions, it is not meant to handle the raising/lowering of your own surface.

    For reference the protocol is at

Leave a Reply

Your email address will not be published. Required fields are marked *