pptx-angular-viewer 1.1.62 → 1.1.63

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to this project are documented here.
 This file is generated from [Conventional Commits](https://www.conventionalcommits.org)
 by [git-cliff](https://git-cliff.org); do not edit it by hand.
 
+## [1.1.62](https://github.com/ChristopherVR/pptx-viewer/releases/tag/pptx-angular-viewer@1.1.62) - 2026-07-03
+
+### Documentation
+
+- **vue,angular:** Correct stale parity-tracker claims (by @ChristopherVR) ([54c4f05](https://github.com/ChristopherVR/pptx-viewer/commit/54c4f0540e33692d82f961c96d8a1818c8678751))
+
 ## [1.1.59](https://github.com/ChristopherVR/pptx-viewer/releases/tag/pptx-angular-viewer@1.1.59) - 2026-07-03
 
 ### Features

package/README.md

@@ -194,8 +194,7 @@ polish/cosmetic, not behavioural gaps:
   image otherwise (the same as the React package).
 
 The `pptx-viewer-core` engine parses all element data, so you can access it from
-the model even where the UI does not expose it yet. Progress and design notes live
-in [`PORTING.md`](./PORTING.md).
+the model even where the UI does not expose it yet.
 
 ## Build (contributing)
 

package/fesm2022/pptx-angular-viewer.mjs

@@ -21862,7 +21862,7 @@ function connectorBendFraction(element) {
  * for straight connectors (which render as a `<line>`). Endpoints are already
  * flip-adjusted by the caller.
  *
- * Viewer-first approximation (full A* routing is a TODO, see PORTING.md):
+ * Viewer-first approximation (full A* routing is a TODO):
  *  - **bent**: orthogonal elbow polyline. `bentConnector2` is a single L-bend;
  *    `bentConnector3..5` route through a vertical mid-axis at `bend`.
  *  - **curved**: `curvedConnector2` is a quadratic Bezier; `curvedConnector3..5`
@@ -34589,10 +34589,9 @@ function segmentFrameCount(durationMs, fps) {
  *   - loader:    load-pipeline helpers (media/image collection, guides).
  *   - types:     CanvasSize, CollaborationConfig, CollaborationRole.
  *   - constants: scalar viewer defaults (canvas size, fallback colours).
- *
- * Roadmap (see packages/angular/PORTING.md and packages/vue/PORTING.md):
- *   color resolution, geometry/clip-paths, connector routing, animation
- *   timeline engine, table-merge math, morph matching, export data helpers.
+ *   - render:    the bulk of the shared logic (colour/geometry/connector/
+ *                animation/table/chart/text/effects/collaboration/i18n).
+ *   - export:    export data helpers.
  */
 
 /**
@@ -39467,10 +39466,9 @@ i0.ɵɵngDeclareClassMetadata({ minVersion: "12.0.0", version: "22.0.5", ngImpor
  * Provide it at the component level so its lifetime tracks the host viewer:
  * `@Component({ providers: [LoadContentService] })`.
  *
- * This is the viewer-first subset; the React hook also populated ~25 extra
- * pieces of presentation metadata (sections, custom shows, embedded fonts,
- * digital signatures, …). Those are tracked in PORTING.md and added here as
- * the corresponding features are ported.
+ * Originally the viewer-first subset of the React hook; the extra pieces of
+ * presentation metadata (sections, custom shows, embedded fonts, digital
+ * signatures, …) were added alongside the corresponding features.
  */
 class LoadContentService {
     /** Parsed slides (with image Blob URLs patched in). */
@@ -40881,7 +40879,7 @@ i0.ɵɵngDeclareClassMetadata({ minVersion: "12.0.0", version: "22.0.5", ngImpor
  * building the SmartArt element payload from a chosen preset, hierarchy
  * parenting) is delegated to the pure functions below so they can be unit-tested
  * in plain vitest (the Angular package's vitest setup has no Angular compiler,
- * so component / TestBed tests are not available - see PORTING.md).
+ * so component / TestBed tests are not available).
  *
  * The preset catalogue itself is the framework-agnostic, vendored
  * `pptx-viewer-shared` source of truth (`render/smart-art-presets`), consumed
@@ -46680,7 +46678,7 @@ function describeSmartArtBounds(layout) {
  * `editor-insert.ts` (sourced from `pptx-viewer-core`). Keeping this logic out of
  * the component lets it be unit-tested in plain vitest (the Angular package's
  * vitest setup has no Angular compiler, so TestBed component tests are not
- * available - see PORTING.md).
+ * available).
  *
  * Mirrors the React inspector:
  *   packages/react/src/viewer/components/inspector/SmartArtPropertiesPanel.tsx
@@ -52369,7 +52367,7 @@ i0.ɵɵngDeclareClassMetadata({ minVersion: "12.0.0", version: "22.0.5", ngImpor
  * Compound (double/triple) lines render as parallel strands and line caps map
  * from `a:ln/@cap`; both derive from the shared connector geometry.
  *
- * Not yet ported (TODO, see PORTING.md): line shadows/glow.
+ * Not yet ported (TODO): line shadows/glow.
  */
 class ConnectorRendererComponent {
     element = input.required(/* @ts-ignore */
@@ -52796,7 +52794,8 @@ function buildDuotoneFilter(element) {
  * and paint text boxes, basic preset shapes, images, and image/gradient fills
  * (the latter via the parser's prebuilt CSS gradient string). Advanced visuals
  * (the structured gradient builder, pattern fills, custom geometry clip-paths,
- * shadows, 3D, image effects, text warp) are tracked in PORTING.md.
+ * shadows, 3D, image effects, text warp) are handled by the shared render
+ * modules (`pptx-viewer-shared`) consumed from the renderer components.
  *
  * Long term the *logic* here is a shared-extraction candidate; only the
  * return type (CSS map shape) differs per framework, so a future refactor
@@ -53234,7 +53233,7 @@ function buildInkContainerStyle(element, zIndex) {
  * radii follow the per-point pressure, matching React's `renderInk`. Strokes
  * without pressure variation degrade to a plain constant-width `<path>`.
  *
- * Not ported (TODO, see PORTING.md): ink replay animation and the
+ * Not ported (TODO): ink replay animation and the
  * highlighter/eraser tool blend modes.
  *
  * All non-trivial pure computation lives in `ink-renderer-helpers.ts` (no
@@ -54629,7 +54628,7 @@ i0.ɵɵngDeclareClassMetadata({ minVersion: "12.0.0", version: "22.0.5", ngImpor
  * its text directly on the diagram. Everything that can be expressed as a pure
  * function lives here so it can be unit-tested in plain vitest (the Angular
  * package's vitest setup has no Angular compiler, so component/TestBed tests are
- * not available - see PORTING.md). The component
+ * not available). The component
  * (`smart-art-renderer.component.ts`) stays thin: it owns only the edit-state
  * signal, the positioned `<textarea>`, and the call into the existing commit
  * path (`EditorStateService.updateElement`, the same channel the inspector's
@@ -57294,8 +57293,7 @@ function runStyleFromSegment(seg) {
  * ElementRendererComponent: Angular port of the React `ElementRenderer.tsx`
  * and the Vue `ElementRenderer.vue`.
  *
- * Renders a single slide element by its `type` discriminant (viewer-first
- * subset):
+ * Renders a single slide element by its `type` discriminant:
  *  - `text` / `shape`    → positioned box with fill/stroke + rich text + effects
  *  - `connector`         → SVG straight/bent/curved connector
  *  - `chart`             → inline-SVG chart (bar/line/area/pie/scatter)
@@ -57303,14 +57301,13 @@ function runStyleFromSegment(seg) {
  *  - `smartArt`          → SVG drawing-shapes / node-text fallback
  *  - `ink`               → SVG ink strokes
  *  - `ole`               → embedded-object preview / icon
- *  - `model3d`           → poster / placeholder (no three.js)
+ *  - `model3d`           → interactive three.js scene when the optional
+ *                          `three` peer is present, else poster / placeholder
  *  - `zoom`              → slide/section zoom thumbnail
  *  - `picture` / `image` → `<img>`
  *  - `media`             → native `<video>`/`<audio>` playback, poster fallback
  *  - `group`             → recursive children (self-referencing selector)
- *  - everything else     → labelled placeholder (TODO, see PORTING.md)
- *
- * Interaction (selection, resize, inline editing) is not yet ported.
+ *  - everything else     → labelled placeholder (defensive fallback)
  */
 class ElementRendererComponent {
     element = input.required(/* @ts-ignore */
@@ -58196,8 +58193,8 @@ function plainText(el) {
  * Renders the active slide as a fixed-size stage scaled by `zoom`, with each
  * element absolutely positioned. When `editable`, supports click-to-select
  * (event delegation), selection outlines, and pointer drag-to-move / resize
- * handles. Rulers, grid, guides, marquee, and collaboration overlays are
- * tracked in PORTING.md.
+ * handles, plus the rulers, grid, guides, marquee, and collaboration
+ * overlays.
  */
 class SlideCanvasComponent {
     slide = input(undefined, /* @ts-ignore */
@@ -71431,7 +71428,6 @@ const GRID_GAP = 16;
  * Escape or clicking the ✕ button emits `closed`.
  *
  * Viewer-first scope: no drag-reorder, no context menu, no section grouping.
- * Those features are tracked in PORTING.md.
  *
  * Usage:
  * ```html
@@ -76999,10 +76995,9 @@ const ZOOM_MAX = 3;
  * and Vue `PowerPointViewer.vue`.
  *
  * Top-level orchestrator that loads `.pptx` bytes and renders the slides with
- * navigation and zoom. This is the viewer-first milestone of the port: the
- * React component additionally composes a full editor (toolbar, inspector
- * panels, dialogs, presentation mode, collaboration, export). The roadmap and
- * per-area status live in `packages/angular/PORTING.md`.
+ * navigation and zoom, composing the full editor (toolbar, inspector panels,
+ * dialogs, presentation mode, collaboration, export) like its React and Vue
+ * counterparts.
  *
  * Conventions vs. React/Vue:
  *  - React `forwardRef` handle / Vue `defineExpose` → public {@link getContent}