This repository is the `bevy_enhanced_input` library, a fully‑featured, observer‑based input management system for the Bevy game engine, inspired by Unreal Engine's Enhanced Input. It provides a component‑driven ECS architecture where actions, bindings, input conditions, and modifiers are all first‑class Bevy components or relationships. The system supports context layering (priorities, activity states), state synchronization, mocking for tests/cutscenes, and a built‑in preset system for common input patterns (e.g., WASD, gamepad sticks). At its core, the library defines the `InputAction` derive macro, the `InputCondition` and `InputModifier` traits, and an evaluation pipeline that runs during `PreUpdate`. Input reading is handled via a dedicated `InputReader` system parameter that also manages input consumption and ignoring. The library is `no_std` compatible and supports reflection and serialization via feature flags. The code is well‑structured with heavy use of Bevy's observer and relationship APIs, and includes extensive integration tests and a comprehensive set of examples ranging from basic action management to rebindable keybinding menus with persistence.
The progressr package provides a minimal, unifying API for reporting progress updates in R. It separates progress signaling (developer-controlled) from progress presentation (end-user controlled) using R's condition system. Developers create progressor functions to signal updates, while end users configure handlers to determine how progress is displayed (terminal, GUI, audio, notifications, or file-based). The architecture centers around a handler plugin system where `with_progress()` manages context and handler state. Key features include integration with parallel frameworks (future, furrr, plyr), Shiny compatibility via `withProgressShiny()`, and a global progression handler for R ≥ 4.0.0. The package emphasizes flexibility—handlers can be mixed and matched, progress reporting can be suppressed, and updates work seamlessly in iterative and parallel contexts. Software engineering rigor is evident through an extensive test suite (50+ test scripts in `inst/testme/`), continuous integration, semantic versioning, and comprehensive vignettes. The design avoids tight coupling—core components like `progressor()`, `with_progress()`, and `progress_aggregator()` are isolated and reusable. While dependencies on optional packages (cli, progress, beepr, etc.) introduce some maintenance complexity, the core remains stable and well-maintained with recent activity.