This article on designing systemic colours (and comment) explores some of the challenges faced with designing color palettes. Example implementation in JS

In D21312#467698, @ngraham wrote:

+1 for restoring the feature, which is very useful! I've wanted this myself many times, so thanks for submitting this! However I'll admit I'm not super thrilled about having the capacity indicator bar always visible. I can't quite put my finger on why, but something about it feels a bit off. Maybe that's why the original only appeared on hover? But that's problematic in an era where we need to be designing for touch-friendliness. Maybe it could be a pie chart to the right of the icon but left of the text? Or maybe it's fine as-is and I'm just being a stick-in-the-mud.

Either way, adding VDG for comment.

In T8755#185695, @ndavis wrote:

In T8755#185693, @lavender wrote:

In T8755#185684, @ndavis wrote:

In T8755#185682, @lavender wrote:

It seems that it works with Breeze but not Breeze Dark, which stays blue regardless of color scheme. I am on Plasma 5.12 LTS admittedly.

This is because the Breeze Light and Breeze Dark desktop themes come with their own built-in colorschemes. If you want your desktop theme to be the same as your system colorscheme, use Breeze, even if you're using a dark colorscheme.

The reason why there are 2 desktop themes with built-in colors is that a user may want to have something like a dark panel with light applications.

Why does the blue color need to be hardcoded is my question

TBH, I just copied the Breeze Dark colorscheme and pasted it here: https://cgit.kde.org/plasma-framework.git/tree/src/desktoptheme/breeze-dark

Maybe if I removed the color settings for everything except the background and text colors, it would get the rest from the system colorscheme, but I don't know.

In T8755#185692, @ngraham wrote:

In T8755#185691, @lavender wrote:

Is there any reason Breeze Dark couldn't follow the color scheme just as Breeze does? Recreating Breeze Dark along with the accent color changes as a Breeze color scheme is a lot of unnecessary work (that I couldn't figure out after having extensively researched it). There should be a user-friendly way to change the main color used by the themes we ship with Plasma.

There is: just use the "Breeze" Plasma theme, rather than the "Breeze Light" or Breeze Dark" theme. Then it will follow the color scheme. I agree that we need to expose this functionality in a much more user-friendly way.

In T8755#185684, @ndavis wrote:

In T8755#185682, @lavender wrote:

It seems that it works with Breeze but not Breeze Dark, which stays blue regardless of color scheme. I am on Plasma 5.12 LTS admittedly.

This is because the Breeze Light and Breeze Dark desktop themes come with their own built-in colorschemes. If you want your desktop theme to be the same as your system colorscheme, use Breeze, even if you're using a dark colorscheme.

The reason why there are 2 desktop themes with built-in colors is that a user may want to have something like a dark panel with light applications.

Is there any reason Breeze Dark couldn't follow the color scheme just as Breeze does? Recreating Breeze Dark along with the accent color changes as a Breeze color scheme is a lot of unnecessary work (that I couldn't figure out after having extensively researched it). There should be a user-friendly way to change the main color used by the themes we ship with Plasma.

It seems that it works with Breeze but not Breeze Dark, which stays blue regardless of color scheme. I am on Plasma 5.12 LTS admittedly.

If you change the colour scheme the taskbar among others don't change with it, that's what he OP is about.

Tangentially related: This article on designing systemic colours explores some of the challenges faced with colour design. Example implementation in JS

I'm not sure if the taskbar is the only place that is hardcoded, it's the only one I tracked down manually.

In T10891#185607, @gikari wrote:

Note that as a part of thie effort, I do not want to try to round the bottom corners of the windows when No Borders is in use. This idea is too controversial and has the (slight, but real) potential to interfere with applications that put interactive elements in the bottom corners. People who want to accomplish this anyway can use https://github.com/alex47/KDE-Rounded-Corners.

Excuse me, could you elaborate on this? What is controversial about it?

I added T8755, I'm not sure how well it fits here but the idea would be to give the user more control over the accent color used by Breeze. Here are examples of how Windows 10 generates a palette based around the selected accent color and MacOS also slightly adjusts the colors, both lets user select the accent color.

OpenToonz: Full-featured 2D animation creation software.

OBS Studio comes to mind. It's used by many creatives, streamers, podcasters, etc. It has a strong community (hundreds of thousands of daily users) and it uses Qt!

In OSX they have Switch Control and Accessibility Keyboard and Panel Editor to edit them.

This redesign seems like a good place to start thinking about integrating accessibility options T8888 with the rest of the settings. I included some screenshots of what OSX does (Switch Control, Accessibility Keyboard, Dwell for head- and eye-tracking and Panel Editor to edit)

I tried some of the examples in your post and the focus chain situation is really bad, many items are simply inaccessible via keyboard navigation.
There definitely should be some guidelines to make sure your plasmoid is navigable via keyboard.

Can you elaborate on what this task is about?

The Plasma layer needs to bring it all together and present it to the user when available.

@nicolasfella the subtask is restricted so others cannot follow the link/see what the subtask is

This is what qvkbd looks like next to xvkdb. qvkbd looks better but xvkbd has more functionality.

Perhaps we can use this project https://github.com/KivApple/qvkbd ?

• require the use of differential privacy tools (e.g. rappor which is what Chrome and Firefox uses)

@bcooksley Done: https://forum.kde.org/viewtopic.php?f=285&t=151062