Getting started with PlatinumSDK Runtime

What you are installing

The Runtime supplies common application services and user-interface behavior. An application brings its own documents, scripts, assets and features; the Runtime supplies the shared machinery. Installing it is not the same as replacing Windows, macOS or Linux, and it does not make every ordinary executable a Platinum application.

Use a Runtime distribution for your operating system and architecture. Its release notes and installed application list are authoritative about which companion applications are included. This repository is a development checkout; it does not yet provide a verified universal public installer or a production download URL. Do not type a guessed installation command from another version's documentation.

Animator and Video Editor have suite preview applications; a preview is not a complete production editor. PlatinumHR is a separate business application using the SDK, not a required Runtime component. Schema, state-worker and authority services are supporting components, not windows you need to open during ordinary work.

Default online services

Winnitude is the default provider. PlatinumAuth supplies account/session identity; PlatinumSHL supplies licensing, verification and registered configuration integrity/recovery. The Runtime verifies the expected service using authenticated HTTPS and a fresh PGP signature checked against its pinned Winnitude signing key. Optional cloud services can be disabled; local/offline trust choices remain available. See security.

Your first session

1. Open the Runtime or a bundled application using the distribution's installed shortcut. Review the installed version, publisher and available services before accepting unfamiliar software.
2. Choose your online-services preference when the installed host offers it. Offline operation and imported signed verification data are distinct from having no verification information. Cloud account sign-in is needed only for the selected account-backed service, not as a universal explanation for local file editing.
3. Open Platinum Write, create a document, type a few lines, and save it to a folder you choose. An explicit file save is different from automatic recovery or a Live Object acknowledgment.
4. Open a second document. Move the windows so both pages are visible. Float a formatting tool, then switch to another application: ordinary floating tools disappear while your document remains visible.
5. Dock the tool if you prefer a single frame. In versions with the Pin control, pin a floating tool to keep it visible when you switch away.
6. Open Platinum Files and browse the saved document's folder. Use Space for a preview or double-click a supported document to edit it. Opening an ordinary executable uses the host's rules; it does not inherit PLA protection.

Open, edit and save

In Write, use File > Open and File > Save, or Ctrl+O and Ctrl+S on Windows. New/Open creates independent document windows in the native workspace. Web versions can use tabs or panels inside one browser canvas; a browser may reserve some shortcuts.

Use .platinum for the SDK's native rich document representation. ODT is a supported subset, and Markdown is useful for text, headings, lists, code and ordinary tables. Markdown cannot preserve every page, font, color or merged-cell feature. Check a converted document before replacing your only copy. Save As or export to a separate file when trying another format.

Recovery helps reopen work after interruption. It is not a backup of every historical edit, a guarantee that a file export completed, or a promise to preserve every app's cursor/undo/Play state. If a save reports failure or an uncertain outcome, keep the window open and inspect the error. Do not assume a gray pending indicator means the disk or server has acknowledged it.

Useful controls

The focused control can own a shortcut: Ctrl+I while editing text is not the same operation as Get Info in a folder window. Platform-specific differences and unsupported gestures are described in Files.

A comfortable workspace

Keep the main view large enough to read at a glance. Put short-lived tools near the work they affect. Dock tools you use continuously; float tools you use across documents; pin a tool only when keeping it visible helps. Closing a tool hides that tool; closing a dirty document may ask what to do with unsaved work.

If a control looks missing, refocus the application, look in its View/Window menu, and check whether the tool is docked, disabled, or on another monitor. Hiding on application unfocus is intentional. If connection or permission status is unclear, open the relevant application's status/settings rather than repeatedly retrying a destructive operation.

Development checkout only

These existing launchers run source-built native apps; they are not public end-user installation instructions:

powershell -ExecutionPolicy Bypass -File scripts/run-native.ps1
powershell -ExecutionPolicy Bypass -File scripts/run-files.ps1
powershell -ExecutionPolicy Bypass -File scripts/run-game-creator.ps1

Follow the repository's compiler coordination and graphical incident hold before using them in this shared checkout. This manual-writing branch does not authorize restarting the graphical programs during that hold.