Next: (heks-linux user-settings), Previous: (heks-linux ssh), Up: API
The window behind the three questions this desktop answers about itself: what do I press, what does it look like, and what could it look like instead? heks-toon answers all three - the keyboard reference, the wall chooser and the palette chooser - in one GTK4 window, painted from the palette the desktop is wearing.
It is a program of its own, installed from the jointhefreeworld collection (‘maak install-heks-toon’), and it already knows this desktop: the palette comes from ~/.config/heks-linux/local-settings.scm, the pictures from the collection ‘maak install-wallpaper-files’ clones, and the switching from ‘heks-wallpaper’ and ‘heks-rofi-theme-menu’, both of which this configuration installs. So the half that belongs here is small - the command lines the bar and the compositor build, the application id the compositor matches on, and the retirement of the three HTML pages this configuration used to render.
Those pages were documents: an HTML file this configuration wrote, a local HTTP server it ran to serve thumbnails, and a Chrome app window to look at them in. heks-toon is the same three views without a browser in the middle, which is why nothing here renders, serves or watches anything.
Default value:
"heks-toon"
Default value:
"/root/.config/heks-linux"
Default value:
"/root/.local/bin"
Retire the pages heks-toon replaces, and leave the window to find its data.
Nothing is written: heks-toon reads the desktop’s own files, so it has no configuration of ours to render. What is removed is what the three HTML pages left behind - their launchers, and the generated keyboard reference with the directory around it - so that a machine which had the pages does not keep scripts and documents nothing maintains.
Return the command that opens the documentation view. The window reads this machine’s own READMEs - heks-linux’s, the editor’s and the shell’s - so the page cannot say something the checkouts do not.
Return the command that opens the keyboard reference. The reference is the window’s first view, so it is the program on its own - which is also why the bar’s question mark needs no argument.
Return the command that opens the palette chooser, on its own view. Choosing a card there runs the same ‘heks-rofi-theme-menu’ the bar’s palette button opens, so a switch reads the same whichever way it was started.
Return command the way a surface that is not the compositor runs it.
The bar is a plain client, and a window that is already open cannot be raised by a client with nothing to prove it was the user who asked: under Wayland that takes an activation token, and a program started by another program has none. Niri’s own IPC spawn hands one over, so the bar asks the compositor to spawn it, and falls back to running it directly on a machine where niri is not the compositor.
Return the command that opens the wall chooser, on its own view.
Next: (heks-linux user-settings), Previous: (heks-linux ssh), Up: API