- User Since
- Sep 4 2017, 6:04 PM (123 w, 6 d)
Tue, Jan 7
Happy that this will land pretty soon!
Fri, Jan 3
I commented on D25343 about this. Also note the following inline comment. If we decide on (really) "OutQuad" for slide-in and "InQuad" (or "OutQuad" in code), we just need to adjust L467. Maybe we should also add a comment at L506 that the easing curve will be reversed.
As mentioned in D18000 I think the following two things should be adjusted. I think it is more natural that way.
Video of what I mean
WAIT. The slide-in animation is choppy, as we are using InQuad. This means it starts smooth and ends linear. IMO it should be the other way around. Start linear, end smooth.
Tue, Dec 24
Dec 6 2019
Couldn't find time for this either. I will probably start working on this again, when my development environment is set up again.
Oct 13 2019
Oct 12 2019
Oct 10 2019
Nice work! It looks very good now.
Looks like replacing the label with a combobox breaks alignment in the KCM and exceeds the full width in the applet.
Sep 28 2019
Sep 27 2019
Change behaviour of configuration.
I think Nate's idea on how to display this in the applet config is better. Will do that instead
Put checkbox into own category
Align mute button centered with slider
Fix wrong display name of default-device button
Sep 26 2019
Add copyright header
Rebase onto master
Make icon full height for playback devices, too
Right! I completely forgot about that. Will work on it
Remove stepping again, change label text of port selection
Remove redundant whitespace from copyright header
Use QQC2 ToolButton instead of Button for Mute. Add stepping to volume slider, similar to applet.
Sep 24 2019
Import QtQuick.Controls as QQC2 and fix ToolTip delay
Sep 23 2019
Set domain for all i18n strings
Sep 15 2019
We should definitely define how the easing curves should look. Generally I think we should always use some kind of decelerating, but not accelerating, easing for appear animations and accelerating, but not decelerating, for disappear animations. We could look at Material design and specifically on how they are doing easing: https://material.io/design/motion/speed.html#easing.
Fix wrong opacity condition for vertical popups
Fix syntax error
Tidy up code
I recently set up a proper working environment again and started tinkering with different easings and slide-lengths. I decided to make a compromise between the old animation and the one I proposed before.
Compomise between old behaviour and my proposal. Now uses fixed slideLength again, but with different easing.
Feb 16 2019
There are probably people, who would still prefer different titlebar colors from the rest of the window. Therefore I'd add a "Breeze Dark Classic" color scheme to @filipf's proposal, that uses the same titlebar color as "Breeze Classic".
Also why are there different text colors between current Breeze Classic and current Breeze Light?
Jan 14 2019
I can only speak from experience. I don't know if there are any scientific studies that look at user experience with a focus of animation.
Jan 8 2019
I don't really think that it looks that different than other animations. If one gets used to it it isn't that strange anymore.
Jan 6 2019
I just added the if statement back (but keeping the interpolate). It actually looks better now!
Change opacity for custom slideLengths only
Jan 5 2019
Restore support for custom slideLength
I personally feel, that timing functions for things appearing should not accelerate, but rather only decelerate.
I am often designing things with influences from different design guidelines, but when it comes to animation I often look at the Material Design Guidelines, as I think that Material Design animations feel natural. They have a section about things appearing and disappearing here. Therefore I chose decelerating/accelerating timing functions.
Dec 26 2018
I thought this is about controlling the system volume and not the media player volume :/
Is this still relevant? As far as I can tell album art and position is not supported with all MPRIS media players.
Nov 25 2018
Can someone benchmark this? Would be nice to know how much this affects performance.
Sep 27 2018
I tried to implement this feature, but I can't seem to get the DropArea working. Could it be possible that PlasmoidViewer does not support drag 'n' drop? It always appears as an icon inside the PlasmoidViewer similar to FolderView on the normal desktop.