Regions
Regions are toggleable, resizable strips inside a pane — Blender's
N/T-panel idea applied to every view. They replaced panel groups: instead of
a hand-rolled mini-dock rendered inside one pane (the old PaneGroupShell),
regions are engine-native and persisted — part of the pane's state in the
layout store, saved with the layout, restored exactly as left.
Concept
A view declares the region views it hosts in its manifest (regions on a
PanelDecl/WidgetDecl):
{
id: 'editor.buffer',
role: 'document',
regions: [
{ id: 'code.outline', label: 'Outline', icon: '≡', key: 'o', position: 'right' },
{ id: 'code.search', label: 'Symbol Search', icon: '⌕', key: 's', position: 'right' },
{ id: 'git.provenance', label: 'Provenance', icon: '⎇', key: 'g', position: 'right' },
{ id: 'editor.recentNotes', label: 'Recent notes', icon: '🗒', key: 'r', position: 'left' },
],
}
- Each position (
left/right/bottom) is one strip; multiple views at the same position stack as tabs within it — one visible at a time, at the strip's full extent. The right-hand strip used to be a special case that showed every view at once; see One view at a time below. - A region view is any registered panel/widget id — cross-module is fine (the
editor hosts views from the
codeandgitmodules). - Region state is per pane instance: every editor buffer keeps its own strip sizes, open flags, and active views, persisted with the layout.
- A strip can also collapse to a thin rail (Blender's tucked toolbar) without forgetting its contents.
┌─────────────────────────────────────────────────────────────┐
│ ✎ ▾ main.py │ notes.md ◧ ◨ ⬓ ☰ │ ← area header