[Sugar-devel] [FEATURES][DESIGN] Network proxy configuration

Sameer Verma sverma at sfsu.edu
Thu Mar 14 21:01:56 EDT 2013

On Thu, Mar 14, 2013 at 1:31 PM, Gonzalo Odiard <gonzalo at laptop.org> wrote:
> While I understand your point about the radio checkbox,
> this show a few bugs or fails in design in Sugar too.
> Trying right now I see:
> * The text is confusing:
> "Turn off the wireless radio to save battery life"
> [] Radio
> Checked is on or off? What means Radio? Is not clear

Should be a radio button. Wi-Fi on/off.


> * After uncheck the checkbox, go to the neightborview,
> the ap are not visible but the ad-hoc are.
> If there are not network, the ad-hoc is not working, right?
> * May be we can show a message in the neighborview.
> "The radio/wireless interface is down, go to the control panel to use it"
> or similar. The same in the device icon in the frame.
> All these issues probably help to make worst the situation.
> About the network proxy configuration, I agree is better have a automatic
> configuration _if_possible_, but there are times when is not possible,
> then we should provide a solution. Has been a request for a long time,
> and the development is already 90% done
> Gonzalo
> On Thu, Mar 14, 2013 at 5:15 PM, Daniel Drake <dsd at laptop.org> wrote:
>> On Thu, Mar 14, 2013 at 2:08 PM, Alan Jhonn Aguiar Schwyn
>> <alanjas at hotmail.com> wrote:
>> >>One problem that I have seen in various places, children untick the
>> >>"Radio enable" checkbox in Sugar's control panel and then return their
>> >>laptop for repair because they can't get online. I fear that proxy
>> >>configuration could become support headache like this.
>> >
>> > Thinking in the same way, we must block the command "rm" from the
>> > terminal because the childrens can remove important files. Or the
>> > command "mv" because generates that an activity no works....
>> I can see why you might think that way. However, I have never
>> experienced this being a problem, and I don't recall seeing other
>> reports of this, so I would not argue for any blocking of terminal
>> commands. The radio checkbox is a real headache that *actually
>> happens* though.
>> Taking a guess as to why we see the radio problem but not the terminal
>> one in our field experiences, I would imagine the crucial difference
>> is that the radio checkbox is presented in a way that it is easily
>> accessible but commonly uncomprehendable to our regular user base. In
>> comparison, those dangerous commands in the terminal are in their own
>> world of inaccessibility...
>> Daniel
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

More information about the Sugar-devel mailing list