Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use multiple layouts at the same time #15985

Open
SimonBrandner opened this issue Dec 16, 2020 · 0 comments
Open

Use multiple layouts at the same time #15985

SimonBrandner opened this issue Dec 16, 2020 · 0 comments
Labels
A-IRC-Layout A-Timeline O-Uncommon Most users are unlikely to come across this or unexpected workflow T-Enhancement X-Needs-Design X-Needs-Product More input needed from the Product team

Comments

@SimonBrandner
Copy link
Contributor

Additional context

I realized this could be useful because of this. This is going to gain importance if the bubble layout gets merged.

The problem

A considerable amount of users would prefer to use the chat-bubble layout for 1:1 chats and at the same time to use the "Slack" layout for group conversations.

This can be applied to other layouts too.

Solution

There are multiple ways to do this from the user perspective:

  • Set the layout for 1:1 and groups chats separately
  • Set the layout by some rules, example:
number of users <= 2: bubble layout
number of users <= 10: modern layout
else: IRC layout

Which one of these to use is a question of giving the user the correct amount (not too little, not too much) of options.

It would also be great to be able to overwrite the layout on per room basis.

@SimonBrandner SimonBrandner added O-Uncommon Most users are unlikely to come across this or unexpected workflow X-Needs-Design X-Needs-Product More input needed from the Product team and removed P3 labels Jul 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-IRC-Layout A-Timeline O-Uncommon Most users are unlikely to come across this or unexpected workflow T-Enhancement X-Needs-Design X-Needs-Product More input needed from the Product team
Projects
None yet
Development

No branches or pull requests

1 participant