Skip to content
Pauta6.0.1

Toolbars and tooltips

A toolbar is a bar of icon-only buttons in a window’s chrome, the fast path to commands that are also in the menus and the Command Palette: nothing lives only on it. Every button is a command, so its icon, title and chord come from the registry and the active keymap. The toolbar says which bars count as one. Reference: Editora’s ui/Icons.java (button, toolbarButton, name), ui/ToolbarCoordinator.java (the customizable bar), ui/WindowChromeCoordinator.java (collapseToolbarSeparators), ui/ToolWindowManager.java (the tool window stripes) and the .tool-bar, .toolbar-button, .tool-stripe-button and .tooltip rules in app.css.

Rules on this page 17
IDLevelRule
Rules
TBAR-01MUST
Every icon-only button, one that shows a glyph or a symbol such as ”?” or ”···” and no word, has a name: one helper sets its tooltip and its accessible text from the same string, the chord included where the tooltip carries one (TBAR-03), so a screen reader says what a sighted user reads.
TBAR-03MUST
The tooltip of a button that runs a command names the command and its chord, read from the active keymap and never typed into a string: “Save (C-x C-s)”. The name is the command’s title (KBD-03), which a tooltip may show without its category prefix, as a menu row may (MENU-01): “Save” for “File: Save”. An unbound command shows its title alone.
TBAR-14SHOULD
Every tooltip shows after the same delay, 400 ms, set where the app makes its tooltips and not tooltip by tooltip.
TBAR-06SHOULD
The bars an app stacks at the top of its main window are one chrome band: whichever of the menu bar, the toolbar and the tab strip it has share -color-bg-subtle and draw no hairline between them. The bars it stacks at the bottom, whichever of a breadcrumb, a bottom stripe and the status bar it has, do the same. An app with one bar at an edge has nothing to join there.
The toolbar
TBAR-02MUST
Toolbar buttons stay out of the Tab order: the command, the palette and the menus reach the action, and Tab is for the content. The keyboard page has the general focus rules.
TBAR-04SHOULD
A toolbar’s groups of buttons are separated by spacing, not rules: where a toolbar holds Separator nodes, keep them (their padding is the gap) and make the line transparent.
TBAR-05SHOULD
Hiding a button group (Simple mode, a build tool that is not detected) hides the leading, trailing and doubled separators it leaves, so no gap stands on its own, and shows them all again when nothing is hidden.
TBAR-07SHOULD
A toggle looks on while it is on: a button that opens an overlay (Find, the palette, a split) and the Simple mode button carry a pseudo-class (Editora’s :open) while their state holds, so the way back out does not look like the way in.
TBAR-08MUST
A toolbar never holds the only way to an action: every icon on it (in Editora, every icon of the cluster the user can customize) is also in the menus and the palette.
TBAR-09MAY
The toolbar is customizable: the user reorders, removes and restores its buttons, and the layout is saved in Settings and shared by every window.
The main toolbar
TBAR-15SHOULD
The main toolbar’s icon cluster and its pinned tail (Settings and the other controls the user must always reach) are separate containers: when the window narrows, the cluster’s icons go into the overflow chevron and the tail keeps every control.
TBAR-16SHOULD
Settings closes the main toolbar at its right end, with the Simple mode toggle just before it in an app that has Simple mode, whether the mode is on or off.
TBAR-17SHOULD
A main toolbar button is disabled while its command can’t act (Save on a saved file, Undo with nothing to undo, Cut and Copy with no selection, a split on a tab that can’t be split), and the events that change that state update it; nothing polls. KBD-04 has the same state in the menus and the palette.
TBAR-18SHOULD
A command hides the main toolbar and shows it again, and the choice is kept across launches.
TBAR-19SHOULD
The main toolbar keeps its height when a control in it hides or shows (in Editora, the project switcher in Simple mode or with Projects off), so the tabs and the content under it never move.
Tool window stripes
TBAR-12SHOULD
A tool window stripe button takes its name from its tool window: the name its tooltip shows (TBAR-03) is the window’s title, with the chord of the command that toggles the window, and it follows the title when the title changes. The button’s right-click menu has Open in Split and Hide.
TBAR-13SHOULD
The right stripe’s first icon lines up with the editor’s first line of text, not with the tab strip.
  1. 1Icon button, 28 px: padding 3 × 5, radius 4, no border, the glyph in -color-fg-muted and -color-fg-default under the pointer. It has a name even though it shows none: the same string is its tooltip and its accessible text.
  2. 2Group gap. A vertical Separator node whose line is transparent: its padding is what separates the groups. No drawn rule.
  3. 3Tooltip. The command's title and its chord in the active keymap, "Save (C-x C-s)". A popup window with the menus' radius 8.
  4. 4Open toggle. A button whose overlay is showing (Find, the palette, a split) wears :open: an accent-subtle fill and the glyph in the accent color. Simple mode's own button does the same while the mode is on.
  5. 5One band. The menu bar, the toolbar and the tab strip sit on -color-bg-subtle with no hairline between them; spacing does the grouping.
  6. 6Pinned tail. The run configuration controls, the project picker, the Simple mode toggle and Settings live in their own container beside the ToolBar, so a narrow window overflows the icons (which are all in the menus too) and never the tail.
PropertyValueReference
Button28 px high: padding 3 × 5, radius 4, style classes button-icon flat toolbar-button; every control on the bar is pinned to 28 px, combos and menu buttons included.toolbar-button, .tool-bar .combo-box-base
BarPadding 5 1 2 6 (asymmetric: the tab strip below adds its own inset); 18 px font for the bar’s own labels, controls inside it at 14 px; -color-bg-subtle, no rule above or below.tool-bar, .menu-bar, .tool-bar
IconThe command’s glyph, 17 px drawn (Torrenta) or a kit glyph at the toolbar scale (Editora); -color-fg-muted, -color-fg-default on hover, -color-accent-fg while :openIcons, .toolbar-icon, .icon-line, .button:open
Group gapA vertical Separator with its line transparent; its 0.75 em padding is the gap.tool-bar .separator:vertical > .line
TailIts own container (.toolbar-tail), same insets and font as the bar, never overflowedToolbarOverflowFxTest
Run controlsThe run configuration combo, then Run, Debug and Stop, the bar’s only state colors: the glyph in -state-green, -state-accent and -state-red; hidden in Simple mode and while there is nothing to launch.run-config-play, .run-config-bug, .run-config-stop, RunConfigToolbar.visible
Tail gapsBlank Regions, no separators: 78 px (about three icons) before the project switcher, 40 px before Simple mode and Settings, 14 px before a badgeWindowToolbar.appendFixedTail
Tooltip<title> (<chord>), the chord from KeymapManager.displayChord; only the title when unbound; radius 8 like the menusToolbarCoordinator.buildExtraButton, ToolWindowManager.tooltipFor, .tooltip
Stripe buttonA toolbar button on the tool window rail: min 24 px, padding 9 × 5, radius 6, 8 px apart on a 30 px rail; the same muted, hover and :open colors; the bottom stripe adds a 14 px label.tool-stripe-button, ToolWindowManager.register
Customize modeThe bar tinted -color-accent-subtle, a move cursor, the dragged button at 0.4 opacity, a 2 px accent insertion line on the drop target’s edge.tool-bar.toolbar-customizing, .toolbar-drop-before
  • TBAR-01 MUST Every icon-only button, one that shows a glyph or a symbol such as ”?” or ”···” and no word, has a name: one helper sets its tooltip and its accessible text from the same string, the chord included where the tooltip carries one (TBAR-03), so a screen reader says what a sighted user reads.
    • Why: a hand-rolled button gets the tooltip and forgets the name, which is how Editora once had seven copies of the helper drifting apart, and how a screen reader comes to announce “button”.
    • Check (code): every icon-only button gets its tooltip and its accessible text in one call that sets both from one string (Editora’s Icons.button, Icons.toolbarButton and Icons.name). A button with a setTooltip and no setAccessibleText fails, and so does one whose tooltip is written again later, to add a chord, while its accessible text keeps the first string.
    • Reference: Editora ui/Icons.java (button, toolbarButton, name), used by its panel toolbars. Torrenta’s copy of all three (ui/Icons.java): its name is the one place Torrenta sets an accessible text, and it names every button of the main toolbar (MainWindow.toolButton) and names them again when the keys change. Termina’s ui/IconNames.java (name), which binds both to one string. Five apps don’t meet it yet. Editora sets the tooltip only on its main toolbar (WindowToolbar.setupButton and ToolbarCoordinator.buildExtraButton) and on the floating buttons that leave Zen and Expert mode and bring the toolbar back (WindowChromeCoordinator.installZenOverlay), and its stripe buttons’ accessible text is the tool window’s title without the chord the tooltip carries (ToolWindowManager.register). Torrenta’s detail pane gives its ”···” button a tooltip and no accessible text (ui/DetailPane.java). Mirada’s ui/Icons.java (button, name) makes the accessible text the command’s title and puts the chord in the tooltip only. nux’s App.java sets the tooltip and the accessible text of its ”?” button from one string, then its shortcut helper writes the tooltip again as “About Nux (F1)” and leaves the accessible text. Modula’s transport, Settings and Record buttons have a tooltip and no accessible text (ui/RadioPane.java), and so has the ”+” button of its preset row (ui/PresetBar.java).
  • TBAR-03 MUST The tooltip of a button that runs a command names the command and its chord, read from the active keymap and never typed into a string: “Save (C-x C-s)”. The name is the command’s title (KBD-03), which a tooltip may show without its category prefix, as a menu row may (MENU-01): “Save” for “File: Save”. An unbound command shows its title alone.
    • Check (code): the tooltip shows the command’s title, whole or without its category prefix, and the keymap’s display chord for its id, and is rebuilt when the keymap changes. The chord is the one of the command the button runs, and no chord is typed into the string. A fixed key of the control itself (Enter in a find field) is no command’s chord and may be written, as KBD-13 allows.
    • Reference: Editora ToolbarCoordinator.buildExtraButton (the command.<id> title, prefix and all) and ToolWindowManager.tooltipFor. Its main toolbar (WindowToolbar.setupButton, refreshToolbarTooltips) takes the chord from the keymap and the name from a tooltip.* catalog key of its own: for most buttons that is the title without its prefix (tooltip.save=Save beside command.file.save=File: Save), for six another name, which doesn’t meet the rule: “Find / Replace” for find.show, whose title is “Find: Incremental Search”; “Open” for file.find (“File: Find File…”); “Close Tab” for buffer.close (“Buffer: Close”); “Open Folder as Project…” for project.open (“Project: Open Folder…”); “New From Template” for template.new (“Template: New File From Template…”); and “Simple UI mode” for view.toggleSimpleMode (“View: Toggle Simple UI Mode”). Two more buttons miss it another way: file.clearRecent (“File: Clear Recent Files”) reads “Clear recent files”, and the pinned tail’s Stop button, which stops the run as run.stop (“Run: Stop Program”) does, is set up with no command id, so it reads “Stop the running program” and shows no chord. Torrenta’s toolbar.withChord. Mirada’s Icons.tooltip builds the same “label (key)” form with the chord from the keymap in use (Command.chord), and TitleBar.relabel names the header buttons again when the keys change; Termina’s IconNames.withChord takes the chord from its keymap too, but its find bar’s arrows don’t meet the rule yet: ui/SearchBar.java names them from search.older and search.newer, “Previous match, up (Enter)” and “Next match, down (Shift+Enter)”, not from a command’s title, and gives each arrow the chord of the command that steps the other way. The up arrow steps to an older match, as findNext does (ui/TerminalWindow.java), and shows the chord of findPrevious; the down arrow steps to a newer one, as findPrevious does, and shows the chord of findNext. The Enter and Shift+Enter in the two strings are the field’s own keys. Modula’s and nux’s tooltips are written in the code, not read from a command: Modula’s carry no chord (ui/RadioPane.java), and nux’s add the display text of a KeyCombination to the button’s label (App.java, shortcut).
  • TBAR-14 SHOULD Every tooltip shows after the same delay, 400 ms, set where the app makes its tooltips and not tooltip by tooltip.
    • Why: JavaFX waits a full second, which reads as no tooltip at all on a row of icons, and a delay set here and there makes some buttons answer faster than their neighbors.
    • Check (code): every Tooltip the app creates gets a 400 ms show delay from one place: each is made by one factory that calls setShowDelay, or the stylesheet’s .tooltip rule sets -fx-show-delay: 400ms. A tooltip made with new Tooltip outside the factory and given no delay fails, as does any other delay.
    • Reference: the app template: its styles/app.css sets -fx-show-delay: 400ms on .tooltip, and the tooltips its code makes get the same from one constant, TOOLTIP_DELAY in ui/Icons.java (bindName, and ui/TabHeaders.java for a tab’s). Termina is nearest among the apps: ui/IconNames.java (name, SHOW_DELAY) sets 400 ms on every tooltip it makes, and ui/TerminalWindow.java sets the same inline on a tab’s folder tooltip, but the tooltip on a disabled row of its ui/CommandPalette.java sets none. Editora sets 300, 350 or 400 ms on some (editor/LazyTooltip.java’s callers, ui/StructurePanel.java, ui/MapSurface.java, ui/DiffViewerPane.java) and leaves the rest at JavaFX’s second; Mirada sets 250 ms on one (ui/MarksBadge.java) and none on the others; Torrenta, Modula and nux set none. No app’s stylesheet sets -fx-show-delay.
  • TBAR-06 SHOULD The bars an app stacks at the top of its main window are one chrome band: whichever of the menu bar, the toolbar and the tab strip it has share -color-bg-subtle and draw no hairline between them. The bars it stacks at the bottom, whichever of a breadcrumb, a bottom stripe and the status bar it has, do the same. An app with one bar at an edge has nothing to join there.
    • Why: three rules within forty pixels read as clutter, not structure.
    • Check (by hand): look at the top and the bottom of the main window in a light and a dark theme for a line between two bars, or a change of ground from one to the next.
    • Reference: Editora app.css (.menu-bar, .tool-bar).

Applies to: an app with a toolbar: a bar of icon-only buttons in a window’s chrome (its title bar, a band of its own under the title bar or the menu bar, or the header of a panel), each a shortcut to a command. Editora’s and Torrenta’s ToolBar, the toolbars of Editora’s panels and Mirada’s header buttons are toolbars. So is a tool window stripe, on every side: the label its bottom buttons add to the glyph does not change what they are. These are not toolbars: a bar of labeled buttons (nux’s ToolBar, whose one icon-only button, ”?”, only TBAR-01 covers); controls that belong to the window’s content, icon-only or not (Modula’s transport and footer controls, Mirada’s controls over the image); the buttons at the end of a tab strip (Termina’s ”+” and its chevron); and a find bar’s buttons (FIND-16 is theirs). Controls that belong to the window’s content include a row of preset chips with its add button (Modula’s) and the buttons inside a panel’s rows (Mirada’s info panel), and an image, PDF or Diff viewer’s own bar in the content area (Editora’s) is content too.

  • TBAR-02 MUST Toolbar buttons stay out of the Tab order: the command, the palette and the menus reach the action, and Tab is for the content. The keyboard page has the general focus rules.
    • Check (code): every button on a toolbar is taken out of the Tab order with setFocusTraversable(false), where it is built or by the helper that builds it (Editora’s Icons.toolbarButton).
    • Reference: Editora Icons.toolbarButton, used by the toolbars of its Git and Markdown lint tool windows; Torrenta’s copy of it, which builds every button of its main toolbar (MainWindow.toolButton); Mirada’s header buttons: its Icons.button takes Rotate out of the Tab order, and ui/TitleBar.java takes Info and ☰ out where it builds them. Editora doesn’t yet, on these toolbars among others: the buttons of its main toolbar, built by WindowToolbar.setupButton and ToolbarCoordinator.buildExtraButton, the stripe buttons, the buttons of the Test Results panel’s toolbar, built by Icons.button (ui/TestRunnerPanel.java), and the float, maximize and close buttons in the header of every tool window (ui/ToolWindowPanel.java) take focus.
  • TBAR-04 SHOULD A toolbar’s groups of buttons are separated by spacing, not rules: where a toolbar holds Separator nodes, keep them (their padding is the gap) and make the line transparent.
    • Check (code): the stylesheet makes the line of every Separator on a toolbar transparent (Editora’s .tool-bar .separator:vertical > .line, a transparent border), on a panel’s toolbar as on the main one. A toolbar that holds no Separator (Mirada’s header buttons) has nothing to restyle and passes.
    • Reference: Editora app.css, for its main toolbar. Editora doesn’t meet the rule on its Debug panel’s toolbar yet: the separators there carry a class of their own, debug-toolbar-separator, whose one rule sets their padding and leaves the line drawn (ui/DebugPanel.java). Torrenta’s separators still draw a line (.main-toolbar .separator:vertical > .line in its styles/app.css).
  • TBAR-05 SHOULD Hiding a button group (Simple mode, a build tool that is not detected) hides the leading, trailing and doubled separators it leaves, so no gap stands on its own, and shows them all again when nothing is hidden.
  • TBAR-07 SHOULD A toggle looks on while it is on: a button that opens an overlay (Find, the palette, a split) and the Simple mode button carry a pseudo-class (Editora’s :open) while their state holds, so the way back out does not look like the way in.
    • Check (code): each such button sets a pseudo-class from its state, and the stylesheet gives that state a fill.
    • Reference: Editora MainController.OPEN, WindowChromeCoordinator (Simple mode), .button:open in app.css. Torrenta’s Simple mode button carries :on, which its stylesheet fills (.toolbar-button:on), but Torrenta doesn’t meet the rule yet: its palette button carries no pseudo-class while the palette shows (ui/MainWindow.java). Its :active marks the alternative speed limit on a label of the status bar, not on a toolbar button.
  • TBAR-08 MUST A toolbar never holds the only way to an action: every icon on it (in Editora, every icon of the cluster the user can customize) is also in the menus and the palette.
    • Why: that is what makes it safe to hide icons in a narrow window and to let the user remove them.
    • Check (code): every button on the toolbar runs a registered command, so the palette lists it, and a menu lists that command too: the menu bar, or the app’s main menu where it has no bar (WIN-14 says what a main menu is). A button that only opens a menu (Editora’s Recent, Mirada’s ☰) is no action of its own. In an app whose toolbar is built from a catalog (Editora’s ToolbarCatalog), every catalog item’s command id is also in the menus’ model.
    • Reference: Mirada’s header buttons, Rotate and Info, which its ☰ menu lists too (ui/TitleBar.java). Eleven of the twelve buttons of Torrenta’s toolbar run a command that a menu row runs too (MainWindow.buildToolbar), but Torrenta doesn’t meet the rule yet: the twelfth, the palette button, opens the palette from a handler of its own, as the View menu’s Command Palette row does, and no command does (PAL-01). Editora toolbar/ToolbarCatalog.java: each item carries the commandId it runs, and the only items without one are declared special widgets, such as the Recent menu button (ToolbarCatalogTest). Editora doesn’t meet the rule yet: three catalog items run commands that are in the palette and in no menu, tool.todo, tool.bookmarks and view.toggleZen, which ui/MenuBarModel.java doesn’t list.
  • TBAR-09 MAY The toolbar is customizable: the user reorders, removes and restores its buttons, and the layout is saved in Settings and shared by every window.
    • Check (code): the user can reorder the toolbar’s buttons, remove one and bring the default layout back (Editora: a customize mode in which a drag along the bar reorders its buttons and a drag off it removes one, and a menu row that restores the default); and the layout is written to the settings, which every window reads. A test that drives a reorder and a removal is the surest evidence.
    • Reference: Editora ui/ToolbarCoordinator.java, ToolbarCustomizeModeFxTest, ToolbarCustomizationFxTest. The cluster is a list of catalog ids in Settings (toolbarLayout), sanitized on read. The bar’s right-click menu offers Customize Toolbar… (or Done), Configure… (the Settings page) and Restore Default. In customize mode the bar tints, buttons drag to reorder with an accent insertion line and drag off the bar to remove; Escape leaves the mode.
  • The toolbar’s right-click menu follows the rules for every right-click menu: MENU-06 and MENU-07.

Applies to: an app with a main toolbar: a toolbar (The toolbar says what one is) that is a band of its own across the top of the main window, as Editora’s and Torrenta’s ToolBar are. Mirada’s header buttons, which share the title bar with the file’s name, are a toolbar and not a main toolbar; nux’s bar of labeled buttons is neither.

The main toolbar reads left to right in two parts. The icon cluster holds the everyday commands in groups (in Editora: file, with Recent as a menu button; edit; find; split; the palette) and is the part that gives way: a narrow window moves its last icons into the ToolBar’s overflow chevron (»). The pinned tail sits beside it in a container of its own and keeps every control at any width. Editora’s holds the run configuration selector with Run, Debug and Stop, the project switcher with Open Folder, a snapshot or dev badge when the build is one, and Simple mode and Settings at the end. A command the bar can lose to a narrow window goes in the cluster. One the user must always reach from the bar, or the way back out of a mode, goes in the tail.

  • TBAR-15 SHOULD The main toolbar’s icon cluster and its pinned tail (Settings and the other controls the user must always reach) are separate containers: when the window narrows, the cluster’s icons go into the overflow chevron and the tail keeps every control.
    • Why: a ToolBar overflows from its end, so with everything in one bar a narrow window hides Settings and the project switcher first and keeps icons that are all in the menus anyway (TBAR-08).
    • Check (code): the tail’s controls sit in a container of their own beside the ToolBar that holds the icon cluster, and are not items of that ToolBar, so its overflow cannot take them. A test that narrows the window and finds the cluster overflowing while the tail’s last control stays flush with the bar’s right edge is the surest evidence.
    • Reference: Editora WindowToolbar.appendFixedTail, ToolbarOverflowFxTest. Torrenta keeps Simple mode and Settings inside its ToolBar, after a spacer, so they are the first to overflow.
  • TBAR-16 SHOULD Settings closes the main toolbar at its right end, with the Simple mode toggle just before it in an app that has Simple mode, whether the mode is on or off.
    • Why: the same two buttons in the same place in every app, and the toggle is the way back out of a mode that empties much of the bar.
    • Check (by hand): look at the bar’s right end with Simple mode off, then on.
    • Reference: Editora WindowToolbar.appendFixedTail; Torrenta MainWindow.buildToolbar.
  • TBAR-17 SHOULD A main toolbar button is disabled while its command can’t act (Save on a saved file, Undo with nothing to undo, Cut and Copy with no selection, a split on a tab that can’t be split), and the events that change that state update it; nothing polls. KBD-04 has the same state in the menus and the palette.
    • Why: a button that does nothing when clicked reads as a broken button.
    • Check (code): each button’s disabled state is bound to its command’s availability, or refreshed from the document’s edit, selection and dirty events and on a tab switch.
    • Reference: Editora WindowToolbar.refreshEditState, refreshSplitButtons and refreshPasteState, which reads the clipboard only on a tab switch, on focus and after a copy, never on a keystroke; the buttons added from the catalog (ToolbarCoordinator.buildExtraButton) stay enabled. Torrenta MainWindow.toolButton binds each button’s disableProperty to its command’s enabled.
  • TBAR-18 SHOULD A command hides the main toolbar and shows it again, and the choice is kept across launches.
    • Check (code): a registered command toggles the bar, and the setting it writes is read back at startup.
    • Reference: Editora view.toggleToolbar (WindowChromeCoordinator.toggleToolbar), with a floating button at the top right that brings a hidden bar back; Torrenta toggle-toolbar, kept as settings.toolbar().
  • TBAR-19 SHOULD The main toolbar keeps its height when a control in it hides or shows (in Editora, the project switcher in Simple mode or with Projects off), so the tabs and the content under it never move.
    • Check (by hand): hide and show each control the bar can lose (in Editora, turn Simple mode on and off) and watch the top edge of what sits under the bar: it stays where it was.
    • Reference: Editora WindowToolbar.stabilizeToolbarHeight, which pins the row’s minimum height to the project switcher’s.

Applies to: an app with tool window stripes.

A stripe is a toolbar (The toolbar), so its buttons stay out of the Tab order (TBAR-02) and an icon-only one has its name as tooltip and accessible text (TBAR-01). These two rules add what only a stripe has.

  • TBAR-12 SHOULD A tool window stripe button takes its name from its tool window: the name its tooltip shows (TBAR-03) is the window’s title, with the chord of the command that toggles the window, and it follows the title when the title changes. The button’s right-click menu has Open in Split and Hide.
    • Check (code): the stripe button’s tooltip is built from the tool window’s title and the keymap’s display chord for the window’s command, and is built again when the title changes; the button has a right-click menu with those two rows.
    • Reference: Editora ToolWindowManager.register (the menu) and tooltipFor, which refreshTooltips runs again on a keymap switch only. Editora doesn’t meet the rule yet: a title change (the Project window becoming “Current Folder”) reaches the button’s accessible text and the bottom stripe’s label, not its tooltip.
  • TBAR-13 SHOULD The right stripe’s first icon lines up with the editor’s first line of text, not with the tab strip.
  • Editora: the customizable cluster, the pinned tail, the stripes.
  • Torrenta: the same Icons.toolbarButton and Icons.name, 32 px buttons, Simple mode as :on; its separators still draw a line, and Simple mode and Settings sit inside the ToolBar, so a narrow window overflows them first.
  • Mirada: a HeaderBar title bar with flat icon buttons around the file name, stroked symbolic icons in the text color, tooltips of the form “label (key)” with the key read from the keymap; Icons.button and Icons.name set each button’s tooltip and accessible text together, and the buttons are out of the Tab order.
  • Termina: no toolbar (the tab strip is the row under the menu bar, and the ”+” and the chevron at its end are the strip’s own buttons); its find bar’s buttons (FIND-16) are 24 × 22 flat icons, their tooltips and accessible text set from one string by ui/IconNames.java, out of the Tab order.
  • Modula: no toolbar: the transport buttons and the footer’s Settings and Record are the radio’s own controls.
  • nux: no toolbar: its JavaFX ToolBar is a bar of labeled buttons, a combo box and two menu buttons, with one icon-only button, ”?”.
  • The app template: no toolbar.
Editora editing a Java file with the project tree and status bar
Editora's toolbar: grouped icons on the chrome band, the run configurations, the project picker and Settings pinned at the right.
Mirada with its file name and folder in a HeaderBar title bar, an info panel and a thumbnail strip
Mirada's HeaderBar: flat icon buttons around the file name.

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