• ono@lemmy.ca
    link
    fedilink
    arrow-up
    1
    ·
    11 months ago

    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++?

    • CopperSpice@hachyderm.io
      link
      fedilink
      arrow-up
      1
      ·
      11 months ago

      @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.

      • ono@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        11 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.