| Bind the terminal backend from the side that renders into it 3cfee15 nandi 17d ago | 1 | {:paths ["src"] |
| 2 | |
| 3 | ;; glimmer-tui is a backend for glimmer, beside glimmer-vidya and against the |
| 4 | ;; same reconciler: glimmer owns the reactive core and knows about no toolkit, |
| 5 | ;; and this project supplies widgets, painting and the frame loop — through |
| 6 | ;; libjolttui's retained-tree C ABI (crates/jolt-tui/include/jolttui.h), which |
| 7 | ;; is libvidya's tree ABI with a terminal under it instead of a GPU window. |
| 8 | ;; |
| 9 | ;; So an app that renders with glimmer-vidya renders here by requiring this |
| 10 | ;; namespace instead. What it loses is what a terminal has not got: pictures, |
| 11 | ;; a pointer, a window title, a clipboard. |
| 12 | :deps {jolt-lang/glimmer {:git/url "https://github.com/jolt-lang/glimmer" |
| 13 | :git/tag "v0.1.0" |
| 14 | :git/sha "5581c331c51aff989259b9e8e92ec920fe5e6741"}} |
| 15 | |
| 16 | ;; libjolttui, built from ../../crates/jolt-tui. Put it on the search path: |
| 17 | ;; cargo build --release -p jolt-tui |
| 18 | ;; LD_LIBRARY_PATH=../../target/release jolt -M:counter |
| 19 | :jolt/native [{:name "jolttui" |
| 20 | :darwin ["libjolttui.dylib"] |
| 21 | :linux ["libjolttui.so"]}] |
| 22 | |
| 23 | :aliases {:counter {:extra-paths ["examples"] |
| 24 | :main-opts ["-m" "glimmer-tui.counter"]}} |
| 25 | |
| 26 | :tasks {counter "jolt -M:counter"}} |