@pie-players/pie-default-tool-loaders 1.0.0-beta.0 → 1.0.0-beta.10

package/dist/registrations/overlay-toolbar-render.d.ts

@@ -1,33 +0,0 @@
-/**
- * The `renderToolbar` shape shared by every packaged capability that puts one
- * overlay behind one toolbar button.
- *
- * What varies between capabilities is the two options below: whether the overlay
- * paints its own chrome or takes a draggable window, and that window's size. The
- * visibility binding, the button, the component-override lookup, the `tool-id`
- * attribute and the sync are shared, so the shell title has one spelling.
- *
- * Catalog keys are derived from `toolId`: `tools.<toolId>.buttonA11y` and
- * `tools.<toolId>.tooltip`. A capability needing a different prefix — the
- * dictionary variants, which compose several capabilities off one element —
- * keeps its own renderer.
- */
-import { type ToolContext, type ToolRegistration, type ToolToolbarRenderResult, type ToolbarContext } from "@pie-players/pie-assessment-toolkit/tools/registration";
-/** A window's geometry. Absent for overlays that paint their own chrome. */
-export interface OverlayToolShell {
-    resizable: boolean;
-    initialWidth: number;
-    initialHeight: number;
-    minWidth: number;
-    minHeight: number;
-}
-export interface RenderOverlayToolbarOptions {
-    /**
-     * `"frameless"` for an overlay that draws its own surface — a ruler or a line
-     * reader sits on the content rather than in a panel.
-     */
-    surface?: "frameless";
-    /** Present when the capability opens in a draggable, closeable window. */
-    shell?: OverlayToolShell;
-}
-export declare function renderOverlayToolbar(registration: ToolRegistration, context: ToolContext, toolbarContext: ToolbarContext, options?: RenderOverlayToolbarOptions): ToolToolbarRenderResult;

package/dist/registrations/selection-actions.d.ts

@@ -1,24 +0,0 @@
-/**
- * Which capabilities appear as actions on the learner's current selection.
- *
- * The one place that pairs a selection gateway to the tools it can open. The gateway
- * renders what it is handed and names nothing; the tools know nothing about
- * selections. Composition is the only layer allowed to know both, which is why this
- * list lives here rather than in either of them.
- *
- * A selection is a shortcut, never the only way in. Chromium does not extend a
- * selection with Shift+Arrow in non-editable content unless caret browsing is on —
- * an OS toggle that does not exist on mobile — so a sighted keyboard-only learner
- * cannot originate one at all. Every tool named here also opens from the toolbar and
- * carries its own term field.
- */
-import type { ToolSelectionAction, ToolSurfaceServices } from "@pie-players/pie-assessment-toolkit/tools/registration";
-/**
- * Actions for the gateway to render, given the services it was handed.
- *
- * Rebuilt on every sync rather than captured once: a host calling
- * `updateAssessment` mid-session swaps the coordinator without remounting the
- * gateway, and an action closing over the previous one would open a tool in a
- * session the learner has left.
- */
-export declare function buildSelectionActions(services: ToolSurfaceServices): ToolSelectionAction[];