Cross-Platform Rewrite Discussion
The EVE community has shown interest in expanding Argus Overview beyond Linux. Currently v3.0 supports Linux (X11/XWayland) and Windows (Win32 API), but Mac support and a Wayland-native path remain open.
What's on the table
- Mac support — Currently unsupported. Requires a new platform backend
- Wayland native — Pure Wayland's security model blocks window management today. A compositor-specific or portal-based approach could change this
- Single-binary distribution — A compiled language (Rust, Go, C++) would simplify packaging across all platforms
Language options being considered
| Language |
Pros |
Cons |
| Qt/C++ |
Closest to current PySide6 arch |
C++ complexity, build toolchain |
| Rust + egui/iced |
Performance, safety, single binary |
Ecosystem maturity for GUI |
| Go + Fyne |
Simple, fast builds |
Less mature GUI ecosystem |
How to contribute
If you're interested in working on any aspect of this:
- Comment here with your platform interest (Mac, Wayland, etc.)
- Read
docs/ARCHITECTURE.md and src/argus_overview/platform/base.py for the abstraction contract
- See CONTRIBUTING.md "High Impact Contributions" section for detailed guidance
- Open a separate issue for your specific implementation proposal
Community validation
This roadmap item was surfaced through community discussion. Your +1 and input helps prioritize this work.
This is a discussion issue — no commitment to a specific timeline or implementation. The goal is to gather interest and let contributors self-organize around the work.
Cross-Platform Rewrite Discussion
The EVE community has shown interest in expanding Argus Overview beyond Linux. Currently v3.0 supports Linux (X11/XWayland) and Windows (Win32 API), but Mac support and a Wayland-native path remain open.
What's on the table
Language options being considered
How to contribute
If you're interested in working on any aspect of this:
docs/ARCHITECTURE.mdandsrc/argus_overview/platform/base.pyfor the abstraction contractCommunity validation
This roadmap item was surfaced through community discussion. Your +1 and input helps prioritize this work.
This is a discussion issue — no commitment to a specific timeline or implementation. The goal is to gather interest and let contributors self-organize around the work.