Is it different from relying on a modem and having a wrong modem-config? I think there are scenarios where "normal" includes the proper proxy-config, otherwise browse won't work either. On Thu, Mar 14, 2013 at 10:33 PM, James Cameron <<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> wrote: <div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But with modem-config a child cannot stop normal operation. With proxy, the child can stop normal operation, in that no Browse will work with wrong proxy. I think proxy configuration should be an optional extension that is disabled by default, allowing a deployment to enable it. <div class="HOEnZb"><div class="h5"> On Thu, Mar 14, 2013 at 10:23:53PM -0400, Martin Abente wrote: > I think this feature (proxy-config) is useful, just as the modem-config is, > which is included now. > > dsd's brings a valid questioning of whether this kind of "technical" features > should be included or not. I think this particular matter requires a broader > discussion about how we could conciliate sugar's education objectives and its > interface responsibilities. > > Until we can do that, the Network CP UI seems a good place. > > Just my opinion. > > On Thu, Mar 14, 2013 at 9:01 PM, Sameer Verma <<a href="mailto:sverma@sfsu.edu">sverma@sfsu.edu</a>> wrote: > > On Thu, Mar 14, 2013 at 1:31 PM, Gonzalo Odiard <<a href="mailto:gonzalo@laptop.org">gonzalo@laptop.org</a>> 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. > <a href="http://article.gmane.org/gmane.comp.education.sugar.devel/34909" target="_blank">http://article.gmane.org/gmane.comp.education.sugar.devel/34909</a> > > Sameer > > > * 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 <<a href="mailto:dsd@laptop.org">dsd@laptop.org</a>> wrote: > >> > >> On Thu, Mar 14, 2013 at 2:08 PM, Alan Jhonn Aguiar Schwyn > >> <<a href="mailto:alanjas@hotmail.com">alanjas@hotmail.com</a>> 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 > >> <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > >> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > > > > > > > _______________________________________________ > > Sugar-devel mailing list > > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > > _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> > > > _______________________________________________ > Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </div></div><div class="HOEnZb"><div class="h5">-- James Cameron <a href="http://quozl.linux.org.au/" target="_blank">http://quozl.linux.org.au/</a> </div></div></blockquote></div>