Difference between revisions of "Usability/Roster"

Jump to navigation Jump to search
135 bytes added ,  01:44, 17 December 2020
m
no edit summary
m
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
The roster is the entry point for the user to their contacts. It is thus a key part in the user experience of any Jabber client.
The roster is the entry point for the user to their contacts. It is thus a key part in the user experience of any XMPP clients.


= Roster groups =
= Roster groups =
Line 7: Line 7:
== Hierarchical model ==
== Hierarchical model ==


One way is to organize contacts in a tree-like (possibly nested, see [https://xmpp.org/extensions/xep-0083.html XEP-0083]) structure, where contacts are nodes which are children to group nodes. If a contact is present in multiple groups, it is is also represented by multiple nodes in the tree. This is the traditional way to do things.
One way is to organize contacts in a tree-like (possibly nested, see [https://xmpp.org/extensions/xep-0083.html XEP-0083]) structure, where contacts are nodes which are children to group nodes. If a contact is present in multiple groups, it is is also represented by multiple nodes in the tree. A contact that is not part of any groups is shown at the highest level of the hierarchy or in a "non-group" group with a generic name.
 
This is the traditional way to do things.


== Tag model ==
== Tag model ==
216

edits

Navigation menu