-
Notifications
You must be signed in to change notification settings - Fork 263
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
Compose box redesign #928
Merged
Merged
Compose box redesign #928
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
8972754
color [nfc]: Add ColorExtension.withFadedAlpha
PIG208 026c048
emoji: Use withFadedAlpha for highlightColor
PIG208 56b7a19
theme: Update borderBar to follow change in Figma design
PIG208 58debf5
compose [nfc]: Refactor away shared iconTheme override
PIG208 88b2ff9
compose [nfc]: Extract compose buttons as a list
PIG208 5956528
compose: Use new icons from the redesign
PIG208 3adb395
compose: Implement most of compose box redesign
PIG208 94cf40e
compose: Support redesigned button feedback
PIG208 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commit message nits:
In the first paragraph, I'm not sure what "instead" refers to. How about: "And use it everywhere we were using
.withValues(alpha:
to fade a color variable, except for one place in lib/widgets/emoji_reaction.dart where the variable is semitransparent to begin with. We'll do that as a non-NFC change in a later commit.About the second paragraph:
withValues
calls in lib/widgets/channel_colors.dart should stay. The linked design for the computation (a replit by Vlad) doesn't specify multiplication; it says to set the alpha channel to 0.3, which we're doing withwithValues
.withValues
in lightbox.dart can stay. It's setting an alpha channel on a constant from Flutter (Colors.grey.shade900
) that realistically won't ever change to be semi-transparent. Even if it did, it's not clear that 0.87 would be the wrong value to end up with.withValues
calls in lib/widgets/theme.dart, I think these don't need to be specifically mentioned in the commit message. They're usingwithValues(alpha:
as intended, to create a color with its alpha channel set to a value. They might have done that same thing a different way, like in theColor
constructor. That's different from "fad[ing] a color variable from [DesignVariables] […]", which we often do e.g. to translate from the Figma anopacity
attribute on an element that's colored with a variable.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Changed the message to
with a minor tweak mentioning that, in dark mode, the color is semi-transparent.