WayfireWM / WayfireWM/wf-shell
panel network: Depends on NetworkManager, which not everyone uses
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 179
- Forks
- 55
- Avg merge
- 16d 1h
- Merged PRs (30d)
- 3
Description
This might be outside of your scope, but the network widget currently seems to use only data from NetworkManager, which not everyone uses. In my case, a solution like IWD has proven itself to be more than enough to automatically manage connections. I'd still like to be able to verify connection status while using wayfire.
The waybar implementation of such a widget supports connections set up through IWD only, so it's possible to take a look at how they implemented it and translate it to your project.
I'm open to helping with this, as well!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the network panel implementation and compare it with the Waybar implementation of an IWD-only connection widget. Define how connection status should work for IWD without assuming NetworkManager, then verify the result in Wayfire with an IWD-managed connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100