Wayland cross-desktop meeting summary

[Hans de Goede]

<For some reason this is missing from the xdg-list archives, resending
  it for archival purposes>

Hi all,

I've organized a Wayland cross-desktop meeting the Friday before Fosdem,
getting people together from various desktop environment to discuss how to
deal with various unsolved problems under Wayland in a cross-desktop
manner.

Here is a summary of what was discussed:

1) Tray Icon / Notification

Lots of discussion, summary:
1a) No xembed (trayicon) or similar functionality for wayland
1b) Notifications should use fdo notifcation spec version 1.2 or later,
     apps are advised to use a lib for this, e.g. libnotify or knotification
1c) For app-indicator like functionality there are 2 different cases:
  -Normal apps, these should use permanent notifications under Wayland
  -System / hw configuration apps, e.g. nm-applet, bluez-applet
   -On some compositors these may use the appindicator spec
   -On other compositors these must be part of the core, or a compositor
    specific extension
1d) In an ideal world / in the future, many cases using trayicons should
     really have a use-case specific xdg API, e.g.:
  -Media player "remote" controls, already solved by the mpris spec
  -Instant Messaging desktop integration
  -Download manager desktop integration
1e) What about toolkits with a tray-icon widget
  -Clearly document that a tray-icon may not work everywhere
  -Maybe implement a gnome-qt-plugin to override QtTrayIcon to use persistent
   notifications in gnome

2) Global hotkey bindings

Offer a compositor API to replace passive keygrabs in X to allow apps to
register a global hotkey? Conclusion: No, global hotkeys can only be
configured / set through / by the compositor.

3) Screenshot / casting API

Lots of discussion again, summary:
3a) This has security implications, compositors should check before allowing
     this, the exact implemtation / policy of the security check is left up
     to the compositor
3b) For screenshots there should be a xdg API handing over a 32 bit rgba
     buffer handle, further details to be discussed on the list
3c) For screencasting there should be a xdg API. This API should enumerate
     formats in which the user can get the screencasting, including
     pre-encoded formats, as hw accelerated encoding is best handled in the
     compositor for various technical reasons. This API should also a number
     of raw image data formats for user who want that. In either case the
     API should push buffer handles to the consumer as soon as it has a
     buffer ready. Further details to be discussed on the list.

4) Allow applications to runtime change the icon show for them by the
    compositor in the taskbar / minimized / running icon from the one
    specied in the .desktop file ?
    Answer: No, but we should extend the notification spec to allow
    applications to specify badges (typically a number) to display "next to"
    the icon

5) Colorpicker API ?
    Yes we want to add a colorpicker API, should be simple, further details to
    be discussed on the list.

Extra items which came up but where not discussed in detail:
- jumplist / runtime add actions to "minimized icon" context menu
- We need an "active" keygrab style keygrab for virtual-machine viewers /
   games. At least one key combo should stay reserved for the compostor to
   break the grab. Compositors may want to show a popup the first time an app
   does the keygrab showing a tooltip about the key combo.

Regards,

Hans