In T4275#298869, @ognarb wrote:

In T4275#298822, @ognarb wrote:

Lays, are there any pages from the web that can help as inspiration for our page?

This one https://kde.org/fundraisers/yearend2022/ which we basically just want to copy past to kde.org/donate. I'll see if I can do that during the promo sprint this weekend

Done https://kde.org/community/donations/ :)

But there are probably some more additional improvements we can do

Lays, are there any pages from the web that can help as inspiration for our page?

I wanted to also mention that whenever infrastructure is added or removed, we should do some change management to prepare the community if there is impact to them. Main aspects of a change include:

If help is needed with the page design, come to the vdg and we can help!

In T16403#294895, @ngraham wrote:

Thanks!

But does the font have to be monospaced? I think a fixed-width font might look better there.

I like it Nate!

In T16403#292367, @ngraham wrote:

Ok, let me play with the wording and propose something.

Still thinking through this, I am asking around to see if we can propose a design that integrates everything properly. Stay tuned.

I think my main thing is I want to simplify a bit.

In T12622#291129, @zamundaaa wrote:

Yes. FYI you can leave out the activities bit, at the sprint we agreed that it would be simpler to make the KCM apply to the current activity only

In T12622#290977, @meven wrote:

In Plasma Sprint 2023 we agreed we want to achieve this (https://invent.kde.org/plasma/plasma-desktop/-/issues/89)

zamundaa suggested design is aligned with the direction we were aiming at
https://phabricator.kde.org/file/data/3ib6sdfnmmw7lh54mbhw/PHID-FILE-ieljnhcfvxlf6wkpmqge/mockup.png

First implementation step would be to separate the Config UI from plasmashell process i.e adding a DBus interface.

What do you want to do exactly?

I am thinking that trademark rules are already decided by law. It would be a matter of developing a process internally of identifying those groups in need of this protection and then running them through the regular trademark registration process in the country of choice.

Just wanted to add a couple of suggestions for features:

I guess something I am missing is the "WHY?" part of the argument. Why should Plasma integrate at a default level with Latte?

I don't think this is a good idea everyone. First, I feel this is basically surrendering our design to the belief that others do better than us. I don't believe that falling into the idea of "the grass is greener on the other side" plays well for an open source project. If there are people who feel inspired by proprietary systems, they have the choice of being able to create their own styles. That's what Plasma enables, but we are not a system copycat. We believe in the power of ingenuity, that means, we believe we propose different ideas for the desktop than others.

Is this being followed up on the KDE Gitlab? I couldn't find it.

Has there been any conclusion here?

My feelings are that we should move to non-hovered controls. Here are some reasons that I find valuable:

I know this is merged now, but I have a bit of a gripe with the interaction. The fact that the global theme becomes part of the toolbar makes it seem like there is no button there. It seems like the global theme button is a header instead. This pseudo header/button also replaces the search button when the syse window is not big enough, leaving the user without the search field. If global theme was "not" a kcm, then it would make sense to have the placement it has. This is the only button that behaves this way. By the same token, you would expect all other headers like Workspace, Personalization, Network to also become header/buttons and have their own kcm, which they don't.

+1

I have a bias for my variation. However, having said that, I really like the differences shown in F8796068. It is soft yet the purple makes things very identifiable. I like it a lot. I personally feel like it's the stronger design. The ocean variation has my vote.

Hey man, can you join our vdg team on Telegram? Here is the link: https://t.me/vdgmainroom

In the current implementation of this, the cursor turns to the selector for the screen. The cursor does not draw a squared selection of screen where there is black outside the selection. The app crashes or closes after the screenshot is taken. This behavior happens on Fedora 32/Plasma 5.18

+1

+1 from me!

+1 from me!

I love this idea. I would request to keep the drag behavior and follow up with a second ticket to propose a change in the drag behavior for the panel.

Could you please try a combination of 2 and 4? I am curious how that would look like.

Look great!

Look cool!

In T13008#227333, @ngraham wrote:

Personally what I think we really need more than this feature is a global "reset everything" button. This is something I hear users asking for all the time, and I think it's a more common use case to want to reset everything to defaults than it is to want to see (and then maybe reset) which individual settings have been changed from their default values. Supporting this was what I thought all the KConfigXT porting was all about. :)

My opinion on this patch from the beginning has been that it really doesn't add much more than was there before. Visually, it clutters the UI. The icon selected for it might also not be visually appealing or meaningful enough. I believe there should be a different approach to this request. However, I am also open to just dropping the idea completely.

Looking at some of the rules, I see that the language seems very high. Surely a user that spends time on this KCM would have some understanding of what they are getting into. I would suggest bringing the language for labels closer to the one used for KCM options, where we make it conversational, inviting action. For example,

If I am understanding correctly, this patch adds icons in the kcm list to indicate changes you can revert by going to the kcm. Basically, default settings have changed and now you have the possibility to see that changes have been made. I am not sure that I like the implementation. I have some questions.

+1

It seems that the most common iteration is using the minus sign when the buttons are outside of the list itself and use some kind of remove button for those items that have things inline
I guess it depends if we are talking about removal from the system versus removal from the list. They are not intrinsically the same thing. However, I tend to favor using a minus sign in most places
I don't think the trashcan icon is probably as appropriate just because we don't always delete.

+1

I would suggest a circular button instead of square.