How jthweb/windows-12 works
Project Type & Purpose
• This is an open-source Windows customization layer (not a full OS) that provides a cohesive UI/UX “skin” on top of Windows 10/11.
Top-Level Components
• Configurator App
– run.py + run.ui: a PyQt/PySide (or similar) GUI that drives installation and configuration
• Python Utility Modules
– Winver: winver.py + logo + version.json
• Asset Repositories
– Cursors, Shell msstyles, Wallpapers under win10/ and win11/ directories
• External Tools & Dependencies
– Rainmeter (widget host)
– UltraUXThemePatcher (theme patching)
– HackBGRT (boot splash)
– Writing Tools API (for “Windows Intelligence” integration)
Data Flow & Interactions
• User launches the Windows 12 Configurator → selects install/uninstall options →
↳ Configurator invokes the relevant Python module (Run, Taskbar, Winver, etc.)
↳ Calls external utilities (Rainmeter, UltraUXThemePatcher, 7tsp, HackBGRT) via CLI to apply skins/patches →
↳ Windows OS & Rainmeter update UI accordingly
• Version checking: Configurator or Winver module reads version.json to prompt updates.
Architectural Patterns & Principles
• Modular design: each feature (Run dialog, Taskbar, Winver, Time widgets) is its own Python module with its own assets and configuration files.
• Presentation vs. Logic separation: UI definitions (.ui) are separate from Python code.
• Command orchestration: the Configurator serves as a central controller that sequences calls to each module and to external patching tools.