TUI (Terminal User Interface) Scripts

A set of scripts to provide a generic terminal user interface (TUI) that can be used for various tasks.

Bugs

tui-menu: defining the menu-key: Do not use ' in description in "disk's" for ex "# 'x') Umount target disks prior installation dirs" Conflicts with initial ''

✦ Animations

• tui-animation / tui-animation2 Animated text ("Ideal Reset") expanding and contracting with colored characters. Version 2 runs more cycles with slower pacing.

• tui-animation3_first Color-shifting horizontal animation of "Ideal Reset", assigning each character a new color over time.

• tui-animation4-column Vertical "rainfall" animation of characters from "Ideal Reset", with each letter cascading down its terminal column independently.

✦ Spinners

• tui-spin to tui-spin5 Spinning indicators with varying complexity, colors, bracket shading, and elapsed time display. Each version explores a different style or spinner pattern (⠋, ▖▘▝▗, ░▒█, etc.).

✦ Checkboxes and Status Indicators

• tui-checkbox Displays colored checkbox output for statuses like success, failure, warning, or mid-state. Accepts an optional -n flag for no newline.

• tui-print-checkboxes Executes all executable scripts in a directory, captures their output and exit codes, and prints labeled, styled checkboxes based on their status.

✦ Menus and Script Runners

• tui-menu Scans a directory of scripts, displays an interactive menu using each script’s second-line metadata, and runs the selected one with passed arguments.

✦ Logging, Parsing, and Coloring

• tui-color-filter Parses input lines and applies colorization for known keywords (warning:, error:, note:, etc.). Also uncolors specific system lines (e.g., :: Synchronizing).

✦ File Operations

• tui-cp Enhanced copy progress visualizer using rsync, showing file counts, data transferred, elapsed time, percent done, and live visual updates.

✦ Visual Signage

• tui-sign Prints a banner-like box with colored borders and styled message text. Supports two visual modes for color schemes.

Let me know if you want this organized into usage categories (e.g., "status", "progress", "interactive"), or documented in Markdown/Manpage form.