@vincentt-xr/sdk 2.0.0-alpha.1 → 2.0.0-alpha.2

package/docs/api/screen-text.mdx

@@ -0,0 +1,39 @@
+---
+title: "Screen Text"
+description: "Standard screen-space text with design-pixel transforms, layout, styles, and editor controls."
+sidebarTitle: "Screen Text"
+icon: "type"
+---
+
+Use `ScreenText` for prompts, captions, banners, badges, and titles. Prefer it
+over manually pairing `ScreenTransform` and `TextLabel` for ordinary screen UI.
+
+```tsx
+import { ScreenSpaceUI, ScreenText } from "@vincentt-xr/sdk";
+
+<ScreenSpaceUI>
+  <ScreenText
+    name="headline"
+    text="Head-Tilt Trivia"
+    coordinateSpace="canvas"
+    canvasSize={{ width: 720, height: 1280 }}
+    position={[0, 500]}
+    size={[620, 140]}
+    textAlign="center"
+    fontSize={270}
+    bgFit="text"
+    bgColor="transparent"
+  />
+</ScreenSpaceUI>;
+```
+
+`coordinateSpace="normalized"` uses normalized screen units. `"canvas"` uses
+design pixels with center origin and positive Y upward. `size` is the text
+bounding rectangle; alignment, overflow, background, stroke, and shadow are
+resolved inside it.
+
+Use `TextLabel` only for world-space text or lower-level composites whose
+parent owns layout. For serialized scenes, combine `ScreenTransform` +
+`ScreenText` and use `mapScreenTextSettingsToProps`. Use
+`ScreenTextSettingsPanel` from `@vincentt-xr/sdk/debug-ui` for creator tooling,
+not production UI.

package/docs/api/texture-sources.mdx

@@ -0,0 +1,55 @@
+---
+title: "Texture Sources and Animation"
+description: "Static images, runtime textures, animated providers, playback capabilities, and lifecycle."
+sidebarTitle: "Texture Sources"
+icon: "film"
+---
+
+`ScreenImage` is the standard render target. Pass a URL image or an existing
+Three.js texture through the core API.
+
+```tsx
+import { ScreenImage, ScreenSpaceUI } from "@vincentt-xr/sdk";
+
+<ScreenSpaceUI>
+  <ScreenImage source={{ kind: "texture", texture }} stretchMode="fit" />
+</ScreenSpaceUI>;
+```
+
+Managed video, GIF, and image-sequence providers should resolve to a live
+`THREE.Texture`. Animated sources can expose forward, reverse, ping-pong,
+random, looping, finite loop counts, pause/resume, restart, frame status, and
+ended state. Gate controls using provider capabilities; static images must not
+show playback controls.
+
+## Example asset layout
+
+Example-app media assets live under `example/src/assets/media`:
+
+- `images/` for static textures and sample stills
+- `images/people/` for face/body tracking sample stills
+- `images/screenshots/` for screenshot references
+- `videos/` for sample MP4/WebM sources
+- `gifs/` for animated GIF inputs
+- `sequences/<demo-name>/` for ordered image-sequence frames
+
+GLB assets live under `example/src/assets/models`. Domain-specific effect
+assets, such as face paint textures, stay under their owning domain folder
+instead of being flattened into `media`.
+
+Low-level integration lives at `@vincentt-xr/sdk/low-level`:
+
+```ts
+import {
+  BasicAnimatedTextureController,
+  createTextureSourceResolver,
+  getPlaybackFrame,
+  getSequenceFrame,
+} from "@vincentt-xr/sdk/low-level";
+```
+
+The controller lifecycle is `play`, `pause`, `restart`, optional `seek`, play
+mode and loop configuration, subscription, then `dispose`. Read `getSnapshot()`
+for current state and errors. Dispose replaced owned sources and keep dynamic
+canvas/video textures marked for GPU upload; source replacement should preserve
+the scene object's transform and material settings.

package/docs/api/trackers.mdx

@@ -0,0 +1,46 @@
+---
+title: "Trackers"
+description: "Face, hand, gesture, body, and segmentation trackers with shared lifecycle and performance controls."
+sidebarTitle: "Trackers"
+icon: "scan"
+---
+
+Import trackers from `@vincentt-xr/sdk/tracking`. They acquire and share their
+MediaPipe model automatically.
+
+```tsx
+import {
+  BodyTracker,
+  FaceTracker,
+  GestureTracker,
+  HandTracker,
+  Segmentation,
+} from "@vincentt-xr/sdk/tracking";
+
+<FaceTracker />;
+<HandTracker hand="right" />;
+<GestureTracker />;
+<BodyTracker />;
+<Segmentation type="portrait" />;
+```
+
+- `FaceTracker`: 468 landmarks and face transform; supports `faceIndex`,
+  `scaleWithFace`, and `followFaceRoll`
+- `HandTracker`: 21-joint skeleton; use `hand` or `handIndex` for selection
+- `GestureTracker`: named gesture recognition
+- `BodyTracker`: 33 pose landmarks
+- `Segmentation`: portrait mask for background replacement
+
+The example app route `/body` shows the recommended body-tracking pattern:
+mount `BodyTracker` once, then attach visible content with `TrackingAnchor`
+targets such as `body.head`, `body.leftShoulder`, and `body.rightWrist`.
+
+Gesture names are exactly `closed_fist`, `open_palm`, `pointing_up`,
+`thumb_down`, `thumb_up`, `victory`, `i_love_you`, and `none`. Use
+`GestureTrigger` for one-shot callbacks and `useXRModelNode` from
+`@vincentt-xr/sdk/low-level` only for fine-grained frame reads.
+
+Mount a tracker once above scene/phase switches when multiple scenes use it.
+Use `active={false}` to pause without disposal. Control inference with
+`targetFps` or the provider/session `perf` configuration; do not build a second
+polling or throttling loop.

package/docs/docs.json

@@ -0,0 +1,70 @@
+{
+  "$schema": "https://mintlify.com/docs.json",
+  "theme": "mint",
+  "name": "Vincentt XR SDK",
+  "colors": {
+    "primary": "#2563eb",
+    "light": "#2563eb",
+    "dark": "#60a5fa"
+  },
+  "navigation": {
+    "groups": [
+      {
+        "group": "Start Here",
+        "icon": "book-open",
+        "pages": ["introduction"]
+      },
+      {
+        "group": "Scene Objects",
+        "icon": "layers",
+        "pages": [
+          "scene-objects/overview",
+          "scene-objects/render-groups",
+          "scene-objects/runtime-rendering"
+        ]
+      },
+      {
+        "group": "API Reference",
+        "icon": "code",
+        "pages": [
+          "api/runtime-3d",
+          "api/screen-space-coordinates",
+          "api/screen-image",
+          "api/screen-text",
+          "api/screen-shape",
+          "api/trackers",
+          "api/face-info",
+          "api/face-actions",
+          "api/face-attribute-expression",
+          "api/face-binding-anchors",
+          "api/face-effects",
+          "api/face-mesh",
+          "api/face-painting",
+          "api/face-retouching",
+          "api/capture-recording",
+          "api/audio",
+          "api/texture-sources",
+          "api/material-render-state",
+          "api/behavior-components",
+          "api/scene-object-store",
+          "api/debug-ui-scene-editor"
+        ]
+      },
+      {
+        "group": "Inspector",
+        "icon": "panel-right",
+        "pages": ["inspector/hierarchy-panel", "inspector/object-inspector-panel"]
+      },
+      {
+        "group": "Client Integration",
+        "icon": "plug",
+        "pages": ["guides/harness-debug-ui"]
+      },
+      {
+        "group": "Examples",
+        "icon": "code",
+        "pages": ["examples/scene-object-recipes"]
+      }
+    ]
+  }
+}

package/docs/examples/scene-object-recipes.mdx

@@ -0,0 +1,194 @@
+---
+title: "Scene Object Recipes"
+description: "Create Screen Image, Screen Text, and 3D Object scene objects."
+sidebarTitle: "Recipes"
+icon: "code"
+---
+
+These recipes show the current serialized authoring pattern.
+
+```ts
+import { createDefaultComponent, createSceneObject } from "@vincentt-xr/sdk/scene-object";
+```
+
+## Screen Image object
+
+```ts
+const object = createSceneObject({
+  name: "Screen Image",
+  renderGroupId: "2d-foreground",
+});
+const screenTransform = createDefaultComponent("ScreenTransform", object.id);
+const screenImage = createDefaultComponent("ScreenImage", object.id);
+const material = createDefaultComponent("Material", object.id);
+const texture = createDefaultComponent("Texture", object.id);
+
+object.componentIds = [screenTransform.id, screenImage.id, material.id, texture.id];
+```
+
+## Screen Text object
+
+```ts
+const object = createSceneObject({
+  name: "Screen Text",
+  renderGroupId: "2d-foreground",
+});
+const screenTransform = createDefaultComponent("ScreenTransform", object.id);
+const screenText = createDefaultComponent("ScreenText", object.id);
+const material = createDefaultComponent("Material", object.id);
+const texture = createDefaultComponent("Texture", object.id);
+
+object.componentIds = [screenTransform.id, screenText.id, material.id, texture.id];
+```
+
+## 3D Object
+
+```ts
+const object = createSceneObject({ name: "Cube", renderGroupId: "general" });
+const transform = createDefaultComponent("Transform", object.id);
+const meshRenderer = createDefaultComponent("MeshRenderer", object.id);
+
+object.componentIds = [transform.id, meshRenderer.id];
+```
+
+## FaceMeshRenderer object
+
+```ts
+import { DEFAULT_FACE_MESH_TRANSFORM } from "@vincentt-xr/sdk/face-effects";
+
+const object = createSceneObject({ name: "Face Mesh", renderGroupId: "scene3d" });
+const transform = createDefaultComponent("Transform", object.id);
+const faceMesh = createDefaultComponent("FaceMeshRenderer", object.id);
+
+transform.settings.position.y = DEFAULT_FACE_MESH_TRANSFORM.position.y;
+
+object.componentIds = [transform.id, faceMesh.id];
+```
+
+FaceMesh consumes `Transform` in landmark space before projection, not as a
+normal world-space parent group. Position and uniform scale are supported;
+rotation and non-uniform scale are ignored until object-space face solving lands.
+
+## 3D object with render state
+
+```ts
+const object = createSceneObject({ name: "Base Plane", renderGroupId: "scene3d" });
+const transform = createDefaultComponent("Transform", object.id);
+const meshRenderer = createDefaultComponent("MeshRenderer", object.id);
+
+transform.settings.position = { x: 0, y: -2.5, z: 0 };
+transform.settings.rotation = { x: -90, y: 0, z: 0 };
+transform.settings.scale = { x: 7.5, y: 7.5, z: 7.5 };
+
+meshRenderer.settings.mesh = "plane";
+meshRenderer.settings.material.color = "#1b2733";
+meshRenderer.settings.material.renderState = {
+  depthTest: true,
+  depthWrite: true,
+  cullMode: "off",
+  colorMask: { r: true, g: true, b: true, a: true },
+};
+meshRenderer.settings.shadowMode = "receive";
+
+object.componentIds = [transform.id, meshRenderer.id];
+```
+
+## Asset-backed GLTF object
+
+```ts
+const micGlbUrl = new URL("../../assets/models/mic.glb", import.meta.url).href;
+
+const object = createSceneObject({ name: "Mic", renderGroupId: "scene3d" });
+const transform = createDefaultComponent("Transform", object.id);
+const meshRenderer = createDefaultComponent("MeshRenderer", object.id);
+
+transform.settings.position = { x: -1.1, y: -0.6, z: 0 };
+transform.settings.scale = { x: 0.1, y: 0.1, z: 0.1 };
+
+meshRenderer.settings.assetUrl = micGlbUrl;
+meshRenderer.settings.shadowMode = "castReceive";
+
+object.componentIds = [transform.id, meshRenderer.id];
+```
+
+Keep example GLB files in `example/src/assets/models`. Put sample image, video,
+GIF, and sequence inputs under `example/src/assets/media` by media type.
+
+## Light object
+
+```ts
+const object = createSceneObject({ name: "Key Light", renderGroupId: "scene3d" });
+const transform = createDefaultComponent("Transform", object.id);
+const light = createDefaultComponent("Light", object.id);
+
+transform.settings.position = { x: 3, y: 5, z: 4 };
+light.settings.type = "directional";
+light.settings.intensity = 2.2;
+light.settings.castShadow = true;
+light.settings.showHelper = true; // editor/debug only
+
+object.componentIds = [transform.id, light.id];
+```
+
+## LookAt behavior
+
+```ts
+const lookAt = createDefaultComponent("LookAt", object.id);
+
+lookAt.settings.enabled = true;
+lookAt.settings.targetObjectId = "target-object-id";
+lookAt.settings.mode = "point";
+lookAt.settings.offsetRotation = { x: 0, y: 0, z: 0 };
+
+object.componentIds = [transform.id, meshRenderer.id, lookAt.id];
+```
+
+## PinToMesh behavior
+
+```ts
+const pinToMesh = createDefaultComponent("PinToMesh", object.id);
+
+pinToMesh.settings.enabled = true;
+pinToMesh.settings.targetObjectId = "base-plane";
+pinToMesh.settings.orientation = "positionAndDirection";
+pinToMesh.settings.uv = { x: 0.5, y: 0.5 };
+pinToMesh.settings.vertexNormal = true;
+pinToMesh.settings.offsetSpace = "local";
+pinToMesh.settings.offsetPosition = { x: 0, y: 0, z: 0 };
+pinToMesh.settings.offsetRotation = { x: 0, y: 0, z: 0 };
+
+object.componentIds = [transform.id, meshRenderer.id, pinToMesh.id];
+```
+
+## Reusable editor store shape
+
+```ts
+const store = {
+  objects: {
+    [mic.id]: mic,
+    [emoji.id]: emoji,
+    [basePlane.id]: basePlane,
+    [keyLight.id]: keyLight,
+  },
+  components: {
+    [micTransform.id]: micTransform,
+    [micMesh.id]: micMesh,
+    [emojiTransform.id]: emojiTransform,
+    [emojiMesh.id]: emojiMesh,
+    [baseTransform.id]: baseTransform,
+    [baseMesh.id]: baseMesh,
+    [lightTransform.id]: lightTransform,
+    [light.id]: light,
+  },
+  renderGroups: {
+    scene3d: {
+      id: "scene3d",
+      name: "3D Scene",
+      domain: "general",
+      enabled: true,
+      objectIds: [mic.id, emoji.id, basePlane.id, keyLight.id],
+    },
+  },
+  renderGroupOrder: ["scene3d"],
+};
+```

package/docs/guides/harness-debug-ui.mdx

@@ -0,0 +1,139 @@
+---
+title: "Debug UI in Harness Clients"
+description: "Integrate Hierarchy, Inspectors, transform controls, and grouped rendering without crossing the R3F Canvas boundary."
+sidebarTitle: "Harness Debug UI"
+icon: "plug"
+---
+
+`test001` is the canonical external Harness-client integration. For new 3D scene
+setup work, prefer the reusable scene editor primitives from
+`@vincentt-xr/sdk/debug-ui` instead of rewriting viewport, hierarchy, inspector,
+and toolbar wiring in the client app.
+
+## Agent routing contract
+
+Use the API door that owns the responsibility:
+
+| Task                                                                  | Import door                     |
+| --------------------------------------------------------------------- | ------------------------------- |
+| Runtime renderers, pass composition, and layer limits                 | `@vincentt-xr/sdk`              |
+| Scene-object state and pure render-group operations                   | `@vincentt-xr/sdk/scene-object` |
+| Reusable viewport, hierarchy, inspector, toolbar, and settings panels | `@vincentt-xr/sdk/debug-ui`     |
+
+The client owns the scene store, `selectedObjectId`, component replacement,
+visibility, reorder/move operations, selected Inspector, and preview/debug
+mounting policy. Panels emit commands; they do not own persistent scene state.
+
+## Required invariants
+
+- Derive ordering from `scene.renderGroupOrder`; do not hardcode group IDs or a
+  default group sequence.
+- Use `createRenderPlan` plus `SequentialRenderPasses` for cross-group visual
+  composition. Three.js `renderOrder` is not a substitute.
+- Treat camera layers as internal visibility masks.
+- Keep every managed object in exactly one materialized compatible group.
+- When selection changes, close 2D guides and 3D transform controls belonging to
+  the previous selection. Initial controls must match the initial selection.
+- Guard group creation with `MAX_RENDER_GROUP_PASSES`.
+- Treat Copy Config as an export/debug payload; no public importer exists.
+
+## Preferred reusable editor tree
+
+```text
+XRProvider
+└─ AspectRatioContainer
+   └─ XRSceneEditorProvider
+      ├─ XRSceneViewport
+      │  ├─ XRScene
+      │  ├─ editor-owned camera-texture plane
+      │  ├─ SequentialRenderPasses
+      │  └─ SceneObjectRenderer instances
+      ├─ ViewportToolbar
+      ├─ SceneHierarchyPanel
+      └─ SceneInspectorPanel
+```
+
+The parent above both branches owns the scene store and selection.
+
+```tsx
+<XRSceneEditorProvider
+  store={store}
+  selectedObjectId={selectedObjectId}
+  onSelectObject={setSelectedObjectId}
+  onStoreChange={setStore}
+  onComponentChange={(component) =>
+    setStore((current) => replaceSceneComponent(current, component))
+  }
+  onObjectChange={(object) => setStore((current) => replaceSceneObject(current, object))}
+>
+  <XRSceneViewport />
+  <ViewportToolbar />
+  <SceneHierarchyPanel />
+  <SceneInspectorPanel />
+</XRSceneEditorProvider>
+```
+
+`XRSceneViewport` owns the editor camera-texture plane. Do not add
+`depthTest/depthWrite` props to core `VideoBackground`; keep `VideoBackground`
+for flat runtime camera backgrounds.
+
+## Placement rule
+
+| Component                                       | Placement                      |
+| ----------------------------------------------- | ------------------------------ |
+| `SceneObjectRenderer`                           | Inside `XRScene`               |
+| `SequentialRenderPasses`                        | Inside `XRScene`               |
+| `XRSceneViewport`                               | Outside panels; owns `XRScene` |
+| `ScreenSpaceUI` and `Transform3D`               | Inside `XRScene`               |
+| Three.js controls and scene content             | Inside `XRScene`               |
+| `HierarchyPanel`                                | Outside `XRScene`              |
+| `ObjectInspectorPanel` and `ComponentEditor`    | Outside `XRScene`              |
+| `SceneHierarchyPanel` and `SceneInspectorPanel` | Outside `XRScene`              |
+| Screen Text/Image settings panels               | Outside `XRScene`              |
+
+Panels update the parent store through callbacks. `XRSceneEditorProvider` shares
+that state with the reusable viewport, hierarchy, inspector, and toolbar.
+Transform changes from inside the scene return to the same store through
+`onComponentChange`.
+
+## R3F error
+
+If React reports “R3F hooks can only be used within Canvas,” an R3F-dependent
+renderer, render-pass controller, guide, or Three.js control was mounted in the
+DOM panel branch. Move that scene component inside `XRScene`. Do not move the DOM
+panels into Canvas.
+
+## Agent failure recovery
+
+| Symptom                               | Check                                                                                                                  | Fix                                                                                            |
+| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
+| R3F Canvas-context error              | Component placement and duplicate React/R3F instances                                                                  | Keep DOM panels outside `XRScene`, scene components inside, and pin peer packages in link mode |
+| Reorder has no visible effect         | Pass layers were not recomputed                                                                                        | Rebuild the plan and feed ordered active layers to `SequentialRenderPasses`                    |
+| Wrong gizmo remains active            | Selection changed without clearing control flags                                                                       | Clear stale guides/controls during the selection state transition                              |
+| Transform drag stops immediately      | Integration replaced or remounted the active renderer                                                                  | Keep one renderer per plan entry and route `onComponentChange` to immutable parent state       |
+| Cross-group move fails                | Component composition is incompatible                                                                                  | Check `validateGroupCompatibility`; preserve state when it returns `false`                     |
+| Group is omitted from the render plan | Its zero-based index is `>= MAX_RENDER_GROUP_PASSES` (`30`), so the 31st group onward is beyond the managed-pass limit | Prevent creation using `MAX_RENDER_GROUP_PASSES`                                               |
+| Copy Config cannot be restored        | No importer is provided                                                                                                | Use the payload only for export, inspection, or handoff                                        |
+
+## Linked SDK workflow
+
+```sh
+# terminal 1 — rebuild the linked SDK
+cd vincentt-xr-sdk
+pnpm build:watch
+
+# terminal 2 — run the Harness client
+cd test001
+PORT=5174 SDK_LINK=1 pnpm dev
+```
+
+`SDK_LINK=1` resolves the sibling SDK checkout while the Harness config pins
+React, React DOM, Three.js, R3F, and Drei to the client copies. This prevents
+duplicate React/R3F instances—the other common cause of Canvas-context errors.
+
+Validate with the client typecheck, linked production build, and local runtime.
+The SDK `/viewport-editor` route is the matching in-repo reusable 3D editor
+fixture. `/unified-architecture`, `/testing-hook`, and `/debugger` are current
+example-app routes that exercise the same debug-ui style for legacy compatibility
+surfaces. `/layer-panel-test` remains useful for older grouped 2D/3D panel
+integration checks.

package/docs/inspector/hierarchy-panel.mdx

@@ -0,0 +1,51 @@
+---
+title: "Hierarchy Panel"
+description: "Select scene objects and edit materialized render-group structure."
+sidebarTitle: "Hierarchy"
+icon: "list-tree"
+---
+
+Import `HierarchyPanel` and the `HierarchyPanelCopyConfig` type from
+`@vincentt-xr/sdk/debug-ui`. It is a DOM authoring panel and must be mounted
+outside `XRScene`.
+
+## Responsibilities
+
+The panel displays materialized groups, selects objects, emits reorder/move
+commands, controls visibility through callbacks, and copies a parent-provided
+scene configuration. It does not own the scene store, selection, Inspector,
+compatibility policy, or renderer.
+
+Internal source layout: hierarchy UI consumes public render-group data from
+`@vincentt-xr/sdk/debug-ui`; low-level layer-stack helpers live in
+`lib/render/layerStack.ts`.
+
+```tsx
+<HierarchyPanel
+  groups={scene.renderGroupOrder.map((id) => scene.renderGroups[id])}
+  objects={scene.objects}
+  selectedObjectId={scene.selectedObjectId}
+  copyConfig={{
+    kind: "scene",
+    version: 1,
+    renderGroupOrder: scene.renderGroupOrder,
+    renderGroups: scene.renderGroups,
+    objects: scene.objects,
+    components: scene.components,
+  }}
+  onSelectObject={selectObject}
+  onReorderGroup={reorderGroup}
+  onReorderObject={reorderObject}
+  onMoveObject={moveObject}
+  onToggleGroupEnabled={toggleGroup}
+  onToggleObjectVisible={toggleObject}
+/>
+```
+
+The panel is expanded by default and can fold. Individual groups can collapse.
+Fold, collapse, drag, position, and feedback messages are transient UI state and
+are excluded from Copy Config.
+
+Cross-group drops must return `false` when
+`validateGroupCompatibility` rejects the target. The panel then displays
+feedback without mutating scene state.

package/docs/inspector/object-inspector-panel.mdx

@@ -0,0 +1,51 @@
+---
+title: "Object Inspector Panel"
+description: "Build shared settings panels with ObjectInspectorPanel and ComponentEditor."
+sidebarTitle: "Object Inspector"
+icon: "panel-right"
+---
+
+`ObjectInspectorPanel` is the shared shell for editor settings. It should be
+used for Screen Image, Screen Text, 3D Object, and future scene objects.
+
+## Props
+
+```ts
+type ObjectInspectorPanelProps = {
+  children: ReactNode;
+  copyConfig: unknown;
+  layer?: string;
+  objectId?: string;
+  objectName?: string;
+  onObjectNameChange?: (name: string) => void;
+  title?: string;
+  visible: boolean;
+  onVisibleChange: (visible: boolean) => void;
+  position?: { x: number; y: number };
+  onPositionChange?: (position: { x: number; y: number }) => void;
+};
+```
+
+## Dynamic component editors
+
+```tsx
+{
+  object.componentIds.map((componentId) => (
+    <ComponentEditor
+      key={componentId}
+      component={store.components[componentId]}
+      editors={componentEditors}
+      onChange={replaceComponent}
+    />
+  ));
+}
+```
+
+If an editor is not registered, the fallback panel shows the component type,
+component ID, and raw component JSON instead of crashing.
+
+The parent editor owns selection. Render one Inspector for `selectedObjectId`
+and preserve its position while selection changes. `ScreenTextSettingsPanel`
+and `ScreenImageSettingsPanel` already contain their Inspector shell when an
+`inspector` binding is supplied; do not nest them in another
+`ObjectInspectorPanel`.