KDE CI: Frameworks » kirigami » kf5-qt5 WindowsMSVCQt5.15 - Build # 725 - Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kirigami/job/kf5-qt5%20WindowsMSVCQt5.15/725/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Wed, 13 Apr 2022 01:02:04 + Build duration: 2 min 26 sec and counting JUnit Tests Name: projectrootC_.CI.Job_Build Failed: 1 test(s), Passed: 15 test(s), Skipped: 0 test(s), Total: 16 test(s)Failed: projectrootC_.CI.Job_Build.autotests.pagepool/tst_layers.qml
Re: portal drag and drop helpers and where to put them
On Mittwoch, 6. April 2022 13:28:50 CEST Harald Sitter wrote: > https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/212 > > To get sandboxed apps to work with drag and drop we need to have drags > take a roundtrip through xdg-desktop-portal and unfortunately enough > that needs to happen by passing an open fd into the relevant API, > presumably to demonstrate that the sender actually can open the file > they want to send. To that end the sender would call a helper > function to extend qmimedata with the relevant transfer context and > the receiver needs to reverse that to get to (potentially in-sandbox) > paths again. > > On top of that there's also the fact that we can drag and drop remote > sources so we kind of also need to first mount remote urls into the > file system using kio-fuse :( > > All in all it's very broad in scope and requires a dependency on > qtdbus so I'm not sure kcoreaddons is necessarily the place for this > to live, at the same time we have related API here already so in the > interest of keeping related things together kcoreaddons kind of makes > the most sense. In particular since the existing helper function for > the receiver already existed meaning we get a lot of applciations to > support this without further changes. > > Thoughts would be much appreciated Is this potentially something for the QPA level? That would seem conceptually like the right place and it isn't affected by dependency considerations. (This might be an entirely stupid suggestion of course, my understanding of both the portal interface and the low-level drag/drop handling is extremely minimal). Regards, Volker signature.asc Description: This is a digitally signed message part.
KF6 meeting notes 2022-04-12
https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/3 https://invent.kde.org/frameworks/kconfigwidgets/-/merge_requests/131 - needs review/feedback - interesting part is openColorScheme() in kcolorschemehelpers_p.h - existing benchmark in the tests shows no change - might not work with Plasma's accent color feature, as that uses kdeglobals - possible approach: store only the accent color in kdeglobals, next to the color scheme name, and move the colors kcm color mixing code for this to KColorScheme https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/ 3#note_425424 - QDesktopWidget porting details noted in the issue - plasma-framework builds, plasma-workspace only blocked by kwayland-server issues with the QDesktopWidget uses resolved - plasma-desktop's biggest issue is the kdelibs4support use in the date/times KCM https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/ 3#note_431116 - two people in favor on mailing list, no objections, so let's go with this https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/ 3#note_431647 - only two applets access KPackage this way, so impact would be quite minimal - let's do it Co-installability/co-usability of KIO slaves with different major versions - kio-extras is not going to be co-installable could be a problem for this - also affects previews, context menu plugins, etc - everything plugin related is in versioned locations, so this is actually co- installable - similar problem with Ark's file manager integration plugins - when transitioning those to 6 would degrade 5-based consumers - probably needs kio-extras to be co-installable after all - for cases like ark, we might want a "plugins only" build flag, in 5 already - also helps with Flatpak bundling next meeting: https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/ issues/4 signature.asc Description: This is a digitally signed message part.
KDE CI: Frameworks » plasma-framework » kf5-qt5 SUSEQt5.15 - Build # 896 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/plasma-framework/job/kf5-qt5%20SUSEQt5.15/896/ Project: kf5-qt5 SUSEQt5.15 Date of build: Tue, 12 Apr 2022 15:35:13 + Build duration: 2 min 27 sec and counting BUILD ARTIFACTS acc/KF5PlasmaQuick-5.94.0.xml JUnit Tests Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 3 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.plasma_dialogqmltestFailed: projectroot.autotests.plasma_dialogstatetestFailed: projectroot.autotests.plasma_framesvgtest Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report44% (8/18)32% (39/123)32% (39/123)34% (4844/14073)26% (2364/9266)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests67% (8/12)67% (8/12)84% (817/976)45% (436/962)src.declarativeimports.calendar0% (0/6)0% (0/6)0% (0/526)0% (0/229)src.declarativeimports.core44% (7/16)44% (7/16)34% (867/2534)26% (381/1457)src.declarativeimports.kirigamiplasmastyle0% (0/2)0% (0/2)0% (0/25)0% (0/20)src.declarativeimports.plasmacomponents0% (0/6)0% (0/6)0% (0/531)0% (0/197)src.declarativeimports.plasmaextracomponents0% (0/3)0% (0/3)0% (0/42)0% (0/16)src.declarativeimports.platformcomponents0% (0/3)0% (0/3)0% (0/59)0% (0/14)src.declarativeimports.platformcomponents.utils0% (0/2)0% (0/2)0% (0/15)0% (0/2)src.plasma40% (8/20)40% (8/20)43% (1673/3875)33% (895/2719)src.plasma.packagestructure43% (3/7)43% (3/7)43% (58/135)47% (16/34)src.plasma.private41% (7/17)41% (7/17)51% (903/1778)37% (358/975)src.plasma.scripting33% (1/3)33% (1/3)12% (21/175)7% (7/105)src.plasmapkg0% (0/1)0% (0/1)0% (0/49)0% (0/42)src.plasmaquick31% (4/13)31% (4/13)24% (474/1963)17% (266/1540)src.plasmaquick.private100% (1/1)100% (1/1)78% (31/40)50% (5/10)src.scriptengines.qml.plasmoid0% (0/7)0% (0/7)0% (0/1266)0%
KDE CI: Frameworks » plasma-framework » kf5-qt5 SUSEQt5.15 - Build # 895 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/plasma-framework/job/kf5-qt5%20SUSEQt5.15/895/ Project: kf5-qt5 SUSEQt5.15 Date of build: Tue, 12 Apr 2022 15:22:41 + Build duration: 12 min and counting BUILD ARTIFACTS acc/KF5PlasmaQuick-5.94.0.xml JUnit Tests Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 3 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.plasma_dialogqmltestFailed: projectroot.autotests.plasma_dialogstatetestFailed: projectroot.autotests.plasma_framesvgtest Cobertura Report Project Coverage Summary Name PackagesFilesClassesLinesConditionalsCobertura Coverage Report44% (8/18)32% (39/123)32% (39/123)34% (4854/14075)26% (2366/9266)Coverage Breakdown by Package Name FilesClassesLinesConditionalsautotests67% (8/12)67% (8/12)84% (816/976)45% (435/962)src.declarativeimports.calendar0% (0/6)0% (0/6)0% (0/526)0% (0/229)src.declarativeimports.core44% (7/16)44% (7/16)34% (867/2534)26% (381/1457)src.declarativeimports.kirigamiplasmastyle0% (0/2)0% (0/2)0% (0/25)0% (0/20)src.declarativeimports.plasmacomponents0% (0/6)0% (0/6)0% (0/531)0% (0/197)src.declarativeimports.plasmaextracomponents0% (0/3)0% (0/3)0% (0/42)0% (0/16)src.declarativeimports.platformcomponents0% (0/3)0% (0/3)0% (0/59)0% (0/14)src.declarativeimports.platformcomponents.utils0% (0/2)0% (0/2)0% (0/15)0% (0/2)src.plasma40% (8/20)40% (8/20)43% (1673/3875)33% (895/2719)src.plasma.packagestructure43% (3/7)43% (3/7)43% (58/135)47% (16/34)src.plasma.private41% (7/17)41% (7/17)51% (914/1780)37% (361/975)src.plasma.scripting33% (1/3)33% (1/3)12% (21/175)7% (7/105)src.plasmapkg0% (0/1)0% (0/1)0% (0/49)0% (0/42)src.plasmaquick31% (4/13)31% (4/13)24% (474/1963)17% (266/1540)src.plasmaquick.private100% (1/1)100% (1/1)78% (31/40)50% (5/10)src.scriptengines.qml.plasmoid0% (0/7)0% (0/7)0% (0/1266)0%
KDE CI: Frameworks » plasma-framework » kf5-qt5 FreeBSDQt5.15 - Build # 882 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/plasma-framework/job/kf5-qt5%20FreeBSDQt5.15/882/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Tue, 12 Apr 2022 15:22:41 + Build duration: 1 min 16 sec and counting JUnit Tests Name: projectroot Failed: 3 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.plasma_dialogqmltestFailed: projectroot.autotests.plasma_dialogstatetestFailed: projectroot.autotests.plasma_framesvgtest
KDE CI: Frameworks » kio » kf5-qt5 WindowsMSVCQt5.15 - Build # 1338 - Fixed!
BUILD SUCCESS Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20WindowsMSVCQt5.15/1338/ Project: kf5-qt5 WindowsMSVCQt5.15 Date of build: Tue, 12 Apr 2022 10:14:56 + Build duration: 4 min 4 sec and counting
Re: portal drag and drop helpers and where to put them
On Tue, Apr 12, 2022 at 2:12 AM Aleix Pol wrote: > > Maybe the alternative would be to use the kdbusaddons for this? It > seems to me like there's no kcoreaddons things being done. I've thought about that but ultimately concluded kdbusaddons actually doesn't work for us. The way the technology works is that the sender and the receiver need to call a helper function to deal with the portal logic, if we had those helpers in kdbusaddons we'd need to have optional kdbusaddons dependencies on every drag and drop enabled application - it'd be super messy. HS
