Reading the repo
Opening the box…
Reading the repo
Opening the box…
How to install on Linux
A Wayland shell with Material Design 3 Expressive, written in Rust
GitHub didn't answer, so this is the saved copy from 14 h ago
Will it work on Linux?
docs/development.mdAntiWebUI comes from GitHub's main, and Cargo.lock pins the commit used. To move to a newer AntiWebUI:
cargo update -p anti-webui -p anti-webui-md3e
To work on a local AntiWebUI checkout at the same time, patch it in from an uncommitted .cargo/config.toml (it is in .gitignore):
[patch."https://github.com/bea4dev/AntiWebUI.git"]
anti-webui = { path = "/path/to/AntiWebUI/src/anti-webui" }
anti-webui-md3e = { path = "/path/to/AntiWebUI/src/anti-webui-md3e" }
The dynamic_linking feature links AntiWebUI dynamically, for faster rebuilds while developing.
Any part of the shell can be drawn to a PNG without a compositor surface, with a simulated pointer and clicks:
shoji-bar-4 preview dock out.png --pointer 470,110
shoji-bar-4 preview quick-settings out.png --width 460 --height 900 --scale 1 --light
shoji-bar-4 preview workspaces out.png --ms 0 --frames 40 --every 30 # out-0.png … out-40.png
shoji-bar-4 preview quick-settings out.png --click 1548,80 --click-frames 1 --ms 0 --frames 8 --every 40
shoji-bar-4 preview bar left.png --bar-position left
shoji-bar-4 preview quick-settings right.png --bar-position right --scale 1
bar, dock, workspaces, title, quick-settings, calendar, launcher, clipboard, media, power, lock and notifications.
lock, the password is shoji, and PAM is not used.title is the window island with a made-up window whose title goes between a long one and a short one every --switch ms (80 by default), from 1.2 s for a second and a half, and then stays on the one --end names (long or short). With --windows, the two titles belong to two windows that take the keyboard in turn. With --spinner, the title is a terminal's with a spinner in front, as Claude Code's is, which at the end changes to another title.preview doesn't save them. --bar-position top|left|right selects the bar edge (top by default), including for panel and component previews.clipboard act on the real cliphist and clipboard.--click X,Y: a click.--right-click X,Y: a right click.--drag X1,Y1:X2,Y2: after the clicks, presses at the first point, moves to the second and lets go.--key K: after the clicks, presses a key (ArrowDown, ArrowUp, Enter, Delete, Escape), or types K if it is a character. It can be given more than once.--click-frames N: how many frames to run after a click (20 by default). Make it small to catch an animation a click starts from its beginning.src/shell_layer.rs owns shell-surface creation, output binding, placement-driven reconfiguration and closing. Production uses its Wayland adapter; unit tests use the recording adapter through the same open_bar and install_panels interface. This covers multi-output assignment, unrelated-setting isolation, in-place placement updates and panel input changes without a compositor.
A bar reserves its thickness from its first commit, and moves to another edge with one set_geometry, which changes the edge, both sizes and the reserved zone in one commit. AntiWebUI's own layer protocol tests cover what that sends.
cargo test --locked --bin shoji-bar-4 shell_layer::tests
When the shell keeps using CPU:
scripts/cpu-report.sh 10 # look for 10 seconds now and write a report
scripts/cpu-report.sh watch 8 30 # stay running; write a report when CPU is over 8% twice in a row
scripts/cpu-report.sh --sudo watch # also record perf's time per function (only perf runs under sudo)
Reports are written to ~/.local/state/shoji-bar-4/reports/. They cover:
msg status: whether a clock keeps ticking (ticking), and whether the UI thread answers quickly.The report ends with what these suggest.
All of it went in as general features, and is in AntiWebUI's main.
WindowOptions::background; layers are transparent by default.ColorScheme::from_seed / from_seed_with, with 9 variants.seed_colors, which takes colors from an image.ColorScheme::lerp and set_color_scheme_animated.MaterialShape (34 shapes), shape / styled_shape (which morph on a spring), and a public Ink (state layers and ripples).DatePickerStyle::no_header().wavy_progress_eased: a wavy progress bar whose line moves to a new value at a speed you choose, for seek bars.MenuItem::submenu.overflow_x_scroll().images::decode_bitmap takes the pixels without showing the image.Battery's energy(), energy_full(), health() and charge_cycles().Then run bash setup.sh. It stops at the first error and is safe to run again. Servers and tests aren't started; it lists them at the end. Read it first.
git clone https://github.com/bea4dev/shoji-bar-4.git cd shoji-bar-4
Rust stable
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
cargo build
cargo run
cargo test
You need ShojiWM, a Rust toolchain, and the usual desktop services: NetworkManager, BlueZ, PipeWire, UPower, power-profiles-daemon and logind. cliphist and wl-clipboard give the clipboard history, and zenity lets you pick a user picture.
git clone https://github.com/bea4dev/shoji-bar-4 ~/.config/shoji-bar-4
cd ~/.config/shoji-bar-4
cargo build --release
ShojiWM's default config starts ~/.config/shoji-bar-4/target/release/shoji-bar-4 with the session, binds its keys (Super for the launcher, Super+N quick settings, Super+C calendar, Super+V clipboard, Super+L lock) and draws the window frames in the shell's colors. With another config, see Using it with ShojiWM.
No reports for Linux yet.
GitManual AI Agent reads the 3 key files and writes a step-by-step guide for Linux. Once written, it's saved for everyone.