[Bug 13727] Re: network-admin locations do not get saved correctly

[Sebastien Bacher]

We are just work with upstream to get that fixed to edgy, but that's not
clear what is confusing for users so some concrete comments on what you
would like to get changed would be welcome.

One thing that can be confusing is that if you select a profile and do
modifications then close the tool the modification are not stored to the
profile. The upstream rational is you might want to do changes to your
current session without wanting to store them. The way to store the
change is to add a profile with the same name, which is not a
discovarable way. I've suggested upstream that adding an "store changes
to current profile" button next to the add,remove option already placed
next to the profiles name. What do you think about that?

Another confusion is the instant apply. If the dhcp timeout issue is
fixed, would you prefer an "apply" button anyway or instant apply would
work good enough for that?

We can get the "store configuration" and "apply changes" button next to
the profile, but 4 options starts being a bunch of option, 3 would be
better if possible. I think the "add a profile with the same name to
modify the current profile" is not clear enough and that a "store
changes to profile" button would be welcome. The instant apply should be
fine if the dhcp timeout issue can be workarounded or fixed.

What do you think about that?

-- 
network-admin locations do not get saved correctly
https://launchpad.net/bugs/13727