Tabs and tool panels
A window shows its documents in a tab strip and its tools in panels docked beside or under them. Both are
driven by commands, both remember their state, and both draw their chrome as one band with the toolbar, not as boxes
inside boxes. Reference: Editora’s ui/TabHeaders.java (the tab header), ui/ClosedTabs.java, ui/Switcher.java,
ui/ToolWindowManager.java, ui/ToolWindowPanel.java and the .tab-pane, .tool-stripe and .tool-window
rules in app.css.
- 1Active tab. Its fill is the editor's own surface (
-editor-surface) with a border on three sides and none at the bottom, so the tab opens into the editor instead of sitting on it. Title bold in-color-fg-default; the file-type glyph tints accent. - 2Unsaved tab. A
•before the name, amber (-state-amber, "not durable yet") and italic. Amber outranks the Git-status color: "you have not saved this" matters more than "this differs from HEAD". - 3Pinned tab. A pin glyph and a bold title, kept at the front of the strip in pin order. Every bulk close (Others, All, Unmodified, Left, Right) skips it.
- 4Read-only tab. Muted and italic, echoing the status bar's Read-Only segment.
- 5Drag to reorder. The header is the drag handle and a snapshot of the whole tab follows the pointer; the dragged tab dims to 40 % and a 2 px accent line marks the edge it would land on (left half of a tab: before it; right half: after).
- 6Tool stripe. A 30 px rail of icon buttons, one per tool window, 8 px apart, on the subtle ground with no drawn edge. The open window's button is tinted; the one holding keyboard focus is tinted stronger. The first icon lines up with the editor's first line of text, not with the tab strip.
- 7Panel header. The window's glyph and title (14 px bold, muted) with float, maximize and close; the same size and glyph as its stripe button, so the two name the same thing. On the subtle ground, with no rule under it; when the panel holds focus the band tints accent-subtle and the title turns accent.
- 8The divider is the edge. The panel draws no frame: the SplitPane divider between it and the editor is the real, grabbable edge, and a hairline beside it would only double it. Its position is remembered.
- 9Bottom stripe. Its buttons carry a 14 px label beside the glyph, side by side; the open one is accent and bold.
Rules on this page 21
| ID | Level | Rule |
|---|---|---|
| Window title | ||
| TABS-10 | SHOULD | The window title names the file, the project and the app, with a ● prefix for an unsaved
file. An app with no files or projects names what the window shows in their place (a terminal, the working
folder or the title its program set), or the app alone where there is nothing to name.
|
| Tabs | ||
| TABS-01 | MUST | Every tab operation is a command, so it can be bound to a chord, is in the palette and has a
menu row: close, close others, close all, close unmodified, close to the left and right, pin, reopen closed, next
and previous. The tab’s right-click menu lists the ones that act on a tab. A terminal app’s tabs
are never saved or unsaved, so a terminal app has no close unmodified, and closing its window closes all its
tabs, so it needs no close all; the other operations are its commands too.
|
| TABS-02 | MUST | The header is the title: the Tab’s own text stays empty, and a graphic header carries the
file-type glyph, the markers and the title in a label of its own (Editora’s style class for it is tab-title). The
tooltip is the full path, in which ~ may stand for the home folder. A terminal app’s tab shows no file: its header
has no file-type glyph, its title names the tab (the user’s own name for it, the title the shell set, the running
program or the working folder), and its tooltip is the working folder’s full path.
|
| TABS-03 | MUST | A tab’s header, the one graphic header of TABS-02, carries the tab’s states: a •
prefix in amber italic for unsaved, a pin and bold for pinned, muted italic for read-only. A terminal app’s tab is
never unsaved or read-only, and its header says in their place what the tab is doing: the title is the running
program’s name while one runs, unless the user or the shell named the tab, and a mark beside the title says what
happened while the tab was not selected (a notification, a bell, or output after a quiet spell), cleared when the
tab is selected. A pinned terminal tab is drawn as any other pinned tab, with a pin and a bold title.
|
| TABS-04 | MUST | Bulk close skips pinned tabs: close others, close all, close unmodified and close to the left
or right never close a pinned tab. A terminal app has three of them (TABS-01), and each skips its
pinned tabs too.
|
| TABS-05 | MUST | Pinning moves the tab to the end of the pinned group, unpinning to just after it.
|
| TABS-06 | MUST | Reopen Closed Tab brings back the files whose tabs this window closed, newest first, bounded
to twenty, a file listed once, with the caret where it was. In a terminal app the tab comes back (its shells,
their directories, the pane arrangement, the names the user gave them, its place in the strip) and not the
scrollback.
|
| TABS-07 | SHOULD | Tabs reorder by dragging, with this feedback: the dragged header dimmed and an
accent line on the edge where it will land.
|
| TABS-08 | SHOULD | In an app whose tabs hold files, a tab shows its file’s Git status in the Project tree’s
colors: modified accent, added green, untracked olive, renamed violet, deleted muted, conflict red. A read-only
tab still shows it; an unsaved one shows amber. The tab’s tooltip names the file’s Git status too, so color is
not the status’s only sign (ACC-05). A terminal app’s tabs hold no files, so the
rule passes it by.
|
| TABS-09 | SHOULD | An app whose tabs hold files has a switcher that lists the open files in tab order. A
command opens it; the arrows or the active keymap’s line chords move, Enter or releasing Ctrl (the Control key,
on macOS too) activates, Esc or the keymap’s cancel chord cancels, and Backspace, Delete or the keymap’s
delete-character chord closes the highlighted file. The switcher’s width is fixed to the longest path on each
open, so it never resizes while you move. A terminal app’s tabs hold no files, so the rule passes it by.
|
| TABS-12 | SHOULD | A command hides the tab bar.
|
| Tool panels | ||
| TABS-13 | MUST | Every tool panel has a command that shows and hides it, with the id tool.<id>, as
Editora’s tool.project is, and where the app has a stripe, the panel’s stripe button runs that command. In the
Emacs keymap, M-1 through M-9 and then M-0 run those commands, one chord to a panel: an app with fewer than
ten panels uses the first of the chords, and one with more chooses the ten panels that get them. An app with one
key table and no Emacs keymap (KBD-09) owes none of these chords.
|
| TABS-15 | SHOULD | Panel state is restored: which panels are open, where each sits and every divider position
go to the session-state file (SET-08; Editora’s is workspace-state.json) and come back
on the next launch. In an app with tool window stripes that includes each window’s side
and order, the stripe buttons the user hid, and the windows that float.
|
| TABS-19 | SHOULD | Closing the panel that holds keyboard focus returns focus to where it was in the content
(in Editora, the editor).
|
| Tool window stripes | ||
| TABS-16 | SHOULD | Tool windows dock on three sides, left, right and bottom, and a side holds at most two
windows stacked (Project over Structure, two consoles along the bottom).
|
| TABS-17 | SHOULD | A tool window re-docks by dragging its stripe button to another stripe, with the same
dim-and-accent-line feedback as a tab; an empty stripe appears as a dashed accent drop zone for the duration of
the drag.
|
| TABS-18 | SHOULD | Tool windows float, maximize, resize and close from the keyboard, and at most one window is
maximized at a time.
|
| TABS-20 | SHOULD | Hidden is not unavailable: the user’s show/hide choice for a stripe button is kept apart
from a context-driven hide (the Commit window outside a Git repository), so the second never clobbers the first.
|
| TABS-21 | SHOULD | A tool window whose content needs more room than the default share of its side can ask for
more on its first open (Editora’s Debug window asks for 42 %); the user’s own size wins afterwards.
|
| TABS-22 | SHOULD | A stripe button badges a spinner while its window has something under way.
|
| TABS-23 | SHOULD | Tool windows follow the active document where they should: the Git UI follows the active
tab’s repository, the status bar’s environment segment the active .http file, Local History the file whose tab
menu opened it.
|
Window title
Section titled “Window title”- TABS-10 SHOULD The window title names the file, the project and the app, with a
●prefix for an unsaved file. An app with no files or projects names what the window shows in their place (a terminal, the working folder or the title its program set), or the app alone where there is nothing to name.- Check (code): the code that sets the stage title adds all three and the marker; in an app with no files or projects, what stands in for them, or the app’s name alone.
- Reference: Editora
MainController.updateWindowTitle. Termina’s title follows the selected tab (TerminalTitle.window: the name the user gave the tab, the title the shell set or the working folder’s path, and the app’s name when it knows none). The app template names the file, its sample project and the app, with the●prefix (windowTitleinui/DocumentTabs.java;TabsAndPanelsTest,theWindowTitleNamesTheFileTheProjectAndTheApp). Modula and nux show the app’s name.
Applies to: an app whose main window holds documents or sessions in tabs the user opens and closes, as
Editora’s files and Termina’s terminals are. The pages of a Settings window (nux’s TabPane), the fixed sections
of a detail pane (Torrenta’s) and a strip that switches the window between views (Torrenta’s Transfers, Search and
RSS) are not such tabs: the user neither opens nor closes them. The Tabs rules cover every tab of the main window’s
strip, whatever it shows (Editora’s image, hex and PDF viewer tabs as much as its editor tabs), not tabs inside a
tool window (those of Editora’s Terminal and Build Output panels).
- TABS-01 MUST Every tab operation is a command, so it can be bound to a chord, is in the palette and has a
menu row: close, close others, close all, close unmodified, close to the left and right, pin, reopen closed, next
and previous. The tab’s right-click menu lists the ones that act on a tab. A terminal app’s tabs
are never saved or unsaved, so a terminal app has no close unmodified, and closing its window closes all its
tabs, so it needs no close all; the other operations are its commands too.
- Check (code): the registry holds a command for each operation, each has a row in the menu bar or in the
tab’s right-click menu, and that menu (Editora’s
TabContextMenu), on every tab of the strip, lists the ones that act on a tab; in a terminal app, each operation but close unmodified and close all. - Reference: Editora
ui/WindowCommandRegistrar.java(buffer.close,buffer.closeOthers,buffer.closeAll,buffer.closeUnmodified,buffer.closeLeft,buffer.closeRight,buffer.togglePin,buffer.reopenClosed,buffer.next),ui/TabContextMenu.java. Editora has no previous-tab command yet, and its image, hex and PDF viewer tabs have no right-click menu:openImageTab,openHexTabandopenPdfTabinui/FileWorkflowCoordinator.javainstall none, andinstallTabMenuinui/MainController.javais called for an editor’s tab alone. Terminaui/TerminalWindow.java(closeTab,closeOtherTabs,closeTabsToTheLeft,closeTabsToTheRight,pinTab,reopenClosedTab,nextTabandpreviousTabinmenuCommands; the tab’s menu inbuildTabMenu). Its File menu closes the tab, the others, the ones to either side, or the window, which is its close all (ui/MenuBarModel.java).
- Check (code): the registry holds a command for each operation, each has a row in the menu bar or in the
tab’s right-click menu, and that menu (Editora’s
- TABS-02 MUST The header is the title: the Tab’s own text stays empty, and a graphic header carries the
file-type glyph, the markers and the title in a label of its own (Editora’s style class for it is
tab-title). The tooltip is the full path, in which~may stand for the home folder. A terminal app’s tab shows no file: its header has no file-type glyph, its title names the tab (the user’s own name for it, the title the shell set, the running program or the working folder), and its tooltip is the working folder’s full path.- Why: the graphic is what makes the header a drag handle and lets each state set its own color.
- Check (code): every tab that shows a file, an editor’s or a viewer’s, gets
setText("")and a graphic that holds the file-type glyph and the title in a label of its own (Editora’s.tab-title); its tooltip is the file’s path. In a terminal app: every tab’s own text is empty, its graphic holds the title label and no file-type glyph, and the tooltip is the working folder of the tab’s active pane. A path that writes the home folder as~is a full path. - Reference: Editora
ui/TabHeaders.java, for its editor tabs (bufferHeader,tooltip). Its image, hex and PDF viewer tabs don’t yet:contentHeader, which builds their header, sets no tooltip. TerminaTerminalWindow.addTab(atab-titlelabel as the tab’s graphic, andinstallDirectoryTooltip) overui/TerminalTitle.java(tab, andtooltip, which writes the home folder as~).
- TABS-03 MUST A tab’s header, the one graphic header of TABS-02, carries the tab’s states: a
•prefix in amber italic for unsaved, a pin and bold for pinned, muted italic for read-only. A terminal app’s tab is never unsaved or read-only, and its header says in their place what the tab is doing: the title is the running program’s name while one runs, unless the user or the shell named the tab, and a mark beside the title says what happened while the tab was not selected (a notification, a bell, or output after a quiet spell), cleared when the tab is selected. A pinned terminal tab is drawn as any other pinned tab, with a pin and a bold title.- Check (code): the code that builds a tab’s header marks it unsaved, pinned or read-only (Editora’s style
classes
dirty,pinnedandread-onlyon.tab-header) and adds the•prefix and the pin, and the stylesheet gives each mark the look the rule names. In a terminal app: the stylesheet styles the pinned title, the code that names the tab puts the running program before the folder, and the header shows the mark and clears it when the tab is selected. - Reference: Editora
ui/TabHeaders.java,app.css; the Unsaved, Pinned and Read-only rows of the Spec table. Terminaui/TerminalTitle.java(tab),ui/TabMarks.javaandTabMarkStateinui/TerminalWindow.java(a dot after the title, in the terminal palette’s magenta, yellow or cyan, and a pin), and.tab-title.pinnedin itsapp.css.
- Check (code): the code that builds a tab’s header marks it unsaved, pinned or read-only (Editora’s style
classes
- TABS-04 MUST Bulk close skips pinned tabs: close others, close all, close unmodified and close to the left
or right never close a pinned tab. A terminal app has three of them (TABS-01), and each skips its
pinned tabs too.
- Check (code): every bulk close the app has (close others, close all, close unmodified, close to the left and
to the right) builds the list of tabs it will close without the pinned ones: it tests each tab for pinned
before taking it (Editora’s
closeOtherTabs,closeAllTabs,closeUnmodifiedTabs,eligibleToLeftandeligibleToRight). A test that asserts it is the surest evidence. - Reference: Editora
ui/MainController.java. Terminaui/TabRanges.java(closing, which leaves out every pinned position and which each bulk close ofui/TerminalWindow.javagoes through) andTabRangesTest.
- Check (code): every bulk close the app has (close others, close all, close unmodified, close to the left and
to the right) builds the list of tabs it will close without the pinned ones: it tests each tab for pinned
before taking it (Editora’s
- TABS-05 MUST Pinning moves the tab to the end of the pinned group, unpinning to just after it.
- Check (code): the code that pins or unpins a tab then moves it to the boundary between the pinned tabs and
the rest, the index equal to the number of other pinned tabs in its strip: the last place of the pinned group
for a tab just pinned, the first place after the group for one just unpinned (Editora’s
togglePin, which callsmoveToPinBoundary). - Reference: Editora
ui/MainController.java(togglePin),ui/EditorArea.java(moveToPinBoundary). Terminaui/TerminalWindow.java(togglePin, which counts the other pinned tabs and moves the tab to that index).
- Check (code): the code that pins or unpins a tab then moves it to the boundary between the pinned tabs and
the rest, the index equal to the number of other pinned tabs in its strip: the last place of the pinned group
for a tab just pinned, the first place after the group for one just unpinned (Editora’s
- TABS-06 MUST Reopen Closed Tab brings back the files whose tabs this window closed, newest first, bounded
to twenty, a file listed once, with the caret where it was. In a terminal app the tab comes back (its shells,
their directories, the pane arrangement, the names the user gave them, its place in the strip) and not the
scrollback.
- Why: the process is gone, and pretending otherwise would be worse than saying so.
- Check (code): each window keeps a list of the tabs it closed, newest first and no longer than twenty; the command takes the newest entry and opens it. In an app whose tabs hold files, an entry is the file, whether an editor’s tab or a viewer’s showed it, with the caret where the tab has one; closing a file again replaces its earlier entry, and reopening puts the caret back. In a terminal app, an entry holds the tab’s panes with each one’s shell and directory, their arrangement, the names the user gave them and the tab’s place in the strip, and no scrollback. A test over the list is the surest evidence.
- Reference: Editora
ui/ClosedTabs.java,ClosedTabsTest;C-S-tin the CUA keymap. Editora doesn’t yet for its image, hex and PDF viewer tabs:rememberClosedinui/MainController.javarecords the file of an editor’s tab alone, so a closed viewer tab does not come back. Terminaui/ClosedTabs.javaandClosedTabsTest, onCtrl+Shift+Z(Cmd+Zon macOS).
- TABS-07 SHOULD Tabs reorder by dragging, with this feedback: the dragged header dimmed and an
accent line on the edge where it will land.
- Check (by hand): drag a tab along the strip and watch the landing edge.
- Reference: Editora
TabHeaders.enableTabDrag; TerminainstallTabDragand the pureTabReorder.insertIndex. In Termina a double-click on a tab renames it, and a pane dragged onto a tab joins it (the whole header outlined,tab-drop-into).
- TABS-08 SHOULD In an app whose tabs hold files, a tab shows its file’s Git status in the Project tree’s
colors: modified accent, added green, untracked olive, renamed violet, deleted muted, conflict red. A read-only
tab still shows it; an unsaved one shows amber. The tab’s tooltip names the file’s Git status too, so color is
not the status’s only sign (ACC-05). A terminal app’s tabs hold no files, so the
rule passes it by.
- Check (code): the code that styles a tab gives it, for its file’s Git status, the style class the Project tree gives that file’s row, read-only or not, and the stylesheet lets the unsaved tab’s amber win over it; and the code that sets the tab’s tooltip adds the status in words (modified, added, untracked and the rest) when the file has one. A test that finds the tree’s class on a changed file’s tab, and the status in its tooltip, is the surest evidence.
- Reference: for the colors, Editora
ui/TabGitStatus.java,TabGitStatusTest. For the tooltip, no app yet: Editora’s tab tooltip is the file’s full path (tooltipinui/TabHeaders.java), so the tint is the tab’s only sign of the status. Its Project tree adds a letter to the color; its tabs add no word, glyph or shape. The app template meets both halves for its sample files:ui/TabGitStatus.javagives a tab the class its Documents window gives the file’s row (TabsAndPanelsTest,aChangedFileWearsTheDocumentsWindowsClass), andui/TabHeaders.javaadds the status in words to the tab’s tooltip, after the path.
- TABS-09 SHOULD An app whose tabs hold files has a switcher that lists the open files in tab order. A
command opens it; the arrows or the active keymap’s line chords move, Enter or releasing Ctrl (the Control key,
on macOS too) activates, Esc or the keymap’s cancel chord cancels, and Backspace, Delete or the keymap’s
delete-character chord closes the highlighted file. The switcher’s width is fixed to the longest path on each
open, so it never resizes while you move. A terminal app’s tabs hold no files, so the rule passes it by.
- Check (by hand): open it with several tabs; move with the arrows and with the active keymap’s line chords, close a file from it, cancel it, and open it again to activate another file; the list keeps its width.
- Reference: Editora
ui/Switcher.java, which reads its keys throughui/PickerKeys.javaand the keymap, andSwitcherFxTest. In Editora’s Emacs keymapC-x C-bopens it (switcher.show),C-nandC-pmove,C-gcancels andC-dcloses the file (keymaps/emacs.json); no other Editora keymap bindsswitcher.show.
- TABS-12 SHOULD A command hides the tab bar.
- Check (code): a registered command hides the tab header, with any number of tabs open. One that hides it only while the window has a single tab does not meet the rule.
- Reference: Editora
view.toggleTabBar,.tab-pane.no-tab-headerinapp.css. Termina doesn’t yet: the nearest it has is a setting, with a palette command that toggles it, that hides the strip only while the window has one tab (settings.hideTabBarinui/SettingCommands.java).
Termina’s HeaderBar holds the menu bar and the window title
(ui/TerminalWindow.java, buildHeaderBar), and its tab strip is the row under it.

Tool panels
Section titled “Tool panels”Applies to: an app with tool panels: a tool panel is a panel docked at an edge of the main window, beside or
under the content, that the user shows and hides as a whole, the content taking its room while it is hidden. A
sidebar, a detail pane, an info panel and a thumbnail strip are tool panels, on a stripe or not. A section that
folds in place and leaves its heading showing is content (nux’s All variables table, a TitledPane under its
dashboard), and so are a terminal’s split panes: neither is a tool panel. Nor is a bar of the window’s chrome
that a command hides (a toolbar, a status bar, a tab strip).
- TABS-13 MUST Every tool panel has a command that shows and hides it, with the id
tool.<id>, as Editora’stool.projectis, and where the app has a stripe, the panel’s stripe button runs that command. In the Emacs keymap,M-1throughM-9and thenM-0run those commands, one chord to a panel: an app with fewer than ten panels uses the first of the chords, and one with more chooses the ten panels that get them. An app with one key table and no Emacs keymap (KBD-09) owes none of these chords.- Check (code): every tool panel has a registered command whose id is
tool.and the panel’s own id, which shows the panel when it is hidden and hides it when it shows; a stripe button, where the app has stripes, runs that command, and one that toggles the panel directly and skips what the command does first fails; andemacs.json, in an app that ships one, bindsM-1,M-2and on throughM-0to those commands, one for each panel up to ten. - Reference: Editora registers a
tool.<id>command for each of its tool windows (ui/WindowCommandRegistrar.java) and binds ten of them toM-1…M-0(keymaps/emacs.json). It doesn’t meet the stripe clause yet:ToolWindowManager.registergives each stripe button the manager’s owntoggle, not the command, so the button skips what some commands do first (tool.remoterefreshes its panel;tool.projectandtool.notestest that the feature is on). Nor does every one of its commands hide a panel that shows:tool.gitLog, for one, only opens its panel (openGitLoginui/GitWindowCoordinator.java), and so do thetool.<id>commands of its build tools (registerCommandsinui/BuildCoordinator.java). Torrenta and Mirada don’t meet the rule yet. Torrenta has notool.<id>command: its two panels’ commands aretoggle-sidebarandtoggle-detail(ui/MainWindow.java), and it ships no keymap file, so it owes no chord. Mirada’s two areview.propertiesandview.thumbnails(ui/Command.java), and itskeymaps/emacs.jsonbinds them toiandt, where the rule requiresM-1andM-2.
- Check (code): every tool panel has a registered command whose id is
- A panel’s content is built on first use: PERF-14.
- TABS-15 SHOULD Panel state is restored: which panels are open, where each sits and every divider position
go to the session-state file (SET-08; Editora’s is
workspace-state.json) and come back on the next launch. In an app with tool window stripes that includes each window’s side and order, the stripe buttons the user hid, and the windows that float.- Check (code): the session state holds each of those, and the code that builds the panels reads them back at startup.
- Reference: Editora
ui/ToolWindowManager.java,config/WorkspaceState.java.
- TABS-19 SHOULD Closing the panel that holds keyboard focus returns focus to where it was in the content
(in Editora, the editor).
- Check (code): the code that closes a panel keeps the content’s last focus owner and refocuses it on close.
- Reference: Editora
ToolWindowManager.focusEditor, a weak reference to the last editor focus owner.
Tool window stripes
Section titled “Tool window stripes”Applies to: an app with tool window stripes.
A stripe is the rail of buttons along an edge of the window, one button per tool window, that Editora has (pins 6 and 9 of the mockup). Its tool windows are tool panels too, so the rules of Tool panels cover them; these cover what only a docking system has.
- TABS-16 SHOULD Tool windows dock on three sides, left, right and bottom, and a side holds at most two
windows stacked (Project over Structure, two consoles along the bottom).
- Why: past that a side stops being a dock and becomes a list of slivers.
- Check (code): the sides are an enum of three and the per-side limit is two.
- Reference: Editora
ToolWindow.Side,ToolWindowManager.MAX_PER_SIDE.
- TABS-17 SHOULD A tool window re-docks by dragging its stripe button to another stripe, with the same
dim-and-accent-line feedback as a tab; an empty stripe appears as a dashed accent drop zone for the duration of
the drag.
- Check (by hand): drag a stripe button to the opposite side.
- Reference: Editora
ui/ToolWindowDock.java,ToolWindowVisibilityTest(an empty stripe shows while dragging).
- TABS-18 SHOULD Tool windows float, maximize, resize and close from the keyboard, and at most one window is
maximized at a time.
- Check (code): floating, maximizing, resizing and closing a tool window are each a registered command, so the palette runs them without the mouse; and maximizing one first restores the one that was maximized.
- Reference: Editora
view.floatToolWindow(palette only),view.maximizeToolWindow(C-x f),view.closeFocusedToolWindow(C-x 0), the resize commands (C-x S-.,C-x S-,,C-x S-6);ui/ToolWindowManager.javakeeps onemaximizedpanel and restores it before it maximizes another.
- TABS-20 SHOULD Hidden is not unavailable: the user’s show/hide choice for a stripe button is kept apart
from a context-driven hide (the Commit window outside a Git repository), so the second never clobbers the first.
- Check (code): the stripe keeps two values for a tool window, the user’s saved show/hide choice and whether the context offers the window now, shows the button only when both hold, and never writes the first when the second changes. A test that asserts it is the surest evidence.
- Reference: Editora
ui/ToolWindowVisibility.java,ToolWindowVisibilityTest.
- TABS-21 SHOULD A tool window whose content needs more room than the default share of its side can ask for
more on its first open (Editora’s Debug window asks for 42 %); the user’s own size wins afterwards.
- Check (code): a tool window can ask for a larger share of the side on its first open (Editora’s
setFirstOpenShare), the docking code grants it only while the user has set no size for that window, and the other windows keep the side’s size. A test that asserts it is the surest evidence. - Reference: Editora
ToolWindow.setFirstOpenShare,ToolWindowFirstOpenShareTest.
- Check (code): a tool window can ask for a larger share of the side on its first open (Editora’s
- TABS-22 SHOULD A stripe button badges a spinner while its window has something under way.
- Check (code): a tool window has a busy state, and its stripe button shows a spinner badge while the state holds and hides it when it ends. A test that asserts it is the surest evidence.
- Reference: Editora
ToolWindow.busy,ToolWindowManagerFxTest.
- TABS-23 SHOULD Tool windows follow the active document where they should: the Git UI follows the active
tab’s repository, the status bar’s environment segment the active
.httpfile, Local History the file whose tab menu opened it.- Check (by hand): switch between tabs from two repositories with the Git window open.
- Reference: Editora
ui/GitPathScope.java.
In the apps
Section titled “In the apps”The other apps have panels and no stripes, so only Tool panels covers them. Torrenta’s filter
sidebar sits down the left or the right of the list or nowhere, kept as two settings keys so hiding it keeps
its side (SidebarPlace); its inner edge drags to resize within readable bounds and a double-click resets it
(SidebarWidth); the detail pane docks under the list in two columns or beside it in one, from the View menu (DetailPane). Mirada’s info panel opens on
the right and its thumbnail strip along the bottom or down the left side, each closed until its command asks for it
(ThumbnailStrip.place). Termina splits a tab into panes instead: a pane is picked up with a drag while
Ctrl+Alt+Shift (Cmd+Option+Shift on macOS) is held, since every smaller chord is spoken for (PaneDrag), and a
maximized pane wears a “Pane 2 of 3” badge so the others are known to still be there.



| Property | Value | Reference |
|---|---|---|
| Tab strip | -color-bg-subtle, padding 3 10 0 10, tabs bottom-aligned so the active one touches the editor; no bottom rule | .tab-pane > .tab-header-area |
| Tab | Transparent, square corners, padding 2 11 3 11; hover -color-bg-inset | .headers-region > .tab |
| Active tab | Two background layers: -color-border-default outside, -editor-surface inset 1 1 0 1; title bold -color-fg-default; glyph -color-accent-fg | .tab:selected |
| Title | Inter 14 px, -color-fg-muted, in a graphic label; the full path as tooltip | .tab .tab-title, TabHeaders.tooltip |
| Unsaved | • prefix, -state-amber, italic | .tab-header.dirty .tab-title |
| Pinned | Icons.pin() in the header, bold; first in the strip | .tab-header.pinned, togglePin |
| Read-only | -color-fg-muted, italic | .tab-header.read-only |
| Drag | Dragged header at 0.4 opacity; 2 px -color-accent-emphasis on the landing edge | .tab-dragging, .tab-drop-before, .tab-drop-after |
| Closed tabs | Twenty, newest first, one entry per file, with the caret | ClosedTabs.DEFAULT_CAPACITY |
| Switcher | 26 px rows, 12 visible, width fixed per open | Switcher.CELL_HEIGHT, MAX_VISIBLE |
| Tool stripe | 30 px wide, -color-bg-subtle, 8 px spacing, no edge; buttons min 24, padding 9 5, radius 6 | .tool-stripe, .tool-stripe-button |
| Stripe states | Open: -color-accent-subtle fill, accent glyph. Focused window: -state-accent-hover | :open, :tw-active |
| Bottom stripe | Label 14 px beside the glyph, padding 3 8; open = accent, bold | .tool-stripe-horizontal .tool-stripe-button |
| Panel | -color-bg-subtle ground, radius 0 0 8 8, no border | .tool-window |
| Panel header | Padding 6 6 6 12, radius 7 7 0 0, no rule under it; title 14 px bold muted with the window’s glyph; active: -color-accent-subtle band, accent title | .tool-window-header, .tool-window:active |
| Panel content | -color-bg-default, padding 8; its tree or list draws no frame of its own | .tool-window-content |
| Per side | Two windows at most, stacked in an inner SplitPane | MAX_PER_SIDE |
| Persisted | Open state, sides, order, visibility, floating windows, divider positions | WorkspaceState in workspace-state.json |
Pauta 6.0.1 · · Changelog · This page in the latest edition