Re: Network Management Plasmoid TODOs
On Monday 09 November 2009 21:32:30 Aaron J. Seigo wrote: On November 9, 2009, Petri Damstén wrote: On Monday 09 November 2009 15:06:40 Sebastian Kügler wrote: Note that I can't test VPN or mobile broadband stuff. If nobody can do that, we should disable it before the release. It would be nice if there could be a simpler configuration dialog shown first on add like: imho, it would be nice if it didn't pop up a second dialog at all and just ask for the username and pasword right inside the nm applet itself; the advanced settings could pop up a dialog perhaps, but there is a lot of room in that new dialog for a simple put in your username, password interface with a couple of buttons. This will only work for WPA-PSK wireless connections though, for EAP, cellular and VPN connections there are just too many mandatory settings to show even a simplified view in the popup. Do you want to introduce a second interaction path just for a different type of wifi connection? Providing secrets in-popup also requires changing the separation between the config UI and the control UIs. Right now the control UIs have no way to modify connections at all. We'd need a way for the control UI to tell the backend to create a default-configured connection for a given SSID (or cellular device, or whatever), activate it, receive the resulting GetSecrets call from NM and forward that to the control UI, get secrets, then pass the secrets back to NM. Will ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Network Management Plasmoid TODOs
On Tuesday 10 November 2009 17:49:04 Will Stephenson wrote: This will only work for WPA-PSK wireless connections though, for EAP, cellular and VPN connections there are just too many mandatory settings to show even a simplified view in the popup. Do you want to introduce a second interaction path just for a different type of wifi connection? I think for cellular Country + Provider would be enough in most cases. For VPN simple config could be just 'import settings file'. Petri signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Network Management Plasmoid TODOs
On November 10, 2009, Will Stephenson wrote: This will only work for WPA-PSK wireless connections though, for EAP, cellular and VPN connections there are just too many mandatory settings to show even a simplified view in the popup. Do you want to introduce a second interaction path just for a different type of wifi connection? Given wireless will be the common case, especially the common case where people change the settings a lot, I think this would be fine if not great. Would Petri's suggestion be workable? Providing secrets in-popup also requires changing the separation between the config UI and the control UIs. Ah, that's probably even more problematic than the above issue ... Right now the control UIs have no way to modify connections at all. We'd need a way for the control UI to tell the backend to create a default-configured connection for a given SSID (or cellular device, or whatever), activate it, receive the resulting GetSecrets call from NM and forward that to the control UI, get secrets, then pass the secrets back to NM. Hm.. would it be possible to have the config UI put its widgets in a user- defined container? *thinks* I suppose for this to work, the config UI would need to be able to ask the control UI where to put some UI elements and be able to differentiate between simple and complex UIs (as they might be treated differently). this is sounding more and more like a KDE 4.5 goal :) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Network Management Plasmoid TODOs
On Monday 09 November 2009 14:06:40 Sebastian Kügler wrote: Status update... On Friday 06 November 2009 19:00:54 Will Stephenson wrote: Off the top of my head: * Check that RemoteVpnConnectionitem and RemoteHiddenWirelessNetworkConnectionitem are complete (service side) * Implement these including Disconnect button * Design the Plasma side graphicsitem family for minimum code duplication * Tooltips Should both be OK, modulo some smallish fixes that will creep in. * Make main interface (not popup) able to show connecting, connected, VPN active states Which main interface are you talking about? What's the proper name for the plasmoid as it appears in a containment in non- popped-up state? That interface. * A plasma-esque way to show the list of all wireless networks (not in the main popup, so this doesn't explode out of the screen). KNetworkManager uses a regular KDialog for this Again, what exactly do you mean? I mean 'do what KNetworkManager does' and don't fill the popup with unconfigured wireless networks that we are not interested in most of the time and just add noise. Instead show configured wireless networks (WirelessInterfaceConnections) in the popup, and show other WirelessNetworks and all HiddenWirelessNetworks (so that people can connect to their configured hidden networks in a second level dialog. * (Optional) icon per interface support Is this off the table for 4.4? * The service needs either properly kded-modulizing or splitting out into a separate process like kwalletd I'm sure we'll come up more in the meeting starting NOW in #plasma Over the weekend, I've done the following: - removed SVGs, use KIcon all over - fix up tooltips and interface item's title - less code duplication, new class UiUtils (in libs/ui now) Next to tackle: 1 connection progress in the panel icon 2 buglet in sorting connection list, an interface that is connecting should be more important than an inactive one 3 layouting bug where the activatablelist overflows its scrollwidget (looks like a parenting problem) 4 I'm asked more than once for the connection's password, I think knetworkmanager has the same problem When exactly? The known 'bug' is that since knetworkmanager, and the KCM, are distinct apps, KWallet policy has to be set independently on those, so you get one KWallet dialog when first creating a connection, and another one when knetworkmanager (or the kded module, for the plasmoid) tries to open the wallet to provide NM with the password. I'd appreciate if someone could look into the latter two (3 and 4), I've been banging my head against the layoutwall enough already. Note that I can't test VPN or mobile broadband stuff. If nobody can do that, we should disable it before the release. I can test those. The main things to do for those are make sure there is a disconnect button shown when they are connected (doesn't need hardware or a VPN login) and check that the 'main UI' (as defined above) shows the right icon when those are active (needs hardware or a VPN login). Will ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Network Management Plasmoid TODOs
On Monday 09 November 2009 15:06:40 Sebastian Kügler wrote: Note that I can't test VPN or mobile broadband stuff. If nobody can do that, we should disable it before the release. It would be nice if there could be a simpler configuration dialog shown first on add like: Add wireless: Network: [ Strongest net v] Password: [ ] [Advanced...] Add mobile: Country: [ From geolocation? v] Operator: [v] [Advanced...] nm-applet has country/operator selection for mobile and it's pretty useful. Petri signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Network Management Plasmoid TODOs
On Monday 09 November 2009 14:34:11 Petri Damstén wrote: On Monday 09 November 2009 15:06:40 Sebastian Kügler wrote: Note that I can't test VPN or mobile broadband stuff. If nobody can do that, we should disable it before the release. It would be nice if there could be a simpler configuration dialog shown first on add like: Add wireless: Network: [ Strongest net v] Password: [ ] [Advanced...] Add mobile: Country: [ From geolocation? v] Operator: [v] [Advanced...] nm-applet has country/operator selection for mobile and it's pretty useful. These are both on the TODO list already. Will ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Network Management Plasmoid TODOs
On Monday 09 November 2009 15:36:17 Sebastian Kügler wrote: On Monday 09 November 2009 14:20:26 Will Stephenson wrote: On Monday 09 November 2009 14:06:40 Sebastian Kügler wrote: * Make main interface (not popup) able to show connecting, connected, VPN active states I'd do it as follows: - we have a progress bar sitting in the bottom (horizontal, seems visually more like a progress bar). That ones laid over the icon dynamically. This progress bar is used for connecting *any* connection. (For wireless you'll see it while - an overlay icon, possibly top-right, half-width and height of the parent icon: - it shows a checkmark for a couple of seconds after connections are established - it shows a permanent overlay (on top of the hardware icon) for connected VPNs - it shows a (!) when user interaction is required (for example a password dialog waits to be filled in) We'll have to see how much visual clutter this adds, though. In knetworkmanager, you have something similar (progress bar + overlay icon), I think that's OK visually, but normally I'd like to hide the progress bar. Can we come up with one design for these extra info overlays in the mails we're exchanging with ademmer and pinheiro that we can use in both KNM and the applet? Which main interface are you talking about? What's the proper name for the plasmoid as it appears in a containment in non- popped-up state? That interface. Let's call it panel view (yeah, just made that up). :) * A plasma-esque way to show the list of all wireless networks (not in the main popup, so this doesn't explode out of the screen). KNetworkManager uses a regular KDialog for this Again, what exactly do you mean? I mean 'do what KNetworkManager does' and don't fill the popup with unconfigured wireless networks that we are not interested in most of the time and just add noise. I'll have a look at how knetworkmanager does it. Maybe some sort of toggle for the list of activatables for showing or hiding those unconfigured networks, possibly with some magic in the background (i.e. toggle to show all when there's no preconfigured network found). Instead show configured wireless networks (WirelessInterfaceConnections) in the popup, and show other WirelessNetworks and all HiddenWirelessNetworks (so that people can connect to their configured hidden networks in a second level dialog. We should sort the known ones on top (note: need an icon for that, right now using the bookmarks one since that's semantically closest to known network). IF you show unconfigured networks in the popup you should have 2 things * scrollview instead of expanding the popup * a searchline for use in densely populated areas * (Optional) icon per interface support Is this off the table for 4.4? I'd say no, though not a priority right now. It shouldn't be very hard to do now. I would try to plan for this now by having a list of interface UNIs that the popup knows about to display info for * The service needs either properly kded-modulizing or splitting out into a separate process like kwalletd I'm sure we'll come up more in the meeting starting NOW in #plasma Over the weekend, I've done the following: - removed SVGs, use KIcon all over - fix up tooltips and interface item's title - less code duplication, new class UiUtils (in libs/ui now) Next to tackle: 1 connection progress in the panel icon 2 buglet in sorting connection list, an interface that is connecting should be more important than an inactive one 3 layouting bug where the activatablelist overflows its scrollwidget (looks like a parenting problem) 4 I'm asked more than once for the connection's password, I think knetworkmanager has the same problem When exactly? The known 'bug' is that since knetworkmanager, and the KCM, are distinct apps, KWallet policy has to be set independently on those, so you get one KWallet dialog when first creating a connection, and another one when knetworkmanager (or the kded module, for the plasmoid) tries to open the wallet to provide NM with the password. After creating the account, it's trying to connect and then immediately it brings up the password dialog again (with password now filled in). It's not a kwallet dialog. Ok then NM is re-issuing GetSecrets when you try to collect, look at the NM logs to see why it might be doing this. Will ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Network Management Plasmoid TODOs
On Monday 09 November 2009 15:45:03 Will Stephenson wrote: We should sort the known ones on top (note: need an icon for that, right now using the bookmarks one since that's semantically closest to known network). IF you show unconfigured networks in the popup you should have 2 things * scrollview instead of expanding the popup It is one already, it only doesn't work. That's the layout problem I'm talking about. * a searchline for use in densely populated areas Hm, sure that's really needed? If we put stronger networks on top, they're probably easy enough to get at. A searchline would add quite some clutter, IMO. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Network Management Plasmoid TODOs
On November 9, 2009, Sebastian Kügler wrote: Let's call it panel view or popup icon as the API is PopupApplet::setPopupIcon() :) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
