93926741b1
UI parity for operators who never touch a CLI, plus a Store that reads more like an app store. Settings dialog: - Channel rows gain a popup menu: Connect / Make active / Enable autostart / Disable autostart. "Connect" still re-points Studio's wire; "Make active" actually writes ~/.fai/current-channel via `fai channel switch`. - Inline output panel surfaces the spawned binary's stdout on success or stderr on failure, so operators see what happened without opening a terminal. Store page rewrite: - Big top search bar with a clear button. Live filter on every keystroke. - Horizontal category strip auto-populated from the index; segmented status row (All / Published / Alpha / Planned), Installed-only chip, result count. - Grid of cards that reflows to fit the viewport — replaces the previous single-column list. Each card shows category-aware icon, version, status, tagline preview, and a one-click Install (or Details for installed / planned). - Per-module detail sheet renders the full bilingual description with a DE/EN toggle, separate Required- capabilities + Required-host-services sections, repo link, Read-docs button. Install + Uninstall live at the bottom. - StoreItem and HubService.searchStore now carry the German tagline + description so the locale toggle has something to switch to. SystemActions extended with `faiChannelSwitch`, `faiDaemonEnable`, `faiDaemonDisable` so Settings can spawn the right CLI without each call site reimplementing the `fai` resolution rules. Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com> |
||
|---|---|---|
| lib | ||
| linux | ||
| macos | ||
| test | ||
| windows | ||
| .gitignore | ||
| .metadata | ||
| analysis_options.yaml | ||
| pubspec.lock | ||
| pubspec.yaml | ||
| README.md | ||
F∆I Studio
Desktop GUI client for the F∆I Platform hub. Tier-2 generic
platform client per docs/architecture/client.md. Connects to a
local or remote fai serve over gRPC.
Status (2026-05-05): MVP scaffold. Three pages with mock data, no live gRPC connection yet. Validates the visual direction before the Dart SDK is wired in.
Pages (MVP scope)
- Modules — installed modules, capabilities, declared permissions. Click → manifest detail.
- Audit — live stream of hub events (when wired). Filter by event type and flow.
- Approvals — pending
system.approval@^0reviews with approve / reject buttons.
These three cover the platform's central properties: composition (modules), audit (events), human-in-the-loop (approvals).
Stack
- Flutter 3.40+ (Desktop: macOS, Linux, Windows)
- gRPC client via
fai_dart_sdk(sibling repo; pinned by relative path during development) - No external runtime dependencies; bundles its own Dart VM
Run locally
flutter run -d macos
Repo placement
Will be published as fai/studio on Forgejo (git.flemming.ws).
The local directory fai_studio/ follows the established
fai_platform/ layout convention.
Why "Studio" and not "Stage"
"Stage" collided too easily with "staging environment" in
developer English. "Studio" is the established industry pattern
for creator-tools (Visual Studio, Android Studio, RStudio) and
matches the GUI's audience of module developers, operators, and
power users. The rename was applied across all docs/ in the
platform repo on 2026-05-05.