DeeJanuzandClaude Opus 5.5 6dd9fb1ad8 One launch switch: scripts/in-box runs a program in the container it was built for ...

Every place an installed Frametop started a program with `distrobox enter dev --` now goes
through scripts/in-box: the pointer and power units, ft-gazed (ft-gaze, ft-eyes), the gaze
check's panel, the desktop's ft-screens, the remote desktop's krdp and VNC, and the three
settings apps. in-box starts the container in a scope of its own (container-up.sh, which now
takes the container's name) and becomes `distrobox enter BOX --`, so callers behave as before.

BOX is "dev" for a source install. A release names its own container in .frametop-release,
so the same tree runs from an image without editing nine call sites. FRAMETOP_BOX overrides
both. Development tools (frame.sh, the headless test, the gaze probe and lab) and hand
tracking, which install.sh doesn't install, keep using the dev container.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-07 20:54:13 -06:00

..

build.sh

Build scripts: one pinned OpenVR recipe, and they run inside the image too

2026-10-06 09:54:08 -06:00

frametop-power.service

One launch switch: scripts/in-box runs a program in the container it was built for

2026-10-07 20:54:13 -06:00

ft-powerd.cpp

Experimental (#29)

2026-10-04 19:44:30 -06:00

run.sh

Installers: ask for sudo in the terminal, and cope with SteamVR off

2026-10-01 15:04:49 -06:00