herzenschein

herzenschein, 21 days ago

It doesn’t accurately describe the issue (animation stutter when using an HDD or during heavy I/O) and it doesn’t mention the solution (put the cache folder in tmpfs), plus it obviously follows the old sensationalist tone used in clickbait.

The point is to be deliberately vague to bait people into watching it.

herzenschein, 21 days ago

I think I started with C#, went to C, then (pre-ES6) JS, Python, then Perl, then C++.

I didn’t get much interest or progress in most of them. C# was somewhat interesting because I could make actual windows, and Perl just has a lot of interesting text-geared concepts and was created by a linguist (my background is in language and literature, not in any IT field). Perl is still delightful to learn, though I’d go with Raku (Perl 6) now.

The only language I really learned properly and use the most is C++, especially with Qt, as my true interest is GUI programming. I was never into raw algorithms and CLI programs.

herzenschein, 1 month 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, 2 months ago (edited 2 months ago)

can I write modern C++ code using the newer standards and still compile with libraries from older standards?

Yes, but then your project ends up requiring that newer standard as minimum too (which can be fine if that’s what you want).

how do I even organize a C++ project?

Well, one way that should be simple and scalable for beginners is leaving the root folder for project configuration/metadata/contribution guidelines/clang-format etc. and putting all source code inside src/.

If it’s just an app, you can make smaller library targets in src/ in separate folders with meaningful names, like src/models/, src/settings/ etc. If it’s a library, you typically put headers you intend to expose to your users in a src/include/ folder and use target_include_directories() to point to it, otherwise the same principle as apps applies.

It requires writing a few more, smaller CMakeLists, but it does mean you’re never lost in your own code.

how do I install dependencies?

We added this recently to KDE’s developer documentation, so at least for Linux it’s a start: Installing build dependencies: Using build errors to find missing dependencies.

herzenschein, 2 months ago

Welcome Linux furson :P

herzenschein, 2 months ago

FYI for whoever is reading this: it wasn’t just a theme, but a Global Theme: it can include a Plasma Style, a color scheme, an icon theme, a panel layout template, an SDDM theme, wallpapers and widgets. Widgets are capable of running arbitrary code, just like GNOME extensions.

Here’s the response article from one of our main developers: blog.davidedmundson.co.uk/…/kde-store-content/

In the short term we need to communicate clearly what security expectations Plasma users should have for extensions they download into their desktops.

We need to improve the balance of accessing third party content that allows creators to share and have users to get this content easily, with enough speed-bumps and checks that everyone knows what risks are involved.

Longer term we need to progress on two avenues. We need to make sure we separate the “safe” content, where it is just metadata and content, from the “unsafe” content with scriptable content.

Then we can look at providing curation and auditing as part of the store process in combination with slowly improving sandbox support.

herzenschein, 3 months ago

Heh, I was expecting it to run on Wayland and I was not disappointed. Nice.

herzenschein, 4 months ago

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

See also: community.kde.org/Plasma/Plasma_6#How_to_use/test…

herzenschein, 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, 5 months ago

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

Yeah.

community.kde.org/…/Why_not_GitLab_Issues

herzenschein, 6 months ago

This was shared recently by one of the people I follow: mastodon.social/

Direct link: www.sofurry.com/forum/view/thread?id=58457&pa…

That link has a few mentions of podcasts:

• 24/7 Chill Furry Lo-fi Radio www.youtube.com/
• Furry Refuge (Old streams) www.youtube.com/
• Catnip Radio www.mixcloud.com/CatnipRadio/stream/
• Furry Rave Crew www.mixcloud.com/FURRYRAVECREW/

herzenschein, 7 months ago (edited 7 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 of the page, 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, 7 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, 7 months ago (edited 7 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, 8 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, 8 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, 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, 4 months ago

Hey there, I’m Herzenschein. I had no formal education in IT, I’m a translator originally. I work with software documentation involving open source Qt apps now, so I get to read quite a bit of C++ code. I get pretty hyped at modern C++ features, and I dabble a bit in Perl and Python.