|
1 | | -Labwc is a [wlroots]-based window-stacking compositor for [wayland], inspired by |
2 | | -[openbox]. |
| 1 | +Labwc is a [wlroots]-based window-stacking compositor for [Wayland], inspired by |
| 2 | +[Openbox]. |
3 | 3 |
|
4 | | -It is light-weight and independent with a focus on simply stacking windows well |
| 4 | +It is lightweight and independent with a focus on simply stacking windows well, |
5 | 5 | and rendering some window decorations. It relies on clients for panels, |
6 | | -screenshots, wallpapers and so on to create a full desktop environment. |
| 6 | +screenshots, wallpapers, and so on to create a full desktop environment. |
7 | 7 |
|
8 | 8 | Labwc tries to stay in keeping with [wlroots] and [sway] in terms of general |
9 | 9 | approach and coding style. |
10 | 10 |
|
11 | | -Labwc only understands [wayland-protocols] & [wlr-protocols], and it cannot |
12 | | -be controlled with dbus, sway/i3-IPC or other technology. The reason for this is |
| 11 | +Labwc only understands [wayland-protocols] & [wlr-protocols], and cannot |
| 12 | +be controlled with dbus, sway/i3-IPC, or other technology. The reason for this is |
13 | 13 | that we believe that custom IPCs and protocols create a fragmentation that |
14 | 14 | hinders general Wayland adoption. |
15 | 15 |
|
16 | 16 | <a href="img/scrot1.png"> |
17 | 17 | <img src="img/scrot1-small.png"> |
18 | 18 | </a> |
19 | 19 |
|
20 | | -[wayland]: https://wayland.freedesktop.org/ |
21 | | -[openbox]: http://openbox.org/ |
| 20 | +[Wayland]: https://wayland.freedesktop.org/ |
| 21 | +[Openbox]: http://openbox.org/ |
22 | 22 | [wlroots]: https://gitlab.freedesktop.org/wlroots/wlroots |
23 | 23 | [sway]: https://github.com/swaywm |
24 | 24 | [wayland-protocols]: https://gitlab.freedesktop.org/wayland/wayland-protocols |
|
0 commit comments