nandi/frq · deps.edn

nandi/frqpublic⑂ Fork 0

⑂ b33f288db8fbd9caaa202ce396497c77f76c1c49

deps.edn · 97 lines · 4.9 KBClojure    Blame HistoryRaw
A freeq client in jolt, as glimmer components on Vidya   1{:paths ["src"]
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   5 ;; 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   6 ;; 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   9 ;; 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   13 :deps {jolt-lang/glimmer   {:git/url "https://gitlab.com/nandithebull/glimmer"
Show the list and the conversation at once on a wide window   14                             :git/sha "399df371c790d690fb6e4560c3d4d7f838502857"}
Take glimmer-vidya from gitlab, so a stranger can build this   15        nandi/glimmer-vidya {:git/url "https://gitlab.com/nandithebull/jolt-native"
Retire the release-bumping script   16                             :git/sha "d970307ccf1fe67e2e971f2837d2282d8ba79a62"
17                             :deps/root "glimmer-backends/glimmer-vidya"}}
A freeq client in jolt, as glimmer components on Vidya   18
Switch frq.av onto the jolt media plane, and stop shipping libjoltmoq   19 ;; libvidya comes from gitlab.com/nandithebull/jolt-native:
Take both native libraries from one place   20
21 ;;   libvidya   the retained-tree ABI glimmer-vidya binds, on egui
Switch frq.av onto the jolt media plane, and stop shipping libjoltmoq   23 ;; Calls used to be the one thing this client could not do in jolt. The media
24 ;; half is `frq.av.plane` now — MoQ over QUIC from libmoq_ffi, Opus from
25 ;; libopus, H.264 from openh264 through a shim, and the devices from V4L2
26 ;; and ALSA. Signaling was always IRC and still lives in src/frq/av.clj.
Take both native libraries from one place   27
Build the desktop libraries rather than fetching a release of them   28 ;;   just run
A freeq client in jolt, as glimmer components on Vidya   29 :jolt/native [{:name "vidya"
30                :darwin ["libvidya.dylib"]
   31                :linux ["libvidya.so"]}
Switch frq.av onto the jolt media plane, and stop shipping libjoltmoq   32               ;; The transport half of a call: MoQ over QUIC, the one
33               ;; piece with no C implementation anywhere. Fetched from
34               ;; moq-ffi's release rather than built — building it means a
35               ;; 1062-crate workspace.
Bind libmoq_ffi from the object's own metadata, not from its header   36
Switch frq.av onto the jolt media plane, and stop shipping libjoltmoq   37               ;; The codecs are NOT in it. moq-ffi's `audio` and `video`
38               ;; features are off in every Linux artifact upstream ships,
39               ;; so Opus and H.264 come from their own C libraries below,
40               ;; which is the whole point of doing this over FFI rather
41               ;; than over a Rust facade.
Fetch libmoq_ffi again, and keep the codecs out of Rust   42
43               ;; No :darwin: :systems is x86_64-linux and aarch64-linux, so
44               ;; a .dylib named here would name a file nothing fetches.
Bind libmoq_ffi from the object's own metadata, not from its header   45               {:name "moq_ffi"
Bind the C libraries a call actually needs   46                :linux ["libmoq_ffi.so"]}
48               ;; The codecs, as C libraries rather than as somebody's
49               ;; bindings to them. Opus first; openh264 beside it when the
50               ;; video half lands.
52               ;; The SONAME, not the bare .so: a `libopus.so` is the -dev
53               ;; symlink and is not what a runtime closure carries. The
54               ;; loader looks these up by name in one directory, which the
55               ;; flake's `nativeAll` is.
56               {:name "opus"
57                :linux ["libopus.so.0"]
58                :darwin ["libopus.0.dylib"]}
60               ;; H.264, one step removed. openh264's C API is a vtable —
61               ;; `ISVCEncoder` is `const ISVCEncoderVtbl*` — and jolt.ffi
62               ;; can only call a literal C symbol, never a function
63               ;; pointer. c/frq_h264.c walks the vtable and exports flat
64               ;; symbols; this is that. libopenh264 itself comes along as
65               ;; its DT_NEEDED and is never named here.
66               {:name "frqh264"
67                :linux ["libfrqh264.so"]
68                :darwin ["libfrqh264.dylib"]}
70               ;; Audio devices. No :darwin — CoreAudio is the other side of
71               ;; that door and is not this library.
73               ;; V4L2 is deliberately absent from this list: the camera is
74               ;; ioctls against libc and the kernel, so there is nothing to
75               ;; load. See frq.capture.v4l2.
76               {:name "asound"
77                :linux ["libasound.so.2"]}]
A freeq client in jolt, as glimmer components on Vidya   78
Paint the same screens into a terminal   79 :aliases {:frq {:main-opts ["-m" "frq.app"]}
A freeq client in jolt, as glimmer components on Vidya   80
Paint the same screens into a terminal   81           ;; The same screens in a terminal. glimmer-tui is the other backend
82           ;; for the same reconciler — libjolttui's tree ABI is libvidya's
83           ;; with cells under it — so `frq.tui` requires it after `frq.app`
84           ;; and renders the hiccup that is already written.
Merge origin/main, and let one jolt-native answer for both backends   86           ;; A path rather than a sha, like glimmer-vidya's would be if this
87           ;; alias were the way in: `just tui` builds jolt-native out of the
88           ;; flake and hands both Jolt halves over with -Sdeps, so this is for
89           ;; a checkout beside the tree and nothing else reads it.
Paint the same screens into a terminal   90
91           ;;   just tui
92           :tui {:extra-deps {nandi/glimmer-tui
Retire the release-bumping script   93                              {:local/root "../jolt-native/glimmer-backends/glimmer-tui"}}
Paint the same screens into a terminal   94                 :main-opts ["-m" "frq.tui"]}}
96 :tasks {frq "jolt -M:frq"
97         tui "jolt -M:tui"}}

A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	1	{: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 ago	5	;; 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 ago	6	;; 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 ago	9	;; 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 ago	13	: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 ago	14	:git/sha "399df371c790d690fb6e4560c3d4d7f838502857"}
Take glimmer-vidya from gitlab, so a stranger can build this 5c40e75 nandi 19d ago	15	nandi/glimmer-vidya {:git/url "https://gitlab.com/nandithebull/jolt-native"
Retire the release-bumping script 4f38d68 nandi 11d ago	16	:git/sha "d970307ccf1fe67e2e971f2837d2282d8ba79a62"
Retire the release-bumping script 4f38d68 nandi 11d ago	17	:deps/root "glimmer-backends/glimmer-vidya"}}
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	18
Switch frq.av onto the jolt media plane, and stop shipping libjoltmoq b33f288 nandi 9d ago	19	;; libvidya comes from gitlab.com/nandithebull/jolt-native:
Take both native libraries from one place a66d1c1 nandi 19d ago	20	;;
	21	;; libvidya the retained-tree ABI glimmer-vidya binds, on egui
	22	;;
Switch frq.av onto the jolt media plane, and stop shipping libjoltmoq b33f288 nandi 9d ago	23	;; Calls used to be the one thing this client could not do in jolt. The media
	24	;; half is `frq.av.plane` now — MoQ over QUIC from libmoq_ffi, Opus from
	25	;; libopus, H.264 from openh264 through a shim, and the devices from V4L2
	26	;; and ALSA. Signaling was always IRC and still lives in src/frq/av.clj.
Take both native libraries from one place a66d1c1 nandi 19d ago	27	;;
Build the desktop libraries rather than fetching a release of them 0b81161 nandi 15d ago	28	;; just run
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	29	:jolt/native [{:name "vidya"
	30	:darwin ["libvidya.dylib"]
Calls f31ad3d nandi 19d ago	31	:linux ["libvidya.so"]}
Switch frq.av onto the jolt media plane, and stop shipping libjoltmoq b33f288 nandi 9d ago	32	;; The transport half of a call: MoQ over QUIC, the one
	33	;; piece with no C implementation anywhere. Fetched from
	34	;; moq-ffi's release rather than built — building it means a
	35	;; 1062-crate workspace.
Bind libmoq_ffi from the object's own metadata, not from its header 9f081a1 nandi 9d ago	36	;;
Switch frq.av onto the jolt media plane, and stop shipping libjoltmoq b33f288 nandi 9d ago	37	;; The codecs are NOT in it. moq-ffi's `audio` and `video`
	38	;; features are off in every Linux artifact upstream ships,
	39	;; so Opus and H.264 come from their own C libraries below,
	40	;; which is the whole point of doing this over FFI rather
	41	;; than over a Rust facade.
Fetch libmoq_ffi again, and keep the codecs out of Rust f518938 nandi 9d ago	42	;;
	43	;; No :darwin: :systems is x86_64-linux and aarch64-linux, so
	44	;; 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 ago	45	{:name "moq_ffi"
Bind the C libraries a call actually needs 87e5be9 nandi 9d ago	46	:linux ["libmoq_ffi.so"]}
	47
	48	;; The codecs, as C libraries rather than as somebody's
	49	;; bindings to them. Opus first; openh264 beside it when the
	50	;; video half lands.
	51	;;
	52	;; The SONAME, not the bare .so: a `libopus.so` is the -dev
	53	;; symlink and is not what a runtime closure carries. The
	54	;; loader looks these up by name in one directory, which the
	55	;; flake's `nativeAll` is.
	56	{:name "opus"
	57	:linux ["libopus.so.0"]
	58	:darwin ["libopus.0.dylib"]}
	59
	60	;; H.264, one step removed. openh264's C API is a vtable —
	61	;; `ISVCEncoder` is `const ISVCEncoderVtbl*` — and jolt.ffi
	62	;; can only call a literal C symbol, never a function
	63	;; pointer. c/frq_h264.c walks the vtable and exports flat
	64	;; symbols; this is that. libopenh264 itself comes along as
	65	;; its DT_NEEDED and is never named here.
	66	{:name "frqh264"
	67	:linux ["libfrqh264.so"]
	68	:darwin ["libfrqh264.dylib"]}
	69
	70	;; Audio devices. No :darwin — CoreAudio is the other side of
	71	;; that door and is not this library.
	72	;;
	73	;; V4L2 is deliberately absent from this list: the camera is
	74	;; ioctls against libc and the kernel, so there is nothing to
	75	;; load. See frq.capture.v4l2.
	76	{:name "asound"
	77	:linux ["libasound.so.2"]}]
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	78
Paint the same screens into a terminal ab83b42 nandi 17d ago	79	:aliases {:frq {:main-opts ["-m" "frq.app"]}
A freeq client in jolt, as glimmer components on Vidya 4719d6f nandi 20d ago	80
Paint the same screens into a terminal ab83b42 nandi 17d ago	81	;; The same screens in a terminal. glimmer-tui is the other backend
	82	;; for the same reconciler — libjolttui's tree ABI is libvidya's
	83	;; with cells under it — so `frq.tui` requires it after `frq.app`
	84	;; and renders the hiccup that is already written.
	85	;;
Merge origin/main, and let one jolt-native answer for both backends 1e8b590 nandi 16d ago	86	;; A path rather than a sha, like glimmer-vidya's would be if this
	87	;; alias were the way in: `just tui` builds jolt-native out of the
	88	;; flake and hands both Jolt halves over with -Sdeps, so this is for
	89	;; a checkout beside the tree and nothing else reads it.
Paint the same screens into a terminal ab83b42 nandi 17d ago	90	;;
	91	;; just tui
	92	:tui {:extra-deps {nandi/glimmer-tui
Retire the release-bumping script 4f38d68 nandi 11d ago	93	{:local/root "../jolt-native/glimmer-backends/glimmer-tui"}}
Paint the same screens into a terminal ab83b42 nandi 17d ago	94	:main-opts ["-m" "frq.tui"]}}
	95
	96	:tasks {frq "jolt -M:frq"
	97	tui "jolt -M:tui"}}