nandi/jolt-nativepublic Fork 0
32fae8d36cadee8d58ff342979aea79722e69784
Commits
Clone
git clone https://git.rickub.com/nandi/jolt-native.git
git clone ssh://git@rickub.com/nandi/jolt-native.git

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

Write dvui's shape in jolt, on SDL3, with no shared object 109c7e4 · on 32fae8d36cadee8d58ff342979aea79722e69784 · Veronika Winters · 9d ago
deps.edn · 25 lines · 1.2 KBClojure Blame HistoryRaw
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
{:paths ["src"]

 ;; glimmer-jvui is a backend for glimmer, beside glimmer-vidya, glimmer-tui and
 ;; glimmer-gfx and against the same reconciler: glimmer owns the reactive core
 ;; and knows about no toolkit, and this project supplies widgets, painting and
 ;; the frame loop.
 ;;
 ;; It supplies them by *not* implementing them. glimmer-gfx writes its own
 ;; measure/place/paint/hit-test because there is nothing underneath it;
 ;; glimmer-vidya keeps a node arena in Rust because egui hands a reconciler
 ;; nothing to hold. Here the retained tree is thirty lines of atoms and the
 ;; walk over it emits jvui calls — jvui does the layout, the routing and the
 ;; painting, because it is a toolkit rather than an ABI.
 :deps {jolt-lang/glimmer {:git/url "https://github.com/jolt-lang/glimmer"
                           :git/tag "v0.1.0"
                           :git/sha "5581c331c51aff989259b9e8e92ec920fe5e6741"}
        jvui/jvui {:local/root "../../jvui"}}

 :aliases {:counter {:extra-paths ["examples"]
                     :main-opts ["-m" "glimmer-jvui.counter"]}
           :test    {:extra-paths ["test" "examples"]
                     :main-opts ["-m" "glimmer-jvui.tests"]}}

 :tasks {counter "jolt -M:counter"
         test    "jolt -M:test"}}