DaisyThemeManager

Overview

DaisyThemeManager is the central theme loader/applicator for the 35+ built-in DaisyUI themes. It tracks available themes, applies palette ResourceDictionaries, and notifies listeners via ThemeChanged. Helpers expose current/alternate theme names and light/dark metadata.

When to Use

Product Themes (96 Industry Palettes)

In addition to the 35+ DaisyUI themes, Flowery.WinUI includes 96 industry-specific product palettes from the UI UX Pro Max Skill project. These are professionally crafted color schemes for specific industries:

Use the DaisyProductThemeDropdown control for easy theme selection, or access programmatically via ProductPalettes:

// Get all product theme names
var allProductThemes = ProductPalettes.GetAllNames();

// Apply a product theme
var palette = ProductPalettes.Get("FintechTrust");
DaisyThemeManager.RegisterTheme(
    new DaisyThemeInfo("FintechTrust", FloweryColorHelpers.IsDark(palette.Base100)),
    () => DaisyPaletteFactory.Create(palette));
DaisyThemeManager.ApplyTheme("FintechTrust");

See DaisyProductThemeDropdown for full documentation.

• DaisyThemeManager.ApplyTheme() adds palette resources to MergedDictionaries. Best for switching between the 35 built-in themes.
• DaisyThemeLoader.ApplyThemeToApplication() updates resources in-place within ThemeDictionaries. Use this for custom themes loaded from CSS files at runtime.

Quick Comparison (in code-behind or ViewModel)

using Flowery.Controls;
using Flowery.Theming;

// Built-in themes: use DaisyThemeManager
DaisyThemeManager.ApplyTheme("Synthwave");

// Custom CSS themes: use DaisyThemeLoader
var theme = DaisyUiCssParser.ParseFile("mytheme.css");
DaisyThemeLoader.ApplyThemeToApplication(theme);

<Application.Resources>
    <ResourceDictionary>
        <ResourceDictionary.MergedDictionaries>
            <ResourceDictionary Source="ms-appx:///Flowery.WinUI/Themes/Generic.xaml" />
        </ResourceDictionary.MergedDictionaries>
    </ResourceDictionary>
</Application.Resources>

Key Members

Theme Visibility and Ordering

Global Additions and Display Names

Use AddTheme to configure both dropdown types globally, without replacing their existing lists:

DaisyThemeManager.AddTheme("Business", "MyBusiness", false);
DaisyThemeManager.AddTheme("TheaterCinema", "DarkAndRed", true);
DaisyThemeManager.AddTheme("Corporate", "Office", true);

The arguments are the original name, the display text, and the preferred flag. Standard, registered custom, and product theme names are supported; unknown names raise ArgumentException. Original names are case-insensitive, and repeated names update the entry without adding a duplicate. Product additions are registered globally, but AddTheme applies no palette.

Preferred entries appear first, sorted by display text, followed by a separator line and the other entries. PreferredThemes supplies defaults for entries without an explicit AddTheme flag. Exclusions always take precedence.

An individual dropdown can override a global entry. Local settings win for that original name only:

themeDropdown.AddTheme("Business", "My local business", true);
productThemeDropdown.AddTheme("TheaterCinema", "Local cinema", false);

themeDropdown.RemoveThemeOverride("Business");          // back to the manager's entry
DaisyThemeManager.RemoveThemeOverride("TheaterCinema"); // registered themes stay registered

Display text is UI text only. SelectedTheme, ApplyTheme, HideTheme, ShowTheme, ExcludedThemes, PreferredThemes and RemoveThemeOverride use the original name.

Hiding and Preferring Themes

// Before creating controls
DaisyThemeManager.ExcludedThemes = ["Cyberpunk", "SaaS"];
DaisyThemeManager.PreferredThemes = ["Business", "MicroSaaS"];

// At runtime, on the UI thread; loaded dropdowns update automatically
DaisyThemeManager.HideTheme("Cyberpunk");
DaisyThemeManager.ShowTheme("Cyberpunk");

// Restore the normal lists
DaisyThemeManager.ExcludedThemes = [];
DaisyThemeManager.PreferredThemes = [];

Both setters copy the names and replace the previous set; the getters return read-only snapshots. Names are case-insensitive and may refer to themes that are not registered yet. These settings neither select nor apply a theme. A hidden theme can still be applied with ApplyTheme.

Usage Notes

• Palettes are generated by DaisyPaletteFactory (code-based); ensure the theme name matches AvailableThemes.
• Applying the same theme twice short-circuits.
• On apply, keep the palette ResourceDictionary stable and update its brushes in-place. Removing/replacing the dictionary breaks ThemeResource bindings because controls keep references to the old brush instances.

Windows Contrast Themes

Windows contrast themes are system accessibility settings. They are separate from the Flowery theme catalog.

The default theme applicator maps palette brushes to these system color pairs:

Changing the Windows contrast setting refreshes the current palette and raises ThemeChanged on the UI thread.

Returning to the normal Windows appearance restores the selected Flowery palette.

They suppress blur and reflection layers. Neumorphic effects are also disabled.

Custom controls can use a HighContrast theme dictionary with matching SystemColor foreground and background resources.

See DaisyAccessibility for UI Automation and the Windows animation setting.

Quick Example (code-behind)

// Apply Synthwave
DaisyThemeManager.ApplyTheme("Synthwave");

// Toggle between base/alternate themes
var target = DaisyThemeManager.CurrentThemeName == DaisyThemeManager.BaseThemeName
    ? DaisyThemeManager.AlternateThemeName
    : DaisyThemeManager.BaseThemeName;
DaisyThemeManager.ApplyTheme(target);

Initialization & Theme Suppression

Theme controls like DaisyThemeDropdown, DaisyThemeController, and DaisyThemeRadio automatically sync to CurrentThemeName during construction. However, in complex scenarios with many controls or custom initialization order, you can use SuppressThemeApplication for explicit control:

// In App.xaml.cs OnLaunched:
var savedTheme = LoadThemeFromSettings() ?? "Dark";

// Option 1: Simple apps - just apply the theme first
// Theme controls will sync to it automatically
DaisyThemeManager.ApplyTheme(savedTheme);

// Option 2: Complex apps - suppress during UI construction
DaisyThemeManager.SuppressThemeApplication = true;
DaisyThemeManager.ApplyTheme(savedTheme); // Only updates internal state

// Create window...
// ...

// After initialization - now actually apply
DaisyThemeManager.SuppressThemeApplication = false;
DaisyThemeManager.ApplyTheme(savedTheme); // Actually applies

Custom Theme Applicator

> Full Migration Example - Step-by-step guide for integrating Flowery.WinUI into existing apps with custom resources.

For apps that need custom theme application logic (e.g., in-place ThemeDictionary updates, persisting settings), set the CustomThemeApplicator delegate at startup:

// In App.xaml.cs OnLaunched:
DaisyThemeManager.CustomThemeApplicator = themeName =>
{
    var themeInfo = DaisyThemeManager.GetThemeInfo(themeName);
    if (themeInfo == null) return false;

    // Get the palette from DaisyPaletteFactory
    var palette = DaisyPaletteFactory.Create(themeInfo.Name);

    var app = Application.Current;
    if (app == null) return false;

    // Keep palette dictionary stable; update or add it
    var existingPalette = app.Resources.MergedDictionaries
        .FirstOrDefault(d => d.ContainsKey("DaisyBase100Brush"));
    if (existingPalette == null)
    {
        app.Resources.MergedDictionaries.Add(palette);
    }
    else
    {
        foreach (var key in palette.Keys)
        {
            existingPalette[key] = palette[key];
        }
    }

    // Persist to settings
    Windows.Storage.ApplicationData.Current.LocalSettings.Values["Theme"] = themeName;

    // Notify listeners
    DaisyThemeManager.SetCurrentTheme(themeName);

    return true;
};

All built-in theme controls (DaisyThemeDropdown, DaisyThemeController, DaisyThemeRadio, DaisyThemeSwap) automatically use the custom applicator when set.