On Mon, 2006-09-11 at 15:08 +0000, Sebastien Bacher wrote: > Let's say you want to use a train station wireless network while > travelling, you probably don't want to modify your profile to connect to > it
If the location was currently set to (eg) my home network, I wouldn't want to change the wireless network name for it if I wanted to connect to the wireless network at the train station. I would either select the blank location, create a new "Train Station" location if I was going to use it frequently, or if not, create a "Roaming" (or similar) location for this sort of situation before modifying anything. Why would I modify my settings for home when I'm at the train station? Again using MacOSX as an example, it by default has an "Automatic" location that just picks an available wireless network if enabled or wired ethernet if plugged in, and uses DHCP to get an address. That is much more useful than network-admin's current behaviour. Perhaps the blank location could be renamed to something similar to "Automatic" and provide some sane default behaviour, like "use DHCP on ethernet if plugged in, else use DHCP on a wireless network if available". When network-admin tells the user "Your location is set to this" and lets them modify some network settings with that still visible, I think it is reasonable to expect that the user will assume they are modifying that location and not some random settings based on the visible location. > Networks might be static but with a laptop you might from from a network > to an another pretty often Would the user be more likely to be using NetworkManager in that case? > DHCP cancel would be nice right. Another question is to know if people > expect to have their network changed only because they are looking at > the available profiles from the list True. I think the UI in X lets you add, duplicate, rename and delete locations, but not activate them from that particular UI. -- ✌ michael gratton, itinerant geek ✇ <http://web.vee.net/> -- [network-admin] locations do not get saved correctly https://launchpad.net/bugs/13727 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
