How kyome22/runcat365 works
Project Type and Purpose
• This is a Windows desktop application (C#/.NET 9.0) that displays a cute running cat animation in the Windows Taskbar and optionally an endless runner “game” window.
• It also contains a secondary project for packaging the app for the Microsoft Store, plus a small static “docs” site for documentation.
High-Level Components
A. Solution (“RunCat365.sln”)
1. RunCat365 (Desktop App)
• Program.cs: Application entry point.
• EndlessGameForm.cs: Main WinForms UI for the endless runner game.
• ContextMenuManager/ContextMenuRenderer/CustomToolStripMenuItem: Tray/context-menu support.
• CPURepository, MemoryRepository, StorageRepository: System-metric collectors.
• ByteFormatter, FPSMaxLimit, GameStatus: Business-logic/utilities.
• Cat, Runner, Road, Theme: Animation/game objects and styling.
• LaunchAtStartupManager: Windows startup integration.
• App.config/App.manifest: Configuration and Windows compatibility.
2. WapForStore (AppX Packaging)
• Wapproj + Package.appxmanifest + StoreAssociation + build scripts.
• Produces MSIX/AppX for submission to Microsoft Store.
B. docs Folder (Static Site)
• HTML/CSS/images for project documentation.
Relationships & Data Flow
• Repositories periodically query Windows APIs for CPU/memory/disk usage.
• Business logic modules (ByteFormatter, FPSMaxLimit) process raw data into display metrics.
• UI components (EndlessGameForm, Runner, Road, Cat) consume metrics and render frames.
• Packaging project (WapForStore) references the build output of RunCat365 and wraps it in an AppX container.
• Documentation site is independent and served via docs/index.html.
Architectural Patterns & Principles
• Modular separation of concerns:
• Data Collection (Repositories)
• Core Logic (Formatters, GameStatus, Limits)
• Presentation (Forms, Renderers, Themes)
• Integration (ContextMenu, LaunchAtStartup)
• Build-time packaging separated into its own project (WAP).