Skip to main content

max / alloy_tui

Depend on makeover instead of a path into the MNW checkout theme-common was reachable only as ../MNW/shared/theme-common, so Alloy could not be built by anyone without that repo. It is now the standalone makeover crate, consumed as a tagged git dependency. The theme files moved with it. The dev fallback used to walk up to MNW/shared/themes; it now asks makeover for the themes it ships, so a fresh clone comes up themed instead of erroring. Packaged themes at /usr/share/alloy/themes still take precedence on an installed system.
Author: Max Johnson <me@maxj.phd> · 2026-07-19 19:15 UTC
Commit: 162fc4d6f37eb078249c0ca25193355beafe492d
Parent: 5129698
3 files changed, +8 insertions, -8 deletions
M Cargo.toml +2 -2
@@ -1,7 +1,7 @@
1 1 [package]
2 2 name = "alloy_tui"
3 3 version = "0.0.0"
4 - description = "Alloy design system: theme-common intents rendered as ratatui Color/Style, plus themed widgets for the alloy console and siblings."
4 + description = "Alloy design system: makeover intents rendered as ratatui Color/Style, plus themed widgets for the alloy console and siblings."
5 5 edition.workspace = true
6 6 rust-version.workspace = true
7 7 license.workspace = true
@@ -10,4 +10,4 @@ authors.workspace = true
10 10
11 11 [dependencies]
12 12 ratatui.workspace = true
13 - theme-common.workspace = true
13 + makeover.workspace = true
M src/lib.rs +1 -1
@@ -1,6 +1,6 @@
1 1 //! Alloy design system for ratatui.
2 2 //!
3 - //! Consumes theme-common `.toml` themes (the same schema every make-family app
3 + //! Consumes makeover `.toml` themes (the same schema every make-family app
4 4 //! reads) and renders them as ratatui `Color` / `Style`. Two Alloy-specific
5 5 //! tokens (`border-subtle`, `border-strong`) are derived locally so theme
6 6 //! files stay minimal — see `docs/TOKENS.md` for the storage format and
M src/theme.rs +5 -5
@@ -1,7 +1,7 @@
1 - //! Theme palette: theme-common intents resolved into ratatui `Color`s, plus
1 + //! Theme palette: makeover intents resolved into ratatui `Color`s, plus
2 2 //! the two Alloy-derived border tokens.
3 3 //!
4 - //! Per docs/TOKENS.md, Alloy consumes theme-common `.toml` files (the same
4 + //! Per docs/TOKENS.md, Alloy consumes makeover `.toml` files (the same
5 5 //! schema every make-family app already reads) and derives two extra tokens
6 6 //! locally so theme files stay minimal and cross-app compatible:
7 7 //!
@@ -13,10 +13,10 @@
13 13 //! ratatui is immediate-mode with per-widget styling — there is no global
14 14 //! visuals object. Widgets in this crate take a `&Theme` at construction time
15 15 //! and pull colors from it. Apps build one `Theme` per theme load (via
16 - //! `theme_common::load_theme` + `Theme::from_theme`) and thread it through.
16 + //! `makeover::load_theme` + `Theme::from_theme`) and thread it through.
17 17
18 18 use ratatui::style::Color;
19 - use theme_common::{Rgb, ThemeColors};
19 + use makeover::{Rgb, ThemeColors};
20 20
21 21 #[derive(Debug, Clone, Copy, PartialEq, Eq)]
22 22 pub enum Mode {
@@ -72,7 +72,7 @@ impl std::fmt::Display for ThemeError {
72 72 impl std::error::Error for ThemeError {}
73 73
74 74 impl Theme {
75 - /// Resolve a loaded theme-common `ThemeColors` into an Alloy `Theme`.
75 + /// Resolve a loaded makeover `ThemeColors` into an Alloy `Theme`.
76 76 /// Requires every intent Alloy renders — a malformed or partial theme is
77 77 /// rejected explicitly rather than silently rendering with defaults.
78 78 pub fn from_theme(theme: &ThemeColors) -> Result<Self, ThemeError> {