[kde] [Bug 474576] New: sddm-theme: add wireless (WiFi) widget
Sergey Katunin
bugzilla_noreply at kde.org
Fri Sep 15 21:08:17 BST 2023
https://bugs.kde.org/show_bug.cgi?id=474576
Bug ID: 474576
Summary: sddm-theme: add wireless (WiFi) widget
Classification: I don't know
Product: kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: sulmpx60 at yandex.ru
Target Milestone: ---
Created attachment 161650
--> https://bugs.kde.org/attachment.cgi?id=161650&action=edit
wireless widget screenshot
I would like to offer an feature with a widget to connect to a wireless
connection directly from sddm-theme (breeze) on the login screen. It seems that
this feature is present in Win 10, and possibly in GDM.
### Description
Anyway, I implemented a working prototype of the Wi-fi widget on SDDM-theme
(breeze) for KDE version 5.27. We needed this feature because we have
implemented a custom authorization that requires Internet on the login screen.
The interesting fact is that it didn't even need any new C++ code. This can be
implemented only by QML code (although it is not very convenient in several
places, but the goal was to minimize the difference from the upstream), by
using present QML plugin for `PlasmaNM` (import
org.kde.plasma.networkmanagement 0.2 as PlasmaNM).
Check attachments for video and image.
For image - description of elements:
1. Button in corner of sddm-theme to launch wireless connection panel.
2. Status and name of wireless connection.
3. Wireless 'select' component.
4. Password input.
5. Connect button.
### Problem
I expect the following problems:
1. Perhaps the KDE community does not want to introduce such a feature in
principle. (However, we can provide this as an optional feature through the
checkbox in the settings).
2. Non-compliance with KDE design requirements.
3. It is necessary to adapt to KDE 6, and it may be necessary to make some
changes to Plasma NM to implement the missing useful functions for this case (I
can't remember specific examples, but something like: 1) get connected wireless
name; 2) get wireless connection status; 3) get wired connection status; 4) is
connection has password; 5) is selected connection has enterprise security;
etc)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list