[sugar] letting the user specify the mesh channel

[Eduardo Heleno]

See http://dev.laptop.org/ticket/2866 for the information wanted. You could
also see if it was possible or wanted to integrate information of
http://dev.laptop.org/ticket/6195 .

P.S.-Am I replying this correctly? Should I just reply to the list, not to
eben and mikus as well?

Edu

2008/8/14 Eben Eliason <eben.eliason at gmail.com>

> On Thu, Aug 14, 2008 at 6:26 AM, Eduardo H Silva <hoboprimate at gmail.com>
> wrote:
> > I like a lot the mockup
> > http://dev.laptop.org/~mdengler/6995/6995_screenshot_45.png<http://dev.laptop.org/%7Emdengler/6995/6995_screenshot_45.png>... I would just
> > add one more sugestion. Include on the primary palette as a secondary
> title
> > the word "Connected". You may think that the coloring of the mesh icon
> makes
> > it clear it is connected, but i think it is important to be plan ahead
> for
> > all potential users of Sugar, like those who are blind (use some kind of
> > text-to-speech interface), color-blind, or even just poor eye-sighted
> > people.
>
> Good points.  We could add, at a minimum, the "Connecting...",
> "Connected", and "Disconnecting..." states as the secondary text in
> the palette. Is this clearer, or should we use "Starting...", "On",
> and "Stopping" instead?  If we use the former, should we change "Turn
> on" and "Turn off"?
>
> > There is also a ticket around about the lack of information on the stages
> of
> > connecting to a network. This could be done as a palette for the network
> > icon which would only appear on-mouse-hover and during the period it is
> > connecting. Users diagnosticating or curious about the connection process
> > could easily see it, while others will be just happy with the blinking
> icon
> > information.
>
> Perhaps.  I'm curious to know what info/stages we actually have,
> before specifying any design there.
>
> - Eben
>
>
> > Eduardo
> >
> > 2008/8/7 Eben Eliason <eben.eliason at gmail.com>
> >>
> >> On Thu, Aug 7, 2008 at 11:45 AM, Mikus Grinbergs <mikus at bga.com> wrote:
> >> >> See http://dev.laptop.org/~mdengler/6995/6995_screenshot_45.png<http://dev.laptop.org/%7Emdengler/6995/6995_screenshot_45.png>
> >> >> for an example of how I currently have it looking.
> >> >
> >> > Thank you.
> >> >
> >> > Currently, I use the presence of a 'Disconnect' entry in the palette
> >> > as a "mnemonic device" to indicate to me that a connection currently
> >> > exists.  Would be nice to keep that.
> >>
> >> Hey Mikus -
> >>
> >> In the new designs, the Mesh device icon "turns on" (becomes colored)
> >> when the mesh is active, and is rendered in white when it's off.  It
> >> should be even easier to tell the present state, without needing to
> >> dig into the palette.
> >>
> >> - Eben
> >>
> >> > p.s.  For laughs:   Now that you are *explicitly* showing channel
> >> > numbers -- I have a friend whose home AP is on channel 9.  At his
> >> > house, I manually use 'iwconfig' to set my XO's radio to channel 9,
> >> > to be able to connect to his AP.  I haven't tried setting multiple
> >> > XOs to channel 9 when there is no AP -- but if "mesh" were
> >> > configured to run that way, would your palette show that?   ;>)
> >>
> >> No, the mesh channels are independent* of the AP channels; if you
> >> connect to an AP on channel 9, you are not on the mesh, which is only
> >> "offered" on channels 1, 6, and 11.  If you turn the mesh on, you'll
> >> implicitly be disconnected from an AP on channel 9.  If you manually
> >> set the mesh channel otherwise, I doubt it will be reflected in this
> >> palette.
> >>
> >> * Note that in the future it will be possible to be connected on the
> >> mesh and to an AP, assuming they are both on the same channel.
> >> _______________________________________________
> >> Sugar mailing list
> >> Sugar at lists.laptop.org
> >> http://lists.laptop.org/listinfo/sugar
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/sugar/attachments/20080814/b2ea3577/attachment.htm