-
-
Notifications
You must be signed in to change notification settings - Fork 21
Description
Congratulations on the release of ISD v0.6!
I am incredibly impressed with ISD's superior visibility and intuitive operation. It truly is a "Gospel" tool that drastically cuts down on the usual command-line hassle.
I have one piece of feedback concerning color accessibility that I believe could significantly boost the tool's wider adoption.
-
The Problem:
The default green color used for active/enabled units is highly difficult to read for me. This is due to a combination of age-related visual changes and general contrast issues (which affect a significant portion of the global male population, about 8-10% in Caucasian communities). This subtle issue might be a barrier preventing broader adoption. -
Reference Example (Custom TUI Solution):
I also develop my own system monitoring TUI in Rust, so I appreciate the difficulty in UI design. In my tool, I've found that carefully adjusting colors and contrast is essential for readability. For instance, in the header below, I use inversion and color shifting to ensure critical system information (like CPU status and frequency) is legible even from a distance. This kind of UI adjustment is vital for system administration efficiency.AMD P-State: guided - powersave 🐰 🐰 AMD Ryzen 9 5900X (24) 4.695GHz
-
Humble Proposal (Considering Ease of Implementation):
I understand that implementing a comprehensive theme system can be a major undertaking. I'd like to propose simpler, less intrusive solutions:- High-Contrast Theme Templates: Could you consider providing high-contrast theme templates or simple configuration examples for popular terminal emulators (WezTerm, Kitty, etc.)? This would allow users to easily override the default ANSI Green with a more discernible color without changing ISD's source code.
- Documentation Clarity: Clearly state in the README/docs that ISD's status colors rely on the terminal emulator's ANSI palette, guiding users toward terminal-side customization for better accessibility.
This small adjustment could help ISD become a more inclusive and universally adopted system tool.
I look forward to your continued development!
