#1157 closed enhancement (incomplete)
Show which jabber server to which you are connected
| Reported by: | dfarning | Owned by: | tomeu |
|---|---|---|---|
| Priority: | High | Milestone: | |
| Component: | Sugar | Version: | 0.84.x |
| Severity: | Unspecified | Keywords: | |
| Cc: | sascha_silbe, eben, garycmartin | Distribution/OS: | Unspecified |
| Bug Status: | Assigned |
Description
We are running a collaboration debug session. It is very difficult to determine which how we are connected. Some people seem to be on local connects, and others are on the jabber server.
Would it be possiable to add information about which server we are connected to in the popup menu of the connection information in the frame.
Change History (12)
comment:1 Changed 14 years ago by sascha_silbe
- Cc sascha_silbe added
comment:2 Changed 14 years ago by CarolineM
comment:3 Changed 14 years ago by tomeu
- Cc eben garycmartin added
- Milestone changed from Unspecified by Release Team to 0.86
we need a design proposal before we can implement anything.
comment:4 Changed 14 years ago by tomeu
- Bug Status changed from New to Needinfo
comment:5 follow-up: ↓ 6 Changed 14 years ago by CarolineM
- Bug Status changed from Needinfo to Assigned
The frame has an icon that pops up IP address and speed on my wired network. How about putting what jabber server or if you are using local collaboration in that popup?
comment:6 in reply to: ↑ 5 Changed 14 years ago by garycmartin
Replying to CarolineM:
The frame has an icon that pops up IP address and speed on my wired network. How about putting what jabber server or if you are using local collaboration in that popup?
Yes, an extra line of text in the various network device palettes (wired, AP, ad-hoc) would be a reasonable solution. It could show "Collaboration: Local network" or "Collaboration: <the.server.ip.address>" but it's critical that information is accurate. Example: if a Jabber server address is entered in the Network control panel, but it is not able to connect for some reason, it should show that Sugar is falling back and actually using "Local network collaboration".
comment:7 Changed 14 years ago by tomeu
- Milestone changed from 0.86 to 0.88
This has missed the 0.86 release :(
comment:8 Changed 14 years ago by tomeu
- Milestone changed from 0.88 to 0.90
part of making sugar a regular telepathy client, plan to work on this for 0.90
comment:9 Changed 14 years ago by sascha_silbe
- Component changed from sugar to SoaS
- Distribution/OS changed from SoaS to Unspecified
- Owner changed from tomeu to mchua sdz
Bulk change distribution=SoaS -> component=SoaS
comment:10 Changed 13 years ago by sdz
- Component changed from SoaS to sugar
- Owner changed from mchua sdz to tomeu
- Status changed from new to assigned
Assigning back to Sugar.
comment:11 Changed 10 years ago by dnarvaez
- Resolution set to incomplete
- Status changed from assigned to closed
Need a design proposal/discussion.
The UI should also indicate if you are connected locally or to a jabber server.
User STory: WiFi access points require login before they connect to the internet. Currently if you connect to them you will locally see other people connected to them, until you login to connect to the internet, then at some point Sugar will try to connect to the Jabber server, notice that it can, and all of a sudden the user sees an entirely different set of people on the jabber server.
We should at least provide some clues to the user as to what is happening by telling them they are connected locally or what jabber server.