@open-matrix/explorer-views (1.1.33)
Installation
@open-matrix:registry=npm install @open-matrix/explorer-views@1.1.33"@open-matrix/explorer-views": "1.1.33"About this package
@open-matrix/explorer-views
The views for the common interfaces — Overview (matrix.framework/v1, what every actor says it is), Form
(property-set/v1), List (collection/v1), Children (thing.children/v1, what the Registry lists under a
thing), About (the row), Interface (the actor's operations), History (owner/v1), State and Source — with the Pad (program/v1) and
Settings (platform.preferences/v1, the SDK's installed-configuration contract) and Inference (inference.choice/v1, which
provider and model an application uses, answered by the inference catalog) — are a package of their own,
published the way every view is (the-explorer 15 R21–R23, 16 C1): declared under browser.views in
matrix.package.json, drawn by the module this package's root serves on request (component.module.get),
and installed in a home like any application. The explorer kit ships no copy of them and imports nothing
from here; an explorer learns of these views from the home's installed-package directory record, whose
live provider is this root's Registry claim, exactly as it learns of the Chat view from the chat
application and the Demo view from the demos.
Prior art, read before this loader was reused rather than invented (founder, 2026-10-20, F19): a VS Code
extension declares what it contributes in its package.json and the host reads the manifests of the
extensions installed locally, a cache of the marketplace package; a COM server is registered under its
class id and a client asks the registry where the server lives before loading it. Here the manifest's
browser.views is the contribution, the installed-package record plus the Registry claim is the
registration, component.module.get is the load, and a local install is the cache of the npm package.
The page (hivecast-explorer-views-page) says what the package brings, for a person who wonders where
the Form, List and About tabs come from. It is listed under Tools and labs.
The Application view
The common application/v1 interface has one view, and it is not installed: the Shell bundles it. The
@open-matrix/explorer-views/application-view entry exports the Application facet view and
bindApplicationViewHost(scope, host). A containing application lends its admitted loader through that
scope; the nearest scope answers a composed request from the actual view. Registering the common view
once does not install a global host callback. Unrelated or nested workspaces can therefore use
independent hosts without rerouting one another. A scope that supplies no host gets an explicit
unavailable explanation.
The host returns a title and dispose(), and can return closed when its application ends itself. The
facet view releases only its own application on final disposal. A state-preserving layout move retains
the live document.
Dependencies
Dependencies
| ID | Version |
|---|---|
| @open-matrix/contracts | 1.1.33 |
| @open-matrix/core | 1.1.33 |
| @open-matrix/explorer | 1.1.33 |
| @open-matrix/hivecast-brand | 1.1.33 |
| @open-matrix/interface-renderer | 1.1.33 |
Development Dependencies
| ID | Version |
|---|---|
| @open-matrix/hive-pm | 1.1.33 |
| @types/node | ^25.0.10 |
| esbuild | ^0.27.3 |
| linkedom | ^0.16.11 |
| tsx | ^4.21.0 |
| typescript | ^5.7.0 |