pptx-angular-viewer 1.1.50 → 1.1.51

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -12,7 +12,7 @@ as real HTML and CSS with full editing and export support.
12
12
 
13
13
  The rendering is done by the framework-agnostic [`pptx-viewer-core`](https://www.npmjs.com/package/pptx-viewer-core) engine (also published as [`@christophervr/pptx-viewer`](https://www.npmjs.com/package/@christophervr/pptx-viewer) -- the two names are identical releases), which turns a `.pptx` file into a structured slide model. This package is the Angular layer that draws that model on screen, and the engine is **bundled in**, so you install just one package.
14
14
 
15
- <samp>**[▶️ Try the live demo](https://christophervr.github.io/pptx-viewer/demo-angular/)** · **[📦 npm](https://www.npmjs.com/package/pptx-angular-viewer)** · **[📖 Full docs](https://christophervr.github.io/pptx-viewer/)**</samp>
15
+ <samp>**[▶️ Try the live demo](https://christophervr.github.io/pptx-viewer/demo-angular/)** · **[📦 npm](https://www.npmjs.com/package/pptx-angular-viewer)** · **[📖 Full docs](https://christophervr.github.io/pptx-viewer/)** · **[🧩 Core SDK](https://www.npmjs.com/package/pptx-viewer-core)**</samp>
16
16
 
17
17
  > **[▶️ Try the live demo](https://christophervr.github.io/pptx-viewer/demo-angular/)**: open a `.pptx` and render it in your browser, no install required.
18
18
 
@@ -164,19 +164,17 @@ async save() {
164
164
  ## Limitations
165
165
 
166
166
  The Angular package has reached functional parity with the React package: all 11
167
- element types render; the full Tailwind 4 Office ribbon is wired; editing,
168
- presentation, export, collaboration, comments, and mobile chrome all work. The
169
- remaining items are polish/cosmetic, not behavioural gaps:
170
-
171
- - **Master/template editing** - Editing routes to slide elements only; edits to
172
- the slide master or layout template are not yet wired.
173
- - **Eyedropper on Firefox/Safari** - Angular uses the native `EyeDropper` API;
174
- React adds a rasterize-and-sample fallback for browsers that don't support it.
167
+ element types render; the full Tailwind 4 Office ribbon is wired; editing
168
+ (including slide master/layout template editing), presentation, export,
169
+ collaboration, comments, and mobile chrome all work. The remaining items are
170
+ polish/cosmetic, not behavioural gaps:
171
+
175
172
  - **Pixel-level cosmetic differences** - Some toolbar controls are not pixel-
176
173
  identical to their React counterparts (spacing, split-button affordances,
177
174
  dropdown chrome).
178
- - **3D models** - GLB/GLTF models fall back to their poster image (requires
179
- optional Three.js peer dependencies).
175
+ - **3D models need the Three.js peer** - GLB/GLTF models render interactively when
176
+ the optional `three` peer dependency is installed, and fall back to their poster
177
+ image otherwise (the same as the React package).
180
178
 
181
179
  The `pptx-viewer-core` engine parses all element data, so you can access it from
182
180
  the model even where the UI does not expose it yet. Progress and design notes live