Author: tilt! Date: To: Edward Bartolo CC: dng Subject: Re: [DNG] netman: support for wlan1, wlan2, ... and eth1, eth2,
.... and new systemd's naming scheme
Hi Edward,
thank you for the explanations.
Am 02.10.2015 um 08:17 schrieb Edward Bartolo: > Tilt wrote: " Does the button "New" take the user to a scan for
> available WiFi networks?"
>
> The button New displays a dialog box which has that functionality, but
> on demand by clicking a button. This avoid users having to wait for
> scanning for wifi signals when they know to which wifi source they
> want to connect.
I think the entire issue "how do i scan for available networks" is badly
implemented in wicd *and* in Windows WiFi Connections (which are two
WiFi connection assistants i know from practice).
In both user interfaces, it is never clear, what a user has to do to
rebuild the list of available networks *now*:
wicd's button for doing that is labeled "Update" (update what?) and it
if the wicd application windows is opened at default size. When
scanning, wicd only offers a marginal user feedback that it currently is
performing a scan: a static, light gray text "Searching" (searching
what?) appears somewhere in the list of networks.
Windows 8 (modern UI) WiFi does not have a Scan-Now-button at all. I
regularly have to jump through hoops to let it rebuild the list of
available WiFi networks by disconnecting, restarting the WiFi network
adapter and other such tricks. It offers no indication that it currently
is scanning at all.
My personal opinion is, netman can offer a clearer implementation of
both interactions:
* If a user wants to scan for available networks *now* there should be a
clearly indicated function to do so.
* If the list of available networks is rebuilt *now*, a clear indication
that says so should be given to the user.