nandi/jolt-nativepublic Fork 0
789bb134c91bfdee346df2dc9656bf2e7f9bbd1a
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.

Paint glimmer with nothing under it f554a01 · on 789bb134c91bfdee346df2dc9656bf2e7f9bbd1a · nandi · 11d ago
deps.edn · 28 lines · 1.4 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
26
27
28
{:paths ["src"]

 ;; glimmer-gfx is a backend for glimmer, beside glimmer-vidya and glimmer-tui
 ;; 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.
 ;;
 ;; Unlike its siblings there is no shared object under it. The rasterizer is
 ;; jolt, the layout is jolt, the font is jolt; the only foreign code is Xlib,
 ;; and Xlib draws nothing here — it opens a window and takes a finished
 ;; framebuffer. So this backend is the one that runs where no toolkit is
 ;; installed, and the one to read to see what a backend actually has to do.
 :deps {jolt-lang/glimmer {:git/url "https://github.com/jolt-lang/glimmer"
                           :git/tag "v0.1.0"
                           :git/sha "5581c331c51aff989259b9e8e92ec920fe5e6741"}}

 ;; The system Xlib, not one of this repo's crates. :optional so the tests,
 ;; which open no window, run on a machine with no X11 at all.
 :jolt/native [{:name "X11" :optional true
                :linux ["libX11.so.6"] :darwin ["libX11.6.dylib"]}]

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

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