gioser

tawasuyu/llimphi

Sovereign retained-mode GPU UI framework in Rust (wgpu+vello+taffy+parley), Elm loop, 40+ widgets.

Rust 229TOML 101Markdown 82Shell 24052 Definitions

⎇ main llimphi-registro/README.md Markdown · 37 lines · 1.6 KB History raw

chore: refresco desde el monorepo — 132 miembros, 79 widgets, la galería vuelve y licencia dual d8edd9a9c · Sergio · 

1# llimphi-registro
2
3> Records a caged app's `EscenaWire` frames to a file — the **master** — and reveals it
4> later, offline, to PNG frames or to a video.
5
6A screencast is already developed: changing the theme means recording again with a person
7in front of the screen. A scene master is re-developed on its own — another resolution,
8another theme, another rasteriser — because what was stored is *what to draw*, not pixels.
9
10Measured on the real editor (`nada`, caged, 1280×720): **17.7 KB per frame, 20.2 KB/s** of
11film. A 1080p screencast runs 125–600 KB/s.
12
13## The binary — `llimphi-scene`
14
15```bash
16llimphi-scene record --out master.scn --size 1280x720 --script take.txt -- ./guest
17llimphi-scene info   master.scn                      # what it weighs, measured
18llimphi-scene render master.scn --out frames/        # PNG frames
19llimphi-scene film   master.scn --out cover.mp4      # H.264 for the web
20```
21
22`record` needs **no GPU**: recording is cheap and can run on a headless box. Developing is
23the expensive half and it repeats without bothering anyone.
24
25## What it does not do
26
27It does not draw (`llimphi-reproductor` does), it does not talk over any socket
28(`llimphi-cable` does) and it knows nothing about ffmpeg (`shared/foreign-av` does). It
29adds the clock, the order and the count.
30
31It also does not record *the desktop*: a Wayland client that is not Llimphi hands over
32pixel buffers, and a scene log proves what the app **asked for**, not what reached the
33panel.
34
35---
36
37Part of **llimphi** — see [llimphi](../README.md) and the widget/module catalogue in [`MANUAL.md`](../MANUAL.md).

README.md

llimphi-registro

Records a caged app's EscenaWire frames to a file — the master — and reveals it later, offline, to PNG frames or to a video.

A screencast is already developed: changing the theme means recording again with a person in front of the screen. A scene master is re-developed on its own — another resolution, another theme, another rasteriser — because what was stored is what to draw, not pixels.

Measured on the real editor (nada, caged, 1280×720): 17.7 KB per frame, 20.2 KB/s of film. A 1080p screencast runs 125–600 KB/s.

The binary — llimphi-scene

llimphi-scene record --out master.scn --size 1280x720 --script take.txt -- ./guest
llimphi-scene info   master.scn                      # what it weighs, measured
llimphi-scene render master.scn --out frames/        # PNG frames
llimphi-scene film   master.scn --out cover.mp4      # H.264 for the web

record needs no GPU: recording is cheap and can run on a headless box. Developing is the expensive half and it repeats without bothering anyone.

What it does not do

It does not draw (llimphi-reproductor does), it does not talk over any socket (llimphi-cable does) and it knows nothing about ffmpeg (shared/foreign-av does). It adds the clock, the order and the count.

It also does not record the desktop: a Wayland client that is not Llimphi hands over pixel buffers, and a scene log proves what the app asked for, not what reached the panel.

Part of llimphi — see llimphi and the widget/module catalogue in MANUAL.md.