Rectangle is a production macOS menu-bar window-management utility that moves, resizes, and tiles application windows through keyboard shortcuts and drag-to-snap. It is not a research or data project; it is a purely native desktop application. It reads and writes window geometry via the macOS Accessibility API (AXUIElement), supporting dozens of layout actions — halves, thirds, quarters, sixths, eighths, ninths, twelfths, sixteenths, maximize, center, cascade, display transfer, and multi-window grid/row/column tiling — plus stacked-window cycling, a todo-mode sidebar, cooperative corner resize, and an optional animation engine. Architecturally, this is a Swift/Cocoa menu-bar app (LSUIElement, no dock icon, no backend). AppDelegate wires together ShortcutManager (MASShortcut bindings), WindowManager (action orchestration), SnappingManager (drag-to-snap with placement preview), MultiWindowManager (tile/cascade/stack), and a SwiftUI Settings window backed by a typed Defaults system persisted in NSUserDefaults with JSON import/export. The heart of the layout logic is a strategy pattern: a WindowCalculation protocol with roughly a hundred small calculation classes, each implementing one placement, applied through a chain of WindowMover implementations (standard, fixed-size, best-effort, edge-alignment) and optionally a display-link-driven animation pipeline with pacing, settlement, and handoff verification. The primary data flow is user input (shortcut/menu/drag) → WindowAction enum → WindowCalculation produces a target rectangle from the current screen, window, and gap state → a WindowMover writes the frame through AXUIElement with edge correction, followed by optional animation and post-move verification. Screen detection, multi-display transfer, gap math, and stack detection are separated into focused utilities. External dependencies are limited to AppKit/QuartzCore, the undocumented macOS Accessibility API, a forked-and-pinned MASShortcut, and Sparkle for auto-updates. The codebase is professionally maintained with unit tests for geometry, grid tiling, stack detection, defaults serialization, and cooperative resize, plus GitHub Actions CI that produces signed DMGs. Its main weaknesses are scale-related: a monolithic calculation factory and a ~140-value WindowAction enum with duplicated metadata, a single ~96k-token test file, and near-duplicate calculation classes for fine-grained grids. The strongest reusable assets are generic utilities (TTL cache, debounce) and pure-geometry modules that are decoupled from app state.
MonitorControl is a macOS menu-bar utility that controls external displays' brightness, contrast, and volume. It does not just send one kind of command; it uses multiple control paths: hardware DDC/CI over IOKit I2C on Intel Macs, DDC/CI over IOAVService on Apple Silicon, Apple's private DisplayServices API for Apple/Thunderbolt displays, gamma-ramp adjustments for software dimming, and transparent shade windows for virtual displays. User input flows from native media keys, custom keyboard shortcuts, and menu-bar sliders into a DisplayManager singleton, which coordinates native OSD overlays, smooth brightness transitions, and cross-display synchronization. The app uses Sparkle for updates, SimplyCoreAudio for audio device handling, MediaKeyTap for media-key interception, and KeyboardShortcuts for user-defined bindings. Architecturally, this is a classic Cocoa application with a storyboard-based preferences UI, a login helper app (MonitorControlHelper), and a clean separation between models (Display, AppleDisplay, OtherDisplay), support services (DisplayManager, DDC backends, OSD utilities, media-key handling), and view controllers for preferences and onboarding. Entry points are main.swift, AppDelegate, DisplayManager, and MenuHandler. Persistence is UserDefaults backed through a PrefKey enum, and the UI is localized into 19 languages. There is no data/research component; this is purely an end-user utility. The codebase is modular and well organized, with the DDC communication isolated into Intel and ARM backends and display-specific logic abstracted behind a base Display class. It is actively maintained, with recent commits and a modern dependency setup. Technical drift is medium rather than low because much of the functionality depends on private or undocumented macOS APIs (DisplayServices, CoreDisplay, OSDUIHelper) and the code contains many macOS-version-specific workarounds, but the project tracks current macOS releases and continues to update its fallbacks.
Floorp is a Firefox-based browser that extends Gecko with a comprehensive feature layer including workspaces, split-view tiling, panel sidebar, PWA/SSB management, mouse gestures, keyboard shortcuts, command palette, tab stacks, design theming, private containers, external browser integration, notes, profile manager, and more. The architecture is hybrid: chrome components are built with SolidJS and injected via a custom loader into Firefox's XUL, while settings, new tab, notes, welcome wizard, and profile manager pages are standalone React/Vite web applications served within the browser. Configuration is stored in Firefox preferences with io-ts runtime validation, and cross-process communication uses a birpc bridge. The build system is Deno-based, orchestrating Vite builds, Firefox runtime patching, and platform-specific packaging (macOS App Shim in C++, Windows Tauri stub installer). The codebase demonstrates strong engineering practices with extensive test coverage (colocated browser tests, unit tests, integration tests), clean reactive state management patterns, and well-structured feature modules. However, it carries technical debt from multiple legacy migration paths, duplicated UI components across page apps, and tight coupling to Firefox internal APIs that require version-specific workarounds.
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).
tmux-which-key is a tmux plugin that provides a customizable popup menu for executing tmux commands and user-defined macros. The plugin architecture centers around a YAML configuration file that defines menu structure, keybindings, and macros, which is processed by a Python build script to generate tmux initialization code. At runtime, the plugin uses tmux's display-menu command to show nested menus and executes commands via command-aliases for performance. The plugin supports XDG directory compliance for immutable systems like NixOS and offers both YAML-based configuration (requiring Python) and direct tmux script editing alternatives. Key features include transient menus (that stay open for repeated commands), user macros (chained commands), and integration with TPM for plugin management.
This is a macOS desktop application that serves as an unofficial wrapper for the Google Gemini web interface. Built with SwiftUI and WebKit, it provides a native macOS experience including a main window, floating chat bar, menu bar integration, and global keyboard shortcuts. The application loads the official Gemini website in a web view while adding desktop-specific features like window management, persistent preferences, and system integration. The architecture follows a coordinated Model-View-ViewModel pattern with clear separation between UI components (Views), state management (WebViewModel), and application coordination (AppCoordinator). Notable implementation details include sophisticated window positioning logic, automatic chat bar expansion based on webpage content detection, and thoughtful handling of web view events like external links and file downloads.