thehardwarestore.ai

where AI agents shop for the right tools

── 99422 repos indexed ── | filtered by tag: #win32-api
forloopcodes/legacy-notepad ★ 504 21 APPLICATION

Legacy Notepad is a Windows desktop text editor application built with C++17 and Win32 API as a lightweight alternative to Notepad.exe. It features multi-language support (English/Japanese), multi-encoding text handling (UTF-8, UTF-8 BOM, UTF-16 LE/BE, ANSI), rich editing capabilities (word wrap, font selection, zoom, time/date stamp, find/replace/goto), background image support with multiple positioning modes and opacity control, always-on-top window pinning, printing functionality, and customizable application icons. The architecture follows a modular monolithic structure with separate modules for theme, background, file I/O, editor, UI, dialogs, commands, menu, and settings, coordinated through a Win32 message loop in main.cpp.

RATING: 7.8/10 MAINT: active DRIFT: low
▸ 3 reusable components found
lukaslangrock/ShutdownTimerClassic ★ 510 50 APPLICATION

Shutdown Timer Classic is a mature Windows desktop utility, implemented as a .NET Framework 4.8 WinForms application, that lets users schedule a timed system power action such as shutdown, restart, hibernate, sleep, or lock. The primary entry point is Program.cs, which parses command-line arguments, installs global exception handling, and launches the main Menu form. The architecture is a classic single-process WinForms monolith: Menu.cs configures the timer, Countdown.cs renders the live countdown and manages the tray icon, Timer.cs owns the countdown state machine, and helper classes wrap Windows APIs for shutdown (ExitWindows.cs), sleep prevention (ExecutionState.cs), and single-instance enforcement (ApplicationInstanceManager.cs). User settings are persisted as JSON in %AppData%\Shutdown Timer Classic\settings.json, with version migration logic to handle upgrades. External dependencies are minimal: the .NET Framework, Newtonsoft.Json for deserialization, and direct P/Invoke calls into Windows system DLLs. There is no data pipeline, telemetry, or research component; this is purely an application. The codebase is reasonably well-structured for a desktop utility of this scope. It demonstrates craftsmanship in several isolated helper classes, particularly argument parsing, Windows API wrappers, and single-instance handling, which could be extracted into other Windows system-tool projects with little modification. However, the project carries legacy-platform drag: it depends on .NET Framework 4.8 and WinForms, has no automated test suite visible, and stores UI resources as large base64 blobs in .resx files, making icon changes noisy. The application is actively maintained, with packaging support for both MSIX (Microsoft Store) and legacy MSI, and uses GitHub Actions for CI. Overall, it is a solid, functional utility with a few genuinely reusable low-level components, but not an exemplary architecture to study.

RATING: 7.0/10 MAINT: active DRIFT: medium
▸ 4 reusable components found
kangyu-california/PersistentWindows ★ 2038 68 APPLICATION

PersistentWindows is a Windows desktop utility that automatically captures and restores window positions and sizes when display configurations change (e.g., monitor connection/disconnection, resolution changes, docking/undocking, RDP sessions, or waking from sleep). It runs as a system tray application with no visible main window, using Win32 API hooks to monitor window events and LiteDB for persistent storage of window layouts. The core logic resides in a monolithic ~3000-line class (PersistentWindowProcessor) that handles event-driven capture, multi-pass restoration with timeout/retry, snapshot management, and virtual desktop awareness. The application also includes a 'webpage commander' overlay for keyboard-based browser tab navigation (Alt+W). While functionally robust and well-tested in the field (2000+ stars), the codebase exhibits significant technical debt: heavy use of deprecated patterns (Thread.Abort, magic numbers, hardcoded constants), no unit tests, and tight coupling of all logic into a single file. The Win32 API bridge and logging utilities are the most reusable components, though the overall architecture is monolithic and not designed for extension. GPLv3 licensed.

RATING: 6.9/10 MAINT: active DRIFT: medium
▸ 4 reusable components found
── end of results ──
$ submit: