<div dir="ltr"><br><br><div class="gmail_quote">On Thu, Jul 31, 2008 at 3:42 PM, <span dir="ltr"><<a href="mailto:pgf@laptop.org">pgf@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">eben wrote:<br>
> On Thu, Jul 31, 2008 at 3:14 PM, <<a href="mailto:pgf@laptop.org">pgf@laptop.org</a>> wrote:<br>
><br>
> > is it intentional that the currently-connected network is no<br>
> > longer differentiated in the neighborhood view? the outer ring<br>
> > of that network icon used to be white -- it no longer is.<br>
> ><br>
><br>
> This is intentional. The colors of the stroke/fill serve as the visual<br>
> representation of the identity of the network; changing them effectively<br>
> strips this identity. The new design does not make any indication of which<br>
> network is presently associated in the Neighborhood view; perhaps we can<br>
> find an alternative method. Thoughts?<br>
<br>
</div>i get the color thing, though those colors are all arbitrary,<br>
right? but i guess you can say "connect to the green/orange<br>
network" as a means of identification, and if the ring is white,<br>
you can't do that. but it still feels like the connected network<br>
should be "special" in that view. maybe little radio waves<br>
emanating from it or something. :-)<br>
<div class="Ih2E3d"></div></blockquote><div><br></div><div>They're arbitrary, but the colors are chosen as a hash of the essid, which makes them consistently arbitrary. Your favorite network will always be the same colors, and a given network will be the same colors on everyone's machine. It's just a hint of an identifier, but it's a lot better than nothing.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d">
><br>
> > it's been pointed out that you can see your current network on<br>
> > the frame, but somehow that's not quite the same (to me).<br>
> ><br>
><br>
> Yes, that's the preferred model. The Frame serves as a perpetual status<br>
> element, and is instantly accessible no matter "where" you are within the<br>
> UI. I'm open to improvements on the model.<br>
<br>
</div>it wasn't until charlie came over and showed me the icon in the frame<br>
that i'd had the frame up at all today. but it's certainly a good place<br>
to go for status information.<br>
<div class="Ih2E3d"></div></blockquote><div><br></div><div>I hope that the Frame will see much more use as a result of the redesign; it's meant to be a crucial interface element, but until now hasn't had much utility. It will help when the notification system is integrated, since the act of connecting to a network will invoke a pulsing network icon in the corner of the screen, which will then slide into the Frame as a hint at where to go to find it later.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d">
><br>
> i'm also not sure how to disconnect from that network -- there's no<br>
> > "disconnect" option in the popup anymore.<br>
> ><br>
><br>
> Well, that's a "bug", but not really. The problem is that there is no<br>
> notion of "disconnect" in network manager at all. The old behavior used to<br>
> switch into mesh mode, which disassociated with the network itself.<br>
> However, we now have a more direct means of accomplishing this, via turning<br>
> the mesh device on or off explicitly. It doesn't make sense to compound<br>
<br>
</div>i'm not sure what you mean by "turning the mesh device on or off explicitly",<br>
at least in terms of the current UI. is that the Radio: checkbox in the<br>
Network control panel?<br>
<div class="Ih2E3d"></div></blockquote><div><br></div><div>There has been lots of confusion about the difference between mesh and APs. They're really not the same at all, apart from the fact that they both depend on the radio. The new design no longer treats the mesh channels as objects in the Neighborhood view. Instead, there will be (is? not sure if the patch landed yet) a mesh device in the Frame, which you can turn on (and off?) at whim.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d">
> these. The more conventional option is something like "turn wireless off"<br>
> to disassociate with the current network, but that assumes that there is no<br>
> other potential use for the wireless at all. In our case we still have the<br>
> mesh to worry about, so that again doesn't map onto our circumstances.<br>
<br>
</div>i guess i'm thinking of it in traditional terms. if i'm browsing<br>
available nets, i might connect to a network by mistake, and want to<br>
disconnect without necessarily connecting to something else, and now<br>
it feels (rightly or wrongly) like i can't do that. i guess it's not<br>
very important, though.</blockquote><div><br></div><div>I'm trying to point out that your assumption isn't actually true. I'm not aware of a "disconnect" option which strictly disconnects from the current network. Instead, there is usually a "turn off my ability to connect to any network, disconnecting from the current one in the process" option. This isn't what we want, because one may want to disconnect from a network but remain on the mesh.</div>
<div><br></div><div>- Eben</div><div><br></div></div></div>