Ticket #833 (new enhancement)

Opened 4 years ago

Last modified 3 years ago

Check box in Sugar control panel to turn off/on jabber without removing server name

Reported by: satellit Owned by: tomeu
Priority: Normal Milestone: 0.90
Component: sugar Version: Unspecified
Severity: Minor Keywords: jabber network panel
Cc: garycmartin, Eben, HoboPrimate, TylerB, dfarning Distribution/OS: Unspecified
Bug Status: Unconfirmed

Description

Put a check box to activate/deactivate jabber without a reboot
There are times local networking is all that is needed. It would
save loading on jabber servers. Also would permit exchange of items
between locally connected students

Change History

Changed 4 years ago by tomeu

  • cc garycmartin, Eben, HoboPrimate added

Note that by setting the jabber server name to a non-existent one will have the same effect. But I guess we should anyway have a more obvious way to do the same.

Eben, Gary, Eduardo, could you comment?

Changed 4 years ago by satellit

see #830
Sugar Desktop installed in Fedora 11 at 800x600 resolution only shows network window down to "Collaboration" Needs slider bar on window. Cannot change Jabber server unless use command line in terminal. Being able to shut off jabber without booting would mean less load on jabber when not needed.

Changed 4 years ago by garycmartin

I can imagine several possible steps depending on the overall aim:

1) Add a standard (x) clear field button to the input field (as found in the search input field), this would just make clearing the server name more obvious and easy – would be a nice detail hint if an empty server input box displayed a greyed out text string stating something like 'using local collaboration'.

2) Give the server field a history/autocomplete, so it's easy to pull back a previous collaboration server name. Bonus points for allowing the history to be easily pre-seeded by a deployment so a school may add some valid alternative server names for easier switching.

3) Servers are currently used a little like the discussed group feature, where different communities have their own server and switch between several depending who they are working with. This is a simple way to scale/isolate working groups for those able to set-up a collaboration server. If this is seen as a valid future work flow case it may be worth exposing the current server name, and history of others, in the Neighbourhood toolbar for quick and easy switching.

FWIW, option 3 could be a replacement for the group feature, especially when combined with a buddy tagging scheme; where buddy tagging would allow easy/quick ad-hoc filtering of a server's participants, and multiple servers (or virtual server hosts) act as way to scale and switch to completely different working groups.

Changed 4 years ago by sascha_silbe

  • cc TylerB, dfarning added

Adding reporter and CC from dupe bug #1163.

Changed 4 years ago by tomeu

  • priority changed from Unspecified by Maintainer to Normal
  • type changed from defect to enhancement
  • severity changed from Unspecified to Minor
  • milestone changed from Unspecified by Release Team to 0.88

Changed 3 years ago by sascha_silbe

  • summary changed from Check box in Sugar control panel to turn off/on jabber without booting to Check box in Sugar control panel to turn off/on jabber without removing server name

Changed 3 years ago by garycmartin

  • milestone changed from 0.88 to 0.90

Pushing out to 0.90. Think we need some design agreement on where/how this UI should go, seems to link in with ideas about allowing misc telepathy users@server to be added to the roster (from a UI perspective).

Changed 3 years ago by tomeu

Agreed, each account would have an Enable checkbox: #476

Note: See TracTickets for help on using tickets.