Skip to content
This repository was archived by the owner on Jul 23, 2026. It is now read-only.

Commit 3b9e216

Browse files
Merge pull request #9 from ernestoCruz05/shader-test
shaders unstable test v1 and hopefully not many versions after this
2 parents d3d531b + aafca8a commit 3b9e216

11 files changed

Lines changed: 950 additions & 47 deletions

File tree

docs/visuals/meta.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
11
{
22
"title": "Visuals",
3-
"pages": ["theming", "status-bar", "effects", "animations"]
3+
"pages": ["theming", "status-bar", "effects", "animations", "shaders"]
44
}

docs/visuals/shaders.md

Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
---
2+
title: Shader Transitions
3+
description: Write custom GLSL fragment shaders for window open/close animations.
4+
---
5+
6+
mangowm can drive a window's open and close animation with a custom GLSL fragment shader instead of (or alongside) the built-in parametric fades and zooms. Each window is snapshotted to a texture once, then your shader runs every animation tick against that texture to produce the visible frame.
7+
8+
This is a small, focused feature. It only covers the open and close transitions (not move/tag/focus animations), and shader files are only discovered at startup and after a GPU reset. There is no hot-reload while the compositor is running.
9+
10+
## Quick start
11+
12+
1. Drop a `.frag` file in `~/.config/mango-ext/shaders/`, e.g. `dissolve.frag`.
13+
2. Reference it by filename (without the `.frag` extension) in your config:
14+
15+
```ini
16+
effect_open=dissolve
17+
effect_close=burn
18+
```
19+
20+
3. Restart mangowm. Shader files are scanned once at startup and again after a GPU reset. Adding or editing a `.frag` file while the compositor is already running has no effect until the next restart.
21+
22+
## Writing a shader
23+
24+
A shader file is just the body of a GLSL ES 3.00 fragment shader, typically a single `void main() { ... }` function. The loader wraps your body with a fixed header before compiling it, equivalent to:
25+
26+
```glsl
27+
#version 300 es
28+
precision highp float;
29+
uniform sampler2D u_texture;
30+
uniform float u_progress;
31+
uniform float u_time;
32+
uniform vec2 u_size;
33+
in vec2 v_texcoord;
34+
out vec4 fragColor;
35+
```
36+
37+
Do not redeclare any of these names in your file: `u_texture`, `u_progress`, `u_time`, `u_size`, `v_texcoord`, or `fragColor`. The header already declares them. Redeclaring any of them is a GLSL compile error and your shader will fail to load (see [Fail-safe behavior](#fail-safe-behavior)).
38+
39+
| Name | Type | Meaning |
40+
| :--- | :--- | :--- |
41+
| `u_texture` | `sampler2D` | A snapshot of the window's contents, sampled with `texture(u_texture, v_texcoord)`. |
42+
| `u_progress` | `float` | Animation progress, `0.0` to `1.0`. See [Progress convention](#progress-convention) below. This is the one thing every shader must get right. |
43+
| `u_time` | `float` | Seconds elapsed since the animation started. Useful for time-based effects (e.g. a glitch shimmer) independent of progress. |
44+
| `u_size` | `vec2` | Output size in pixels (the window width and height being rendered into). |
45+
| `v_texcoord` | `vec2` | Interpolated texture coordinate, `0.0` to `1.0` across the window. |
46+
| `fragColor` | `out vec4` | Your shader's output color for the pixel. Write to this instead of `gl_FragColor`. |
47+
48+
Your shader writes its output to `fragColor`, which the header declares as `out vec4`. Since the engine composites the result with premultiplied alpha, the RGB channels you write must already be multiplied by the alpha you write. That means `fragColor = vec4(color.rgb * alpha, alpha)`, not `vec4(color.rgb, alpha)`. Forgetting this produces a white or light halo around fading-out windows.
49+
50+
### GLSL ES 3.00
51+
52+
The shader is compiled as GLSL ES 3.00. The loader prepends the `#version 300 es` line and the header above, so you write only the body:
53+
54+
- Sample textures with `texture(sampler, uv)`, not `texture2D(...)`.
55+
- Write the output to `fragColor`, not `gl_FragColor`. The `out` variable is already declared in the header, so do not declare your own.
56+
- Read the interpolated coordinate from `v_texcoord` (declared `in` by the header). Inputs from the vertex stage use `in`, not `varying`.
57+
- No redeclaring `u_texture` / `u_progress` / `u_time` / `u_size` / `v_texcoord` / `fragColor` (see above).
58+
59+
### Precision: highp is guaranteed
60+
61+
GLSL ES 3.00 fragment shaders are guaranteed `highp` (fp32) floats. The classic noise hash works with no workaround:
62+
63+
```glsl
64+
float hash12(vec2 p) {
65+
return fract(sin(dot(p, vec2(127.1, 311.7))) * 43758.5453);
66+
}
67+
```
68+
69+
You do not need the multi-round fp16-safe hashes found in older GLES2 shader code, and you do not need `GL_FRAGMENT_PRECISION_HIGH` guards. `mediump` is still available if you want it for a hot loop, but the default `highp` is fine everywhere.
70+
71+
## Progress convention
72+
73+
Write your shader so `u_progress == 0.0` means the window is fully present and `u_progress == 1.0` means the window is fully gone. The compositor runs progress in the right direction for both open and close, so a single shader body works for both:
74+
75+
- **Close**: progress is driven directly from the close animation's elapsed fraction (`progress = min(animation_passed, 1.0)`), so it runs `0 -> 1` as the window closes: present, then gone.
76+
- **Open**: progress is driven from `1.0 - min(animation_passed, 1.0)`, so it runs `1 -> 0` as the window opens: gone, then present.
77+
78+
The engine inverts progress for you on open. You never need two different shaders (or an `if` on direction) for the open vs. close case. One body covering `progress: 0 = present, 1 = gone` dissolves a window away on close and dissolves it in on open.
79+
80+
## Configuration
81+
82+
| Setting | Scope | Description |
83+
| :--- | :--- | :--- |
84+
| `effect_open` | global | Name (no `.frag`) of the shader to use for window open animations. |
85+
| `effect_close` | global | Name (no `.frag`) of the shader to use for window close animations. |
86+
87+
```ini
88+
effect_open=dissolve
89+
effect_close=burn
90+
```
91+
92+
Both can also be set per-window via a `windowrule`, which takes precedence over the global setting for matching windows:
93+
94+
```ini
95+
windowrule=appid:firefox,effect_close:glitch
96+
```
97+
98+
If `effect_open`/`effect_close` is left unset (globally and per-window), or the window doesn't match a rule, the window uses the existing parametric animation (`animation_type_open`/`animation_type_close`, fade, zoom, etc.) exactly as before this feature existed. Shaders are strictly opt-in.
99+
100+
## Fail-safe behavior
101+
102+
Shader loading and selection are designed to never break your session:
103+
104+
- **Compile/link failure**: if a `.frag` file fails to compile or link, the loader logs an error (visible with `WLR_ERROR` logging) and skips that file. It is never registered. Other shaders in the directory still load normally.
105+
- **Unknown shader name**: if `effect_open`/`effect_close` (global or per-window) names a shader that was never successfully loaded (typo, compile failure, or you just haven't created the file), that window silently falls back to the normal parametric open/close animation. No crash, no missing window content. It just behaves as if the shader setting weren't there.
106+
- **Missing shader directory**: if `~/.config/mango-ext/shaders/` doesn't exist, it's logged at `INFO` level and skipped. Having no custom shaders at all is a normal, supported configuration.
107+
108+
## Restart required for new files
109+
110+
`~/.config/mango-ext/shaders/` is scanned for `*.frag` files once at startup, and again automatically after a GPU reset (which also clears all previously compiled shader programs). There is no file-watching or hot-reload. If you add a new `.frag` file or rename one while mangowm is running, you need to restart the compositor before `effect_open` / `effect_close` can reference it. Editing the contents of an already-loaded shader also requires a restart to take effect.
111+
112+
## Example shaders
113+
114+
Example shaders live in a separate repo, [ernestoCruz05/shader_examples](https://github.com/ernestoCruz05/shader_examples). Clone it and copy whichever `.frag` files you want into your shader directory:
115+
116+
```sh
117+
git clone https://github.com/ernestoCruz05/shader_examples.git
118+
cp shader_examples/*.frag ~/.config/mango-ext/shaders/
119+
```
120+
121+
Then restart mangowm and reference them by basename (without the `.frag` extension) in your config (see [Quick start](#quick-start)).

meson.build

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,8 @@ libscenefx_dep = dependency('scenefx-0.4',version: '>=0.4.1')
3939
pixman_dep = dependency('pixman-1')
4040
cjson_dep = dependency('libcjson')
4141
pangocairo_dep = dependency('pangocairo')
42+
egl_dep = dependency('egl')
43+
glesv2_dep = dependency('glesv2')
4244

4345
# version info
4446
git = find_program('git', required : false)
@@ -97,6 +99,7 @@ executable('mango-ext',
9799
'src/mango.c',
98100
'src/common/util.c',
99101
'src/draw/text-node.c',
102+
'src/draw/effect_pass.c',
100103
'src/ext-protocol/wlr_ext_workspace_v1.c',
101104
wayland_sources,
102105
dependencies : [
@@ -114,6 +117,8 @@ executable('mango-ext',
114117
pixman_dep,
115118
cjson_dep,
116119
pangocairo_dep,
120+
egl_dep,
121+
glesv2_dep,
117122
],
118123
install : true,
119124
install_rpath : get_option('install_rpath'),

0 commit comments

Comments
 (0)