|
Some checks failed
Security / Security check (push) Failing after 1s
Studio's Flows destination is now the swappable fai_studio_flow_editor's full surface: a drag-and-drop graph view, the raw YAML text editor, and the run tab with inputs form + live step progress + outputs. What's gone: - The old saved-flows list + per-row run dialog. - The separate "flow-editor" navigation destination (one icon, not two — operators reach the editor by clicking Flows, period). - _FlowEditorAdapter (no longer needed; FlowsPage hands the runDriver to the editor directly). What's new: - lib/data/flow_run_driver.dart — StudioFlowRunDriver: adapter implementing the editor's FlowRunDriver. Maps runFlow() to HubService.runSavedFlow and events() to HubService.streamEvents filtered to step.* event types. Converts proto-shaped FlowOutput variants to the editor's host-agnostic FlowOutputValue family. - lib/pages/flows.dart — replaced with a 50-line wrapper that loads capabilities into the editor's picker dropdown and forwards the active locale. Editor pinned to fai_studio_flow_editor 0.2.0 (commit 870cbc2). All editor state — file list, dirty tracking, tab selection, graph layout sidecar, properties panel — lives in the editor package now; Studio just supplies the hub bridge. Version 0.51.10 -> 0.52.0 (minor bump — Flows-page contract changed, separate flow-editor destination removed). flutter analyze: 0 issues. flutter test: 12/12 green. Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| .githooks | ||
| assets/docs | ||
| docs | ||
| lib | ||
| linux | ||
| macos | ||
| test | ||
| tools | ||
| windows | ||
| .gitignore | ||
| .metadata | ||
| .security-allow | ||
| analysis_options.yaml | ||
| l10n.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_client_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.