Home /Modules/docs/GUI.WORK.md

GUI.WORK.md

docs/archive/GUI.WORK.md · 226 line(s) · markdown

<img align="right" src="../../images/sleela/sleela-medium-profile-permanent-icon-002.jpg" width="45" height="45" alt="SLeeLa">

GUI.WORK.md — SLeeLa Terminal GUI Work Log

SLeeLa

<p align="center"><img src="../../images/sleela/sleela-wordmark.svg" alt="SLeeLa — The Now. The Ingredient." width="560"></p> <p align="center"><img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela-programming-language-002.jpg" alt="SLeeLa Marketing Logo" width="560"></p>

Working handoff for the next development session. Keep this file current as decisions are implemented, tested, or revised.

1. Purpose

This document records the SLeeLa Terminal GUI decisions, implementation context, visual direction, open questions, and next actions so work can resume without reconstructing prior conversations.

Repository: mearvk/SLeeLa Primary GUI source: sleela-terminal/sleelaterminal-gui.cpp Shell executor: sleela-terminal/executor.cpp GUI principles: sleela-terminal/UI-PRINCIPLES.md

Work should be committed to both main and master, keeping the branches aligned unless a task explicitly calls for a different workflow.

2. Current visual direction

Main surfaces and command output

The current target palette is:

UI elementTarget colorRGBNotes
Main terminal workspace#FCFCFC(252, 252, 252)Very light neutral background
Command output response surface#4B4B4B(75, 75, 75)Shared background for output text from every command
Text inside the response surface#F2F2F2(242, 242, 242)Lighter than the response surface for legibility

Core rule: whenever a command produces output text, present that output using the same dark response surface and light foreground text. This is not an ls-only treatment. It applies consistently to ordinary commands, compiler/build output, status messages, and error output. Preserve meaningful output and error distinctions through text, icons, or restrained accents without breaking the shared surface treatment.

The response surface should only appear when output exists. Empty commands should not create an empty response panel.

The intended design is a visually unified, rounded response rectangle/panel. Do not interpret this as requiring a separate background rectangle for every line or filename. The earlier per-file tile colors were an experiment for ls; the broader output-panel rule supersedes that treatment as the overall direction.

GUI component labels and visual inventory

Use the following names consistently in issues, code reviews, screenshots, and future GUI work. These labels describe the visible part and its role; they are documentation labels, not a request to add permanent text labels to every widget.

LabelLocation / appearanceFunction and behavior
Application title barTop edge; dark-purple/blue gradientShared window chrome for the SleelaTerminal application.
SLeeLa title-bar logoFar left of the title barBranding image; decorative, with a tooltip describing the application.
New Tab (+) buttonTitle bar, beside the logoOpens a new independent terminal session. Shortcut: Ctrl+Shift+T.
Window controlsRight side of the title barNative minimize, maximize/restore, and close controls.
Settings button (hamburger)Right side of the title bar, before the window controlsOpens the settings interface.
Throbber / activity railThin, bright strip directly below the title barAnimated light-blue cells indicate ambient activity; this is decorative and not a command-progress indicator.
Terminal tab stripAbove the terminal contentSwitches between independent shell sessions. Tabs can be reordered.
Terminal tab titleInside each tab, e.g. “Terminal 1”Identifies the session. Titles are currently sequential labels, not live shell-directory names.
Close Tab (×) buttonInside each tabCloses only that tab's shell session. Shortcut: Ctrl+Shift+W. Closing the final tab closes the application.
Terminal workspaceMain near-white outer work area, #FCFCFCGTK workspace surrounding the active terminal view.
Interactive terminal surfaceMain charcoal area, #4B4B4BVTE terminal receiving keyboard input and displaying the PTY stream; text defaults to #F2F2F2.
Terminal glow overlaySubtle light effect over the terminal surfaceDecorative reflection from the activity rail. It must not intercept mouse or keyboard input.
Command summary rectangle / warm-brown command stripBrown-toned row printed immediately after an interactive command is submittedSummarizes the exact command text and its local date/time. This is the command-append summary row; the command's actual output begins on the following line. The brown appearance is ANSI background applied to VTE text cells, not a standalone GTK rectangle or a command-output panel.
Command outputTerminal lines after the command summary rowActual stdout/stderr and interactive-program output. It remains in the charcoal terminal surface and must retain shell/PTY semantics.
Footer brandBottom-left, “SLeeLa”Static product branding.
Footer separatorVertical divider beside the footer brandSeparates branding from the footer message.
Footer status/ticker textMiddle of the footerDisplays the configured status/feed text within the available width.
CMD / software launcher controlImage control toward the footer's right sideOpens the software/install menu; it is a launcher, not a shell tab.
Version labelBottom-right of the footerDisplays the GUI version string.
Terminal context menuRight-click inside a terminalContext actions for terminal interaction, such as copy/paste/select-all where available.
Settings interfaceOpened from the title-bar Settings buttonHolds presentation and data-orientation preferences; settings are shared by tabs.

Command summary strip: exact meaning

The warm-brown row is specifically the command summary rectangle (also called the command summary strip or command-append row). It records what interactive command was submitted and when it was submitted, using the local timestamp. It is distinct from both the shell prompt and the output produced by the command:

  1. Prompt/input — the user enters a command.
  2. Command summary strip — the submitted command and local date/time are shown with the muted warm-brown ANSI cell background.
  3. Command output — the command's actual result starts on the next line.

The strip is a presentation row for interactive shell use. It must not inject styling into scripts, pipelines, redirected file contents, or the actual command's argv. Do not describe it as a separate rounded GTK widget unless a future implementation actually creates one.

Important implementation distinction

The current terminal uses GTK 4 with VTE. ANSI background sequences can color terminal cells, but they do not create a true independent GTK rounded rectangle around a block of output.

Any new output presentation must preserve shell behavior:

3. ls output and shell behavior

The custom ls builtin has been removed. slsh now resolves ls through the normal external-command PATH lookup, so the operating system's standard ls handles -l, -la, and its full native option set. Command flags remain separate argv entries and are not stripped or reinterpreted by the shell. Standard output, pipelines, and redirection remain unstyled.

External commands continue to receive option flags in argv; the leading hyphen is not stripped by the shell. Regression checks exercise ls -l, ls -la, ls -lh, ls -F, ls -d, ls -1 -- PATH, and an external command receiving -la as an argument.

Continue testing long and Unicode filenames, paths with spaces, empty directories, and output redirection.

4. Window chrome and motion

The broader GUI direction includes:

Prior motion preferences:

Confirm the exact interpretation of these speed ratios against the animation code before changing timing. Motion should be smooth, bounded, and preferably respect reduced-motion/accessibility settings if supported.

Window title-bar icon palette previously discussed:

5. Prompt styling

The shell prompt should distinguish its components without making the prompt noisy:

A previous rendering issue was noted: when the prompt fades or repaints, reset the cursor to prompt column 1 before repainting. Verify that animations or redraws do not duplicate prompt text, leave fragments behind, or move the input cursor unexpectedly.

6. Technology and build context

7. Recent change references

The following commits were reported as pushed previously; this is historical context, not proof that the current branch heads or CI are still at these commits.

Relevant source links:

8. Next-session checklist

Priority 1 — Inspect before editing

Priority 2 — Implement the unified response appearance

Priority 3 — Build and verify

Priority 4 — Document and synchronize

9. Definition of done

The next milestone is complete when all command output consistently uses the approved shared response styling, the visual treatment is honest about VTE/GTK capabilities, shell semantics remain intact, the GUI builds and relevant tests pass, and the resulting code/docs are present on both branches.

10. Session notes

Append dated notes here after each work session.

2026-10-12

2026-10-12 — terminal surface correction

2026-10-12 — standard command results and summary rows

2026-10-12 — independent terminal tabs