Show which jabber server to which you are connected

[dfarning]

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.

[CarolineM]

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.

[tomeu]

we need a design proposal before we can implement anything.

[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?

[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".

[tomeu]

This has missed the 0.86 release :(

[tomeu]

part of making sugar a regular telepathy client, plan to work on this for 0.90

[sascha_silbe]

Bulk change distribution=SoaS -> component=SoaS

[sdz]

Assigning back to Sugar.