Window Framework for UI Toolkit v2.0.x
Application Directory Reference
Directory dependency graph for Application:
D:/GameDevelopment/Projects/AssetProjects/WindowFramework/WindowFramework_Dev/Assets/GarageWareGames/WIndowFramework/Scripts/Editor/Resources/WindowFramework/RepositoryReadmes/Application

Detailed Description

Application styling infrastructure

Required precautions

  • Do not casually modify shared application infrastructure to change a single theme. Shared changes affect every theme that uses the collection's application stylesheet composition.
  • Do not clear or replace the required framework stylesheet roles on ThemeData. They provide framework styling and are separate from a selected theme's settings sheet.
  • Preserve stylesheet order and asset references when making deliberate application-wide changes. Moving a stylesheet or its artwork may also require updating string-based Resources paths.

Purpose

This README belongs in Runtime/Application, not a separate root-level Application folder. Publication from the package defaults places the configured native-control stylesheet (WFW.UnityControls.tss), framework-component stylesheet (WFW.Styling.uss) and slide-toggle stylesheet (WFW.SlideToggle.uss) here. ThemeData's required stylesheet roles and application composition reference these copied assets.

These are shared application infrastructure files, not another theme or a dumping place for unrelated developer files. Their imports and references are rebased when the starter repository is published; copying an existing developer repository retains its existing locations and relinks only copied references.

Where to customize

Use each theme's settings and artwork for theme-specific appearance. Put developer-owned content in your chosen folders and configure its stylesheet references intentionally. Repository copying preserves existing folders and external references; it does not enforce ownership, invent a Shared folder or rewrite this README for developer-owned repositories.