Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
There also is the possibility of a false positive if we check too little. Some networks might like to act like everything is available when that is not the case. Captive portals such as those seemingly found at pretty much every university and hotel I've gone to lately come to mind, and these may vary in their approaches. On 02/16/11 04:53, Sascha Silbe wrote: > Excerpts from Martin Langhoff's message of Tue Feb 15 14:57:01 +0100 2011: > >> Going back to your original post to note something important: these >> statuses aren't important _just_ to show in the UI. This should be a >> system status property that can be queried by activities and by >> cronjobs / cli utils. > > Please be very careful with this. If your sensor incorrectly detects > that no internet connection is available, everything that relies on it > will break. Even just checking the NetworkManager status without a way > for the user to override it is a bad idea since NetworkManager might not > have a complete idea of what's going on [1,2]. > > When trying to check availability of "the internet", you are bound to > get false positives. The server(s) you ping in your sensor might be > down even though the server you are going to connect is still be > reachable. The IPv4 default route might be down, but there might still > be a way to reach the target (IPv6, proxy, ...). > > Unless there's a large application-level cost associated to it, it > might be a better idea to just try establishing the connection. A > SYN packet is as cheap as an ICMP echo request and you'll know for > sure whether the exact server you're trying to reach is available or > not. > > The "internet" sensor might be useful to monitor changes and trigger > connection attempts, though. If you use exponential back-off, you could > reset the retry timer whenever the sensor switches from "offline" to > "online". > > Sascha > > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511439#35 > [2] https://bugzilla.gnome.org/show_bug.cgi?id=418745 > > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
Excerpts from Martin Langhoff's message of Tue Feb 15 14:57:01 +0100 2011: > Going back to your original post to note something important: these > statuses aren't important _just_ to show in the UI. This should be a > system status property that can be queried by activities and by > cronjobs / cli utils. Please be very careful with this. If your sensor incorrectly detects that no internet connection is available, everything that relies on it will break. Even just checking the NetworkManager status without a way for the user to override it is a bad idea since NetworkManager might not have a complete idea of what's going on [1,2]. When trying to check availability of "the internet", you are bound to get false positives. The server(s) you ping in your sensor might be down even though the server you are going to connect is still be reachable. The IPv4 default route might be down, but there might still be a way to reach the target (IPv6, proxy, ...). Unless there's a large application-level cost associated to it, it might be a better idea to just try establishing the connection. A SYN packet is as cheap as an ICMP echo request and you'll know for sure whether the exact server you're trying to reach is available or not. The "internet" sensor might be useful to monitor changes and trigger connection attempts, though. If you use exponential back-off, you could reset the retry timer whenever the sensor switches from "offline" to "online". Sascha [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511439#35 [2] https://bugzilla.gnome.org/show_bug.cgi?id=418745 -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Tue, Feb 15, 2011 at 6:37 PM, James Cameron wrote: > NetworkManager already has sufficient functionality for reporting the > state of a network connection. No it doesn't; if it did I'd use it :-) If we know whether we can see the XS or the internet we can, for example - run a backup (or not) - enable or disable the register option - show an icon on screen too cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Tue, Feb 15, 2011 at 08:57:01AM -0500, Martin Langhoff wrote: > Going back to your original post to note something important: these > statuses aren't important _just_ to show in the UI. This should be a > system status property that can be queried by activities and by > cronjobs / cli utils. I disagree. It should not be queried by activities or other applications. Doing so would greatly enlarge the scope of the feature. NetworkManager already has sufficient functionality for reporting the state of a network connection. What this thread was discussing was providing the user with a measurement of internet connectivity, in addition to what NetworkManager and the Neighbourhood View already provides. I think we should stick to that. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Tue, Feb 15, 2011 at 10:57, Martin Langhoff wrote: > On Thu, Feb 10, 2011 at 10:46 AM, Anish Mangal > wrote: >> Currently, the 'network' icon on the frame tells us whether we're >> connected to a network or not. Would it make sense for it to test for >> internet connectivity and maybe reflect that by displaying a small >> globe overlaid on the 'Network' icon? > > Hi Anish, > > Going back to your original post to note something important: these > statuses aren't important _just_ to show in the UI. This should be a > system status property that can be queried by activities and by > cronjobs / cli utils. Agree. > > cheers, > > > m > -- > martin.langh...@gmail.com > mar...@laptop.org -- Software Architect - OLPC > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > --Anish | an...@activitycentral.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Thu, Feb 10, 2011 at 10:46 AM, Anish Mangal wrote: > Currently, the 'network' icon on the frame tells us whether we're > connected to a network or not. Would it make sense for it to test for > internet connectivity and maybe reflect that by displaying a small > globe overlaid on the 'Network' icon? Hi Anish, Going back to your original post to note something important: these statuses aren't important _just_ to show in the UI. This should be a system status property that can be queried by activities and by cronjobs / cli utils. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
Excerpts from Anish Mangal's message of Mon Feb 14 22:20:23 +0100 2011: > Since this discussion has many different areas (Usage goals, Backend > implementation, UI implementation) should we move this to a wiki page? > This way, anyone replying to a specific point won't have to waste time > filtering the points relative to them. Please don't. That hides the discussion; everyone would need to "watch" (explicit action required) the wiki page in order to be notified about changes and since the change notifications don't contain diffs, we need to visit the page each time (requiring an internet connection, i.e. cannot be done while reading mail offline). And unless you're going to make it an entire hierarchy of wiki pages, I don't see how people could filter more easily than when the discussion is on the list. If there's actually that much to discuss, I suggest splitting up into several threads. Everyone not interested in one or more of the threads can simply tell their MUA to ignore the respective thread(s). Wikis are great for conserving and collecting information and for presenting information to the outside, but IMO they are not suited well to discussion. Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Mon, Feb 14, 2011 at 4:20 PM, Anish Mangal wrote:
> [cc += peace-corps@sl-devel]
>
> {...}
>
> Since this discussion has many different areas (Usage goals, Backend
> implementation, UI implementation) should we move this to a wiki page?
> This way, anyone replying to a specific point won't have to waste time
> filtering the points relative to them.
http://wiki.sugarlabs.org/go/Features/Network_status
is available.
(also referenced at
http://wiki.sugarlabs.org/go/Design_Team/Proposals/Neighborhood )
> {...}
> Cheers,
> Anish
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
[cc += peace-corps@sl-devel] I think everyone agrees that 'more (than current)' information can be conveyed to the user which might actually be of use... Everyone has raised very valid points... Lets aim to address the simple issues first, try them out in different (network setup) environments incrementally and keep (please) this thread alive... * * * * * * * * * * Here's my take... > "The Sugar UI should make network health discoverable." >>> Good point in general. To what is trying to get solved, I'd word it as >>> "Sugar UI should make network _affordances_ discoverable". Yes! What are the use cases for such information? Michael suggested a number of mechanisms which can be reliably used to determine 'levels of network connectivity' >In particular: > a) are we trying to expose affordances that are useful when the network is >working perfectly or are we more interested in making discoverable those >affordances that will be useful when things are broken? Actually, both. > In particular, is this the core issue? No. The core issue is determining the ways that information can or should be used. That will determine what we implement both at the backend and UI wise before jumping into finer details. > b) are we more interested in making indicators (whose status is automatically >updated) or in sensors that can be activated to learn about the world? My intention was to have automatically updating indicators. Are there good use cases for implementing the feature as a 'sensor'? > Anish started a thread with a [DESIGN] tag. I took that to mean, in part, that > he wanted feedback about the interplay of his idea with the Sugar HIG and the > broader intended Sugar UX and I tried to recast the discussion in those terms. +1, Exactly * * * * * * * * * * == Miachel's proposed implementation == For the sake of concreteness, here are some examples of how these considerations might affect Anish's general idea: 1) Let's make an autonomous binary internet indicator to be displayed on the frame and in the network-view. The sensor driving the indicator will periodically make HTTP HEAD requests at a deployment-configured rate against a URL chosen uniformly at random from a deployment-configured list. The indicator will be "happy" when the most recent request succeeded with status code 200 and will be "sad" otherwise. 2) Let's make a three-state autonomous indicator to be displayed on the frame and in the network view. The sensor driving the indicator will periodically run a complete network diagnostic procedure which, at a minimum, checks that we: 1) have a network interface, 2) that is up, 3) with an IP address, 4) that the interface IP is pingable 5) with default route configured 6) that the default route is pingable 7) with a nameserver entry in resolv.conf 8) that is pingable 9) that successfully resolves a list of test addresses 10) such that the resolved IPs are pingable 11) such that there are HTTP servers running on port 80 on the IPs returned from a configured subset of the resolved names that that return status code 200 for HTTP 1.0 HEAD requests for url "/" The indicator will be "happy" if all tests past in the most recent test run. The indicator will be "sad" if any "hard" tests failed. The indicator will be "worried" if all hard tests passed but some soft tests failed. If the indicator is "sad" or "worried", then hovering or clicking on the indicator will display a modal dialog or palette listing all tests, showing their pass/fail status, and showing folded blocks of logs for all tests. Thoughts? Michael [1]: As background, I'm going to assume that an "affordance" is "a quality of an object, or an environment, that allows an individual to perform an action" (http://en.wikipedia.org/wiki/Affordance). Please correct me if you prefer a different definition. [2]: For example, are all these opportunities included? * "to join a shared activity" * "to send an object to a friend" * "to store or to load a backup" and * "to browse the web" How about these? * "to join #sugar-devel" * "to host a web page" * "to copy an activity from a friend's journal" Or these? * "to ping a default route?" * "to resolve names to IP addresses?" * "to send IP packets to and to receive packets from public IPs?" * "to communicate without interference from middlepeople?" * * * * * * * * * * I don't have much idea as to what should be the finer details of a 'network indicator' so I won't argue here. We could code something pretty quickly that implements all or a part of the above. >>> We can get a rough initial version with a ping to 'schoolserver', and >>> a ping to a configurable internet host. * * * * * * * * * * >> Couldn't we use the presence service (or its equivalent)? I've always >> wanted to see a schoolserver ico
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Mon, Feb 14, 2011 at 12:11 PM, Michael Stone wrote: >> Let's not get too academic. > > FYI, this remark stings rather more than I think you intended. Apologies. It was short for "too long and formal, let's communicate in shorter messages, I don't need formal or logical proof of every statement, I need practical & productive". Personally, I prefer short emails, more code. ask interesting questions. working code first :-) You posted very good ideas I agree with on the very specific topic of this interesting idea from Anish. And then threw some open questions, that I decline to follow, preferring to KISS. I leave the semantic meaning of "network is up" for Sugar v3.0 :-) More than enough for me this week -- I won't post on this thread anymore. Apologies to Anish and to the whole list for soaking up everyone's time. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Mon, 14 Feb 2011 at 10:12:40 -0500, Martin Langhoff wrote: On Sun, Feb 13, 2011 at 8:59 PM, Michael Stone wrote: So what network affordances [1, 2] are we supposed to make discoverable? :) Martin, I don't want to hijack any threads this month, so, if the following isn't worth your time, please ignore it and move on to more pressing matters. Let's not get too academic. FYI, this remark stings rather more than I think you intended. Perhaps you have a constructive criticism to substitute? Reading back the thread: - can we reach the "internet"? (or it might be a controlled WAN) - can we reach an XS? In both cases, ping + HEAD can work. No argument that ping + HEAD are useful and usefully cheap. Frankly, for the two cases you mention above, HEAD alone should suffice. Keep it simple, this is for a simple, low cost (cognitive _and_ computer-resources wise) indicator. Anish started a thread with a [DESIGN] tag. I took that to mean, in part, that he wanted feedback about the interplay of his idea with the Sugar HIG and the broader intended Sugar UX and I tried to recast the discussion in those terms. To that end, I asked whether the goal of the network UI is to reassure people whose network is already working or to help people whose network is broken, e.g., by making the tools for diagnosing the failure more discoverable. I also tried to provide sufficient detail to establish the feasibility of both approaches and to support robust and concrete debate. Finally, regarding your "keep it simple" comment above: what do you know that I don't that convinces you that all of the above is a waste of time? Regards, Michael ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Sun, Feb 13, 2011 at 8:59 PM, Michael Stone wrote: > So what network affordances [1, 2] are we supposed to make discoverable? :) Let's not get too academic. Reading back the thread: - can we reach the "internet"? (or it might be a controlled WAN) - can we reach an XS? In both cases, ping + HEAD can work. Keep it simple, this is for a simple, low cost (cognitive _and_ computer-resources wise) indicator. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Sun, 13 Feb 2011 at 19:41:32 -0500, Martin Langhoff wrote: On Sun, Feb 13, 2011 at 6:38 PM, Michael Stone wrote: > "The Sugar UI should make network health discoverable." Good point in general. (Thanks! :) To what is trying to get solved, I'd word it as "Sugar UI should make network _affordances_ discoverable". So what network affordances [1, 2] are we supposed to make discoverable? :) In particular: a) are we trying to expose affordances that are useful when the network is working perfectly or are we more interested in making discoverable those affordances that will be useful when things are broken? b) are we more interested in making indicators (whose status is automatically updated) or in sensors that can be activated to learn about the world? We can get a rough initial version with a ping to 'schoolserver', and a ping to a configurable internet host. For the sake of concreteness, here are some examples of how these considerations might affect Anish's general idea: 1) Let's make an autonomous binary internet indicator to be displayed on the frame and in the network-view. The sensor driving the indicator will periodically make HTTP HEAD requests at a deployment-configured rate against a URL chosen uniformly at random from a deployment-configured list. The indicator will be "happy" when the most recent request succeeded with status code 200 and will be "sad" otherwise. 2) Let's make a three-state autonomous indicator to be displayed on the frame and in the network view. The sensor driving the indicator will periodically run a complete network diagnostic procedure which, at a minimum, checks that we: 1) have a network interface, 2) that is up, 3) with an IP address, 4) that the interface IP is pingable 5) with default route configured 6) that the default route is pingable 7) with a nameserver entry in resolv.conf 8) that is pingable 9) that successfully resolves a list of test addresses 10) such that the resolved IPs are pingable 11) such that there are HTTP servers running on port 80 on the IPs returned from a configured subset of the resolved names that that return status code 200 for HTTP 1.0 HEAD requests for url "/" The indicator will be "happy" if all tests past in the most recent test run. The indicator will be "sad" if any "hard" tests failed. The indicator will be "worried" if all hard tests passed but some soft tests failed. If the indicator is "sad" or "worried", then hovering or clicking on the indicator will display a modal dialog or palette listing all tests, showing their pass/fail status, and showing folded blocks of logs for all tests. Thoughts? Michael [1]: As background, I'm going to assume that an "affordance" is "a quality of an object, or an environment, that allows an individual to perform an action" (http://en.wikipedia.org/wiki/Affordance). Please correct me if you prefer a different definition. [2]: For example, are all these opportunities included? * "to join a shared activity" * "to send an object to a friend" * "to store or to load a backup" and * "to browse the web" How about these? * "to join #sugar-devel" * "to host a web page" * "to copy an activity from a friend's journal" Or these? * "to ping a default route?" * "to resolve names to IP addresses?" * "to send IP packets to and to receive packets from public IPs?" * "to communicate without interference from middlepeople?" ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Sun, Feb 13, 2011 at 8:00 PM, Samuel Greenfeld wrote: > For the schoolserver (and other jabber-based environments), wouldn't the > best check be to see if there is a working gabble connection and that we are > not on salut? That only works _after_ you've registered. So no. I'd be interested in your thoughts on -testing- this stuff. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
For the schoolserver (and other jabber-based environments), wouldn't the best check be to see if there is a working gabble connection and that we are not on salut? It seems like a lot of people are trying to guess how deployments like to configure their networks (DNS, ICMP ping support to gateway and/or Internet, HTTP, etc.). As at least a few deployments have shown us (hidden SSIDs, HTTP Proxies, cellular modem routing requests, MAC-based network restrictions limited to XOs, etc.), our initial guesses are often wrong. Personally, I think we might want to separate this out into a basic icon sort of check in the frame, and a more advanced control panel for adults/teachers which can do tests and explain things in more detail. On 2/13/2011 7:41 PM, Martin Langhoff wrote: On Sun, Feb 13, 2011 at 6:38 PM, Michael Stone wrote: "The Sugar UI should make network health discoverable." Good point in general. To what is trying to get solved, I'd word it as "Sugar UI should make network _affordances_ discoverable". We can get a rough initial version with a ping to 'schoolserver', and a ping to a configurable internet host. m ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Sun, Feb 13, 2011 at 6:38 PM, Michael Stone wrote: > "The Sugar UI should make network health discoverable." Good point in general. To what is trying to get solved, I'd word it as "Sugar UI should make network _affordances_ discoverable". We can get a rough initial version with a ping to 'schoolserver', and a ping to a configurable internet host. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Thu, 10 Feb 2011 at 12:46:18 -0300, Anish Mangal wrote: Hi, Currently, the 'network' icon on the frame tells us whether we're connected to a network or not. Would it make sense for it to test for internet connectivity and maybe reflect that by displaying a small globe overlaid on the 'Network' icon? Folks, Speaking as someone who has spent a fair bit of time thinking through a few of the narrow technical issues [1], I'd like to gently suggest that we might get better design ideas from our design team if we focused a bit more on the core UI problem before diving into a long thread on the relative merits of HTTP vs. ICMP sensors. Therefore, with this gentle suggestion in mind, what do you all think of the following design thesis: "The Sugar UI should make network health discoverable." In particular, is this the core issue? If so, what kinds of affordances does it suggest? If not, then what, in your words, is the core issue? Regards, Michael [1]: http://wiki.laptop.org/go/Network2/Paper#Self-Test_Algorithm ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On Thu, Feb 10, 2011 at 10:46 AM, Anish Mangal wrote: > Currently, the 'network' icon on the frame tells us whether we're > connected to a network or not. Would it make sense for it to test for > internet connectivity and maybe reflect that by displaying a small > globe overlaid on the 'Network' icon? I like the idea, but worry also about how to do it. Some thoughts - make it hit a configurable (from olpc-os-builder) host, make it also easy to disable from olpc-os-builder - add a similar feature that pings 'schoolserver' and indicates we have an XS within reach cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
On 10 Feb 2011, at 15:46, Anish Mangal wrote: > Hi, > > Currently, the 'network' icon on the frame tells us whether we're > connected to a network or not. Would it make sense for it to test for > internet connectivity and maybe reflect that by displaying a small > globe overlaid on the 'Network' icon? If the technical issues of actually testing for a working Internet connection can be solved reliably/globally, perhaps that extra information could be placed in the device pop-up palette as a text item? There are a number of different possible network device svg icons that would all need to work well with an extra visual globe overlay, I'm not convinced we could make one clear enough but closest would likely be a minimal fill/stroke circle in one corner. Certainly would need a line of text in the palette to aid discoverability/clarity. Obviously would need to be clear exactly what was being tested to come up with wording/design (ping of some agreed server/s, working http get, etc). --Gary > -- > Anish > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
[Posting to sugar-devel only because it's not specific to dextrose] Excerpts from Anish Mangal's message of Thu Feb 10 16:46:18 +0100 2011: > Currently, the 'network' icon on the frame tells us whether we're > connected to a network or not. Would it make sense for it to test for > internet connectivity and maybe reflect that by displaying a small > globe overlaid on the 'Network' icon? FWIW, some previous discussion happened on this thread: http://lists.laptop.org/pipermail/devel/2011-January/thread.html#30807 Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
It might indicate connectivity to either the school server, Jabber server, or successful NTP synchronisation. A deployment might customise what method to use, including hostnames of their own infrastructure. The default should be harmless. This feature is present on at least three modern consumer routers that I've used in the past six months, in the form of an extra LED called "INTERNET". It isn't clear how it is implemented, but it seems quite reliable ... not indicating when I've got a problem loading pages, for example. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [DESIGN] Reflect internet connectivity in the 'Network' frame icon
Hi, Currently, the 'network' icon on the frame tells us whether we're connected to a network or not. Would it make sense for it to test for internet connectivity and maybe reflect that by displaying a small globe overlaid on the 'Network' icon? -- Anish ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
