Export & Publish: package contents, full export, and current page
Export & Publish is the final step that turns your PPT pages into a runnable screen package on the host. The Export group on the HQ VISU ribbon tab has three buttons: Export HTML (export the whole PPT as one screen package), Current Page (export only the current page, for small page-level updates), and Export History (manage the recent export folders on this machine). The output is a self-contained folder holding the page HTML, per-page SVG graphics, JS (page data and scripts), JSON (global and per-page config data), and IMG images. The official rule is one PPT equals one screen package: one business screen is one PPT and may contain one main page plus a few sub-pages in the same package. After export, upload the folder to HQControl, which manages and runs it by screen code (screenCode). The host is a different machine from your dev box, and you publish a screen package, not your local PPT file path.
Feature
Feature: Export & Publish: package contents, full export, and current page
Export your finished PPT into one HQ VISU screen package (HTML + SVG + JS + JSON + IMG), then upload it to the HQControl host to run. One PPT equals one screen package; replacing the whole package is the cleanest update.
What it is and what it is for
Export & Publish is the final step that turns your PPT pages into a runnable screen package on the host. The Export group on the HQ VISU ribbon tab has three buttons: Export HTML (export the whole PPT as one screen package), Current Page (export only the current page, for small page-level updates), and Export History (manage the recent export folders on this machine). The output is a self-contained folder holding the page HTML, per-page SVG graphics, JS (page data and scripts), JSON (global and per-page config data), and IMG images. The official rule is one PPT equals one screen package: one business screen is one PPT and may contain one main page plus a few sub-pages in the same package. After export, upload the folder to HQControl, which manages and runs it by screen code (screenCode). The host is a different machine from your dev box, and you publish a screen package, not your local PPT file path.
How to use it: the three buttons and package contents
Pick an export mode in the Export group; choose the target folder from history or create a new one. A typical exported package looks like this (HTML stays in the package root, generated styles and scripts are centralized into css/ and js/):
Export HTML: full-package export. Required whenever you changed the global script, global JSON, shared styles, or added/deleted/renamed pages or changed the navigation structure.
Current Page: exports only the current page's resources. Suitable only for page-level changes like current-page graphics / current-page script / current-page JSON / current-page component behaviors.
Export History: view recent export folders, delete a selected folder, or clear all history. It only cleans the local records and does not delete your real exported files on disk.
Package contents: <page>.html (pages; the first page's file name follows the export file name configured for that page in PPT), <page>.svg (per-page graphics), css/app.css (shared styles), js/<page>.js (page data and scripts), json/global.json and json/pages/<page>.json (config data), img/ (images).
Choose the export mode by the scope of your change, then upload to HQControl:
Changed only one page's graphics/script/data in a screen: open that PPT, export with Current Page, and do a page-level replace.
Changed global script, global JSON, shared styles, or added/deleted/renamed a page or changed navigation: export with Export HTML (Current Page will not carry these changes).
Official publish: export the full package, upload to the host, let the host replace the package as a whole, and optionally keep one backup. The host manages by screenCode; do not pile loose files from different export dates into one folder over time.
Boundaries and common mistakes
A few real pitfalls:
If the PPT has unsaved changes, export shows a prompt; prefer Save and Export. Choosing Export Without Saving may produce files that do not match your latest edits.
Adding, deleting, or renaming pages is a package-level change: do not use Current Page, use a full export, otherwise the host keeps stale pages and links open removed pages.
Delete/Clear in Export History only clears local history records; it never removes the real export folder.
For official delivery, use qtedit.openPage for same-package jumps and qtedit.openScreen for cross-package jumps; do not use relative disk paths like ../../xxx.html, because the host package path can change and relative paths break.
Figure 1: Export HTML
Choose the export folder or pick a recent location to export the whole PPT as one screen package.
