Dock Workspace
Dock Workspace is for professional applications that continuously rearrange context, a primary canvas, inspectors, previews, and output. A3S UI re-exports the complete Dockview 8.1.0 MIT API and adds an A3S theme, versioned layout persistence, and React/Vue hooks. The host still owns panel content, permissions, data, and window policy.
The container needs a computed width and height. Do not use panel layout as a replacement for business routing; persist only user-recoverable view state.
Framework usage
useDockviewLayout restores a versioned snapshot when the layout becomes ready, creates the default layout after an unsuccessful restore, and debounce-saves subsequent changes. It returns api, status, save(), restore(), clear(), and reset(). The reset path removes retained Edge Group slots before rebuilding the default layout; native integrations can call resetDockviewLayout(api, initialize) for the same behavior. Supply migrate and validate for older snapshots; never place business data in a layout snapshot.
MIT capability coverage
Essential orchestration
Edge, floating, popout, and maximize
External drag and events
External resources must pass host authorization before a panel is created. onWillDrop may reject a target; onDidDrop records only a completed result.
Licence boundary
These entrypoints depend only on the MIT edition and do not reproduce commercial modules. Advanced overflow, multi-row tabs, pinned tabs, tab and Group Chip context menus, DnD compass, Smart Guides, auto-hide Edge Groups, automatic edge docking, layout history, spatial keyboard navigation, and keyboard docking are outside this integration. Evaluate the upstream commercial licence when those capabilities are required.
Product and accessibility requirements
- Give every panel a stable ID, understandable title, and explicit scroll owner; position must not carry the only meaning.
- A blocked popout must preserve the original panel and provide a retry path.
- Persistence failure must not block dragging or resizing; failed restoration falls back to a usable default layout.
- Custom tabs, header actions, and panel content need visible focus and accessible names.
- Touch targets need sufficient size. On narrow screens, merge complex panes into a tab group instead of squeezing unreadable columns.
