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

Indicate active/current narrow in side panels #516

Open
blenderskool opened this issue Feb 25, 2020 · 10 comments · May be fixed by #1334
Open

Indicate active/current narrow in side panels #516

blenderskool opened this issue Feb 25, 2020 · 10 comments · May be fixed by #1334
Labels
area: UI General user interface update enhancement New feature or request

Comments

@blenderskool
Copy link
Collaborator

The currently selected stream can be indicated a little differently from the rest of the streams. Few ideas that I have:

  • Maybe a specific highlight color
  • Making the active stream bold
@neiljp
Copy link
Collaborator

neiljp commented Feb 25, 2020

@blenderskool I agree we could do this, though we already do show the active stream (or more broadly, 'narrow') at the top of the message list. Do you mean the active narrow being highlighted in eg. the stream list, user list, or whichever other place matches the narrow being shown?

@blenderskool
Copy link
Collaborator Author

@neiljp Yes, the active stream is shown at the top of message list. But I think it's more natural to see the active stream on the sidebar. So that while choosing another stream, you don't have to look away from the sidebar to remind yourself of the active stream.

In the screenshot, we could have something highlighting the #frontend while still keeping it at the top of the messages list.

zt-active-stream

@neiljp
Copy link
Collaborator

neiljp commented Feb 26, 2020

@blenderskool Right, that's what I suspected you meant, but also note that we'd likely want to do it for all other 'special' narrows that there is a user-interface for - ie. if a topic list is shown, highlight the topic, if in the top-left narrows, highlight those, if a single-user conversation, highlight the user, etc.

@blenderskool
Copy link
Collaborator Author

@neiljp Yeah makes sense. There is already highlighting for the selected message, online users. Maybe a consistent pattern across the layouts could be built based on that.

@sumanthvrao sumanthvrao added the enhancement New feature or request label Mar 7, 2020
@SGeetansh
Copy link
Collaborator

SGeetansh commented Mar 8, 2020

@neiljp @amanagr @sumanthvrao
I think this would be interesting to implement, should/can I work on this?

@amanagr
Copy link
Member

amanagr commented Mar 9, 2020

Yes, of course! (You can use @zulipbot claim to assign yourself on issues)

@SGeetansh
Copy link
Collaborator

@zulipbot claim

@zulipbot
Copy link
Member

zulipbot commented Mar 19, 2020

Hello @SGeetansh, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days.

You can reclaim this issue or claim any other issue by commenting @zulipbot claim on that issue.

Thanks for your contributions, and hope to see you again soon!

@SGeetansh
Copy link
Collaborator

@zulipbot claim

@zulipbot
Copy link
Member

zulipbot commented Apr 3, 2020

Hello @SGeetansh, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days.

You can reclaim this issue or claim any other issue by commenting @zulipbot claim on that issue.

Thanks for your contributions, and hope to see you again soon!

@neiljp neiljp added the area: UI General user interface update label Apr 11, 2022
@neiljp neiljp changed the title Indicate active stream Indicate active/current narrow in side panels Apr 11, 2022
@neiljp neiljp linked a pull request Mar 18, 2023 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: UI General user interface update enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants