idea: settings need to also be supported in the TUI #29

New Issue

hugo · 2026-07-15T18:27:35Z

hugo commented

2026-07-15 18:27:35 +00:00

the TUI needs to be able to operate on the same preferences as the GUI application. so there needs a new panel and sidebar linked to number 6 to open the preferences editor and when selecting a sidebar entry, a specific editor for that section of the preferences is opened and allows the user to work on preferences there.

hugo added the idea label 2026-07-15 18:29:02 +00:00

hugo added the ctritical label 2026-07-16 20:28:26 +00:00

hugo referenced this issue from a commit

2026-07-17 06:38:32 +00:00

feat: TUI settings panel on key 6 with per-section preference editors backed by the same GUI settings backends (issue #29)

hugo commented

2026-07-17 06:40:32 +00:00

Implemented in 505527a and pushed to main.

The TUI now has a settings panel on key 6, matching the GUI panel numbering. The sidebar lists the same preference sections as the GUI settings editor (Project, Editor, Content, AI, Technology, Publishing, Data, MCP, Style), and pressing enter on a section opens a section-specific editor in the main area:

enter edits a text field in a status-line prompt, toggles a boolean, or cycles an enum through its options
ctrl+s saves the section through the exact same backends the GUI uses (BDS.Metadata, BDS.Settings, BDS.AI, BDS.MCP.AgentConfig), so both frontends operate on the same preferences
esc cancels the prompt, then closes the editor

The section forms come from a new shared, renderer-agnostic module (BDS.UI.SettingsForm); the AI save pipeline was extracted from the GUI settings editor so both frontends share it. Data is shown read-only (maintenance commands already live under the : prompt), and category removal plus AI model discovery remain GUI-only for now.

Covered by tests (10 new for the shared forms, 4 new TUI panel tests), localized for de/fr/it/es, and the tui.allium spec was extended with a SettingsPanel rule.

Implemented in 505527a and pushed to main. The TUI now has a settings panel on key **6**, matching the GUI panel numbering. The sidebar lists the same preference sections as the GUI settings editor (Project, Editor, Content, AI, Technology, Publishing, Data, MCP, Style), and pressing enter on a section opens a section-specific editor in the main area: - **enter** edits a text field in a status-line prompt, toggles a boolean, or cycles an enum through its options - **ctrl+s** saves the section through the exact same backends the GUI uses (BDS.Metadata, BDS.Settings, BDS.AI, BDS.MCP.AgentConfig), so both frontends operate on the same preferences - **esc** cancels the prompt, then closes the editor The section forms come from a new shared, renderer-agnostic module (BDS.UI.SettingsForm); the AI save pipeline was extracted from the GUI settings editor so both frontends share it. Data is shown read-only (maintenance commands already live under the : prompt), and category removal plus AI model discovery remain GUI-only for now. Covered by tests (10 new for the shared forms, 4 new TUI panel tests), localized for de/fr/it/es, and the tui.allium spec was extended with a SettingsPanel rule.

hugo closed this issue

2026-07-17 06:40:45 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: hugo/bDS2#29