- User Since
- Sep 14 2018, 11:24 AM (70 w, 5 d)
Sun, Jan 19
I posted the previous comment in a eccessive state of tiredness and nervousness :-) I will look into doing a better mask *before* asking to land the patch, so I can be sure it's the right patch forward.
Yes, I *DID* take some code from Zren plugin and wrote some other. My intention was absolutely not to steal his code, I want to be clear about that: I had opened an issue on his repo asking him to upstream the code, but then I thought that it was probably simple enough that I could figure out how it could be implemented in master based on his code, and get back to him with the patch directly to make the whole process easier for him. I did not do that yet because this patch is missing some stuff, my intention was not to already submit the patch for landing, I tried to make that clear in the summary because I couldn't find the phab button to flag it as 'not done'. I opened the diff because I had already worked on it for 4/5 hours and did not want to keep changes on local, and keeping the open diff helps me remember what I'm working on, plus I wanted to know if there were objections to implementing the feature before spending more time on it.
Regarding the mask: I'd keep it as is right now and look more into it in the (very near) future. Currently the difference is not noticeable even on different scalings and I cannot find another working solution, so I think it should not be a blocking issue. But yes, I will surely look more into it. But right now I have little time and I spent the last four days without studying and working on KDE and I know I can't keep up that, so I'm just a bit afraid that this patch would end up blocked for weeks again.
Regarding the corners, I will also look into it but not in this patch, as that would be an unrelated change.
Mh, but this is specifically to blur just the wallpaper, as you might want to get information from other windows. At that point, it would be weird for it to be a kwin effect, as it's much more related to just the wallpaper, and the user would expect it to be in the wallpaper settings.
I've tried to ask some users, and I received generally positive feedback on the idea, as many considered it pretty. There's a plugin that does this (with many positive reviews on the store), but I think it's not a good idea to fork very similar codebases, and this patch would make it much more discoverable by default. I just think it would be a pretty feature that users might like. I love it myself. It make the eye focus on the active window rather than the background.
Sat, Jan 18
Fix possible bug
Resized mask to better fit rounding shape
Removed unrelated tabbar change
Can you please doublecheck that you see everything correctly? The mask thing was weird, but I think I fixed it
- Merge branch 'master' into bettershadows
- Changed masks
Added links to hardware page from distributions and plasma-desktop pages
Updated Tuxedo image
Fri, Jan 17
Thu, Jan 16
Mon, Jan 13
Yeah. I'd suggest 20th of February. I'd also officially close the Apps section, as we did not receive any submission at all.
Sat, Jan 11
Hi! Can I ask you to send me that theme file, if you still have it, as I'm unable to create on with similar rounded corners?
Thu, Jan 9
Sun, Dec 29
Making the task manager icon-only: +1
Sat, Dec 28
I would disagree on that because the points where both excel aren't mutually exclusive; Latte features could be implemented in normal Panels and Latte could be improved in RAM usage (if needed?), stability and performance. Having two different products will keep the situation as it is today: two different kind of dock/panels, each failing in some spot. Unifying them would instead give the opportunity to focus on a single, great product that could be a selling point of Plasma. If you look Latte long list of features, you will notice that there are some that the current panel would highly need (shortcut and notification badges, spacers, dodge windows, ...) that I don't think will ever implemented on the Plasma Panels based on its recent history of improvements; furthermore, there are a lot of features that, although not used by default, would definitively be appreciated by lots of users. Having those features by default instead would improve discoverability and the number of people actually using them by orders of magnitude: many people would enjoy the smart background, but they probably wouldn't want to install and having to configure a third party app to get that. Furthermore, having two different product has two other consequences; in the first place, Latte is not well integrated into Plasma, and you can see that by how the super key has to be added in a file to work, extremely not user-friendly; plus, Latte cannot be a selling point of Plasma: this issue was also raised when doing the kde.org/plasma-desktop webpage, as Latte could've been a great feature but was only mentioned in a sub-section. Furthermore, Latte itself follows KDE motto: it is simple by default, and powerful when needed. What is not simple by default and powerful when needed is having a feature-limited product by default and having to install a different one which does not integrate well immediately, that does the same things but with more features but less stable. If Latte was to be chosen as a default (e.g.), the developer and user attention alone would help the developers find many of the bugs and instabilities that it currently has, thus giving Plasma Panels no reason to exist anymore really.
The above reasoning is very specific to the Latte/Panels situation, but I think the point are those, more generally, of lack of consistency: you get product A which is good at X and product B good at Y; people who value X more will go with A and suffer for lack of Y, and people who value Y more will go with B and suffer for the lack of X, although X and Y could be implemented in the same product; but since A target is people who mostly like X, developers will not focus on Y, and B developers won't focus on X. Making the two a single product could help to get both features. And I think that Latte features would really improve Plasma experience for the majority of users that will not search for a third party app, install it, remove normal panels, and find the FAQ to fix the super key, and will help promoting the Plasma environment as maker of quality products.
Fri, Dec 27
Hi! I was using the app, and I was worried that some things could be little user-intuitive. So I tried to give my phone to various users asking them to do a simple task. Here's the feedback I got. Feel free to ignore it though, but I generally observed a dissatisfaction towards the application:
Dec 20 2019
+1, this is quite in line with the consistency goal
Dec 15 2019
Got it. Blur is not rounded either to me. The shadow was hiding it.
I just compared the blur and contrast effects and the mask is used in the exact same way :-/ I have no idea what could be wrong there.
Breeze dark highlight is currently #3daee9 in the Breeze Dark colorscheme. If that's too light, we could darken it there, right?
Darker could be (example value):
Otherwise, the highlight effect could be made more transparent so that it's darker, but that would be a problem for consistency, as the same highlight color is also used throughout the desktop theme.
Dec 11 2019
Dec 8 2019
Dec 7 2019
Reset tabbar to master
Changed inactive to 5%
Dec 3 2019
Since Noah will work on a new QStyle, we will have those areas in windows:
Nov 28 2019
Got it. The shape is actually rounded BUT the desktop contract effect is applied in the whole rectangle underneath, and it makes everything look like a rectangle. Here's the widget with fully transparent background, but with the contract effect on:
Of course, I can't just turn off the contrast desktop effect. I'm unsure how to move forward with this.
Here's Plasma without desktop effect:
As you can see, shadows are working!
Nov 27 2019
Nov 24 2019
Nov 23 2019
Might be too subtle, maybe more opacity would be needed
This should have a 13% vs 23% opacity, what do you think?
Changed opacity of inactive vs non-visible application background color
I'm sorry, isn't this right?
The top one was like that before, and I just edited the bottom one, and they seem to be the same; shouldn't it be right then?
I just can't get the padding right on angles when changing their size. What size should I change of the colored rectangles?
Nov 19 2019
Another possibility is to have different transparency for panel and widgets:
Or opposite (probably less favorable):
Nov 17 2019
+1, should we land this while HIG animation page and easing curves are being discussed?
Now that we got back the 3px line, I would say that it is recognizable. I like the idea of having the background and reinforcing the idea that line=visible. But it's such a minor change that I would be okay with any option really.
I understand that leaving (shutdown/logout) is an important option, but please consider that:
Finally! I'm 100% this works now.
Updated breeze shadows
While D25343 is being discussed, we can change the effect to Quad from Sine so it's already more consistent, eventually change to cubic if there's agreement on that in the future.
Changed sliding popup easing curve to In and Out cubic
Tweaked colors of icon view backgrounds
Changed 2px lines to 3px
Resized 2px tabbar line to 3px
Nov 16 2019
I agree that animations should be consistent and specified in the HIG. I will see if there's anything I can do to help you with this page.
Added background colors to active and inactive icon view
Here's what I think:
- The line should indicate that the app is opened, the window is not minimized and the window is focused (opaque blue) or inactive (opaque gray)
- The background should indicate whether an app is not opened (no BG), minimized or inactive (semi-transparent gray), or focused (semi-transparent blue)