aboutsummaryrefslogtreecommitdiffstats
path: root/docs/scripting.md
diff options
context:
space:
mode:
authoruser <user@clank>2026-08-14 14:13:33 +0200
committeruser <user@clank>2026-08-14 14:13:33 +0200
commit6e2786c0ca394a77fe9db22362d1932728c24012 (patch)
treee91568a5f9c03fea841e1a7df14c13dbf18517c6 /docs/scripting.md
parentsl0ppty: dashed borders and a deeper push-back while dragging (diff)
downloadslosh-6e2786c0ca394a77fe9db22362d1932728c24012.tar.gz
slosh-6e2786c0ca394a77fe9db22362d1932728c24012.tar.xz
slosh-6e2786c0ca394a77fe9db22362d1932728c24012.zip
sl0ppty: positional shaders, and a config block to ask for them
Six passes that are pure functions of where a cell is: vignette, gradient, zebra, ruler, margin, spotlight. The position was already in the context and nothing had used it; these are what it was for. The one worth having on its own merits is `ruler`. A column guide that costs no columns, needs no support from the program in the pane, and works in anything — an editor that has never heard of one, a pager, a shell. It marks the background only: a guide that recoloured the text would be making the code it marks harder to read, which is the opposite of the job. `margin` is the same idea from the other side, everything past a column receding so an over-long line visibly runs out of the pane you meant to use. `spotlight` is the first thing to need something new in the context. The cursor belongs to whichever pane is focused, so it is handed only to that pane — otherwise every other pane's light would chase a cursor somewhere else. It leaves everything inside its radius completely alone, because dimming the text you are actually working on to make it easier to find would be silly, and ramps rather than stepping at the edge. `vignette` and `spotlight` both measure distance with a row counting double, because a cell is about twice as tall as it is wide and an effect that claims to be round has to say so in cells. The layout's own centre-distance already does this. The test for it is that on a 41x21 pane — square on screen, not in cells — the top edge and the left edge come out equally dark. Scanlines are not a seventh shader. A CRT scanline is `zebra` with a band of one row, and shipping the same arithmetic under two names would be pretending they are different things. These are not policy, so they needed a way to be asked for, and a KDL block whose children are the passes gets it without inventing a syntax: order in the block is order in the chain, because a chain is a sequence, and listing a shader twice is how you get two rulers. Unknown names are refused with a warning rather than guessed at. Empty by default — these are yours to want, not opinions we hold.
Diffstat (limited to 'docs/scripting.md')
0 files changed, 0 insertions, 0 deletions