2b65cd771f
Some checks failed
Security / Security check (push) Failing after 2s
+ label opacity in lockstep (no more glitchy expand) The previous "fixed-width icon column" commit already locked the icon's horizontal pixel-X, but the rail still _felt_ glitchy on expand because the rail's geometry and the rail's content were animated by two different mechanisms: - Width: AnimatedContainer over FaiMotion.fast (120 ms) - Content: setState(_hovered = true) → conditional `if (expanded) Expanded(label)` snaps in one frame So on mouse-enter the label widget appeared INSTANTLY while the rail was still 72 px wide. The label tried to render in 0 px of available space and Flutter's layout engine clamped it; over the next 7 frames the rail grew to 220 px and the label visibly "settled in". That's the perceived glitch. Replace the two-source animation with a single SingleTickerProviderStateMixin + AnimationController whose value `t` (0..1, eased via easeInOutCubic) drives both: - rail width = lerp(72, 220, t) - label opacity = t - labelsInteractive = t > 0.5 (so hidden buttons can't eat clicks meant for the icon column) Labels are wrapped in `t > 0 ? IgnorePointer(Opacity(...)) : SizedBox.shrink()`. Once the animation starts, the label joins the tree at opacity ≈ 0 (invisible — no pop) and fades up smoothly as t grows. When fully collapsed (t == 0) the label is removed from layout entirely, so the connection pill's tall "Start hub" affordance doesn't inflate the collapsed rail's height (this also fixes the widget_test vertical-overflow that 0.51.4 introduced). Same pattern applied to the footer (settings icon stays in the 72-px column always; theme/lang/clock fade in beside it) and to each _SidebarItem destination row. End result: width AND content travel together along the same animation curve. No more "snap then catch up" — they're mathematically inseparable. Version 0.51.4 → 0.51.5. 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.