SpanFinder is a fully-featured Windows file explorer replacement built with WinUI 3 and .NET 8, implementing the macOS Finder Miller Columns paradigm. The application supports multiple view modes (Miller Columns, Details, List, Icons), multi-tab with tear-off, split pane, Quick Look preview, batch rename, archive handling (ZIP, RAR, 7z via native OtterZip engine), remote file access (FTP/SFTP/SMB), Git integration, cloud sync badges, and a file shelf for drag-and-drop staging. The architecture follows MVVM with dependency injection, extensive use of Win32 P/Invoke and COM interop for shell integration, and a separate thumbnail worker process for crash isolation. The codebase is well-organized into Services, Models, ViewModels, and Helpers, with over 150 unit tests and 40+ UI automation tests. However, it exhibits some mixed abstraction layers and a few large partial classes (MainWindow, MainViewModel), and many comments reference specific bug fixes, indicating ongoing refinement. The repository is actively maintained with recent commits, a single open issue, and regular versioned releases (v2.0.7).
QTTabBar is a GPLv3-licensed Windows Explorer shell extension that enhances the file manager with tabbed browsing, customizable toolbars, breadcrumb navigation, file operations, and a rich plugin system. It integrates deeply into Windows Explorer via COM band objects (IDeskBand2), native API hooking (MinHook), and extensive P/Invoke into shell32, user32, and other system libraries. The core application runs inside the explorer.exe process and provides a tab bar, command bar, folder groups, fast file renaming, file hash computation, and a variety of UI tweaks (double-click to go up, thumbnail tooltips, subdirectory tips). The plugin SDK (QTPluginLib) allows third-party developers to create custom toolbar buttons, dropdowns, and background plugins. The architecture is a classic WinForms application layered on top of a massive COM interop surface, with some WPF used for the options dialogs. Configuration is stored in the Windows registry. While the codebase is functional and feature-rich, it suffers from aging dependencies, hardcoded constants, scattered TODO comments, and heavy reliance on undocumented Windows internals, making it fragile against OS updates.