@thatopen/services 0.3.16 → 0.4.0

package/src/built-in/UIManager/src/app/examples/FileDrop/example.ts

@@ -1,124 +1,124 @@
-/* MD
-  ## File drag-and-drop with top:files-dropped
-  ---
-  Desktop BIM workflows often rely on dragging files straight from the OS file
-  manager onto the browser window — but wiring a document-level dragenter,
-  dragover, dragleave, and drop handler that correctly tracks nested enter/leave
-  counts, shows a visual overlay, and forwards the files to the right component
-  is tedious boilerplate to repeat for every app.
-
-  top-app handles all of that automatically. It listens for file drag events on
-  the document, shows a configurable overlay while files are in flight, and fires
-  a single top:files-dropped event when the user releases the files. The drop
-  message can be a static string or a function evaluated at render time, so it
-  can reflect live application state.
-
-  This tutorial covers receiving dropped files via top:files-dropped; filtering
-  them by extension and surfacing a warning when none are supported; setting
-  dropMessage as a function that reads a live model counter so the hint text
-  updates as models are loaded; and showing a toast on success using the
-  top:notification event from the same handler.
-
-  By the end, you'll have an app with a drag-and-drop zone whose overlay message
-  adapts to how many models are already loaded, and that reports unsupported
-  files with a warning toast.
-*/
-
-import { html } from "lit";
-import * as THREE from "three";
-import * as OBC from "@thatopen/components";
-import * as OBF from "@thatopen/components-front";
-import * as FRAGS from "@thatopen/fragments";
-import * as BUI from "@thatopen/ui";
-import { PlatformClient, UIManager } from "@thatopen/services";
-import type { App, AppReadyEvent } from "../../index";
-
-const client = PlatformClient.fromPlatformContext();
-const { components } = (await client.setup(
-  { OBC, OBF, BUI, THREE, FRAGS },
-  { uuid: UIManager.uuid },
-)) as { components: OBC.Components };
-components.get(UIManager).init();
-
-const app = document.createElement("top-app") as unknown as App;
-
-app.setup = (waitUntil) => {
-  waitUntil(
-    (async () => {
-      const fragments = components.get(OBC.FragmentsManager);
-      const workerUrl = await FRAGS.FragmentsModels.getWorker();
-      fragments.init(await FRAGS.toClassicWorker(workerUrl), {
-        classicWorker: true,
-      });
-    })(),
-    "Fragments Core",
-  );
-  return { components, client };
-};
-
-app.elements = {
-  viewer: () =>
-    html`<top-viewer><top-viewer-tools></top-viewer-tools></top-viewer>`,
-};
-
-app.base = "viewer";
-app.layouts = {
-  main: {
-    label: "Main",
-    icon: "solar:home-bold",
-    template: `"_" 1fr / 1fr`,
-  },
-};
-app.layout = "main";
-
-// dropMessage as a function is evaluated at render time so it can read live state.
-// Here it reads how many models are already loaded and adjusts the hint text.
-let loadedCount = 0;
-app.dropMessage = () =>
-  loadedCount === 0
-    ? "Drop an IFC or FRAG file to load your first model"
-    : `Drop a file to add to the ${loadedCount} loaded model${loadedCount === 1 ? "" : "s"}`;
-
-// top:files-dropped fires when the user drops files onto the window.
-// e.detail.files is a File[]. Handle upload, load, or validation here.
-app.addEventListener("top:files-dropped", (e) => {
-  const { files } = (e as CustomEvent<{ files: File[] }>).detail;
-
-  const supported = files.filter(
-    (f) => f.name.endsWith(".ifc") || f.name.endsWith(".frag"),
-  );
-
-  // Dispatch top:notification to surface feedback without a reference to top-app.
-  if (!supported.length) {
-    app.dispatchEvent(
-      new CustomEvent("top:notification", {
-        bubbles: true,
-        composed: true,
-        detail: { message: "No supported files dropped", type: "warning" },
-      }),
-    );
-    return;
-  }
-
-  loadedCount += supported.length;
-  app.dispatchEvent(
-    new CustomEvent("top:notification", {
-      bubbles: true,
-      composed: true,
-      detail: {
-        message: `${supported.length} file${supported.length === 1 ? "" : "s"} received`,
-        type: "success",
-        description: supported.map((f) => f.name).join(", "),
-      },
-    }),
-  );
-});
-
-app.addEventListener("top:app-ready", (e) => {
-  const { app: readyApp } = (e as AppReadyEvent).detail;
-  readyApp.showToast("App ready — try dropping an IFC or FRAG file", "info");
-});
-
-const container = document.getElementById("that-open-app") ?? document.body;
-container.appendChild(app);
-document.body.style.margin = "0";
+/* MD
+  ## File drag-and-drop with top:files-dropped
+  ---
+  Desktop BIM workflows often rely on dragging files straight from the OS file
+  manager onto the browser window — but wiring a document-level dragenter,
+  dragover, dragleave, and drop handler that correctly tracks nested enter/leave
+  counts, shows a visual overlay, and forwards the files to the right component
+  is tedious boilerplate to repeat for every app.
+
+  top-app handles all of that automatically. It listens for file drag events on
+  the document, shows a configurable overlay while files are in flight, and fires
+  a single top:files-dropped event when the user releases the files. The drop
+  message can be a static string or a function evaluated at render time, so it
+  can reflect live application state.
+
+  This tutorial covers receiving dropped files via top:files-dropped; filtering
+  them by extension and surfacing a warning when none are supported; setting
+  dropMessage as a function that reads a live model counter so the hint text
+  updates as models are loaded; and showing a toast on success using the
+  top:notification event from the same handler.
+
+  By the end, you'll have an app with a drag-and-drop zone whose overlay message
+  adapts to how many models are already loaded, and that reports unsupported
+  files with a warning toast.
+*/
+
+import { html } from "lit";
+import * as THREE from "three";
+import * as OBC from "@thatopen/components";
+import * as OBF from "@thatopen/components-front";
+import * as FRAGS from "@thatopen/fragments";
+import * as BUI from "@thatopen/ui";
+import { PlatformClient, UIManager } from "@thatopen/services";
+import type { App, AppReadyEvent } from "../../index";
+
+const client = PlatformClient.fromPlatformContext();
+const { components } = (await client.setup(
+  { OBC, OBF, BUI, THREE, FRAGS },
+  { uuid: UIManager.uuid },
+)) as { components: OBC.Components };
+components.get(UIManager).init();
+
+const app = document.createElement("top-app") as unknown as App;
+
+app.setup = (waitUntil) => {
+  waitUntil(
+    (async () => {
+      const fragments = components.get(OBC.FragmentsManager);
+      const workerUrl = await FRAGS.FragmentsModels.getWorker();
+      fragments.init(await FRAGS.toClassicWorker(workerUrl), {
+        classicWorker: true,
+      });
+    })(),
+    "Fragments Core",
+  );
+  return { components, client };
+};
+
+app.elements = {
+  viewer: () =>
+    html`<top-viewer><top-viewer-tools></top-viewer-tools></top-viewer>`,
+};
+
+app.base = "viewer";
+app.layouts = {
+  main: {
+    label: "Main",
+    icon: "solar:home-bold",
+    template: `"_" 1fr / 1fr`,
+  },
+};
+app.layout = "main";
+
+// dropMessage as a function is evaluated at render time so it can read live state.
+// Here it reads how many models are already loaded and adjusts the hint text.
+let loadedCount = 0;
+app.dropMessage = () =>
+  loadedCount === 0
+    ? "Drop an IFC or FRAG file to load your first model"
+    : `Drop a file to add to the ${loadedCount} loaded model${loadedCount === 1 ? "" : "s"}`;
+
+// top:files-dropped fires when the user drops files onto the window.
+// e.detail.files is a File[]. Handle upload, load, or validation here.
+app.addEventListener("top:files-dropped", (e) => {
+  const { files } = (e as CustomEvent<{ files: File[] }>).detail;
+
+  const supported = files.filter(
+    (f) => f.name.endsWith(".ifc") || f.name.endsWith(".frag"),
+  );
+
+  // Dispatch top:notification to surface feedback without a reference to top-app.
+  if (!supported.length) {
+    app.dispatchEvent(
+      new CustomEvent("top:notification", {
+        bubbles: true,
+        composed: true,
+        detail: { message: "No supported files dropped", type: "warning" },
+      }),
+    );
+    return;
+  }
+
+  loadedCount += supported.length;
+  app.dispatchEvent(
+    new CustomEvent("top:notification", {
+      bubbles: true,
+      composed: true,
+      detail: {
+        message: `${supported.length} file${supported.length === 1 ? "" : "s"} received`,
+        type: "success",
+        description: supported.map((f) => f.name).join(", "),
+      },
+    }),
+  );
+});
+
+app.addEventListener("top:app-ready", (e) => {
+  const { app: readyApp } = (e as AppReadyEvent).detail;
+  readyApp.showToast("App ready — try dropping an IFC or FRAG file", "info");
+});
+
+const container = document.getElementById("that-open-app") ?? document.body;
+container.appendChild(app);
+document.body.style.margin = "0";

package/src/built-in/UIManager/src/app/examples/FloatingLayout/example.ts

@@ -1,90 +1,90 @@
-/* MD
-  ## Floating layout
-  ---
-  Developers building BIM coordination tools often want the 3D model to fill the
-  entire window while control panels float above it — but standard grid layouts
-  give every area equal standing, shrinking the viewer into one cell and leaving
-  visible seams between it and the panels.
-
-  top-app supports a floating mode where one element is mounted as an absolute
-  background that fills the container edge-to-edge, and all other layout areas
-  render as a transparent overlay on top of it with independent pointer events.
-
-  This tutorial covers assigning the viewer as the absolute background of the app;
-  defining an overlay layout where a side panel floats above the viewer without
-  sharing grid space; and annotating why the base element is excluded from the
-  layout template.
-
-  By the end, you'll have a full-screen 3D viewer with a floating side panel
-  hovering above it, with the model filling the entire window and the panel
-  receiving its own pointer events.
-*/
-
-import { html } from "lit";
-import * as THREE from "three";
-import * as OBC from "@thatopen/components";
-import * as OBF from "@thatopen/components-front";
-import * as FRAGS from "@thatopen/fragments";
-import * as BUI from "@thatopen/ui";
-import { PlatformClient, UIManager } from "@thatopen/services";
-import type { App } from "../../index";
-
-const client = PlatformClient.fromPlatformContext();
-const { components } = (await client.setup(
-  { OBC, OBF, BUI, THREE, FRAGS },
-  { uuid: UIManager.uuid },
-)) as { components: OBC.Components };
-components.get(UIManager).init();
-
-const app = document.createElement("top-app") as unknown as App;
-
-app.setup = (waitUntil) => {
-  waitUntil(
-    (async () => {
-      const fragments = components.get(OBC.FragmentsManager);
-      const workerUrl = await FRAGS.FragmentsModels.getWorker();
-      fragments.init(await FRAGS.toClassicWorker(workerUrl), {
-        classicWorker: true,
-      });
-    })(),
-    "Fragments Core",
-  );
-  return { components, client };
-};
-
-app.elements = {
-  // "viewer" is referenced by app.base — rendered as a position:absolute layer
-  // behind all layout content so it fills the container edge-to-edge.
-  viewer: () =>
-    html`<top-viewer><top-viewer-tools></top-viewer-tools></top-viewer>`,
-
-  // Panels declared here appear in the floating content grid on top of the viewer.
-  // Their container has pointer-events: none; each child re-enables them individually.
-  panel: () => html`
-    <bim-panel>
-      <bim-panel-section label="Models" icon="solar:layers-bold">
-        <bim-label>Load models here</bim-label>
-      </bim-panel-section>
-    </bim-panel>
-  `,
-};
-
-// Setting app.base to an element key mounts that element as the absolute background.
-// Layout templates then only list the floating overlay areas — not the base element.
-// Without app.base, every area in the template is a peer grid cell (inline mode).
-app.base = "viewer";
-
-app.layouts = {
-  main: {
-    label: "Main",
-    icon: "solar:home-bold",
-    // Only overlay areas appear here. "viewer" is not listed because it is the base.
-    template: `"panel" 1fr / 22rem`,
-  },
-};
-
-app.layout = "main";
-
-const container = document.getElementById("that-open-app") ?? document.body;
-container.appendChild(app);
-document.body.style.margin = "0";
+/* MD
+  ## Floating layout
+  ---
+  Developers building BIM coordination tools often want the 3D model to fill the
+  entire window while control panels float above it — but standard grid layouts
+  give every area equal standing, shrinking the viewer into one cell and leaving
+  visible seams between it and the panels.
+
+  top-app supports a floating mode where one element is mounted as an absolute
+  background that fills the container edge-to-edge, and all other layout areas
+  render as a transparent overlay on top of it with independent pointer events.
+
+  This tutorial covers assigning the viewer as the absolute background of the app;
+  defining an overlay layout where a side panel floats above the viewer without
+  sharing grid space; and annotating why the base element is excluded from the
+  layout template.
+
+  By the end, you'll have a full-screen 3D viewer with a floating side panel
+  hovering above it, with the model filling the entire window and the panel
+  receiving its own pointer events.
+*/
+
+import { html } from "lit";
+import * as THREE from "three";
+import * as OBC from "@thatopen/components";
+import * as OBF from "@thatopen/components-front";
+import * as FRAGS from "@thatopen/fragments";
+import * as BUI from "@thatopen/ui";
+import { PlatformClient, UIManager } from "@thatopen/services";
+import type { App } from "../../index";
+
+const client = PlatformClient.fromPlatformContext();
+const { components } = (await client.setup(
+  { OBC, OBF, BUI, THREE, FRAGS },
+  { uuid: UIManager.uuid },
+)) as { components: OBC.Components };
+components.get(UIManager).init();
+
+const app = document.createElement("top-app") as unknown as App;
+
+app.setup = (waitUntil) => {
+  waitUntil(
+    (async () => {
+      const fragments = components.get(OBC.FragmentsManager);
+      const workerUrl = await FRAGS.FragmentsModels.getWorker();
+      fragments.init(await FRAGS.toClassicWorker(workerUrl), {
+        classicWorker: true,
+      });
+    })(),
+    "Fragments Core",
+  );
+  return { components, client };
+};
+
+app.elements = {
+  // "viewer" is referenced by app.base — rendered as a position:absolute layer
+  // behind all layout content so it fills the container edge-to-edge.
+  viewer: () =>
+    html`<top-viewer><top-viewer-tools></top-viewer-tools></top-viewer>`,
+
+  // Panels declared here appear in the floating content grid on top of the viewer.
+  // Their container has pointer-events: none; each child re-enables them individually.
+  panel: () => html`
+    <bim-panel>
+      <bim-panel-section label="Models" icon="solar:layers-bold">
+        <bim-label>Load models here</bim-label>
+      </bim-panel-section>
+    </bim-panel>
+  `,
+};
+
+// Setting app.base to an element key mounts that element as the absolute background.
+// Layout templates then only list the floating overlay areas — not the base element.
+// Without app.base, every area in the template is a peer grid cell (inline mode).
+app.base = "viewer";
+
+app.layouts = {
+  main: {
+    label: "Main",
+    icon: "solar:home-bold",
+    // Only overlay areas appear here. "viewer" is not listed because it is the base.
+    template: `"panel" 1fr / 22rem`,
+  },
+};
+
+app.layout = "main";
+
+const container = document.getElementById("that-open-app") ?? document.body;
+container.appendChild(app);
+document.body.style.margin = "0";