90dd28c910
Currently keycodes are always converted using xkbcommons `State::key_get_one_sym` function. This may be not what the compositor wants, e.g. if it represents keybindings with explicit modifiers. Applying Shift in this case changes the sym, making it necessary for the compositor to *undo* this transformation, which is hard or even impossible and very unnecessary, when we have all the necessary information in smithay. Therefor this commit replaces the `Keysym` argument of the filter closure with a `KeysymHandle`, which allows for different variants of keysyms to be received. Modified (as previously), unmodified or even as a raw keycode. |
||
|---|---|---|
| .github/workflows | ||
| anvil | ||
| examples | ||
| src | ||
| wlcs_anvil | ||
| .gitignore | ||
| .rustfmt.toml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| Cargo.toml | ||
| LICENSE.txt | ||
| README.md | ||
| build.rs | ||
| compile_wlcs.sh | ||
| doc_index.html | ||
| matrix_badge.svg | ||
README.md
Smithay
A smithy for rusty wayland compositors
Goals
Smithay aims to provide building blocks to create wayland compositors in Rust. While not being a full-blown compositor, it'll provide objects and interfaces implementing common functionalities that pretty much any compositor will need, in a generic fashion.
Also:
- Documented: Smithay strives to maintain a clear and detailed documentation of its API and its functionalities. Compiled documentations are available on docs.rs for released versions, and here for the master branch.
- Safety: Smithay will target to be safe to use, because Rust.
- Modularity: Smithay is not a framework, and will not be constraining. If there is a part you don't want to use, you should not be forced to use it.
- High-level: You should be able to not have to worry about gory low-level stuff (but Smithay won't stop you if you really want to dive into it).
Anvil
Like others, Smithay as a compositor library has its own sample compositor: anvil.
You can run it with cargo after having cloned this repository:
cd anvil;
cargo run -- --{backend}
The currently available backends are:
--winit: start anvil as a Winit application. This allows you to run it inside of an other X11 or Wayland session.--tty-udev: start anvil in a tty with udev support. This is the "traditional" launch of a Wayland compositor. Note that this requires you to start anvil as root if your system does not have logind available.