Replaces the previous approach of spawning new PipeWire main loops and
awaiting a 100ms timeout for every `get_all_devices` call. Instead,
this introduces a `PipeWireManager` which maintains a single, persistent
background thread with a PipeWire main loop and registry listener. The
actor caches `AudioDevice`s and `Port`s continuously in a `HashMap`,
providing instantaneous responses to device queries via a channel.
This architectural change replaces `Sender<Terminate>` with a simple
`PwTerminator` drop-guard to manage the lifetimes of PipeWire objects
(virtual mic and links) via `PwCommand::DestroyObject` without creating
additional OS threads or PipeWire contexts.
Co-authored-by: arabianq <55220741+arabianq@users.noreply.github.com>
* Refactor project into a Cargo workspace with distinct packages
- Created a root `Cargo.toml` defining a workspace.
- Moved `src/types` and `src/utils` into a new `pwsp-lib` crate for shared logic.
- Split binaries into their own crates: `pwsp-daemon`, `pwsp-cli`, and `pwsp-gui`.
- Shifted all dependencies into `[workspace.dependencies]` for centralized version management.
- Updated import paths across all crates (e.g. from `pwsp::` to `pwsp_lib::`).
- Updated build scripts, GitHub actions, Flatpak manifest, and AUR PKGBUILD to support the new workspace structure.
- Ensured no core application logic was altered.
Co-authored-by: arabianq <55220741+arabianq@users.noreply.github.com>
* Fix cargo-deb build process in GitHub actions for workspace architecture
Co-authored-by: arabianq <55220741+arabianq@users.noreply.github.com>
* Fix cargo-deb asset discovery by using exact target/release paths
Co-authored-by: arabianq <55220741+arabianq@users.noreply.github.com>
* refactor deps in Cargo.toml files
* fix incorrect assets path
---------
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
google-labs-jules[bot]
Tarasov Aleksandr