rickub
nandi/frqpublic⑂ Fork 0
⑂ 596dc29918234b30998f1f9406391ae6b4b3bfc0
Branches
claude/add-remote-repository-47d12e main View all branches → View all tags →
Commits
⬇ Clone ▾
git clone https://git.rickub.com/nandi/frq.git
git clone ssh://git@rickub.com/nandi/frq.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

deps.edn · 105 lines · 5.4 KBClojure Blame HistoryRaw
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago1{:paths ["src"]
2
3 ;; glimmer owns the reactive half (ratom, components, reconciler);
4 ;; glimmer-vidya paints it as Vidya/egui through libvidya's retained-tree ABI.
Show the list and the conversation at once on a wide window 10a1bd0 nandi 19d ago5 ;; Our fork of glimmer, until the reconciler fixes in it land upstream. A
Keep a row's actions from wandering when its line gets an id 5b5e90e nandi 19d ago6 ;; component unmounted between a cell firing and the queued render running
7 ;; used to render anyway, into widgets the backend had already freed and
8 ;; handed out again — which took the message list apart in a busy channel.
Show the list and the conversation at once on a wide window 10a1bd0 nandi 19d ago9 ;; And replacing a native node with one of another tag left every watcher
10 ;; under it subscribed, so swapping the phone layout for the split one and
11 ;; back shredded the chat: one component's props painted onto another's
12 ;; widget.
Keep a row's actions from wandering when its line gets an id 5b5e90e nandi 19d ago13 :deps {jolt-lang/glimmer {:git/url "https://gitlab.com/nandithebull/glimmer"
Show the list and the conversation at once on a wide window 10a1bd0 nandi 19d ago14 :git/sha "399df371c790d690fb6e4560c3d4d7f838502857"}
Take glimmer-vidya from gitlab, so a stranger can build this 5c40e75 nandi 19d ago15 nandi/glimmer-vidya {:git/url "https://gitlab.com/nandithebull/jolt-native"
Retire the release-bumping script 4f38d68 nandi 11d ago16 :git/sha "d970307ccf1fe67e2e971f2837d2282d8ba79a62"
17 :deps/root "glimmer-backends/glimmer-vidya"}}
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago18
Take both native libraries from one place a66d1c1 nandi 19d ago19 ;; Both objects come from gitlab.com/nandithebull/jolt-native, one crate each,
20 ;; out of one target directory:
21 ;;
22 ;; libvidya the retained-tree ABI glimmer-vidya binds, on egui
23 ;; libjoltmoq the AV media plane — MoQ over QUIC, Opus, H.264, capture
24 ;;
25 ;; Calls are the one thing this client cannot do in jolt. Signaling is IRC and
Rename the source files from .jolt to .clj 3c3a947 nandi 11d ago26 ;; lives in src/frq/av.clj; the media half is three thousand lines of codec
Take both native libraries from one place a66d1c1 nandi 19d ago27 ;; and transport that would only be written badly a second time here.
28 ;;
Build the desktop libraries rather than fetching a release of them 0b81161 nandi 15d ago29 ;; just run
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago30 :jolt/native [{:name "vidya"
31 :darwin ["libvidya.dylib"]
Calls f31ad3d nandi 19d ago32 :linux ["libvidya.so"]}
33 {:name "joltmoq"
34 :darwin ["libjoltmoq.dylib"]
Bind libmoq_ffi from the object's own metadata, not from its header 9f081a1 nandi 9d ago35 :linux ["libjoltmoq.so"]}
Fetch libmoq_ffi again, and keep the codecs out of Rust f518938 nandi 9d ago36 ;; moq-ffi's own object, fetched from its release. Not a
37 ;; second media plane: it is the TRANSPORT alone — MoQ over
38 ;; QUIC, the one piece of a call with no C implementation
39 ;; anywhere — and it is here so `frq.moq.*` has something to
40 ;; load while the port off libjoltmoq happens. Both are
41 ;; declared for now, and the day frq.av stops calling
42 ;; joltmoq_* is the day that entry goes.
Bind libmoq_ffi from the object's own metadata, not from its header 9f081a1 nandi 9d ago43 ;;
Fetch libmoq_ffi again, and keep the codecs out of Rust f518938 nandi 9d ago44 ;; The codecs are NOT in it: moq-ffi's audio and video
45 ;; features are off in every Linux artifact upstream
46 ;; publishes, and turning them on means compiling a
47 ;; 1062-crate workspace. Opus and H.264 come from their own C
48 ;; libraries instead, which is the whole point of doing this
49 ;; over FFI rather than over a Rust facade.
50 ;;
51 ;; No :darwin: :systems is x86_64-linux and aarch64-linux, so
52 ;; a .dylib named here would name a file nothing fetches.
Bind libmoq_ffi from the object's own metadata, not from its header 9f081a1 nandi 9d ago53 {:name "moq_ffi"
Bind the C libraries a call actually needs 87e5be9 nandi 9d ago54 :linux ["libmoq_ffi.so"]}
55
56 ;; The codecs, as C libraries rather than as somebody's
57 ;; bindings to them. Opus first; openh264 beside it when the
58 ;; video half lands.
59 ;;
60 ;; The SONAME, not the bare .so: a `libopus.so` is the -dev
61 ;; symlink and is not what a runtime closure carries. The
62 ;; loader looks these up by name in one directory, which the
63 ;; flake's `nativeAll` is.
64 {:name "opus"
65 :linux ["libopus.so.0"]
66 :darwin ["libopus.0.dylib"]}
67
68 ;; H.264, one step removed. openh264's C API is a vtable —
69 ;; `ISVCEncoder` is `const ISVCEncoderVtbl*` — and jolt.ffi
70 ;; can only call a literal C symbol, never a function
71 ;; pointer. c/frq_h264.c walks the vtable and exports flat
72 ;; symbols; this is that. libopenh264 itself comes along as
73 ;; its DT_NEEDED and is never named here.
74 {:name "frqh264"
75 :linux ["libfrqh264.so"]
76 :darwin ["libfrqh264.dylib"]}
77
78 ;; Audio devices. No :darwin — CoreAudio is the other side of
79 ;; that door and is not this library.
80 ;;
81 ;; V4L2 is deliberately absent from this list: the camera is
82 ;; ioctls against libc and the kernel, so there is nothing to
83 ;; load. See frq.capture.v4l2.
84 {:name "asound"
85 :linux ["libasound.so.2"]}]
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago86
Paint the same screens into a terminal ab83b42 nandi 17d ago87 :aliases {:frq {:main-opts ["-m" "frq.app"]}
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago88
Paint the same screens into a terminal ab83b42 nandi 17d ago89 ;; The same screens in a terminal. glimmer-tui is the other backend
90 ;; for the same reconciler — libjolttui's tree ABI is libvidya's
91 ;; with cells under it — so `frq.tui` requires it after `frq.app`
92 ;; and renders the hiccup that is already written.
93 ;;
Merge origin/main, and let one jolt-native answer for both backends 1e8b590 nandi 16d ago94 ;; A path rather than a sha, like glimmer-vidya's would be if this
95 ;; alias were the way in: `just tui` builds jolt-native out of the
96 ;; flake and hands both Jolt halves over with -Sdeps, so this is for
97 ;; a checkout beside the tree and nothing else reads it.
Paint the same screens into a terminal ab83b42 nandi 17d ago98 ;;
99 ;; just tui
100 :tui {:extra-deps {nandi/glimmer-tui
Retire the release-bumping script 4f38d68 nandi 11d ago101 {:local/root "../jolt-native/glimmer-backends/glimmer-tui"}}
Paint the same screens into a terminal ab83b42 nandi 17d ago102 :main-opts ["-m" "frq.tui"]}}
103
104 :tasks {frq "jolt -M:frq"
105 tui "jolt -M:tui"}}