You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if there's any technical hurdles, but I think replacing the current tints API where we provide multiple HazeTints with an API where HazeTint itself takes a gradient brush would be pretty awesome.
That'll make it easy to customize the gradient, and make the API feel a lot more natural and easier to use.
This design would also enable us to define better fallback tints using the same HazeTint class, e.g. replacing a progressive blur with a translucent gradient, but that's a separate issue (#398).
That's all! Would love to hear your thoughts on this, and thanks for the great work!
The text was updated successfully, but these errors were encountered:
Hi there! Thanks for the awesome library.
I'm not sure if there's any technical hurdles, but I think replacing the current
tints
API where we provide multipleHazeTint
s with an API whereHazeTint
itself takes a gradient brush would be pretty awesome.That'll make it easy to customize the gradient, and make the API feel a lot more natural and easier to use.
This is what I envision the API to look like:
Because it's tedious to add the
.copy(alpha = ...)
to every color, I'd suggest adding anopacity
parameter (to both versions):This design would also enable us to define better fallback tints using the same
HazeTint
class, e.g. replacing a progressive blur with a translucent gradient, but that's a separate issue (#398).That's all! Would love to hear your thoughts on this, and thanks for the great work!
The text was updated successfully, but these errors were encountered: