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 --- core/updater.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'core/updater.py') diff --git a/core/updater.py b/core/updater.py index d22cd42..471ef0b 100644 --- a/core/updater.py +++ b/core/updater.py @@ -21,7 +21,7 @@ from typing import Optional from core.app_settings import app_data_dir from core.version import __version__ as CURRENT_VERSION -APP_NAME = "labdaq" +APP_NAME = "labui" _RELEASE_BASE_URL = "https://github.com/c-kolset/labUI-python/releases/download/updates/" METADATA_BASE_URL = _RELEASE_BASE_URL @@ -50,7 +50,7 @@ def _bootstrap_root_json(metadata_dir: Path) -> None: remotely on first use, by design (TUF's root of trust has to come from somewhere already trusted, not from the same server being verified). - So the copy bundled into the app (labdaq.spec bundles + So the copy bundled into the app (labui.spec bundles scripts/release/repository/metadata/root.json to "repository/metadata") has to be seeded into metadata_dir before the first Client is ever constructed on a given machine. sys._MEIPASS is where PyInstaller puts -- cgit v1.2.3