From 0aa59c13af65beeae104662593b21ba4d8a37789 Mon Sep 17 00:00:00 2001 From: Christian Kolset Date: Sat, 1 Aug 2026 19:06:36 -0600 Subject: Rename LabDAQ → LabUI and overhaul plugin system MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Branding: - Rename app, window title, file extension (.labdaq → .labui), user data dirs (~/.labui/), spec file (labdaq.spec → labui.spec), and APP_NAME throughout all source, docs, and config files Plugin system: - Plugins no longer bundled in the PyInstaller build — installed at runtime by users via Settings → Plugins → Install Plugin (zip) - PluginManager now takes user_dir + extra_scan_dirs; user plugins live in ~/.labui/plugins/, dev scan additionally covers project plugins/ - install_from_zip / uninstall / is_user_installed added to PluginManager - vendor/ dir inside plugin zips: prepended to sys.path at load time so plugins can ship their own deps without requiring pip on end-user machine - source_url field in manifest.json: shown as Download button in the missing-plugins dialog when a profile requires an absent plugin - Frozen-app pip install now targets ~/.labui/plugin_packages/ using a real system Python (sys.executable is the exe in frozen builds) Profile loading: - Profile now stores plugins_manifest snapshot (id, name, version, source_url) alongside plugins_enabled - On load, missing or dep-broken plugins trigger MissingPluginsDialog before the rest of the profile is applied; user can install from zip or download via source_url in-dialog, or cancel the load - Plugin reconciliation only enables installed plugins — missing ones are not written to enabled.json UI: - Version label added to status bar (bottom-right, muted colour) - Settings → Plugins tab: Install Plugin… button, per-plugin Remove button for user-installed plugins, live list refresh after install/remove Docs: - New docs/building.md covers the full release pipeline - docs/plugin-development.md updated for new install flow, vendoring, source_url, profile behaviour, and distribution instructions Co-Authored-By: Claude Sonnet 4.6 --- scripts/release/repo_release.py | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'scripts/release/repo_release.py') diff --git a/scripts/release/repo_release.py b/scripts/release/repo_release.py index a3c8d03..d50e458 100644 --- a/scripts/release/repo_release.py +++ b/scripts/release/repo_release.py @@ -1,14 +1,14 @@ """ scripts/release/repo_release.py -Run after every `pyinstaller labdaq.spec` build, from anywhere (paths are +Run after every `pyinstaller labui.spec` build, from anywhere (paths are made absolute below before the working directory changes). Packages the -freshly built dist/LabDAQ bundle as a new signed tufup target. +freshly built dist/LabUI bundle as a new signed tufup target. Prerequisites: - repo_init.py has been run once already (./repository and ./keystore exist) - core/version.py has been bumped to the new version - - dist/LabDAQ/ exists (pyinstaller labdaq.spec has just been run) + - dist/LabUI/ exists (pyinstaller labui.spec has just been run) After this completes, see README.md in this directory for how to publish the updated ./repository/metadata and ./repository/targets files to the @@ -21,7 +21,7 @@ from pathlib import Path _THIS_DIR = Path(__file__).resolve().parent _REPO_ROOT = _THIS_DIR.parent.parent -_DIST_DIR = _REPO_ROOT / "dist" / "LabDAQ" +_DIST_DIR = _REPO_ROOT / "dist" / "LabUI" # Import core.version before changing cwd — needs the repo root on sys.path, # which won't be true anymore once we chdir into scripts/release below. @@ -38,7 +38,7 @@ os.chdir(_THIS_DIR) def main(): if not _DIST_DIR.is_dir(): raise SystemExit( - f"{_DIST_DIR} not found — run `pyinstaller labdaq.spec` from the " + f"{_DIST_DIR} not found — run `pyinstaller labui.spec` from the " f"repo root first." ) -- cgit v1.2.3