How srwi/everythingtoolbar works
Project Type and Purpose
• Project type: Native Windows desktop integration + WPF application + Shell extension + installer + build pipeline.
Break the System into Main Components
a. EverythingSDK (C library)
b. EverythingToolbar Core (C# WPF UI + MVVM logic)
c. Deskband COM Extension (Shell integration component)
e. Installer (WiX-based MSI/EXE)
f. Build & Release Pipeline (GitHub Actions + Winget/Chocolatey publishing)
Component Relationships and Data Flows
1) User interacts with UI (either deskband in Explorer or the Launcher window).
2) UI layer (EverythingToolbar core) invokes Search subsystem.
3) Search subsystem calls EverythingSDK (native library) over IPC to the Everything service.
4) Everything returns file results; returned to Search subsystem → ViewModels → UI.
5) User selects an item → Helper (ShellContextMenu or Process.Start) invokes OS to open file, apply rules (reg-ex based commands), or hand off to QuickLook/Seer.
6) Settings and history saved via Helpers into Windows Registry or local config.
7) Installer at install time registers the deskband COM component in Registry and installs the Launcher shortcut and Win+Alt+S hotkey association.
8) GitHub Actions build all projects (.sln), run tests (if any), package artifacts, push releases to GitHub and publish to winget/choco.
Architectural Patterns
• MVVM (Model-View-ViewModel) in all WPF components.
• COM Deskband pattern (IDeskBand, COM registration, Explorer extension).
• Native P/Invoke / IPC wrapper (EverythingSDK → Everything service).
• Plugin-like extensibility for custom filters and rules (data-driven).
• Resource theming (Light/Dark, Win10/Win11 XAML resource dictionaries).
Don’t Overthink—Capture All Pieces
• Them according to build output and runtime interactions.
• Even simple helper classes (RegistryWatcher, HistoryManager) can be grouped under “Persistence Services” in the core library.
• At the bottom or side, show DevOps folder (.github + tools) as the “Build & Release pipeline.”
• Clearly separates frontend (Deskband/Launcher) from backend (search engine),
• Shows all integration points (COM, IPC, global hotkey, registry, installer),
• Annotates architectural patterns (MVVM, COM extension, native bridging),