You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I gathered some ideas for a network widget with features such as scanning and connecting.
Most people use NetworkMananger, which, thankfully, provides introspection and has LGI examples.
Some, like me, use iwd. For that, we can communicate through dbus, and there are also examples in Python for that.
A question though, should we provide an abstracted backend that delivers information like scanned networks and methods for connecting (like our Playerctl backend), or should we provide a full, built widget?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I gathered some ideas for a network widget with features such as scanning and connecting.
Most people use NetworkMananger, which, thankfully, provides introspection and has LGI examples.
Some, like me, use iwd. For that, we can communicate through dbus, and there are also examples in Python for that.
A question though, should we provide an abstracted backend that delivers information like scanned networks and methods for connecting (like our Playerctl backend), or should we provide a full, built widget?
Or should I scrap the idea? 😄
Beta Was this translation helpful? Give feedback.
All reactions