-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
feat(message-ui/system): stylize system messages specially #1377
Conversation
Mmmm I don't like having an avatar for system messages... if we could work on styling the line itself, instead of pretending there's a system user, I think would be best... but that's my personal opinion on this. :) what do others think? @RocketChat/core |
Hmm. I agree with @marceloschmidt. Really subjective personal preference. Mega-use of avatars big and small, while fun initially, eventually gives an overall 'swiss cheese feel'. On multi rows of edited messages, it often looks like Evil Sing Gru and his mischievous Minions 👿 Again, very personal and subjective. |
I agree, this is very personal. But one option I'd be OK with, would be if we make Rocket.Cat enable by default (but with no funny scripts), than we could have an option for Rocket.Cat to be the standard system messenger... I like the idea of turning Rocket.Cat into our little buttler. |
I think it would look great just the contents of that message instead of a system user label or avatar. |
This will help differentiate user messages from events like "room join" or "room leave."
e01e6c7
to
0ef3de7
Compare
@geekgonecrazy I removed the extra system username and icon. @geekgonecrazy @engelgabriel @marceloschmidt @Sing-Li : thoughts? |
@blaskovicz The leave / join messages look much better. I'd move the time to the left side instead of on top. The /me in my opinion doesn't look good with the style we have going. Can we do something more similar to how the edit looks? Maybe some icon that would represent an action on the left side kind of like the edit is. So something like: Maybe if its always alone and never showing the square even if its their first message? |
I don't like the way leaves/joins are being displayed. It looks as if when bob leaves the room, bob is somehow related to zach... to me it's not clear that "bob leaves" is not one of zach's message. |
@marceloschmidt I agree. What if the leave/join message simply wasn't indented to the normal message width, but instead started at the same position as the user's square avatar? Also, @blaskovicz I'd suggest for
To help differentiate these system messages, maybe we want to give them a light grey background, with rounded borders? Make them look a little like a label, only not nearly as high contrast. It'd be worth seeing how it looked. (Also this should be part of the site's theme, as I could see some people preferring, say, a deep rich purple for the background of system messages.) |
yes i'd love it if we could make /me just like the join / part messages you have. |
To bring this back, what if the join/leave messages were sent by the |
@graywolf336 I personally dislike that. The problem here is that if Rocket.Cat says join/part, there's no immediate visual clue as to the importance of the information. I most cases, messages from users >> messages from the system. If we train users that big square avatar with a name and text is important, they'll have that moment of, "Oh, someone said something? No, no, just Rocket.Cat. Again." |
For another project I'm working on, I've prototyped a microchat. I feel it might be useful to see some of what I've been talking about: Personally, I'm a big fan of this styling (but I am biased ;)). I feel it's very clean, and visually intuitive for users. System messages are separate, emotes are visually distinct from system messages, and messages are clearly distinct from both of those. It should be pretty easy to achieve the same in Rocket.Chat, even without using this look and feel wholesale. Keep unimportant information to a single line, use color cues, and don't underestimate using the right hand side of the page for the least valuable information. |
@Morgul I agree. I would love it if join/part /me all performed that way |
Guys, can I propose we close this PR... at least for now? There is a lot of personal taste involved on this, and we don't have a real problem to solve here... the current design works and we have so many other issues open that I think we have higher priorities to focus on. |
@blaskovicz any objection? I would for sure like to see this PR or another that does this make it in. Its not a make it or break it change. But this little bit of design change just makes it look a lot better. |
@engelgabriel if it's a choice between closing this, or merging it as it, I'd rather merge it as is, unless you guys have objections to the styling as @blaskovicz presented it. I was suggesting improvements, but I think that this change as-is improves on the current styling. |
I tend to agree... I'd rather have some improvement then none at all |
@blaskovicz let us know if you don't have time to work on this. Before long if you don't have time, i'd like to take a look at this. Its a small thing, but i'd love to see it improved :) |
What state should I get it in before we accept it? |
0bb125d
to
163aa59
Compare
163aa59
to
5e9f93d
Compare
@blaskovicz Excuse me if the above doesn't make perfect sense; it is due to lack of sleep. |
Other choice was the 💬 icon. I just didn't want the border + megaphone any more. |
My concern here is still that this is very personal taste. This change of layout needs to be configurable on the admin. |
Bump, I'd really like to see an option to allow users to customize the chat environment! |
I am closing this as it is already too far behind the current branch, and as I said before, there is too much of personal taste involved. We now have @karlprieb as full time front end engineer, and a design agency starting to work on the UI in Jan. So the learning from this PR will be that we will add more classes to the messages, with their Also more work needs to be done on the definition and classification of system messages, so they can be easily styled. |
This will help differentiate user messages from events like
"room join" or "room leave."