herzenschein

herzenschein Mod , 27 days ago

It's small enough that we actually don't get many things to moderate either. I don't think I've even done any mod action so far. :D

herzenschein Mod , 3 months ago

What’s the best or recommended way to test out Plasma 6 RC2?

See also: https://community.kde.org/Plasma/Plasma_6#How_to_use/test_it

herzenschein Mod , 4 months ago

without the need of the moc

I got a bit of a mind freeze reading that sentence since my first thought was "why would someone deliberately give up on Qt's reflection system" but only then realized they're still using QMetaObject (the thing that actually enables reflection and signals and slots), just building it with something else.

herzenschein Mod , 4 months ago

Afaik the reason why they're not using GitLab issues it's missing some features they need, which Bugzilla has.

Yeah.

https://community.kde.org/Get_Involved/Issue_Reporting/Why_not_GitLab_Issues

herzenschein Mod , 6 months ago (edited 6 months ago)

So what you want to do is put a Kirigami.SearchField inside the global toolbar created by the Kirigami.Page. It’s not a header.

In the first case you’re putting it inside the page, and because it’s a direct child of a Kirigami.Page, it is automatically laid out for you, which is fine, but not what you want.

In the second case you’re putting it in the header of the ApplicationWindow, but you actually want to put in the global toolbar, so it’s not what you want.

In the third case you’re just putting a SearchField before the initialPage, so it’s loaded on the same level as the page, it’s not what you want.

You can put it in the header property of the Kirigami.Page, but the header area of the page doesn’t include the global toolbar, so they just happen to be close together by chance.

The way I’d have expected to do that would be to override the globalToolBarItem of the Kirigami.Page, but it’s read only, so I don’t really know how to help you with that. You should ask in the Kirigami Matrix room or in the Discuss forum.

herzenschein Mod , 6 months ago

Also, you should only use Layout attached properties when the object you’re using it on is a child of a Layout, for example:

<span style="color:#323232;">ApplicationWindow {
</span><span style="color:#323232;">    ColumnLayout {
</span><span style="color:#323232;">        anchors.fill: parent // Not a child of a layout, so you use anchors
</span><span style="color:#323232;">        Controls.Button {
</span><span style="color:#323232;">            Layout.fillWidth: true // It's a child of a layout, so you use Layout.fillWidth
</span><span style="color:#323232;">        }
</span><span style="color:#323232;">    }
</span><span style="color:#323232;">}
</span>

herzenschein Mod , 6 months ago

I can’t tell you why this is happening, but what is clearly happening is that your apps are being run under a nested kwin_wayland instance. It’s as though you were running kwin_wayland krunner.

If anyone’s wondering, my main issue with Wayland was that it wasn’t setting the DISPLAY and WAYLAND_DISPLAY environment variables for some reason, and this would cause all kinds of software like Steam and Firefox to not even launch. I tried setting them manually but that didn’t go do well either.

My guess is that whatever fix you attempted here caused this, so you’d need to be more specific about what you tried.

herzenschein Mod , 7 months ago

If, instead, you won’t do it and prefer to keep Bugzilla as the main issue tracking platform, could you tell us why?

Here are the reasons why: community.kde.org/…/Why_not_GitLab_Issues

The tldr is that Gitlab Issues is limited for users, developers and triagers compared to current Bugzilla, given the current KDE infrastructure. These are just technical issues. The moment Gitlab solves those limitations, KDE would gladly use it.

[…] since they’re right there by the code base.

Note the section “Bugs need to be filed against individual repos”. At it stands right now, if a non-technical user finds a plasmashell bug, they can just go to “File a bug”:

https://pawb.social/pictrs/image/d038d29e-9291-491c-a6e3-531618cfed98.png

and they’re greeted with this:

https://pawb.social/pictrs/image/420f2343-2da4-4d42-979b-0b0dd24342e5.png

And then they can choose Plasma and then plasmashell, both with very descriptive text mentioning what should be reported there. It’s not too bad to find the right place to report things, to be honest. And there’s an “I don’t know” field, which is great. :)

Finding issues can be a bit finnicky, yeah. But you can click on the search field in the first page, type what you want to find, click on Quick Search and you get a list of results based on your keywords, and you can also click on the Search button and then click on Simple Search to look for some keyword in a specific product. Once you know it’s pretty simple.

herzenschein Mod , 7 months ago

I was thinking, with the recent news of a contributor to GitLab adding support for forge federation, some time we could see that being enabled in the KDE instance as well, I hope.

It would be cool indeed. It would mean that people on KDE Invent could make issues and MRs directly to the Freedesktop Gitlab, for example, if both were federated.

herzenschein Mod , 8 months ago

Maybe keep the Overview text and icon color as white for better contrast. The blue background color already conveys selection I think.

herzenschein Mod , 10 months ago

I answered something similar elsewhere:

If you mean migrating the files yourself, it’s just a matter of copying the file from the old place ~/.config/yourconfigrc to ~/.config/yourapp/yourconfigrc.

If you mean you want the application to manage the migration itself, that’s an implementation detail I hadn’t thought about yet, but which I assume wouldn’t be difficult to do with KConfig.

You can see this bit of code from Konsole showing how to migrate from old entries to new entries in the same config file for example: >invent.kde.org/utilities/konsole/-/…/main.cpp#L99

The implementation could probably be something similar, with two KConfig/KSharedConfigPtr instances I assume 👀 so:

• if oldConfig exists, create an object for it
• read all oldConfig entries
• if it differs from newConfig, store which ones differ
• write all different oldConfig entries in newConfig object
• sync()

Something like that.

herzenschein Mod , 10 months ago

I think so. I mean, the migration code would still be there afterwards, maybe removed after several versions later.

If the user syncs machines with different application versions I’m not sure there’s anything that can be done at the code level though. 👀