It’s an interesting project, but as a fork, I would be concerned about its compatibility with standard Qt & KDE libraries, widgets, and styles. Can you comment on that?
@ono, Thanks for your question. One of our main goals was to maintain compatibility with Qt user code. We have worked with a significant number of projects who migrated to CS and no one lost functionality. Most code will work without any modifications.
We have a parser (PepperMill) which you run one time to convert anything in your header files which used moc. For example, we change Q_OBJECT to CS_OBJECT(class_name).
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++?
@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.
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.
@ono, Can you could let us know which existing libraries you are using. We know a few have already been migrated to CopperSpice and we are happy to review the process for adding other libraries.
It’s an interesting project, but as a fork, I would be concerned about its compatibility with standard Qt & KDE libraries, widgets, and styles. Can you comment on that?
Also, what language bindings does it offer?
@ono, Thanks for your question. One of our main goals was to maintain compatibility with Qt user code. We have worked with a significant number of projects who migrated to CS and no one lost functionality. Most code will work without any modifications.
We have a parser (PepperMill) which you run one time to convert anything in your header files which used moc. For example, we change Q_OBJECT to CS_OBJECT(class_name).
Here is a link to the macros which are modified.
https://www.copperspice.com/docs/cs_overview/m_macros_metaobj.html
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++?
@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.
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.
@ono, Can you could let us know which existing libraries you are using. We know a few have already been migrated to CopperSpice and we are happy to review the process for adding other libraries.