Claus Ibsen created CAMEL-24793:
-----------------------------------
Summary: camel-jbang - TUI theme-specific syntax highlighting
palettes for the built-in themes
Key: CAMEL-24793
URL: https://issues.apache.org/jira/browse/CAMEL-24793
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
The Camel TUI themes (.tcss stylesheets under tui/themes/) support optional
syntax-* tokens (syntax-comment, syntax-string, syntax-keyword,
syntax-function, syntax-type, syntax-constant, syntax-text). They style source
code in the Source tab and fenced code blocks in AI answers. Themes that omit
them fall back to a fixed Monokai palette (dark themes) or a GitHub-inspired
palette (light themes).
Today only the Turbo Pascal theme defines them, where the Borland editor look
(reserved words white, code yellow, comments grey) is the whole point.
Revisit the other built-in themes and decide, theme by theme, whether code
should follow the theme's own palette rather than Monokai/GitHub. Good
candidates are the themes that already come with an editor palette upstream:
Dracula, Nord, Solarized, Gruvbox, Catppuccin, Tokyo Night, Rosé Pine,
Kanagawa, Everforest. CRT and Monochrome should probably stay within their
single-hue idea as well, since Monokai pink on green phosphor is odd.
The guiding rule is that code must stay readable and pleasant for humans:
keywords, strings and comments distinguishable from each other and from
base-fg, with enough contrast on base-bg. Do not override tokens just because
it is possible. The token reference and design guidelines live in
tui/themes/theme.md in camel-jbang-plugin-tui.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
