Separation of contacts from accounts (#67)
wojciech.kapcia@tigase.net opened 7 years ago

Currently in the roster view it's impossible to distinguish to which account particular contact belongs. In the chat view we don't know which account we are using.

Andrzej Wójcik (Tigase) commented 7 years ago

%wojtek How would you this to be done? I cannot group accounts on per account basis (I can have only one level of grouping and we have roster groups) and for sure I cannot do this for chats. Give me some idea how it should be done without adding to much to current layout (space is a constraint here).

Artur Hefczyc commented 7 years ago

From my point of view, I would definitely want to know which of my accounts is used for the specific chat. Right now, there is no way to get the information. But I do not need chat grouping. For me, it would be good enough to have this done in either the way iMessages does (prints the account name in the empty input line) - preferred way, or some other way, like, when I press on the contact name in the chat, it shows me the contact JID information. This view could be extended with more information, like my own account for this chat for example. Or maybe some information at the top of the chat view, next to the contact name or something like this.

As for the contacts grouping in the roster view. I can see how this can be useful. I use this kind of view in Psi. But this is more needed for me during tests than during normal use. If you cannot have nested groups, than maybe a switch between grouping by XMPP groups and by accounts?

Andrzej Wójcik (Tigase) commented 7 years ago

%kobit Thank you for your ideas. I think that grouping contacts by the account in roster view should be simple to implement, but nested groups are not available in iOS so I can not use them.

It should be also possible to stretch roster row a little and add account name at the bottom contacts JID.

It could be also possible to group by groups and accounts but I would need to display group name (account) instead of group name@, so if you have group @People which is now displayed as People it would be displayed as People (tigase.org)

As for chat view, I can modify view accessible from contact button at the top and replace Enter message.. with ie. (at tigase.org) or (using tigase.org)...

wojciech.kapcia@tigase.net commented 7 years ago

I don't need grouping by account in roster (I actually don't use any grouping). Maybe color-code? 5-10px strip that would match colour of the account (something similar is present in k9mail and I find it quite useful).

Regarding chat view - something as simple as information in "about contact view" like "using account" would be more than enough (or again - colour code some part of the UI if that's possible - possibly not, but maybe.

Andrzej Wójcik (Tigase) commented 7 years ago

I've added a few ways to tell which account your are using:

  • In chat view you can see it in placeholder text (@using xx@yy.com@)

  • In contact details view with small text in gray saying using xx@yy.com

  • In roster, once you long-tap on the item you will see new menu with contact name as the title and message saying using xx@yy.com and options to select what to do:

    • open chat

    • edit roster item

    • show details (vcard)

I hope this helps. I've tried to think about adding colors to items but it would be rather difficult and extensive task.

Andrzej Wójcik (Tigase) commented 7 years ago

Changes will be released within the next build.

wojciech.kapcia@tigase.net commented 7 years ago

Thanks Andrzej - it definitely helps with readability and general UX. One small comment:

  • In chat view you can see it in placeholder text (@using xx@yy.com@)

This usually causes to display two lines, and then when you tap it shrinks to one (until you type enough text). Could you insert the placeholder text with something like non-breakable space to make it one-liner?

Andrzej Wójcik (Tigase) commented 7 years ago

I've needed to reimplement placeholder code, but it was required to make it display it in one line. I suppose we needed to do so, in case if someone had very long JID or very small screen.

This issue was caused by the fact that I've tested it on a device with bigger screen iPhone 6s.

Will be part of the next build.

issue 1 of 1
Type
New Feature
Priority
Normal
Assignee
RedmineID
6033
Version
Version 2.0
Issue Votes (0)
Watchers (0)
Reference
tigase/_clients/siskin-im#67
Please wait...
Page is in error, reload to recover