Icons and color
One typeface pair, one palette, one color vocabulary and one way of drawing icons, so a tab, a status segment, a
tree row and a Settings row say the same thing in the same way in every app. Reference: Editora’s
styles/ui-font.css and ui/Fonts.java (type), styles/atlantafx-themes/editora-light.css and editora-dark.css
(the Caret & Ink palette, which Torrenta and Termina vendor), the .root block at the top of
styles/app.css (the state vocabulary), ui/Themes.java and ui/EditorThemes.java (themes), ui/Icons.java,
ui/FileIcons.java, ui/MenuBarIcons.java and editor/MenuIcons.java (icons), and StyleContrastTest, which
pins the color rules.
Inter speaks, JetBrains Mono works. Inter is the chrome: menus, buttons, settings, pickers, status bar. The monospace face is for text that is code or output: the editor, a terminal, the environment block in About, log timestamps.
| Property | Value | Reference |
|---|---|---|
| UI family | Inter, in four faces, bundled in the app’s resources and registered before any CSS is applied | Fonts.UI, Fonts.loadForFirstPaint, resources/com/editora/fonts/inter/ |
| Root size | 14 px, the AtlantaFX theme’s root size; popups pin absolute pixels where an owner’s font would leak (see Menus) | MainMenuBar.UI_FONT_SIZE |
| How it is attached | A scene stylesheet (ui-font.css, one .root rule whose -fx-font-family names Inter) on every window’s scene, dialogs and popups included | App.installUiFont |
| Monospace | JetBrains Mono by default; Cascadia Code, Fira Code, IBM Plex Mono and Source Code Pro are bundled as editor choices | Fonts.DEFAULT, Fonts.BUNDLED |
- ICON-01 MUST Inter is attached by a scene stylesheet on every window’s scene, dialogs, popups and
tooltips included, not by a rule in the app stylesheet.
- Why: dialogs, the Settings window, the palette, context menus and tooltips each live in a scene of their own
that does not share
app.css, and a scene sheet is re-applied cleanly when the theme switches at run time (setUserAgentStylesheet). AtlantaFX neither bundles nor names Inter, and JavaFX does not fall through a font-family list, so without the sheet the whole interface renders in the platform’s “System” face. - Check (code): a listener on
Window.getWindows()addsui-font.cssto each window’s scene, and to a new scene when the window’s scene changes; no.rootrule inapp.csssets-fx-font-family. - Reference: Editora
App.installUiFont,styles/ui-font.css. Termina and Torrenta carry the same sheet.
- Why: dialogs, the Settings window, the palette, context menus and tooltips each live in a scene of their own
that does not share
- ICON-02 MUST The app bundles Inter’s four faces and registers them before any CSS is applied; it never
maps the platform’s own UI font.
- Why: an earlier macOS-only sheet used San Francisco, which JavaFX faux-bolds; Inter has a real bold on every platform.
- Check (code):
Inter-Regular,Inter-Bold,Inter-ItalicandInter-BoldItalic.ttfare under the app’sfonts/inter/with theirOFL.txt, andFont.loadFontruns on them before the first window is shown. - Reference: Editora
src/main/resources/com/editora/fonts/inter/,ui/Fonts.java(loadForFirstPaint, called fromApp). Termina and Torrenta bundle the same four faces.
Modula is the stated exception to ICON-01 and ICON-02: IBM Plex Mono everywhere, because every reading on a radio is a number (see Before adding a setting in Settings).
The palette: Caret & Ink
Section titled “The palette: Caret & Ink”The flagship theme pair, “Editora Light” and “Editora Dark”, is authored (not vendored) and derived from Editora’s icon: a caret teal accent, ink navy as the text in light and the surface in dark, porcelain and abyss grounds, and brace periwinkle reserved for the keyboard. Amber, red and green are semantic and never decorate.
- ICON-04 SHOULD A theme file follows the vendored AtlantaFX community themes: a
.rootblock of-color-*tokens, then component rules that reference only those tokens.- Check (code): the file’s first rule is
.root, and no rule after it holds a#hex. - Reference: Editora
styles/atlantafx-themes/editora-light.css,editora-dark.css.
- Check (code): the file’s first rule is
- ICON-05 SHOULD A new app ships the Caret & Ink pair as its default theme, with
editora-light.cssandeditora-dark.csscopied unchanged into its ownstyles/.- Why: the palette is the family’s, not the editor’s.
- Check (code): the app’s two files are identical to Editora’s.
- Reference: Torrenta and Termina
styles/. Both copies ofeditora-dark.cssmatch Editora’s; both copies ofeditora-light.cssstill have the earlier-color-accent-fg,-color-warning-fgand-color-success-fg, which Editora has since darkened.
- ICON-06 SHOULD Brace (
-state-key) is aladder()over-color-bg-defaultthat picks a deep ink on a light ground and a lighter periwinkle the darker the ground gets, and reads at 4.5:1 or more on every bundled theme’s default and subtle surfaces.- Why: Brace has no AtlantaFX role, so it has to be a literal.
- Check (test): a contrast test resolves the ladder against every bundled theme’s grounds.
- Reference: Editora
app.css(.root),StyleContrastTest.theKeyboardPeriwinkleReadsOnEveryBundledAppTheme.
State colors
Section titled “State colors”A color is a meaning, named once on .root and referenced everywhere. The same state wears the same color in a
tab, a status segment, a tree row, a picker and a Settings row.
| Token | Chains to | Meaning | Where it appears |
|---|---|---|---|
-state-amber | -color-warning-fg | Not durable yet | An unsaved tab, a read-only file, a narrowed view, a snapshot build |
-state-red | -color-danger-fg | Broken | Errors in the echo area and the Message Log, breakpoints, a recording |
-state-green | -color-success-fg | Verified | Found, added, passing, running |
-state-accent | -color-accent-fg | The app is offering something | An update, a link, the current branch, a selected row’s bar |
-state-olive, -state-violet | A ladder of the ground | Git only: untracked, renamed | The Project tree and tabs, the Map’s structure columns |
-state-key | A ladder of the ground | The keyboard, and nothing else | Chord chips, the menu chord column, brace matching |
-state-sel | -color-accent-subtle | The selected overlay row | The palette, pickers, the Message Log (about a 13 % accent wash) |
Each of the first four also has a -bg (the role’s -subtle) and a -hover (the role’s -muted) variant, so a
pill, a row tint and a hover state come from the same place. .state-pill is the shape (bold, radius 999, padding
1 × 8); the color variant beside it carries the meaning.
- ICON-07 MUST Each state color is named once, as a
-state-*token on.rootthat chains to one of the theme’s roles (or aladder()of its ground), and component rules use the token.- Check (code): the
-state-*tokens are declared only in the.rootblock at the top ofapp.css, each chaining to a-color-*role or aladder(). - Reference: Editora
styles/app.css(.root).
- Check (code): the
- ICON-08 MUST No fixed hex in a component rule.
- Why: a hex suits one theme; the roles track every theme for free.
- Check (code): outside the
.roottoken block,app.cssholds no#hex. A test fails a severity or debug color that is not a state token. - Reference: Editora
StyleContrastTest.severityAndDebugColoursComeFromTheStateTokens. Editora doesn’t yet pass the whole check:.breakpoint-marker,.exec-arrow,.view-mode-bar,.recent-remove,.personal-note-tooltip-content, the fold-gutter markers and the default editor and Markdown preview palettes inapp.cssstill carry fixed hexes.
- ICON-09 SHOULD Readable text uses
-color-fg-mutedor stronger, which is 4.5:1 on the default, subtle and overlay grounds in both flagship themes: a line of UI text is-color-fg-defaultand secondary text-color-fg-muted.-color-fg-subtle(about 3:1) is for disabled or decorative text only.- Check (test): a contrast test computes muted ink on each ground, and fails a readable selector set in
-color-fg-subtle. - Reference: Editora
StyleContrastTest.textThatMustBeReadUsesTheMutedRoleNotSubtle.
- Check (test): a contrast test computes muted ink on each ground, and fails a readable selector set in
- ICON-10 MUST Tinted text (
-color-<role>-fg) reaches 4.5:1 on its own subtle fill and on both grounds.- Check (test): a contrast test computes each role’s
-fgon its-subtle, on-color-bg-subtleand on-color-bg-default, in both flagship themes. - Reference: Editora
StyleContrastTest.lightTintedTextReachesAaOnItsOwnGroundAndOnTheSubtleSurface,darkTintedTextStaysAa.
- Check (test): a contrast test computes each role’s
- ICON-11 MUST Ink on an emphasis fill is
-color-fg-emphasis, never white.- Why: white on the dark accent is 1.68:1.
- Check (test): a contrast test computes
-color-fg-emphasison each role’s-emphasis, and the rules that paint on an emphasis fill use it. - Reference: Editora
StyleContrastTest.inkOnAnEmphasisFillIsTheThemesOnEmphasisColour.
- ICON-12 MUST One focus ring,
-focus-ring: -color-accent-emphasis, drawn by the:focus-visibleblock at the end ofapp.css, at 3:1 or better on every surface (see Keyboard first).- Check (test): a test reads
-focus-ringfrom.rootand computes it on the default, subtle, inset and overlay grounds. - Reference: Editora
app.css(Keyboard focus),StyleContrastTest.theFocusRingIsAtLeastThreeToOneOnEverySurface.
- Check (test): a test reads
- ICON-13 SHOULD A brand hue the theme has no role for (periwinkle, olive, violet) is a
ladder()of-color-bg-default, never a fixed pair.- Why: the old fixed light hexes read at 3.2:1 on Editora Dark.
- Check (test): a contrast test resolves each ladder on every bundled theme’s ground.
- Reference: Editora
app.css(-state-olive,-state-violet,-state-key),StyleContrastTest.theGitOliveAndVioletFollowTheAppThemesGround.
- ICON-14 SHOULD A pure test reads the stylesheets and does the WCAG arithmetic.
- Why: a contrast regression is invisible in a code diff.
- Check (code): a test class reads the app’s
.cssresources and computes contrast ratios without starting the toolkit. - Reference: Editora
StyleContrastTest. Mirada’sAccentTestchecks that the accent reads as text on both grounds; Termina’sThemeTestkeeps every chromatic color of its terminal schemes legible.
Themes
Section titled “Themes”- ICON-15 MUST The app has light and dark themes and switches between them at run time, without a restart
(see Window shell).
- Check (code): picking a theme calls
Application.setUserAgentStylesheetin the running app. - Reference: Editora
ui/Themes.java(applyAppTheme).
- Check (code): picking a theme calls
- ICON-16 MUST A “follow the system” choice applies the light or dark theme to match the system’s color
scheme, and changes with it.
- Check (code): the theme setting has a system value, and a listener on
Platform.getPreferences().colorSchemeProperty()re-applies the theme. - Reference: Mirada
settings/Settings.java(ThemeChoice.SYSTEM),ui/Theme.java; nuxconfig/Advanced.java(THEME_SYSTEM),ui/Theme.java. Editora, Torrenta, Termina and Modula don’t yet: their pickers list named themes only.
- Check (code): the theme setting has a system value, and a listener on
- ICON-17 MUST A theme name the app does not know falls back to the first-run default theme.
- Check (code): the lookup from a saved name to a theme ends in the default, not an exception.
- Reference: Editora
Themes.themeFor, falling back toThemes.DEFAULT(Editora Light).
- ICON-18 SHOULD Semantic colors never decorate: a theme may change the teal, the ground and the ink, but
amber still means “not durable yet”, red “broken” and green “verified”.
- Check (code): every rule that uses
-state-amber,-state-redor-state-greenmarks one of the meanings in the State colors table. - Reference: Editora
app.css.
- Check (code): every rule that uses
Editora lists 28 app themes: the Caret & Ink pair, AtlantaFX’s Primer, Nord, Cupertino and Dracula, and 19
community themes (Army, Autumn, Blacky, Blue, Browny, Fall, Navy, News, Spring, Summer, Winter, Yacht, several with
light and dark variants) vendored unmodified from the MIT-licensed dlsc atlantafx-themes collection. User themes
under <config>/themes/ join the list (Themes.names()).
Editor themes are separate (EditorThemes). The flagship pair carries its own editor stylesheet; every community
theme is served by one adaptive editor theme whose syntax palette is expressed in the theme’s own -color-*
tokens, so it follows whatever ground the theme has.

Every icon is an SVG path drawn in code, colored by the stylesheet so it follows the theme, and returned as a fresh node per call (a JavaFX node has one parent). There are two families, mid-migration to the UI Kit, and they are not interchangeable.
icon-line · -fx-stroketoolbar-icon · -fx-fill| Property | Line family | Filled family | Reference |
|---|---|---|---|
| Source | The UI Kit’s 16-unit outline glyphs, drawn for the kit | Material Design 24 dp single-path glyphs (Apache-2.0), plus Simple Icons brand marks (CC0) | Icons.line, Icons.of, NOTICE |
| Style class | icon-line | toolbar-icon | app.css |
| Color | -fx-stroke: -color-fg-muted, stroke width 1.3, round caps and joins, fill transparent | -fx-fill: -color-fg-muted | .icon-line, .toolbar-icon |
| Hover, disabled | -color-fg-default on hover, -color-fg-subtle disabled; every context mirrors the matching rule of the other family | The same | .button:hover .icon-line, .button:hover .toolbar-icon |
| Drawn size | 16 × 1.2 = 19.2 px (LINE_SCALE = ICON_SCALE × 24 ÷ 16) | 24 × 0.8 = 19.2 px (ICON_SCALE) | Icons |
| Used for | The chrome the kit draws: toolbar, tool stripe, tabs, and every action that has a kit glyph | Everything the kit specifies no glyph for: file types, context-menu rows, build-tool and browser brand marks | Icons, FileIcons |
- ICON-19 MUST A glyph node carries one family’s style class,
icon-lineortoolbar-icon, never both.- Why: a line glyph is colored by its stroke, and any
X .toolbar-iconfill rule (there are dozens) would paint its outline solid. A glyph that moves family moves its CSS with it. - Check (test): a test builds every line glyph and fails when one also carries
toolbar-icon. - Reference: Editora
ui/Icons.java(line,of),MenuIconFamilyFxTest.aLineGlyphIsNeverAlsoTaggedAsAFilledOne.
- Why: a line glyph is colored by its stroke, and any
- ICON-20 MUST The same action wears the same glyph wherever it is reached: Save is one floppy on the
toolbar, in the File menu and in a tab’s menu.
- Check (test): a test compares the path data and style class of each action’s glyph across the icon classes.
- Reference: Editora
ui/MenuBarIcons.javareusesIcons;editor/MenuIcons.java(the editor package may not depend onui) copies each twin’s family and path data verbatim, held byMenuIconFamilyFxTest.everySharedActionUsesTheSameGlyphInBothIconSets.
- ICON-21 MUST An icon-only control has a name: it is built through
Icons.buttonorIcons.toolbarButton, which set the tooltip and the accessible text together (see Keyboard first).- Check (code): no icon-only
Buttonis given a graphic outside those helpers withoutIcons.name. - Reference: Editora
ui/Icons.java. Editora doesn’t yet pass the check on its main toolbar:WindowToolbar.setupButtonandToolbarCoordinator.buildExtraButtonset only the tooltip (see Toolbars and tooltips).
- Check (code): no icon-only
- ICON-23 SHOULD A file’s icon comes from a pure function from file name to icon key, unit-tested without the
toolkit, and any type it does not know gets the generic document glyph, so a new type never regresses the look.
- Check (test): a unit test resolves names to keys, an unknown one to the generic key.
- Reference: Editora
ui/FileIcons.java:iconKeyFor(name)resolves the key,forFileNameturns it into a node; brand logos from Simple Icons, category glyphs (image, archive, PDF, table, lock, JSON, settings) from Material.FileIconsTest.unknownAndNullFallBackToGeneric.
- ICON-24 MUST Every glyph set and font the app ships is credited in
NOTICEwith its license.- Check (code): each icon source named in the icon classes and each family under
fonts/has an entry inNOTICE. - Reference: Editora
NOTICE: Material Design Icons (Apache-2.0), Simple Icons (CC0; the logos stay their owners’ trademarks), Inter and the monospace faces (OFL), and the glyph sets inside the bundled Symbols Nerd Font, Octicons and Seti UI (MIT) among them.
- Check (code): each icon source named in the icon classes and each family under
In the apps
Section titled “In the apps”| App | Icons | Size |
|---|---|---|
Both families, ui/Icons, FileIcons, MenuBarIcons, editor/MenuIcons | 19.2 px on the toolbar and in menus | |
Both families, copied from Editora as Icons.Glyph, which knows its box and resizes with at(px); the toolbar is all line glyphs (stroke 1.5, -torrenta-icon) | 17 px toolbar, 16 px menu and tab (MENU_SIZE), 13 px sidebar | |
Material filled, ui/MenuIcons, colored by .menu-icon (-color-fg-muted; -color-fg-default focused; subtle and half opacity disabled) | 24 × 0.7 = 16.8 px, menus only | |
Hand-drawn stroked paths on a 24-unit grid, two-unit strokes, round caps, in GNOME’s symbolic style, so nothing carries a license; .icon strokes -color-fg-default | 16 px, centered in a 16 px box | |
Glyphs: the transport symbols (tune, seek, star) as shapes, because the characters are missing from most faces and render differently on every platform | 11 px | |
No in-window icons; the tray icon is rendered as a bitmap by severity (TrayIconRenderer) | Tray only |
Pauta 4.0.0 · · Changelog · This page in the latest edition