You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The top of the GUI sidebar is still visually crowded in the Windows v0.2.0rc12 candidate. It permanently shows a large branding card, the tagline/version, the absolute run-directory path, a large Workspace expander, and the tutorial button before navigation begins.
This is cosmetic/UX feedback only: preserve all workspace behavior, but simplify the persistent header and disclose secondary information only when requested.
Open the GUI and inspect the top of the left sidebar.
Use a run directory with a realistic long Windows path, for example C:\fp-tools-win-test\pr49\test-output\....
Actual result
The persistent sidebar header contains:
A bordered branding card with fp-tools.
Command-first footprinting workflows · v0.2.0rc12 underneath the name.
A separate Run dir: <absolute path> line, which becomes truncated and visually noisy.
A large Workspace expander immediately below it.
A full-width Show guided tutorial button.
The tagline does not help routine navigation, the version is overly prominent, and the environment-specific absolute path competes with the actual navigation. The path is also duplicated conceptually because Workspace already exists to inspect/change it. Together these controls consume substantial vertical space before OVERVIEW begins.
Expected result / recommended layout
Keep the default collapsed state compact:
fp-tools
Workspace >
Show guided tutorial (secondary/compact treatment is sufficient)
OVERVIEW
...
Recommended behavior:
Keep only fp-tools in the persistent brand area.
Remove Command-first footprinting workflows from the persistent sidebar.
Do not show the complete Run dir: path above the collapsed Workspace control.
When Workspace is expanded, show the full current run directory and the existing edit/apply controls there.
Keep the application version accessible but unobtrusive—for example inside expanded Workspace, an About area, or a sidebar footer.
Preserve the full path (not only an ellipsis) when expanded so it can still be inspected/copied.
Reduce the branding container padding/height, or use a simple text heading rather than a large bordered card.
Relevant implementation
src/fp_tools/gui_app.py currently renders all persistent header content in _render_sidebar_header():
The existing _render_sidebar_run_dir_controls() already provides the natural place for on-demand workspace details:
withst.sidebar.expander("Workspace", expanded=False):
run_dir_input=st.text_input("GUI run dir", ...)
A focused implementation would therefore remove the subtitle/run-dir pill from _render_sidebar_header(), move the current-path display into that expander, and tighten .fp-sidebar-brand spacing.
Acceptance criteria
In the default collapsed sidebar, the persistent brand header shows only fp-tools.
Command-first footprinting workflows is not permanently displayed.
No absolute run-directory path is displayed until Workspace is expanded.
Expanding Workspace shows the full current run directory and still allows it to be changed/applied.
The app version remains discoverable in a secondary location.
OVERVIEW and the navigation begin noticeably higher than in the rc12 candidate.
Long Windows and POSIX paths do not overflow, overlap, or force horizontal scrolling when Workspace is expanded.
Layout is checked in the native Windows window and Chrome at common widths (including a narrow sidebar).
Workspace path semantics and all existing run behavior remain unchanged.
Scope
Cosmetic/sidebar information architecture only. This issue should not change how run directories are resolved, created, persisted, or used by workflows.
Summary
The top of the GUI sidebar is still visually crowded in the Windows
v0.2.0rc12candidate. It permanently shows a large branding card, the tagline/version, the absolute run-directory path, a largeWorkspaceexpander, and the tutorial button before navigation begins.This is cosmetic/UX feedback only: preserve all workspace behavior, but simplify the persistent header and disclose secondary information only when requested.
Candidate tested
dfd283e9a1d64f5728b310af6e0b2c373337de5a324526923359436464405/fp-tools-gui-windows-x64c8cfbd635a2835980f69fa45ed8cb03787ffa2069706a174b91e811a742c389dv0.2.0rc12Steps to reproduce
fp-tools-gui-windows-x64.exe.C:\fp-tools-win-test\pr49\test-output\....Actual result
The persistent sidebar header contains:
fp-tools.Command-first footprinting workflows · v0.2.0rc12underneath the name.Run dir: <absolute path>line, which becomes truncated and visually noisy.Workspaceexpander immediately below it.Show guided tutorialbutton.The tagline does not help routine navigation, the version is overly prominent, and the environment-specific absolute path competes with the actual navigation. The path is also duplicated conceptually because
Workspacealready exists to inspect/change it. Together these controls consume substantial vertical space beforeOVERVIEWbegins.Expected result / recommended layout
Keep the default collapsed state compact:
Recommended behavior:
fp-toolsin the persistent brand area.Command-first footprinting workflowsfrom the persistent sidebar.Run dir:path above the collapsedWorkspacecontrol.Workspaceis expanded, show the full current run directory and the existing edit/apply controls there.Workspace, an About area, or a sidebar footer.Relevant implementation
src/fp_tools/gui_app.pycurrently renders all persistent header content in_render_sidebar_header():The existing
_render_sidebar_run_dir_controls()already provides the natural place for on-demand workspace details:A focused implementation would therefore remove the subtitle/run-dir pill from
_render_sidebar_header(), move the current-path display into that expander, and tighten.fp-sidebar-brandspacing.Acceptance criteria
fp-tools.Command-first footprinting workflowsis not permanently displayed.Workspaceis expanded.Workspaceshows the full current run directory and still allows it to be changed/applied.OVERVIEWand the navigation begin noticeably higher than in the rc12 candidate.Scope
Cosmetic/sidebar information architecture only. This issue should not change how run directories are resolved, created, persisted, or used by workflows.