Skip to content

OXT-Beyond 0.2.7 “Make It So”

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 10 Nov 02:13
· 203 commits to main since this release
v0.2.7
8451629
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

OXT-Beyond 0.2.7 for Windows, macOS and Linux.

Download from the release page, under Assets:

  • Windows 10 or later (x64): OXT-Beyond-0.2.7-win-x86_64-setup.exe
  • macOS 11 or later: OXT-Beyond-0.2.7-mac-universal.dmg
  • Linux x86-64 (glibc 2.31 or later): OXT-Beyond-0.2.7-linux-x86_64.tar.xz (64-bit ARM: -linux-arm64.tar.xz)

The Mac app is not notarized, so macOS blocks it until you allow it (see below).

The bundled xTalk extensions need macOS 10.15 or later on an Intel Mac.

The notes below list every file, what each platform needs, and how to check downloads.

Windows (x64)

Needs 64-bit Windows 10 or later.

  • OXT-Beyond-0.2.7-win-x86_64-setup.exe: the installer. It installs for all users or only for you, and adds a Start menu shortcut and the .oxtstack and .oxtscript file types.
  • OXT-Beyond-0.2.7-win-x86_64-portable.zip: the same program folder without an installer. Extract it and run OXT-Beyond.exe.
  • OXT-Beyond-0.2.7-win-x86_64-binaries.zip: the engine, externals and tools as built (win-x86_64-bin), without debug symbols, plus the licence files.
  • OXT-Beyond-0.2.7-win-x86_64-symbols.zip: debug symbols (*.pdb) for the binaries.
  • OXT-Beyond-0.2.7-win-x86_64-server.zip: OXT-Beyond Server, the server engine that runs .lc pages on a web server (see Server below).

The executables are not code-signed, so Windows SmartScreen may warn when they are run for the first time.

macOS (Apple Silicon and Intel)

One universal app, OXT-Beyond.app. It needs macOS 11 Big Sur or later, on Apple Silicon and on an Intel Mac (up to 0.2.7-rc.6.18, macOS 10.13 High Sierra on Intel; on macOS 10.15 Catalina it hung at launch). Standalones built with it need macOS 11 too.

  • OXT-Beyond-0.2.7-mac-universal.dmg: the disk image. Open it and drag OXT-Beyond onto the Applications folder next to it.
  • OXT-Beyond-0.2.7-mac-universal.zip: the same app, for scripted installs (ditto -x -k OXT-Beyond-0.2.7-mac-universal.zip /Applications).
  • OXT-Beyond-0.2.7-mac-universal-binaries.tar.xz: the build output (Release/, the Apple Silicon and Intel builds joined with lipo), signed ad hoc, without debug symbols and the build's own tools, plus the licence files.
  • OXT-Beyond-0.2.7-mac-universal-symbols.zip: debug symbols (.dSYM bundles) for the binaries.
  • OXT-Beyond-0.2.7-mac-universal-server.zip: OXT-Beyond Server, the server engine that runs .lc pages on a web server (see Server below).

Opening it for the first time. The app is signed ad hoc: it is not signed with an Apple Developer ID and not notarized by Apple, so macOS does not open a downloaded copy until you allow it. You do this once. On macOS 15 Sequoia and later:

  1. Double-click OXT-Beyond. macOS says that it was not opened; click Done (not Move to Trash).
  2. Open System Settings > Privacy & Security and scroll down to Security. Next to "OXT-Beyond was blocked to protect your Mac", click Open Anyway.
  3. Confirm with Open Anyway and your password (or Touch ID).

On macOS 13 and 14, Control-click the app in Finder, choose Open and then Open again; on macOS 12 and earlier, the button is in System Preferences > Security & Privacy > General. Or, in Terminal, remove the quarantine flag that the browser set on the download:

xattr -dr com.apple.quarantine /Applications/OXT-Beyond.app

The same command helps if macOS says the app "is damaged and can't be opened": that is how some macOS versions report an app that is not notarized.

Linux (x86-64)

Needs 64-bit x86 Linux with glibc 2.31 or later (Ubuntu 20.04, Debian 11, Fedora 32 or later) and an X11 desktop (on Wayland it runs through XWayland), with GTK 2: on Debian and Ubuntu the package libgtk2.0-0 (libgtk2.0-0t64 on Ubuntu 24.04 and Debian 13), on Fedora gtk2. The launcher names any library that is missing, with its package. The browser widget and revBrowser also need NSS, ALSA and a few more X11 libraries; without them the launcher turns the browser off. The bundled xTalk Suite extensions need nothing more: their libraries need glibc 2.28 at most and carry their own OpenSSL.

  • OXT-Beyond-0.2.7-linux-x86_64.tar.xz: the program folder OXT-Beyond-0.2.7. Extract it onto a Linux file system (not FAT, exFAT or a Windows drive) and run ./oxt-beyond in it, or run ./install.sh to install it for yourself: under ~/.local/share/oxt-beyond, with a menu entry, icons, the .oxtstack and .oxtscript file types and the command oxt-beyond, without administrator rights.
  • OXT-Beyond-0.2.7-linux-x86_64-binaries.tar.xz: the engine, externals and tools as built (linux-x86_64-bin), without debug symbols and the build's own tools, plus the licence files.
  • OXT-Beyond-0.2.7-linux-x86_64-symbols.tar.xz: debug symbols (.dbg files) for the binaries.
  • OXT-Beyond-0.2.7-linux-x86_64-server.zip: OXT-Beyond Server, the server engine that runs .lc pages on a web server (see Server below).

Linux (64-bit ARM)

For 64-bit ARM Linux with glibc 2.31 or later: a Raspberry Pi 3, 4 or 5 running a 64-bit system (Raspberry Pi OS 64-bit, Ubuntu), or an ARM server. It needs what the x86-64 package needs, and is installed the same way. New in 0.2.4-rc.2 and experimental. It has no browser widget or revBrowser, because CEF, the browser engine they use, has no Linux ARM build at the version OXT-Beyond uses; everything else, the player and the bundled xTalk Suite extensions included, is there, with the same glibc needs as on x86-64. It is built and tested on GitHub's ARM machines; no Raspberry Pi has run it in CI.

  • OXT-Beyond-0.2.7-linux-arm64.tar.xz: the program folder OXT-Beyond-0.2.7, as for x86-64.
  • OXT-Beyond-0.2.7-linux-arm64-binaries.tar.xz: the engine, externals and tools as built (linux-arm64-bin), without debug symbols and the build's own tools, plus the licence files.
  • OXT-Beyond-0.2.7-linux-arm64-symbols.tar.xz: debug symbols (.dbg files) for the binaries.
  • OXT-Beyond-0.2.7-linux-arm64-server.zip: OXT-Beyond Server, the server engine that runs .lc pages on a web server (see Server below).

Plugins for other xTalks

The xTalk Assistant and the xTalk MCP Bridge, which are built into OXT-Beyond, as extension packages for the IDEs of LiveCode Community 9, HyperXTalk and OpenXTalk. Install one with Tools > Extension Manager and its install button; it is then in Development > Plugins. OXT-Beyond does not need them. Experimental: checked as the Extension Manager checks a package, and not yet tried in every one of those IDEs (see tools/plugins/README.md).

  • OXT-Beyond-0.2.7-xtalk-assistant-plugin.lce: the xTalk Assistant.
  • OXT-Beyond-0.2.7-mcp-bridge-plugin.lce: the xTalk MCP Bridge, which lets Claude work in the IDE.

Web

The Stack Player: OXT-Beyond's web engine with a stack that opens any stack you give it, so that people can try stacks in a browser. Put the folder in the zip on any web server (browsers do not run it from a file on disk) and open its index.html; then open or drop a stack file, a folder or a .zip with a stack and its files. It carries every script library, the web externals (revXML, revZip, revDB with SQLite, revSpeech) and every widget and library extension that run in a browser, and keeps the stacks it opened, and what they save, in the browser for the next visit. New in 0.2.7-rc.3 and experimental; it opens HyperCard stacks as File > Import Stack does on the desktop, and the stacks on a Mac disk image (see tools/web-player/README.md).

  • OXT-Beyond-0.2.7-web-player.zip: the Stack Player's folder.

The web IDE: the OXT-Beyond IDE itself in a web page, run by its own engine built for the web, with the Script Editor, the Property Inspector, the Message Box, the Dictionary and the xTalk Academy. Extract the zip and, in its folder, double-click Start Web IDE.bat on Windows or run python3 serve.py on macOS and Linux (it needs Python 3); your browser then opens it at http://localhost:8000/. Or put the folder's files on any web server. Stacks you make are kept in the browser, and File > Download Stack gives you a copy. Experimental: building standalones and a few other things a browser cannot do are left out (see tools/web-ide/README.md).

  • OXT-Beyond-0.2.7-web-ide.zip: the web IDE's folder, with its README.

Server

OXT-Beyond Server runs xTalk scripts on a web server, as LiveCode Server did: a page is a .lc file with xTalk between <?lc and ?>, which reads the request in $_GET, $_POST, $_FILES, $_COOKIE and $_SERVER and answers with put header, put cookie and put. Each zip above holds the engine livecode-community-server with its externals (revDB, revXML, revZip) and drivers (SQLite, MySQL, PostgreSQL, ODBC) in the layout of LiveCode Community's server zips, so a web server set up for one runs it unchanged; its README.txt says how to set it up with Apache, IIS or nginx and what to change before putting it on the internet. New in 0.2.7-rc.6.15 and experimental. Every build runs it as a CGI program on each platform, and through Apache on Linux.

All platforms

  • OXT-Beyond-0.2.7-xtalk-sources.zip: every file of the bundled xTalk Suite extensions as this release took it from their repositories, with the manifest that pins them, so that the release can be rebuilt without those repositories (see BUILDING.md, "xTalk Suite extensions").
  • SHA256SUMS: SHA-256 checksums of all the files above.

Checking a download. Compare its SHA-256 with the line for it in SHA256SUMS:

  • Windows, in Command Prompt: certutil -hashfile OXT-Beyond-0.2.7-win-x86_64-setup.exe SHA256
  • macOS, in Terminal: shasum -a 256 OXT-Beyond-0.2.7-mac-universal.dmg
  • Linux, in the folder with the download and SHA256SUMS: sha256sum -c SHA256SUMS --ignore-missing

About this release

Made by the "Release" workflow (.github/workflows/release.yml) from commit 8451629, which builds and tests all three platforms and publishes the release only when every package has passed.

The programs include the xTalk Suite extensions (SodiumXT, TorrentXT, enetxt, DataChannelXT, Box2Dxt, CoinXT, OnionXT and NostrXT) in their Extensions folder, taken from their own repositories at the commits listed in Extensions/XTALK-EXTENSIONS.txt. The Windows packages include the Microsoft Visual C++ runtime DLLs that enetxt and Box2Dxt need; the macOS and Linux packages do not, so a Windows standalone built there with either of them needs the Visual C++ Redistributable on the PC that runs it.

Each package's engine, externals and tools are built from this repository, for Windows x86-64, for macOS (Apple Silicon and Intel, joined into universal files) and for Linux x86-64, and so are the standalone runtimes every package carries for Windows (x86-64 and x86) and Linux (x86-64 and x86), with the time zone library code for them. Every package also carries the HTML5 standalone runtime for web browsers, built from this repository into WebAssembly. The Android standalone runtime's Java layer is built from this repository too; its engines and its other files are taken unchanged from OpenXTalk Lite 1.15 (stock LiveCode 9.6.3 builds and files as Tom Perry shipped them; see THIRD-PARTY-NOTICES.md). A stack can ask for OXT-Beyond's own Android engine instead, built from this repository with a current NDK, with its "android,engine" standalone setting; LiveCode 9.6.3's engines stay the default. Only the macOS package has the macOS runtimes.

OXT-Beyond continues OpenXTalk Lite, started by Terry Little and developed by Tom Perry with contributions from the OpenXTalk community. It is based on LiveCode Community and licensed under the GNU GPL version 3.

What's Changed

Full Changelog: v0.2.7-rc.6.19...v0.2.7

Contributors

SethMorrowSoftware
Assets 26
Loading