viewit/KX-Bridge-Release
9
13
Fork 6
Code Issues 4 Pull Requests Actions Packages Projects Releases 39 Wiki Activity

WIP: Theming #27

Manually merged
viewit merged 1 commits from hirnwunde/KX-Bridge-Release:master into master 2026-05-21 14:37:40 +02:00
Conversation 1 Commits 1 Files Changed 7 +3291 -3
hirnwunde commented 2026-05-21 02:18:24 +02:00
Contributor
Copy Link

Refactor: Introduce Theme Management System

  • Extract HTML/CSS/JS from Python into separate web/themes/default/ files
  • Enable UI customization without Python knowledge
# Refactor: Introduce Theme Management System - Extract HTML/CSS/JS from Python into separate `web/themes/default/` files - Enable UI customization without Python knowledge
hirnwunde added 1 commit 2026-05-21 02:18:24 +02:00
bump theming to 0.9.13 5b4ba567ab
viewit added the
enhancement
 label 2026-05-21 13:11:10 +02:00
viewit commented 2026-05-21 14:07:37 +02:00
Owner
Copy Link

Your theming is in! 🎨 Pulled into our dev branch and tested through:

  • Your default theme with the current ACE2 UI runs cleanly, asset routing via /kx/ui/ works, and the theme-name validation is solid. ✓
  • Removed the dead _web_assets import (from our earlier interim solution) — the frontend now comes entirely from your theme system.
  • Single-file binary solved: I built a shared kx-bridge.spec that embeds web/ (themes) into the one-file binary via datas; at runtime the bridge reads them from sys._MEIPASS (_WEB_BASE). So the Linux binary and the Windows EXE both ship the UI — verified the spec-built binary serves the themes correctly. Linux and Windows builds now use the same spec.
  • Docker build tested too (UI, theme assets, ACE2/skip, API).

Shipped in v0.9.14, with credit to you in the source + changelog. Really clean work — the hook docs make it genuinely pleasant for future themes. 🙏

Your theming is in! 🎨 Pulled into our dev branch and tested through: - Your `default` theme with the current ACE2 UI runs cleanly, asset routing via `/kx/ui/` works, and the theme-name validation is solid. ✓ - Removed the dead `_web_assets` import (from our earlier interim solution) — the frontend now comes entirely from your theme system. - **Single-file binary solved:** I built a shared `kx-bridge.spec` that embeds `web/` (themes) into the one-file binary via `datas`; at runtime the bridge reads them from `sys._MEIPASS` (`_WEB_BASE`). So the Linux binary **and** the Windows EXE both ship the UI — verified the spec-built binary serves the themes correctly. Linux and Windows builds now use the same spec. - Docker build tested too (UI, theme assets, ACE2/skip, API). Shipped in **v0.9.14**, with credit to you in the source + changelog. Really clean work — the hook docs make it genuinely pleasant for future themes. 🙏
viewit manually merged commit 312b4083d2 into master 2026-05-21 14:37:40 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
bug
documentation
duplicate
This issue or pull request already exists
enhancement
New feature
enhancement
help wanted
Need some help
invalid
Something is wrong
known-issue
question
More information is needed
wontfix
This won't be fixed
No Label
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
viewit
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: viewit/KX-Bridge-Release#27
No description provided.
Delete Branch "hirnwunde/KX-Bridge-Release:master"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?