this post was submitted on 17 Jan 2024
43 points (95.7% liked)

KDE

5026 readers
37 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 8 months ago (1 children)

I think you're talking about migration from Qt to CopperSpipce, though, yes? I'm talking about integration with existing desktop environments. Making use of the themes that are already installed. Communicating with existing libraries via the existing interfaces. Are there any hitches to be aware of on that front?

And language bindings, for those of us who are trying to get away from writing in C++?

[–] [email protected] 1 points 8 months ago (1 children)

@ono, In terms of using an existing library, if it is a C++ library this works great. If the library was written using Qt it will need to be migrated to CopperSpice. This has already been done for a few libraries.

Our CS team has experience with library migration and we are available to help with this process.

[–] [email protected] 1 points 8 months ago* (last edited 8 months ago)

That's as I expected; Thanks for confirming.

Unfortunately, that leaves out the kind of integration I was asking about (and the kind implied in this post), through existing Qt & KDE shared libraries and such.

CopperSpice might still be interesting for stand-alone projects written in C++, though, and I appreciate that you're here engaging with the community.