<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Managing your Wireless Networks</title>
	<atom:link href="http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/feed/" rel="self" type="application/rss+xml" />
	<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/</link>
	<description>Little n desigN</description>
	<pubDate>Fri, 29 Aug 2008 07:19:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Bryan Clark</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-3082</link>
		<dc:creator>Bryan Clark</dc:creator>
		<pubDate>Tue, 20 Nov 2007 17:54:50 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-3082</guid>
		<description>Jay:  Yeah, that's just the inline way of accessing the preferences dialog.  The network preferences dialog should also be accessible from either the System Preferences menu or right clicking on the nm-applet icon.</description>
		<content:encoded><![CDATA[<p>Jay:  Yeah, that&#8217;s just the inline way of accessing the preferences dialog.  The network preferences dialog should also be accessible from either the System Preferences menu or right clicking on the nm-applet icon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-2328</link>
		<dc:creator>Jay</dc:creator>
		<pubDate>Mon, 05 Nov 2007 20:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-2328</guid>
		<description>Bryan,
One hiccup I see with this is that you have to wait for NM to connect to AP's before you can manage them.</description>
		<content:encoded><![CDATA[<p>Bryan,<br />
One hiccup I see with this is that you have to wait for NM to connect to AP&#8217;s before you can manage them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Clark</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-2165</link>
		<dc:creator>Bryan Clark</dc:creator>
		<pubDate>Wed, 31 Oct 2007 19:13:39 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-2165</guid>
		<description>David: The preference menu should take you to a dialog that would allow for these kinds of settings.  I haven't worked out a dialog yet, but so far we're thinking it will have at least 2 sections for wireless and wired settings as well as some kind of static IP config.</description>
		<content:encoded><![CDATA[<p>David: The preference menu should take you to a dialog that would allow for these kinds of settings.  I haven&#8217;t worked out a dialog yet, but so far we&#8217;re thinking it will have at least 2 sections for wireless and wired settings as well as some kind of static IP config.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Fraser</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-2003</link>
		<dc:creator>David Fraser</dc:creator>
		<pubDate>Sun, 28 Oct 2007 18:23:43 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-2003</guid>
		<description>What I would appreciate is an advanced dialog that lets you specify IP settings for a particular wireless network.
For me DHCP works in most cases but there are a few networks I use occasionally that haven't been set up. It would be nice to be able to configure settings for these networks that are remembered for them but don't mess up anything else</description>
		<content:encoded><![CDATA[<p>What I would appreciate is an advanced dialog that lets you specify IP settings for a particular wireless network.<br />
For me DHCP works in most cases but there are a few networks I use occasionally that haven&#8217;t been set up. It would be nice to be able to configure settings for these networks that are remembered for them but don&#8217;t mess up anything else</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Quist</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1968</link>
		<dc:creator>Frank Quist</dc:creator>
		<pubDate>Sat, 27 Oct 2007 15:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1968</guid>
		<description>Shouldn't post at night, I start to mix up thing. Correction on previous post:
"“Auto-switched from wireless to wired network”
[Don’t prefer wired]"</description>
		<content:encoded><![CDATA[<p>Shouldn&#8217;t post at night, I start to mix up thing. Correction on previous post:<br />
&#8220;“Auto-switched from wireless to wired network”<br />
[Don’t prefer wired]&#8220;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Clark</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1966</link>
		<dc:creator>Bryan Clark</dc:creator>
		<pubDate>Sat, 27 Oct 2007 14:52:19 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1966</guid>
		<description>Zack: I like the prefer this network idea. It does bring the concept of "this" network and is pretty short.  For the other button something like just Preferences or Configure is probably fine, looking at it now I'm not sure why I put Network in front of it :)

onox, Jakub, others: You can't use a checkbox because of the way the notification system was designed.  The protocol doesn't allow for arbitrary widgets in the bubbles, you can only place buttons.  It's a crappy constraint we have to work with until someone fixes the notification system.

David: the Network Preferences (for wireless) would bring up such a dialog where you could fix and organize how your networks are configured. 

Jose: I like the ideas, if only we could use a checkbox...

j: The automatic behavior is going to remain, however only having a right click access to fixing things doesn't help more people to find and use that dialog.  We want it to be upfront, but not in the way.

richard:  The wired option seems kind of silly in my mind as well.  However a lot of people have expressed the desire to plug in a wired connection, yet not disconnect their wireless until it's gone.  This is mostly application behavior related to network switching, but for some things like IRC you can't just swap out networks. 

Frank: good points, you combined a lot of the good ideas.</description>
		<content:encoded><![CDATA[<p>Zack: I like the prefer this network idea. It does bring the concept of &#8220;this&#8221; network and is pretty short.  For the other button something like just Preferences or Configure is probably fine, looking at it now I&#8217;m not sure why I put Network in front of it <img src='http://clarkbw.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>onox, Jakub, others: You can&#8217;t use a checkbox because of the way the notification system was designed.  The protocol doesn&#8217;t allow for arbitrary widgets in the bubbles, you can only place buttons.  It&#8217;s a crappy constraint we have to work with until someone fixes the notification system.</p>
<p>David: the Network Preferences (for wireless) would bring up such a dialog where you could fix and organize how your networks are configured. </p>
<p>Jose: I like the ideas, if only we could use a checkbox&#8230;</p>
<p>j: The automatic behavior is going to remain, however only having a right click access to fixing things doesn&#8217;t help more people to find and use that dialog.  We want it to be upfront, but not in the way.</p>
<p>richard:  The wired option seems kind of silly in my mind as well.  However a lot of people have expressed the desire to plug in a wired connection, yet not disconnect their wireless until it&#8217;s gone.  This is mostly application behavior related to network switching, but for some things like IRC you can&#8217;t just swap out networks. </p>
<p>Frank: good points, you combined a lot of the good ideas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Klawiter</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1954</link>
		<dc:creator>Jakub Klawiter</dc:creator>
		<pubDate>Sat, 27 Oct 2007 07:46:46 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1954</guid>
		<description>I'm still not sure if anyone need any button/checkbox here, but i'm sure that you don't need to close it (click teh button) because it is notification, it will be available on the screen just for few seconds.

I understand that there is no other way to make the task (like preferences dialog hidden in right click). If so, IMO small checkbox is better than two buttons.</description>
		<content:encoded><![CDATA[<p>I&#8217;m still not sure if anyone need any button/checkbox here, but i&#8217;m sure that you don&#8217;t need to close it (click teh button) because it is notification, it will be available on the screen just for few seconds.</p>
<p>I understand that there is no other way to make the task (like preferences dialog hidden in right click). If so, IMO small checkbox is better than two buttons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ubuntu</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1948</link>
		<dc:creator>ubuntu</dc:creator>
		<pubDate>Sat, 27 Oct 2007 03:51:14 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1948</guid>
		<description>I say dump the Network Preferences button entirely, that type of button should not be on a notification dialog at all.</description>
		<content:encoded><![CDATA[<p>I say dump the Network Preferences button entirely, that type of button should not be on a notification dialog at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Quist</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1937</link>
		<dc:creator>Frank Quist</dc:creator>
		<pubDate>Sat, 27 Oct 2007 00:04:50 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1937</guid>
		<description>I think the wording on the button could be clearer and less ambiguous. You add an explanation to both the wired bubble with the following:

The wired bubble: "Always Auto-connect"/"Don't Auto-connect again". In this case you specifically explain the behaviour to be only applicable to an automatic switch from wireless to wired. 

On the wireless bubble, however, you explain the auto-connect option to apply to only the particular network that's popping up. Without these explanations, however, neither buttons' right meaning would have been clear.

This difference in behaviour between wired/wireless (auto-connect in wired mode is a general option, in wireless it only pertains to connecting to *one* network) makes the text ambigious when it is the same in both situations, and probably trains the user wrong. On both bubbles, I would read it to mean "(Don't) autoconnect me to a wired/wireless connection". I wouldn't read any of the mentioned meanings int that, and would thus mistake the message.

I like the "Prefer this network" idea. I would also not mind anything like the following, which would cut out the mentioned ambiguities:

"Auto-switched from wired to wireless network"
[Don't prefer wired]

"You are now connected to the wired network"
[Always prefer wired]</description>
		<content:encoded><![CDATA[<p>I think the wording on the button could be clearer and less ambiguous. You add an explanation to both the wired bubble with the following:</p>
<p>The wired bubble: &#8220;Always Auto-connect&#8221;/&#8221;Don&#8217;t Auto-connect again&#8221;. In this case you specifically explain the behaviour to be only applicable to an automatic switch from wireless to wired. </p>
<p>On the wireless bubble, however, you explain the auto-connect option to apply to only the particular network that&#8217;s popping up. Without these explanations, however, neither buttons&#8217; right meaning would have been clear.</p>
<p>This difference in behaviour between wired/wireless (auto-connect in wired mode is a general option, in wireless it only pertains to connecting to *one* network) makes the text ambigious when it is the same in both situations, and probably trains the user wrong. On both bubbles, I would read it to mean &#8220;(Don&#8217;t) autoconnect me to a wired/wireless connection&#8221;. I wouldn&#8217;t read any of the mentioned meanings int that, and would thus mistake the message.</p>
<p>I like the &#8220;Prefer this network&#8221; idea. I would also not mind anything like the following, which would cut out the mentioned ambiguities:</p>
<p>&#8220;Auto-switched from wired to wireless network&#8221;<br />
[Don't prefer wired]</p>
<p>&#8220;You are now connected to the wired network&#8221;<br />
[Always prefer wired]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: richard</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1936</link>
		<dc:creator>richard</dc:creator>
		<pubDate>Sat, 27 Oct 2007 00:04:21 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1936</guid>
		<description>I like your idea about the wireless options but I don't think I get why you need the same for wireline.  Why not just have a preference called 'Prefer wireline connections'.  If this option is checked auto-connect to a wireline connection, if its not, require manual intervention to switch to wireline.  Seems simple enough.</description>
		<content:encoded><![CDATA[<p>I like your idea about the wireless options but I don&#8217;t think I get why you need the same for wireline.  Why not just have a preference called &#8216;Prefer wireline connections&#8217;.  If this option is checked auto-connect to a wireline connection, if its not, require manual intervention to switch to wireline.  Seems simple enough.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: j</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1932</link>
		<dc:creator>j</dc:creator>
		<pubDate>Fri, 26 Oct 2007 22:29:16 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1932</guid>
		<description>I'd say, no option in the notification bubble. Keep the current automagic behaviour by default.

Add an entry "Manage behaviour" or something like that in the right-click menu for the applet.

NM would then show a dialog with a history of the networks it connected to. And here you'd have options like "never again".</description>
		<content:encoded><![CDATA[<p>I&#8217;d say, no option in the notification bubble. Keep the current automagic behaviour by default.</p>
<p>Add an entry &#8220;Manage behaviour&#8221; or something like that in the right-click menu for the applet.</p>
<p>NM would then show a dialog with a history of the networks it connected to. And here you&#8217;d have options like &#8220;never again&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jose Moreira</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1927</link>
		<dc:creator>Jose Moreira</dc:creator>
		<pubDate>Fri, 26 Oct 2007 21:24:10 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1927</guid>
		<description>I thought the same as onox and Jakub, use a checkbox instead of a button.

Also replaced "Network preferences..." by "More options..." in button,
because the button looks to me like a continuation of the check box option.

Also I made these poor-man mockups for how the pop-ups could look like
(there woul be just two of them, not four). They'll surely look bad with this
proportional font, though.

Wired case:
   ------------------------------------------------------------------
  &#124;    Connected to Wire                                                             X  &#124;
  &#124;                                                                                                            &#124;
  &#124;    You are now connected to the wired network            &#124;
  &#124;    EFGH                                                                                             &#124;
  &#124;                                                                                                            &#124;
  &#124;        [v] Auto-switch to this wire next time                       &#124;
  &#124;                                                                                                            &#124;
  &#124;                                                           [More preferences...]     &#124;
  --------------------------------------------------------   ---------
                                                                                               \/

Wireless case:
   ------------------------------------------------------------------
  &#124;    Connected to Wireless                                                     X  &#124;
  &#124;                                                                                                            &#124;
  &#124;    You are now connected to the wireless network       &#124;
  &#124;    XYZT                                                                                            &#124;
  &#124;                                                                                                            &#124;
  &#124;        [v] Auto-connect next time                                            &#124;
  &#124;                                                                                                            &#124;
  &#124;                                                           [More preferences...]     &#124;
  --------------------------------------------------------   ---------
                                                                                               \/

I might be totally wrong in these things, of course. After all my only
network connection at home is an old-fashioned 56 Kbps modem
(not handled by NM, sigh).</description>
		<content:encoded><![CDATA[<p>I thought the same as onox and Jakub, use a checkbox instead of a button.</p>
<p>Also replaced &#8220;Network preferences&#8230;&#8221; by &#8220;More options&#8230;&#8221; in button,<br />
because the button looks to me like a continuation of the check box option.</p>
<p>Also I made these poor-man mockups for how the pop-ups could look like<br />
(there woul be just two of them, not four). They&#8217;ll surely look bad with this<br />
proportional font, though.</p>
<p>Wired case:<br />
   &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
  |    Connected to Wire                                                             X  |<br />
  |                                                                                                            |<br />
  |    You are now connected to the wired network            |<br />
  |    EFGH                                                                                             |<br />
  |                                                                                                            |<br />
  |        [v] Auto-switch to this wire next time                       |<br />
  |                                                                                                            |<br />
  |                                                           [More preferences...]     |<br />
  &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;   &#8212;&#8212;&#8212;<br />
                                                                                               \/</p>
<p>Wireless case:<br />
   &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
  |    Connected to Wireless                                                     X  |<br />
  |                                                                                                            |<br />
  |    You are now connected to the wireless network       |<br />
  |    XYZT                                                                                            |<br />
  |                                                                                                            |<br />
  |        [v] Auto-connect next time                                            |<br />
  |                                                                                                            |<br />
  |                                                           [More preferences...]     |<br />
  &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;   &#8212;&#8212;&#8212;<br />
                                                                                               \/</p>
<p>I might be totally wrong in these things, of course. After all my only<br />
network connection at home is an old-fashioned 56 Kbps modem<br />
(not handled by NM, sigh).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zack Cerza</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1924</link>
		<dc:creator>Zack Cerza</dc:creator>
		<pubDate>Fri, 26 Oct 2007 20:04:10 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1924</guid>
		<description>If a button is used, clicking on the button logically will dismiss the notification popup. If you use a checkbox, it logically would not dismiss the popup. So while you may solve one problem, you create another by requiring an extra click to dismiss the popup.</description>
		<content:encoded><![CDATA[<p>If a button is used, clicking on the button logically will dismiss the notification popup. If you use a checkbox, it logically would not dismiss the popup. So while you may solve one problem, you create another by requiring an extra click to dismiss the popup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Klawiter</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1923</link>
		<dc:creator>Jakub Klawiter</dc:creator>
		<pubDate>Fri, 26 Oct 2007 19:56:45 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1923</guid>
		<description>Isn't it better idea to change don't autoconnect / always autoconnect button into checkbox "autoconnect to this network"? This way, teh text cen be longer also, because it is not button, but just checkbox label.</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t it better idea to change don&#8217;t autoconnect / always autoconnect button into checkbox &#8220;autoconnect to this network&#8221;? This way, teh text cen be longer also, because it is not button, but just checkbox label.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adel</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1922</link>
		<dc:creator>adel</dc:creator>
		<pubDate>Fri, 26 Oct 2007 19:36:59 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1922</guid>
		<description>epiphany/evolution thinks am offline while am connected using adsl, this is because NM! can you fix it?</description>
		<content:encoded><![CDATA[<p>epiphany/evolution thinks am offline while am connected using adsl, this is because NM! can you fix it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Benjamin</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1920</link>
		<dc:creator>David Benjamin</dc:creator>
		<pubDate>Fri, 26 Oct 2007 18:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1920</guid>
		<description>Could n-m also add  configuration dialog (Maybe like "Advanced configuration" or something if it's not "user friendly") that lets us see the list of remembered networks and add/remove them and possibly mess with remembered passwords and such? Network-manager has gotten quite confused for me in the past and cleaning things out with gconf is very unpleasant.

A lot of those auto-connect features are great and all, but I think they are too unforgiving to mistakes. If someone accidentally marks some network or changes their mind, it takes a lot of work to remove it. I don't think this is desirable behavior.

Plus, such a UI will probably be necessary anyway to support auto-recognizing of hidden networks. (Unless you want for any hidden network to be automatically added to a list to check for which seems quite silly.) And that really should be fixed because typing in all the details every time is a huge pain. Especially since the "Connect to Other Wireless Network" dialog does not auto-detect anything about the access point, and so I have to select the flavor of WPA, and everything each time. Somewhat annoying.</description>
		<content:encoded><![CDATA[<p>Could n-m also add  configuration dialog (Maybe like &#8220;Advanced configuration&#8221; or something if it&#8217;s not &#8220;user friendly&#8221;) that lets us see the list of remembered networks and add/remove them and possibly mess with remembered passwords and such? Network-manager has gotten quite confused for me in the past and cleaning things out with gconf is very unpleasant.</p>
<p>A lot of those auto-connect features are great and all, but I think they are too unforgiving to mistakes. If someone accidentally marks some network or changes their mind, it takes a lot of work to remove it. I don&#8217;t think this is desirable behavior.</p>
<p>Plus, such a UI will probably be necessary anyway to support auto-recognizing of hidden networks. (Unless you want for any hidden network to be automatically added to a list to check for which seems quite silly.) And that really should be fixed because typing in all the details every time is a huge pain. Especially since the &#8220;Connect to Other Wireless Network&#8221; dialog does not auto-detect anything about the access point, and so I have to select the flavor of WPA, and everything each time. Somewhat annoying.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: onox</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1919</link>
		<dc:creator>onox</dc:creator>
		<pubDate>Fri, 26 Oct 2007 17:44:36 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1919</guid>
		<description>I would suggest creating a checkbox with the label "Auto-connect". Depending on whether NM always auto-connects for some wired/wireless network, this checkbox has a corresponding state.</description>
		<content:encoded><![CDATA[<p>I would suggest creating a checkbox with the label &#8220;Auto-connect&#8221;. Depending on whether NM always auto-connects for some wired/wireless network, this checkbox has a corresponding state.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zack Cerza</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1917</link>
		<dc:creator>Zack Cerza</dc:creator>
		<pubDate>Fri, 26 Oct 2007 17:14:22 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1917</guid>
		<description>(Note to Bryan: escape your comment input!)

However the auto-connect options are worded, this is how I will read them:

[ &#60;3 this network! ]  -OR- [ This network fails D: ]

So maybe something like:

[ Configure... ] [ Prefer this network ]
[ Configure... ] [ Don't prefer this network ]

I think 'Configure' sounds way less crappy than 'Network Preferences'. I mean, those settings aren't optional after I set them; If NM bugs out and ignores them, I'm not going to say "well, those were just my /preferences/... I don't care /that/ much." ;)</description>
		<content:encoded><![CDATA[<p>(Note to Bryan: escape your comment input!)</p>
<p>However the auto-connect options are worded, this is how I will read them:</p>
<p>[ &lt;3 this network! ]  -OR- [ This network fails D: ]</p>
<p>So maybe something like:</p>
<p>[ Configure... ] [ Prefer this network ]<br />
[ Configure... ] [ Don't prefer this network ]</p>
<p>I think &#8216;Configure&#8217; sounds way less crappy than &#8216;Network Preferences&#8217;. I mean, those settings aren&#8217;t optional after I set them; If NM bugs out and ignores them, I&#8217;m not going to say &#8220;well, those were just my /preferences/&#8230; I don&#8217;t care /that/ much.&#8221; <img src='http://clarkbw.net/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Clark</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1915</link>
		<dc:creator>Bryan Clark</dc:creator>
		<pubDate>Fri, 26 Oct 2007 16:42:49 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1915</guid>
		<description>Ubuwu: Interesting idea, NM doesn't watch traffic at all right now and we've tried to be really smart about things like this before and it often ends up being confusing to people.  The MRU algorithm works well most of the times, however it doesn't allow you to never connect to a network again. 

nona: Agreed!  I've asked for this several times!

Rob: it's not adding an extra click.  NM still performs the same way it always does, however these buttons allow the option to alter it's behavior after it's done something.</description>
		<content:encoded><![CDATA[<p>Ubuwu: Interesting idea, NM doesn&#8217;t watch traffic at all right now and we&#8217;ve tried to be really smart about things like this before and it often ends up being confusing to people.  The MRU algorithm works well most of the times, however it doesn&#8217;t allow you to never connect to a network again. </p>
<p>nona: Agreed!  I&#8217;ve asked for this several times!</p>
<p>Rob: it&#8217;s not adding an extra click.  NM still performs the same way it always does, however these buttons allow the option to alter it&#8217;s behavior after it&#8217;s done something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Adams</title>
		<link>http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1914</link>
		<dc:creator>Rob Adams</dc:creator>
		<pubDate>Fri, 26 Oct 2007 16:09:24 +0000</pubDate>
		<guid isPermaLink="false">http://clarkbw.net/blog/2007/10/26/managing-your-wireless-networks/#comment-1914</guid>
		<description>Please don't add an extra click every time you connect to a network.  Getting rid of those notification popups is really quite annoying, and this particular one is useless _nearly always_</description>
		<content:encoded><![CDATA[<p>Please don&#8217;t add an extra click every time you connect to a network.  Getting rid of those notification popups is really quite annoying, and this particular one is useless _nearly always_</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.415 seconds -->
