Settings window: language, theme, connection and the palette

Open
#90 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
csharp
Domain
desktop

Research direction

Start by reading docs/plans/completed/20260915-window-chrome.md and tracing the startup reads of app/app.yaml and connection/connection.yaml. Resolve the live-update, --config-dir, and multiple-YAML questions before implementation; done means an Edit → Settings window edits language, theme, archive connection, and the palette.

Written by the indexing model from the issue text.

Description

The viewer reads app/app.yaml (locale, theme) and connection/connection.yaml (host, port, database, user, password, source time zone, poll interval) at startup and refuses to start without them. An operator who has to change any of it edits YAML by hand, and the shipped connection.yaml carries an empty password, which is a named startup failure by design.

A settings window gives the operator the values that are meant to change, and nothing else.

Scope

  • Language and theme, written back to app/app.yaml.
  • The archive connection, written back to connection/connection.yaml. The password is stored in plain text for now; how it is protected is a separate decision.
  • The palette editor.
  • Edit -> Settings in the menu bar. The Edit menu does not exist yet: the window chrome deliberately shipped no menu item without a command behind it (docs/plans/completed/20260915-window-chrome.md).

Open questions for the plan

  • Which values apply live and which need a restart. Language and theme are read once at startup today; the connection was raised as the case that should reconnect without one.
  • Whether the window edits the tracked configuration directory or the copy the run was given by --config-dir.
  • What the window does when a section folder holds several *.yaml files, since a key may live in only one of them.
Dominant language
C#
Stars
0
Forks
0
Avg merge
18m
Merged PRs (30d)
42

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Semiteq/SemiPlot

All issues in Semiteq/SemiPlot

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.