diff options
| author | Devin J. Pohly <djpohly@gmail.com> | 2020-12-27 17:15:21 -0500 |
|---|---|---|
| committer | Devin J. Pohly <djpohly@gmail.com> | 2020-12-27 17:15:21 -0500 |
| commit | 0090b6bed61c21aae2a30ff5f2556baa97be5069 (patch) | |
| tree | f09076dd7fe22eff56e7f03c2375bdebcab7b310 | |
| parent | 7b1b5c75e9498cb21f9d71aee36c8021c5cb23d3 (diff) | |
clarify intention of feature suggestions
| -rw-r--r-- | README.md | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -18,9 +18,10 @@ dwl is not meant to provide every feature under the sun. Instead, like dwm, it s - XWayland support as provided by wlroots - Zero flickering - Wayland users naturally expect that "every frame is perfect" -Features yet to be implemented (possibly as patches) are: +Features under consideration (possibly as patches) are: -- Communication from the compositor to status bars. One possibility is to create a dwl-status protocol that bars can implement to be notified of compositor information. You can already use Waybar or yambar, but without tag information +- Protocols made trivial by wlroots +- Communication from the compositor to status bars. A straightforward possibility would be to use stdout or a provided file descriptor. - Implement the input-inhibitor protocol to support screen lockers - Implement the idle-inhibit protocol which lets applications such as mpv disable idle monitoring - Layer shell popups (used by Waybar) |