Skip to content
Pauta6.1.0

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.

Rules on this page 21
IDLevelRule
Type
ICON-01MUST
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.
ICON-02MUST
The app bundles Inter’s four faces and registers them before any CSS is applied; it never maps the platform’s own UI font.
The palette: Caret & Ink
ICON-04SHOULD
A theme file follows the vendored AtlantaFX community themes: a .root block of -color-* tokens, then component rules that reference only those tokens.
ICON-05SHOULD
A new app ships the Caret & Ink pair as its default theme, with editora-light.css and editora-dark.css copied unchanged into its own styles/.
ICON-06SHOULD
Brace, the palette’s periwinkle for the keyboard (chord chips, the menus’ chord column), is one token on .root (Editora’s -state-key): a ladder() over -color-bg-default that 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.
State colors
ICON-07MUST
Each state color is named once, as a token on .root (Editora’s -state-*) that chains to one of the theme’s roles (or a ladder() of its ground), and component rules use the token.
ICON-08MUST
App stylesheets take their colors from AtlantaFX -color-* tokens, or from tokens the app builds on them; no component rule carries a fixed color, whatever its spelling: a hex, an rgb(), rgba() or hsb() value, or a named color such as white. A fixed color may stand only in a token’s definition, on .root or in a scoped block that sets -color-* tokens, and only where the theme has no role to build on: a scrim’s or a shadow’s color, a color drawn over an image or a canvas and not on the theme’s ground, or a color inside a ladder() of the ground (ICON-13). The ground, ink or accent of the app’s own windows given there as a fixed color, in place of the theme’s role, fails this rule; a state color given so is ICON-07’s failure and is not counted here again. transparent is not a color.
ICON-09MUST
Readable text uses -color-fg-muted or stronger, which is 4.5:1 on the default, subtle and overlay grounds in both flagship themes, Editora Light and Editora Dark: a line of UI text is -color-fg-default and secondary text -color-fg-muted. -color-fg-subtle (2.7:1 to 3.9:1, under 3:1 on Editora Light’s subtle and inset grounds) is for disabled or decorative text only. An app whose default light and dark themes are another pair is held to the same on that pair. A test holds it.
ICON-10MUST
Text in a role’s tint (the theme’s -color-<role>-fg, for the accent, success, warning and danger roles) reaches 4.5:1 on that role’s subtle fill (-color-<role>-subtle) and on the default and subtle grounds (-color-bg-default, -color-bg-subtle), in both flagship themes, Editora Light and Editora Dark, or, in an app whose default light and dark themes are another pair, in that pair. A test holds it.
ICON-11MUST
Ink on an emphasis fill is -color-fg-emphasis, never a fixed white: the token is white in the light themes and a dark ink in the dark ones, 4.5:1 or more on the emphasis fill of the accent, success, warning and danger roles in the two themes ICON-09 names. A test holds it.
ICON-12MUST
One focus ring color, the theme’s -color-accent-emphasis, named once on .root (Editora’s -focus-ring) and drawn by the :focus-visible block in the app stylesheet (KBD-16), at 3:1 or better on every surface: the default, subtle, inset and overlay grounds of the two themes ICON-09 names (see Keyboard first). A test holds it.
ICON-13SHOULD
A state color the AtlantaFX theme has no role for (Editora’s Git olive and violet) is a ladder() of -color-bg-default, never one fixed hex for light themes and another for dark. Brace, the periwinkle, is ICON-06.
ICON-14SHOULD
The contrast tests are pure: they read the stylesheets and do the WCAG arithmetic without starting the toolkit, so they run with the unit tests on every OS.
Themes
ICON-15MUST
The app has light and dark themes and switches between them at run time, without a restart.
ICON-16MUST
The theme setting offers “follow the system”: a choice that applies the light or dark theme to match the system’s color scheme, and changes with it.
ICON-17MUST
A theme name the app does not know falls back to the first-run default theme.
ICON-18SHOULD
The state colors never decorate: in every theme amber means “not durable yet”, a warning (WIN-01 requires a warning in the echo area in amber) or an update available in About (ABOUT-10 asks for it there), red “broken” and green “verified”, and nothing is colored amber, red or green for any other reason. A theme may change the accent, the ground and the ink, never these meanings.
Icons
ICON-19MUST
In an app whose icons come in two families, one colored by its stroke and one by its fill, a glyph node carries the style class of one family, never both (Editora’s two are icon-line and toolbar-icon). An app with one icon family, or with no icons in its window, has nothing to mix.
ICON-20MUST
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.
ICON-23SHOULD
In an app that shows files with an icon each (a project tree, file tabs, a list of files), 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.
ICON-24MUST
Every glyph set and font the app ships is credited in NOTICE with its license.

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.

PropertyValueReference
UI familyInter, in four faces, bundled in the app’s resources and registered before any CSS is appliedFonts.UI, Fonts.loadForFirstPaint, resources/com/editora/fonts/inter/
Root size14 px at the default zoom, the AtlantaFX theme’s root size, scaled by the UI zoom (WIN-12); a popup sets its own size from that one value, so an owner’s font never leaks into it (MENU-16)MainMenuBar.UI_FONT_SIZE
How it is attachedA scene stylesheet (ui-font.css, one .root rule whose -fx-font-family names Inter) on every window’s scene, dialogs and popups includedApp.installUiFont
MonospaceJetBrains Mono by default; Cascadia Code, Fira Code, IBM Plex Mono and Source Code Pro are bundled as editor choicesFonts.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): every window’s scene gets the font sheet (Editora’s ui-font.css): a listener on Window.getWindows() adds it to each window’s scene, and to a new scene when the window’s scene changes, or every window and dialog the app builds adds it itself, none left out. A popup or a tooltip needs no call of its own: when JavaFX shows one, it gives it the scene stylesheets of the window it is shown from (PopupWindow.applyStylesheetFromOwner). No .root rule in the app stylesheet (Editora’s app.css) sets -fx-font-family.
    • Reference: Editora App.installUiFont, a listener on Window.getWindows(), and styles/ui-font.css; the app template’s ui/Themes.java (installUiFont, hookUiFont) and Mirada’s ui/Fonts.java (installSheet) do the same. Termina and Torrenta carry the same sheet with no listener: each window and dialog adds it by calling Fonts.installUiFont, about forty times in Torrenta. Termina doesn’t meet the rule yet: its helper is called for seven windows and ui/Confirm.java adds the sheet to its questions, but four dialogs get none: the two alerts and the rename-tab TextInputDialog built in ui/TerminalWindow.java, and the TextInputDialog in ui/SettingsWindow.java. Modula doesn’t yet: the .root rule of its modula.css sets IBM Plex Mono for the whole window.
  • 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-Italic and Inter-BoldItalic .ttf are under the app’s fonts/inter/ with their OFL.txt, and Font.loadFont runs on them before the first window is shown.
    • Reference: Editora src/main/resources/com/editora/fonts/inter/, ui/Fonts.java (loadForFirstPaint, called from App). Termina and Torrenta bundle the same four faces. Modula doesn’t yet: its fonts/ holds IBM Plex Mono only.

Modula sets everything in IBM Plex Mono today. Its readings may stay monospace, as content; Inter on its menus, settings and dialogs is a gap (Gaps per app).

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.

LightDarkToken
Ground#ffffff#1b1e2a-color-bg-default
Porcelain / Abyss#f4f5f9#12141d-color-bg-subtle / -color-bg-inset
Ink#1b1e2a#e8eaf3-color-fg-default
Muted ink#575d6e#9ba1b5-color-fg-muted
Subtle ink#8b91a3#6c7288-color-fg-subtle
Caret#0e8577#43dec5-color-accent-emphasis
Caret, as text#0d786b#43dec5-color-accent-fg
Amber#8d6309#e3a93c-color-warning-fg
Red#c03434#ee7a6e-color-danger-fg
Green#2c784c#5bc98a-color-success-fg
Brace#3c4380#b8bee5-state-key (a ladder of the ground)
  • ICON-04 SHOULD A theme file follows the vendored AtlantaFX community themes: a .root block of -color-* tokens, then component rules that reference only those tokens.
  • ICON-05 SHOULD A new app ships the Caret & Ink pair as its default theme, with editora-light.css and editora-dark.css copied unchanged into its own styles/.
    • Why: the palette is the family’s, not the editor’s.
    • Check (code): the app’s two files are identical to Editora’s.
    • Reference: Termina styles/ and the app template’s styles/, whose two files match Editora’s. Torrenta’s editora-dark.css matches too; its editora-light.css still has the earlier -color-accent-fg, -color-warning-fg and -color-success-fg, which Editora has since darkened.
  • ICON-06 SHOULD Brace, the palette’s periwinkle for the keyboard (chord chips, the menus’ chord column), is one token on .root (Editora’s -state-key): a ladder() over -color-bg-default that 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 (code): the token is a ladder() of -color-bg-default, and the color it resolves to on each bundled theme’s default and subtle grounds is 4.5:1 or more against that ground. A contrast test that resolves the ladder against every bundled theme’s grounds is the surest evidence.
    • Reference: Editora app.css (.root), StyleContrastTest.theKeyboardPeriwinkleReadsOnEveryBundledAppTheme.

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.

TokenChains toMeaningWhere it appears
-state-amber-color-warning-fgNot durable yet, a warning, or an update available in AboutAn unsaved tab, a read-only file, a narrowed view, a snapshot build; warnings in the echo area and the Message Log; “Update available” in About (ABOUT-10)
-state-red-color-danger-fgBrokenErrors in the echo area and the Message Log, breakpoints, a recording
-state-green-color-success-fgVerifiedFound, added, passing, running
-state-accent-color-accent-fgThe app is offering somethingAn update, a link, the current branch, a selected row’s bar
-state-olive, -state-violetA ladder of the groundGit only: untracked, renamedThe Project tree and tabs, the Map’s structure columns
-state-keyA ladder of the groundThe keyboard, and nothing elseChord chips, the menu chord column, brace matching
-state-sel-color-accent-subtleThe selected overlay rowThe 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 token on .root (Editora’s -state-*) that chains to one of the theme’s roles (or a ladder() of its ground), and component rules use the token.
    • Check (code): each state color has one token (Editora’s -state-*), declared once, in a .root block of the app stylesheet, as a -color-* role or a ladder() of the ground. A component rule that colors one of those states uses the token: none names the role behind it (-color-danger-fg for an error) or writes the ladder out again.
    • Reference: the app template’s styles/app.css (.root), held by StyleContrastTest (theStateTokensAreDeclaredOnceAtTheTopAndChainToARole, and severityColorsComeFromTheStateTokens, which fails a component rule that names a danger, warning or success role). Termina meets it too: its styles/app.css declares -state-red, -state-amber and -state-green on .root, and no component rule of its stylesheets names the role behind one. The other five apps don’t yet. Editora’s styles/app.css declares its tokens the same way (.root), but Editora doesn’t hold the last clause: 79 declarations in that file’s component rules name -color-danger-fg, -color-warning-fg or -color-success-fg directly, errors among them (.crontab-error, .md-math-error). Torrenta’s tokens are on .root too (-torrenta-*), and two of its component rules write out the ladder of -torrenta-up again (styles/app.css, .speed-graph-up, .speed-graph-legend-up). Torrenta doesn’t hold the last clause either: 24 declarations in that file’s component rules and five in add-dialog.css name -color-danger-fg, -color-warning-fg or -color-success-fg directly (.port-dot.port-down, .add-fetch-failed), not the -torrenta-error, -torrenta-stall and -torrenta-done tokens that chain to them. Mirada and nux have no token for a state (Mirada’s one -state-* token is -state-key, the keyboard’s): Mirada’s styles/mirada.css redefines the roles themselves on .root, as ladders, and four of its component rules name -color-danger-fg or -color-warning-fg (.status-echo-error, .status-echo-warn and the Message Log’s two); nux’s nux.css has no .root block, and three of its rules name -color-warning-fg or -color-danger-fg (.on-battery-note, .settings-problem, .detail-warn). Modula’s modula.css has tokens its rules use (-lock, -fault), set as fixed hexes on .root and again on .root.daylight, chained to no role.
  • ICON-08 MUST App stylesheets take their colors from AtlantaFX -color-* tokens, or from tokens the app builds on them; no component rule carries a fixed color, whatever its spelling: a hex, an rgb(), rgba() or hsb() value, or a named color such as white. A fixed color may stand only in a token’s definition, on .root or in a scoped block that sets -color-* tokens, and only where the theme has no role to build on: a scrim’s or a shadow’s color, a color drawn over an image or a canvas and not on the theme’s ground, or a color inside a ladder() of the ground (ICON-13). The ground, ink or accent of the app’s own windows given there as a fixed color, in place of the theme’s role, fails this rule; a state color given so is ICON-07’s failure and is not counted here again. transparent is not a color.
    • Why: a fixed color suits one theme; the roles track every theme for free.
    • Check (code): every color in a component rule of the app’s stylesheets is an AtlantaFX -color-* role or a token, and a fixed color stands only where a token is defined, in a .root block or in a scoped block that sets -color-* tokens: as the plain value of a token for a scrim, a shadow or what is drawn over an image or a canvas (an rgba() of black, say), or inside a ladder() of the ground. A token for the ground, ink or accent of the app’s own windows whose value is a fixed color and no role fails; a state color’s token with no role behind it is ICON-07’s to judge, not this rule’s. A fixed color is a hex (grep -nE '#[0-9a-fA-F]{3,8}\b' over those stylesheets lists them), an rgb(), rgba(), hsb() or hsba() value, or a named color such as white; transparent is not one. No component rule holds one, whichever property it sets (a -fx-*-color, a -fx-fill, an effect’s color), inside a ladder() or not. A test that fails a fixed color outside the token block is the surest evidence.
    • Reference: Termina’s AppCssColorsTest (componentRulesUseTokensNotLiteralColours) and Mirada’s StyleContrastTest (noRuleAfterTheTokenBlockHoldsAFixedColour) fail a fixed color outside the .root block: a hex, an rgb() or an hsb() value, a shadow’s color included, and in Mirada’s a named color too. Both apps keep the scrim behind an overlay and their shadows’ colors as tokens on .root, and so does the app template: -scrim and -shadow on .root in its styles/app.css, used by .overlay-backdrop and the cards’ shadows, with no test that holds it. Editora’s StyleContrastTest.severityAndDebugColoursComeFromTheStateTokens holds six selectors it names, and Editora doesn’t yet pass the whole check: .breakpoint-marker, .debug-menu-logpoint, .exec-arrow, .view-mode-bar, .recent-remove, .personal-note-tooltip-content, the fold-gutter markers and the default editor and Markdown preview palettes in app.css still carry fixed hexes, other rules an rgba() (the scrim of .overlay-backdrop, the diff and merge tints and shadows among them), and .breakpoint-condition-mark a fixed white. Torrenta doesn’t either: .speed-graph-up and .speed-graph-legend-up in its styles/app.css hold a ladder of two hexes, and .palette-backdrop and two shadows an rgba(). Modula and nux write the palette’s scrim as an rgba() background in a component rule, and a shadow’s color the same way (.palette-backdrop and .palette-card in modula.css and nux.css), so neither meets the rule yet; nux also sets -fx-text-fill: white on .status-pill and .update-badge.
  • ICON-09 MUST Readable text uses -color-fg-muted or stronger, which is 4.5:1 on the default, subtle and overlay grounds in both flagship themes, Editora Light and Editora Dark: a line of UI text is -color-fg-default and secondary text -color-fg-muted. -color-fg-subtle (2.7:1 to 3.9:1, under 3:1 on Editora Light’s subtle and inset grounds) is for disabled or decorative text only. An app whose default light and dark themes are another pair is held to the same on that pair. A test holds it.
    • Check (test): a contrast test computes muted ink on the default, subtle and overlay grounds of both flagship themes (Editora Light and Editora Dark), or of the app’s own default light and dark themes where it ships another pair, and finds 4.5:1 or more; and it walks every rule of the app’s stylesheets: it fails a rule that sets a text fill (-fx-text-fill, or -fx-fill on text) to -color-fg-subtle unless its selector is on a list the test names, of disabled and decorative selectors only. A test that checks a list of readable selectors instead passes every selector it doesn’t name.
    • Reference: only the app template’s test walks every rule. Editora’s StyleContrastTest.textThatMustBeReadUsesTheMutedRoleNotSubtle computes the ratios and checks six selectors it names (the palette’s and the switcher’s hints, an unbound shortcut, the line numbers of the notes and structure trees, the blame date), so it passes while .encryption-locked-hint and .pom-version-unknown in app.css set text a person reads in -color-fg-subtle. The app template’s test of the same name (StyleContrastTest) walks every rule of its app.css and both themes and fails a text fill in -color-fg-subtle on any selector but the disabled and decorative ones it lists (SUBTLE_TEXT), and computes the muted role’s ratio on the grounds of both themes. Mirada’s StyleContrastTest has no test for this rule, and Termina, Torrenta, Modula and nux have no contrast test of their stylesheets.
  • ICON-10 MUST Text in a role’s tint (the theme’s -color-<role>-fg, for the accent, success, warning and danger roles) reaches 4.5:1 on that role’s subtle fill (-color-<role>-subtle) and on the default and subtle grounds (-color-bg-default, -color-bg-subtle), in both flagship themes, Editora Light and Editora Dark, or, in an app whose default light and dark themes are another pair, in that pair. A test holds it.
    • Check (test): a contrast test computes each role’s -fg on its -subtle, on -color-bg-subtle and on -color-bg-default, in both flagship themes (Editora Light and Editora Dark), or in the app’s own default light and dark themes where it ships another pair, and finds 4.5:1 or more.
    • Reference: Editora StyleContrastTest.lightTintedTextReachesAaOnItsOwnGroundAndOnTheSubtleSurface, darkTintedTextStaysAa. Mirada’s StyleContrastTest (tintedTextReachesAaOnItsOwnFillAndOnBothGrounds) holds it on Cupertino Light and Cupertino Dark, the pair it ships.
  • ICON-11 MUST Ink on an emphasis fill is -color-fg-emphasis, never a fixed white: the token is white in the light themes and a dark ink in the dark ones, 4.5:1 or more on the emphasis fill of the accent, success, warning and danger roles in the two themes ICON-09 names. A test holds it.
    • Why: white on the dark accent is 1.68:1.
    • Check (test): a contrast test computes -color-fg-emphasis on the -emphasis fill of the accent, success, warning and danger roles, in both flagship themes (Editora Light and Editora Dark) or in the app’s own default light and dark themes where it ships another pair, and finds 4.5:1 or more; and the rules that paint on an emphasis fill use it.
    • Reference: Editora StyleContrastTest.inkOnAnEmphasisFillIsTheThemesOnEmphasisColour, and Mirada’s test of the same name (StyleContrastTest), on Cupertino Light and Cupertino Dark: each holds 4.5:1.
  • ICON-12 MUST One focus ring color, the theme’s -color-accent-emphasis, named once on .root (Editora’s -focus-ring) and drawn by the :focus-visible block in the app stylesheet (KBD-16), at 3:1 or better on every surface: the default, subtle, inset and overlay grounds of the two themes ICON-09 names (see Keyboard first). A test holds it.
    • Check (test): a test reads the ring’s token from .root (Editora’s -focus-ring) and computes it on the default, subtle, inset and overlay grounds of both flagship themes (Editora Light and Editora Dark), or of the app’s own default light and dark themes where it ships another pair, and finds 3:1 or more.
    • Reference: Editora app.css (Keyboard focus), StyleContrastTest.theFocusRingIsAtLeastThreeToOneOnEverySurface.
  • ICON-13 SHOULD A state color the AtlantaFX theme has no role for (Editora’s Git olive and violet) is a ladder() of -color-bg-default, never one fixed hex for light themes and another for dark. Brace, the periwinkle, is ICON-06.
    • Why: the old fixed light hexes read at 3.2:1 on Editora Dark.
    • Check (code): each such token is declared as a ladder() of -color-bg-default; none is a fixed hex, or a pair of hexes switched by theme. A contrast test that resolves each ladder on every bundled theme’s ground is the surest evidence.
    • Reference: Editora app.css (-state-olive, -state-violet, -state-key), StyleContrastTest.theGitOliveAndVioletFollowTheAppThemesGround.
  • ICON-14 SHOULD The contrast tests are pure: they read the stylesheets and do the WCAG arithmetic without starting the toolkit, so they run with the unit tests on every OS.
    • Why: a test that starts the toolkit is an FX test, tagged and run apart from the unit tests (QUAL-06); a pure one fails the plain unit run on every OS, the first time a color changes.
    • Check (code): every test class that computes a contrast ratio reads the app’s .css resources as text and starts no toolkit: none is an FX test.
    • Reference: the app template’s StyleContrastTest and Mirada’s StyleContrastTest: each reads the stylesheets as text and uses javafx.scene.paint.Color for the arithmetic alone. The template’s key color is held there too (theKeyColorReadsOnBothThemesGrounds), and no FX test of its computes a contrast. Mirada’s AccentTest is pure too, over the accent it derives from the system’s, and so is Termina’s ThemeTest, which holds the colors of its terminal schemes and not the chrome’s stylesheet. Editora’s StyleContrastTest is pure as well, but Editora doesn’t meet the rule yet: FX tests compute contrast ratios on rendered nodes too, ChordChipThemeFxTest, DebugValuePopupThemeFxTest and SettingsFrameFxTest among them.
  • ICON-15 MUST The app has light and dark themes and switches between them at run time, without a restart.
    • Check (code): the app has a light theme and a dark one, and picking a theme calls Application.setUserAgentStylesheet in the running app.
    • Reference: Editora ui/Themes.java (applyAppTheme).
  • ICON-16 MUST The theme setting offers “follow the system”: a choice that applies the light or dark theme to match the system’s color scheme, and changes with it.
  • 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 to Themes.DEFAULT (Editora Light).
  • ICON-18 SHOULD The state colors never decorate: in every theme amber means “not durable yet”, a warning (WIN-01 requires a warning in the echo area in amber) or an update available in About (ABOUT-10 asks for it there), red “broken” and green “verified”, and nothing is colored amber, red or green for any other reason. A theme may change the accent, the ground and the ink, never these meanings.
    • Check (code): every rule that uses the amber, red or green state token (Editora’s -state-amber, -state-red and -state-green) marks one of the meanings in the table under State colors.
    • Reference: Editora app.css.

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.

Editora's Settings page for themes and fonts
Editora's Settings, Appearance: the app theme and the editor theme both on Editora Light, the editor's font and size, and a live preview.

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.

PropertyLine familyFilled familyReference
SourceThe UI Kit’s 16-unit outline glyphs, drawn for the kitMaterial Design 24 dp single-path glyphs (Apache-2.0), plus Simple Icons brand marks (CC0)Icons.line, Icons.of, NOTICE
Style classicon-linetoolbar-iconapp.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 familyThe same.button:hover .icon-line, .button:hover .toolbar-icon
Drawn size16 × 1.2 = 19.2 px (LINE_SCALE = ICON_SCALE × 24 ÷ 16)24 × 0.8 = 19.2 px (ICON_SCALE)Icons
Used forThe chrome the kit draws: toolbar, tool stripe, tabs, and every action that has a kit glyphEverything the kit specifies no glyph for: file types, context-menu rows, build-tool and browser brand marksIcons, FileIcons
  • ICON-19 MUST In an app whose icons come in two families, one colored by its stroke and one by its fill, a glyph node carries the style class of one family, never both (Editora’s two are icon-line and toolbar-icon). An app with one icon family, or with no icons in its window, has nothing to mix.
    • Why: a line glyph is colored by its stroke, and any X .toolbar-icon fill rule (there are dozens) would paint its outline solid. A glyph that moves family moves its CSS with it.
    • Check (code): the method that builds a line glyph adds the line family’s class alone, the one that builds a filled glyph adds the filled family’s alone (Editora’s Icons.line and Icons.of), and no other code adds the second class to a glyph node. A test that builds every glyph and fails when one carries both classes is the surest evidence.
    • Reference: Editora ui/Icons.java (line, of) and editor/MenuIcons.java, whose glyphs MenuIconFamilyFxTest.aLineGlyphIsNeverAlsoTaggedAsAFilledOne holds. Torrenta’s IconsTest (everyGlyphIsAStyledScaledPath) builds every glyph and fails one that carries both classes or neither. Termina, Mirada and Modula draw one family each.
  • 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 (code): wherever an action is drawn (a toolbar button, a menu row, a tab’s menu), its glyph comes from one icon class or one lookup keyed by the command. Where a second icon class holds a copy of its own, the copy has the same path data and style class. A test that compares the path data and style class of each action’s glyph across the icon classes is the surest evidence. An app that draws no glyph anywhere has nothing to compare and passes.
    • Reference: Editora ui/MenuBarIcons.java reuses Icons; editor/MenuIcons.java (the editor package may not depend on ui) copies each twin’s family and path data verbatim, held by MenuIconFamilyFxTest.everySharedActionUsesTheSameGlyphInBothIconSets. Mirada gives a command’s menu row and its button one glyph from one lookup (ui/Icons.java, forCommand).
  • ICON-23 SHOULD In an app that shows files with an icon each (a project tree, file tabs, a list of files), 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, forFileName turns 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 NOTICE with its license.
    • Check (code): each icon source named in the icon classes and each family under fonts/ has an entry in NOTICE. An app that ships no glyph set and no font has nothing to credit here.
    • 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.

An icon-only control gets its tooltip and its accessible name from one helper (Icons.button, Icons.toolbarButton, Icons.name): TBAR-01.

AppIconsSize
EditoraBoth families, ui/Icons, FileIcons, MenuBarIcons, editor/MenuIcons19.2 px on the toolbar and in menus
TorrentaBoth 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
TerminaMaterial 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
MiradaHand-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-default16 px, centered in a 16 px box
ModulaGlyphs: the transport symbols (tune, seek, star) as shapes, because the characters are missing from most faces and render differently on every platform11 px
nuxNo in-window icons; the tray icon is rendered as a bitmap by severity (TrayIconRenderer)Tray only

Pauta 6.1.0 · · Changelog · This page in the latest edition