On Wednesday, December 6, 2023 9:51:20?PM CET Nicolas Fella wrote: > Hi,
Hi, > the transition of many apps to Qt6 provides some challenges for apps > producing and consuming KParts. > > KParts are implemented as Qt plugins and as such are specific to the Qt > version they are built against. In other words, a KPart built against > Qt5 cannot be loaded by an app using Qt6 and vice versa. > > Since some parts are used by a variety of apps this is causing problems. > When we last discussed this problem the consensus was "Port as many > things as possible and see where we are at then". Now we are approaching > a point where we need to take stock and decide what to do. > > There's several cases to consider: > > 1) Applications using their own parts without external users. This > happens in PIM where e.g. kmailpart is only used by KMail and Kontact. > No problem here > > 2) Applications loading specific parts from other applications. These > are easy enough to search for. We have the following cases: > > ..... > > okularpart (Okular is in the process of getting ported): > > - kile (no Qt6 port) > > - kbibtex (no Qt6 port) It looks like kbibtex was ported two days ago. Would it be possible to have a gitlab issue or wiki page to keep track of the changes? This also let people know where help is needed. Cheers, Carl