|
Window Framework for UI Toolkit v2.0.x
|
Give your interface a visual identity without rebuilding its window content for every look.
Theme Studio brings the theme collection, appearance controls, and a representative preview together in one editor workspace. Start from a project-owned theme, adjust the surfaces and typography, refine component details, and save the result back to its source files.
This page covers the authoring workflow. Stylesheet Setup and Theme Structure explains the underlying files and scope; Built-in Styling Class Reference lists actual reusable roles and component classes for your custom UI.
Choose Tools > Garage-Ware Games > Window Framework > Theme Manager.
Open your project ThemeData through the repository browser or the manager's asset selection. The ThemeData Inspector also provides an Open Theme Manager Window launcher, but that button preserves the manager's selected repository; it does not automatically switch to the asset you were inspecting.
Use the repository name and the pinned ThemeData field to confirm where you are working. Project repositories, shipped defaults, and Demo examples have different purposes. For your application, create the project-owned setup through Installation and Setup before customizing its theme files.
The split view lets you adjust the space allocated to the inspector and preview. Expanding a group or scrolling changes the editor workspace, not your theme values.
The preview helps you evaluate supported appearance settings. It is not your application's scene and does not reproduce every custom selector, inline style, input interaction, or gameplay condition. Test your actual interface after authoring.
Click Switch Theme to open the Theme Master List.
A theme can have more than one badge because these are separate roles. The active/default actions update collection configuration; a row click simply chooses what you are editing.
Theme application scope is also a collection choice. Window Frames Only, Parent Panel, and All Panels determine where the configured composition reaches the UI. See Make Sure the Theme Reaches the Control before applying a theme broadly to an existing interface.
For a straightforward first workflow, open a valid 2.0 theme from your project repository and choose Duplicate Theme.
Duplication copies the saved, owned theme folder, including supported nested source and preview assets, then registers a new independent entry with its own identity. Shared application rules remain collection-owned. The copy is not automatically the default theme.
Save before duplicating if you want your latest token edits included.** Duplicate reads authored source, not a snapshot of unsaved inspector colors and sliders.
A destination conflict offers a separately named copy or cancellation, not overwrite. If the source has appearance imports outside its owned folder that prevent an independent copy, the workflow reports the problem instead of silently flattening them. External artwork references outside the source boundary remain shared when the copy workflow retains them.
The + control in the master list adds a blank theme entry. It does not create a complete TSS/USS folder or fill in every required value. Assign an appropriate configured theme sheet to that entry, or use duplication when you want a ready-to-edit starting point. Creating a repository is a different operation from adding a theme row.
Under Theme Identity & Metadata:
This preview artwork is separate from the Window Background and Default Theme Indicator settings. A thumbnail, a window wallpaper, and a default marker serve different purposes.
Metadata controls update the collection entry and mark the asset dirty. Appearance-token controls drive the preview until saved through Save To Disk. Collection actions and options can have their own immediate save paths, so switching themes is not a universal undo operation for every kind of edit.
Work from broad visual decisions toward specific component details:
Choose readable contrasts for normal, hovered, selected, and disabled controls. Check the smaller text samples as well as titles; a theme that looks attractive in a large heading may be difficult to use in a dense form.
These are theme values, not automatically reusable classes for each setting. Content Background, for example, can be used by your own application rule with var(--wfw-surface-background). Changing that value does not create a class to assign to a control. See 5. Theme Your Own Control for the practical custom-control pattern.
Expand Scrollbars, Modals, Context Menu, or the supported extension-control group to refine component settings.
A line such as Linked: var(--wfw-surface-background) means that the component value currently follows another authored setting. The field is read-only until you enable Override for that supported linked row.
Rows authored as independent values do not have a linked-variable description; the variable area remains blank. Override availability is based on the authored mode, not a promise that every literal field can invent a new link. After saving an explicit value and reloading, that row is authored as independent; Studio does not retain the old link as a permanent automatic reset target.
For example, keeping a modal body linked to Content Background gives the two a coordinated appearance.Overriding that component value lets the modal body differ without changing every consumer of Content Background.
The linked text is an explanation of the source value. It is not a USS class name or an AddToClassList argument. Studio does not infer a reusable class from whichever component selector happens to consume a value.
Under Images & Framework Asset Overrides, choose supported artwork for window backgrounds, lock/options/resize icons, context-menu checkmarks, default markers, warnings, and cursors.
The asset rows provide the appropriate type choice, object field, thumbnail, and clear action. Where available, choose Texture2D or VectorImage; cursor rows and developer image settings use their supported raster restrictions rather than accepting every image type.
Assets assigned through Studio's resource-validating pickers must be project assets under a suitable Resources folder. Resource expressions use a Resources-relative path without the extension. A folder's location and spelling therefore matter; an arbitrary asset elsewhere under Assets does not make a resource path valid.
Clearing an optional value writes the supported empty/none reference. It does not delete the source image. Save To Disk preserves image files and updates the relevant source/reference metadata; it is not a background-removal, recoloring, or artwork-generation tool.
Test vector artwork, cursor hotspot behavior, contrast, and scaling in your target application. A visible editor thumbnail is not proof of identical runtime rendering on every platform.
The Developer Extensions area groups installed WFWDevExt declarations by namespace. Fields are generated from their declared number, color, or image type, authoring text, and supported constraints.
An empty area can display None installed. That means no valid declarations were discovered in the configured source graph; it does not mean you must register every custom control just to reuse an existing framework color.
Developer fields write explicitly changed values back to their original declarations. Their source path is included in the field tooltip. Asset source under your project can be edited through the supported workflow; read-only or unavailable sources are not silently copied into a second settings store.
See Stylesheet Setup and Theme Structure for file ownership, and Developer Extensions for the complete declaration/application workflow. Studio is not a general inspector for every arbitrary USS property.
Choose Save To Disk after reviewing the theme.
The save workflow expects the selected TSS to have a matching USS file beside it with the same base filename. The existing creation/duplication workflow supplies this pairing. Keep the pair intact when managing files yourself; a TSS reference alone is not proof that its expected save target exists.
Saving updates supported framework settings and explicitly edited developer declarations at their original source/scope. It preserves unrelated developer selectors, metadata headers, and values rather than replacing the entire source with the preview's appearance.
Successful saving imports the changed sources, saves the collection's supported preview references, and reloads the selected theme into Studio. If a save is blocked by missing source, invalid developer values, or a source change that conflicts with the loaded developer edits, read the diagnostic before retrying. Do not overwrite another author's work to dismiss that warning.
Check the saved theme in your actual UI. The Preview Canvas is representative; custom rules, local inline overrides, panel scale, fonts, and runtime interactions may still affect the application result.
In Switch Theme, the master list provides:
Save your source before preparing so the snapshot represents the intended authored theme. The preparation control reads the configured collection/application graph and stores the prepared snapshot on that theme entry. It does not save unsaved token-control edits for you, create a player theme copy, or prove every custom styling rule can be reproduced in a player theme.
Preparation and saving are distinct actions. Upgrade legacy entries before portable preparation. Keep a compatible prepared default configured if player-copy workflows depend on it, and prepare the themes your application offers through those workflows.
Review the preparation message, then verify runtime selection, editable-copy creation, and supported player overrides through Player Themes. Arbitrary player CSS, code, or selector changes are not enabled by preparing values.
Legacy 1.0 themes do not use the modern Studio preview. Their view displays a compatibility notice and Upgrade to 2.0 actions.
Upgrade creates separate modern output from the selected legacy source rather than changing that original theme in place. Review the output and its preparation result before using it. This is an appearance upgrade workflow, not guaranteed automatic conversion of every custom layout or unmarked rule.
The master list's remove action confirms removal of a theme entry. It leaves its source stylesheets and image files on disk and keeps at least one collection entry. If removing the configured default, deliberately check the remaining default/active configuration afterward; removal is not automatic default-theme design.
Continue to Developer Extensions for custom editable settings, Player Themes for player customization, or Troubleshooting for configuration problems. The advanced stylesheet guides remain available whenever you need to understand which file or selector owns the result.