Ed, if you're taking requests for features, I've got some...

1. netman --help (to show what command line options exist)

2. If the config file will accept a definition for an interface other than
wlan0 or eth0, a commented example showing the correct syntax would help.
And while you're thinking about this, maybe it's a good time to think
ahead to when the interface names will change, if you haven't already done
that. (e.g. from ethX to enp-blah.)

3. Some way to display the IP address when connected, either on-demand or
along with the word, Connected, or some other way.

fsr


@Hendrik,

Here's are the places I know where wireless connection information gets
stored. You can probably just copy the files over to a new system. I've
never tried it.

/var/lib/wicd/configurations/*
/etc/NetworkManager/system-connections


fsr


On 09/26/2015 12:13 PM, Edward Bartolo wrote:
> Hi All,
>
> Now netman, the GUI uses a systray icon. Right clicking shows a popup
> menu and left clicking displays the netman main window.
>
> Since there are window manager users and I don't use a window manager,
> I would like to know whether using a systray icon will negatively
> impact users of window managers. In other words, is it possible to
> display a systray icon in a window manager? If not I will need to do
> something about that.
>
> Please give me feedback.
>
> Edward
>
>
> On 26/09/2015, Edward Bartolo <edbarx@???> wrote:
>> If you know the essids and the corresponding password you can reenter
>> these by clicking the New button and filling the essid and password.
>> You can also switch between obfuscating the password chars and seeing
>> exactly what you type.
>>
>> netman uses an algorithm where it gives first priority to the best
>> wifi signal available provided a corresponding essid file exists. So,
>> if you are away from say wifiX, netman will not attempt to use it
>> unless you force to do so.
>>
>> Edward
>>
>> On 26/09/2015, Hendrik Boom <hendrik@???> wrote:
>>> On Sat, Sep 26, 2015 at 01:25:09PM +0200, Edward Bartolo wrote:
>>>> This is a screen shot with the Edit dialog shown.
>>>> http://postimg.org/image/9obv7fnlp/
>>>
>>>
>>> Your aerial view walpaper is lovely. It's on the verge of giving me
>>> vertigo.
>>>
>>> I'm wondering if there are technical reasons to switch from wicd to
>>> netman. As far as I know, wicd is systemd-free. Is there any reason to
>>> suspect it's going to be otherwise?
>>>
>>> There is a nontechnical reason, of course, which is supporting our own
>>> developers.
>>>
>>> The main issue is I have with switching is that if I have trouble with
>>> it, whether it's my fault or not, I'll lose the convenient network
>>> access I use to ask for help.
>>>
>>> I'm currently using wicd, and there's one user-oriented feature it seems
>>> to lack. When I'm at a site where they provide wifi, it detects it,
>>> then allows me to enter the local wifi password.
>>>
>>> But when I'm away from it, there seems to be no way to tell it about the
>>> now-remote site.
>>>
>>> Now the occasions on which I want to use it are vanishingly small. But
>>> is has once happened that I'm initialising a new device, and it would be
>>> massively convenient not to have to visit every wifi spot I plan to use
>>> merely to transfer the passwords from the old device to the new.
>>>
>>> Can netman do this?
>>>
>>> I also like a mode in which I can see the password I'm entering. I'm
>>> not a great typist, and I'd like to know whether I have the wrong
>>> password or merely entered it wrong. When my wife broke her wrist,
>>> correct password typing became an unsurmountable obstacle for her.
>>> Seeing the password is a security risk, but it's also an invaluable
>>> accessibility feature.
>>>
>>> All in all, considering where you started from, you've done an
>>> amazing job. I haven't read the code or tried it, but the UI looks
>>> straightforward and to the point. You have probably learned a lot, too.
>>> Keep up the good work.
>>>
>>> -- hendrik