Prompted by the a1k.org announcement thread: a MorphOS user said they'd have preferred a MUI interface so they could run AmiAuth there.
The current GUI requires the ReAction/ClassAct classes (window, layout, listbrowser, fuelgauge, button), which MorphOS does not ship — its native toolkit is MUI. Nobody has reported trying AmiAuth on an NG system yet; the CLI (plain 68k, OS 2.04+) should run under MorphOS/OS4 68k emulation, but the GUI presumably won't start there.
Proposal: an alternative MUI front-end sharing the same portable core (vault, OTP, clock) and the existing commodity/ARexx/CLI-forwarding glue where feasible. MUI is also popular with a slice of classic 3.x users, so this isn't only an NG play.
Open questions:
- How much of
src/amiga/ GUI code is toolkit-agnostic vs ReAction-specific — i.e. is this a new front-end or a refactor plus two thin toolkit layers? (Related: a GadTools fallback front-end is proposed separately; if the GUI logic gets split from the toolkit layer, both benefit.)
- MUI would be an optional build/binary — the zero-mandatory-runtime-dependencies rule stays intact for the shipped default binaries.
- Whether to verify the CLI under MorphOS/OS4 emulation first and document the status regardless.
🤖 Generated with Claude Code
https://claude.ai/code/session_01CRP4gJ7zq9zy1DoC4toRWc
Prompted by the a1k.org announcement thread: a MorphOS user said they'd have preferred a MUI interface so they could run AmiAuth there.
The current GUI requires the ReAction/ClassAct classes (window, layout, listbrowser, fuelgauge, button), which MorphOS does not ship — its native toolkit is MUI. Nobody has reported trying AmiAuth on an NG system yet; the CLI (plain 68k, OS 2.04+) should run under MorphOS/OS4 68k emulation, but the GUI presumably won't start there.
Proposal: an alternative MUI front-end sharing the same portable core (vault, OTP, clock) and the existing commodity/ARexx/CLI-forwarding glue where feasible. MUI is also popular with a slice of classic 3.x users, so this isn't only an NG play.
Open questions:
src/amiga/GUI code is toolkit-agnostic vs ReAction-specific — i.e. is this a new front-end or a refactor plus two thin toolkit layers? (Related: a GadTools fallback front-end is proposed separately; if the GUI logic gets split from the toolkit layer, both benefit.)🤖 Generated with Claude Code
https://claude.ai/code/session_01CRP4gJ7zq9zy1DoC4toRWc