OpenSite/Downloads
Jump to navigation
Jump to search
Get the right OpenSite build before following a tutorial.
Download availability
Public downloads are not yet available for this development version. OpenSite 0.0.1 is an internal development build. No public application release or verified installer is provided for this documented build. Use an authorized development package until a public release is supplied.
If you have been given an authorized development package, use OpenSite/Installation. Otherwise obtain availability information from the product owner through your established BathAfrica contact.
Choose the right package
| Package | Who should use it | What to check |
|---|---|---|
| Windows desktop development package | Users following the graphical lessons | The matching GUI extensions, Qt platform files and embedded runtime are included. |
| Headless Python host | Users running supplied scripts without the desktop | The matching embedded Python runtime is included; there is no viewport. |
| Native SDK | Extension developers | Compiler/SDK compatibility and dependency prefix match the host. |
| Debug build | Developers diagnosing the application | Requires its matching Debug runtime and developer environment; it is not a general user download. |
Before installing
- Read OpenSite/System requirements and OpenSite/Licensing.
- Keep the package version and build identifier with your project records.
- If the distributor supplies a checksum, compare it using the distributor’s instructions. No checksum is invented by this documentation.
- Extract or install the complete package. Copying only an executable leaves out required libraries and extensions.
- Start with a practice document and follow OpenSite/Guides/First desktop session.
For authorized developers
The repository has build presets and an installed SDK workflow. See OpenSite/Guides/Build OpenSite on Windows. Source access is not a public binary download and does not grant an open-source licence.
Updates
See OpenSite/Guides/Update OpenSite and OpenSite/Release notes. Document format compatibility matters more than the unchanged development product number alone.
