Gacky

A PoC GTK4 frontend to tacky.

Build & run (development)

The frontend needs gjs, GTK 4 and libadwaita installed. The backend is built from the submodule:

git clone --recurse-submodules <repo> gacky   # or: git submodule update --init --recursive
cd gacky
make run        # builds tacky/dist/tackyd-json, stages it, and launches gacky

make backend builds just the daemon (into build/tackyd-json). At runtime gacky finds the backend via, in order: --tackyd PATH, $GACKY_TACKYD, the local build/ or tacky/dist/ build, then tackyd-json on $PATH.

Run ./bin/gacky --help for the backend CLI options gacky forwards (--transient, --debug-level, …).

Flatpak

The manifest builds both the backend (from a pinned tacky commit, with all Tcl/native deps pre-staged for an offline build) and the frontend onto the GNOME runtime; both binaries land in /app/bin.

Install the runtime once (the build expects it to be present):

flatpak install --user flathub org.gnome.Platform//49 org.gnome.Sdk//49

Then:

make flatpak-install        # build + install for the current user
flatpak run io.github.pounceandmiss.Gacky