Ticket #1381 (new enhancement)

Opened 4 years ago

Last modified 21 months ago

hierarchical groups

Reported by: rakaur Owned by: asterix
Priority: high Milestone:
Component: usability Version: hg
Severity: normal Keywords: nested roster groups
Cc: travis@… Blocked By:
OS: All Blocking:

Description

I think it'd be awesome if we could make groups under groups. It would work well for things like transports where you'd like to keep them sorted by AIM, MSN, Jabber, etc.

Also, being able to arrange the groups in something other than alphabetical order would be nice. I like sorting mine by people that I most often talk to, but unless i name things like "01 - Family" then "Buddies" is always on top.

Attachments

Change History

Changed 4 years ago by asterix

  • milestone 0.10 deleted

for the subgroup, this can maybe be done only with groupname:

group/subgroup1 and group/subgroup2. This way other clients won't have strange things

Changed 4 years ago by nk

I would not use a roster that would look like that, nor liked to see bloated UI that can do this. GMail Web Interface doesn't have a Delete button and most don't care. I would like to have one, but I guess majority does not care so the UI is kept simple and nice. I propose WONTFIX evnethough I share your funcionality problems

Changed 4 years ago by nicfit

  • cc travis@… added

I disagree. For huge rosters, group hierarchies are a great thing. Using a Group/Subgroup syntax is also compatible with other clients (Exodus), they just nest the UI tree.

Changed 4 years ago by rakaur

Perhaps a look at JEP-0083 would help.

 http://www.jabber.org/jeps/jep-0083.html

Changed 4 years ago by rakaur

Even if there's no way of implementing this, I'd enjoy seeing meta-contacts at the very least. For people that want to use transports and have the same person on XMPP/AIM/MSN/etc it's nice to have them in the roster once instead of three+ times.

Changed 4 years ago by nicfit

Ahh, I was not even aware of JEP 83. Thanks for the pointer. Also, gmail wised up and added a delete button :-)

Changed 4 years ago by nk

yes I also didn't that JEP. Travis, I was using Gmail Delete Button Firefox Extension until today.. so it's the same for me :)

Changed 4 years ago by anonymous

Is there any chance to have this feature in one of the next releases? It's

the last thing I really miss in gajim.

Changed 3 years ago by jim++

  • type changed from defect to enhancement

anonymous > One day maybe...

Changed 3 years ago by Cast

I miss this functionality too fully agree with author

Changed 3 years ago by anonymous

  • component changed from roster to usability

Changed 3 years ago by Armin Ronacher

  • priority changed from normal to high

*bump* :-) I miss it too

Changed 2 years ago by mq

  • os set to All

*bump* any news on this?

Changed 2 years ago by gluth

When this will be?

Changed 2 years ago by asterix

not planned now. not for 0.12

Changed 21 months ago by dtoshack

  • keywords nested roster groups added
  • version changed from 0.9.1 to svn
  • milestone set to 0.12

YES PLEASE! :-) I've wanted this feature for ages.

According to  http://www.xmpp.org/extensions/xep-0083.html groups should be implemented with a delimiter for non compliant clients as mentioned above. But preferably a string instead of a single character to avoid misinterpretation.

Such as:

group1 group1::subgroup1 group1::subgroup2

... etc.

Changed 21 months ago by dtoshack

  • cc travis@… removed

hmm strange rendering. Apologies, that was meant to come out like:

group1

group1::subgroup1

group1::subgroup2

... etc.

So thats why these ticket systems have a preview button! :-D

Changed 21 months ago by dtoshack

  • cc travis@… added

sorry Travis ... added your cc back. Last ticket correction. I promise!

Changed 21 months ago by asterix

  • milestone 0.12 deleted

we won't add that for 0.12.

Add/Change #1381 (hierarchical groups)

Author


E-mail address and user name can be saved in the Preferences.


Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change from asterix. Next status will be 'new'
Next status will be 'needinfo'
The owner will change from asterix to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.