Simplified Theming for Big Box
š Summary
Make theming for Big Box more accessible by simplifying the theming language and providing better tools and documentation. The current XAML-based system is powerful but requires programming knowledge, which makes it difficult for designers and hobbyists to create or modify themes.
šÆ Feature Overview
Introduce a simpler markup-style theming language, inspired by web standards like:
HTML + CSS for layout and styling.
Lightweight scripting (e.g., JavaScript-like logic) for animations and interactivity.
Add a visual theme editor or live preview tool within Big Box or LaunchBox, so users can design and test themes without coding.
Create an official theming documentation hub, including:
Starter templates and component examples.
Style references and layout guides.
Tutorials for both beginners and advanced creators.
š Example Use Case
A designer wants to make a minimalist grid-based theme.
Current process: Must learn XAML syntax and understand C# bindings.
Proposed process: Use a simple markup layout and CSS-like stylingāor adjust visuals directly in a built-in editorāwith instant preview.
š¦ Benefits
š§ Makes theming approachable for non-programmers.
š§° Encourages more community-made themes and experimentation.
š Speeds up theme creation and customization.
š Builds a stronger, more diverse theme creator community.
š Improves consistency and flexibility across all Big Box setups.
š” Notes
This would future-proof Big Boxās theming framework by aligning it more closely with familiar design paradigms, lowering the learning curve, and encouraging broader creative participation.

Log in to comment and vote
Comments3
Oct 25, 2025
PinnedHi there!
Thanks so much for submitting this request and for taking the time to explain your use case ā that context is always super helpful.
Iāve gone ahead and fleshed out the main idea using the info you provided, and Iām opening it up to the community for further discussion and feedback. Please let me know if this fleshed-out version doesnāt match your original intended request.
Feel free to let me know if you have any extra thoughts, examples, or edge cases you think might be relevant!
Cheers,
The LaunchBox team
light.sock6996
Feb 22
I think itās a bad idea because XAML has been well implemented for years in BigBox and it would require a considerable amount of development time to fix something that aināt broken. I know XAML can be a pain but anyone can learn it nowadays with the help of a context-aware LLM. Plus thereās CTC which is a full blown visual editor to mitigate this exact issue.
Plus the alternative you brought up would impact performance and would be less than ideal knowing BigBox already has to do miracles in order to get huge libraries loading fine. I would rather see the dev time spent on performance improvements on the current stack.
I already asked if they were interested in rewriting the core LaunchBox because it would benefit from a new codebase for multi-OS support and massive performance gains. Unless they open source their current codebase they wouldnāt be able to pull off such a rewrite without impacting dev time on the current version, which would impact paying users. Anyway their answer was ānot gonna happenā so I believe this hasnāt changed over the past few years.
But even if they would completely rewrite LaunchBox I think it would be easier to keep WPF support with something like Avalonia for Mac and Linux support.
Take this with a grain of salt, Iām not an expert, but as a theme creator Iām against this feature request.
elwooha6
Oct 25, 2025
Theming for BigBox CrossPlat
Problem: Theming for BigBox is currently a task that requires programming knowledge.
Desired Solution: Simpler method for theming so that a simple-minded designer like me can actually make something coherent.
To be clear Iām not even a complete novice with programming but when I try to convert my xml knowledge into xaml knowledge my brain pickles and catches on fire because I canāt make head nor tails of it. I figure now is the time to request simpler theme creation since the cross platform rewrite is hopefully in the design/early phases.
I think this request could be tackled in a couple ways. Adopting a simple markup-style language for themes, something that feels more like traditional html+css for layout and javascript for logic. As well as a robust documentation hub so anyone looking to create something unique has a place to go instead of having to try and pick apart existing themes, hoping their caveman attempts to distinguish the important bits bears fruit.
Maybe the ideas here are way off but the tldr is this: theming needs to be more accessible so anyone with a healthy interest in it can make something cool to share.