PPTX2HTML Documentation

A theme file must include components in this exact order to function correctly:

1. Include mixins.scss: Import /css/theme/template/mixins.scss to access shared utility functions.
2. Include settings.scss: Import /css/theme/template/settings.scss. This declares the custom variables required by the template. You should perform your variable overrides immediately after this step.
3. Override: Specify your custom variables or add custom selectors and styles to override the default theme behavior.
4. Include theme.scss: Finally, import /css/theme/template/theme.scss. This template file uses the variables defined in the previous steps to generate the final CSS output.

// 1. Shared utilities
@import "../template/mixins.scss";

// 2. Variable declarations
@import "../template/settings.scss";

// 3. Overrides
$theme-primary-color: #ff0000;
.custom-selector {
  color: blue;
}

// 4. Final template generation
@import "../template/theme.scss";

PPTX2HTML supports the conversion of various PowerPoint elements into web-compatible formats. The following object types are supported:

• Text: Includes font size, font family, styles (bold, italic, underline), color, location, and hyperlinks.
• Pictures: Supports jpg/jpeg, png, and gif formats with location preservation.
• Graphs: Converts Bar charts, Line charts, Pie charts, and Scatter charts.
• Tables: Preserves location and size.
• Text Blocks: Converted to <div> elements, supporting horizontal/vertical alignment and single-color background colors, as well as borders (color, width, type, and strokeDasharray).
• Drawings: Converted to SVG, including simple blocks like rect, ellipse, and roundRect. Supports alignment, background color, and border properties.
• Groups/Multi-level Groups: Supports grouping with z-index (level) preservation.
• Theme/Layout: Supports PowerPoint themes and layouts.

The Multiplex plugin enables synchronized presentation states across multiple clients using Socket.io. It uses a secure handshake mechanism to prevent unauthorized state changes.

1. Token Acquisition: A client requests a token from the /token endpoint. The server returns a secret and a socketId (which is a Blowfish hash of the secret).
2. State Change: When a client wants to broadcast a state change (e.g., moving to a new slide), it emits a multiplex-statechanged event via Socket.io.
3. Security Validation: The payload must include the secret. The server re-hashes the provided secret and compares it to the socketId. If they match, the server broadcasts the data to all other connected sockets using the socketId as the target event name.

This ensures that only the client holding the valid secret for a specific session can trigger state updates for that session.

// Conceptual flow of state synchronization

// 1. Get token from server
// GET /token -> { "secret": "...", "socketId": "..." }

// 2. Emit state change with secret
// socket.emit('multiplex-statechanged', { 
//   secret: '...', 
//   slideNumber: 5, 
//   ... 
// });