Alex
* Reworking the KDeclarative ConfigPropertyMap API, also moving the
QML bindings to the respective framework
https://invent.kde.org/frameworks/kconfig/-/merge_requests/85
* Unfortunately porting of plasma-workspace
(https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1182)
is blocked by
* the property for the wallpaper config being part of
plasma-frameworks and thus public API.
* I will create a KF6 task to keep track of it
* Did lots of porting in plasma-workspace,
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1195,
there was a regression so I had to revert a part of the change
* I will need to investigate this further
* Also https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1201
could use a review from d_ed[m] :)
* Besides that mostly work on the KF6 tasks, nothing too much related
to Plasma :)
* I made a small MR in plasma-workspace fixing some inconsistencies
regarding the translation domain and plugin id of the icons KCM
* Then KAboutData can be dropped for the icons KCM too


Arjen
* I think the most important things of last week are that I merged a
bunch of touch drag and drop fixes in kwayland-server, though I left
out window-to-window drag since that currently causes crashes until qt
is fixed
* I also managed to break qtdeclarative by backporting something that
was apparently insufficient
* which was in preparation of touch support for the overview effect,
which is now also merged (with a workaround for the thing I tried to
fix in qtdeclarative)
* explanation: taphandler and some other code in qtquick currently
assumes touch point id 0 is invalid
which is a stupid assumption and meant that initially, kwin's touch
code didn't work
because it was sending events as touch id 0
the workaround is to add an offset to touch ids when sending them to qt...
* oh and I also spent some time on my qmlmodule cmake thing to resolve
open review comments, to hopefully move that forward


Kai Uwe
Notifications:
    Receiving files via Bluetooth now shows "Bluetooth transfer" as
app name instead of "KDE Daemon"
    Add "transient" flag to jobs, allows to skip showing a "finished"
notification once done
        for e.g. "loading archive..." or statjob that provide no
meaningful actions to the user when done, please review
            Plasma part:
https://invent.kde.org/frameworks/kjobwidgets/-/merge_requests/13
            Frameworks part:
https://invent.kde.org/frameworks/kjobwidgets/-/merge_requests/13
KRunner:
    I believe we can speed up (make more determinstic) KRunner showing
up by not waiting for Plasma's strut manager
        When Plasma is randomly busy/frozen it jeopardizes KRunner showing up
        Had a brief look but the positioning/window handling code is
quite brittle, so did not dare touching it
KIO:
    Fixed various minor bugs in KPropertiesDialog, e.g. time labels
not hiding correctly if info is unavailable
    Replaced that massive "File type options" in KPropertiesDialog
with an "Open with: [name of default handler]" line
        Makes it more obvious to the user what all of this file type
association stuff means
        
https://invent.kde.org/frameworks/kio/uploads/9f7d390631d5e28a7b47077a630d5b26/Screenshot_20211119_233644.png
Dolphin:
    Generate thumbnails for visible files first since folders take a
long time to generate, please review:
https://invent.kde.org/system/dolphin/-/merge_requests/291
Other:
    Fix Ark "Create new archive" not hiding welcome screen
    Worked on improving job reporting in Ark, found some issues with
meta type registration
        https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/154
but not sure if this is the correct layer

-----------------------------------------------------------------------------------
Discussion about Krunner: can we move it already to layershell?
krunner has a single window so we could try to do it already.
may be a problem on the free floating option tough
DavidR has a prototype, there is a problem with dialog shadows still
(Dialog problem?)
And also you need to kinda not make dialog create a plasmashellsurface
-----------------------------------------------------------------------------------


Vlad
* Made various improvements in the overview effect, e.g. krunner
search integration, better launch times, cursor handling, etc
* Created a merge request to extract reusable parts of the overview
effect to simplify writing new qtquick effects in kwin
* I would like to start a discussion about phasing out desktop grid
and present windows effects some time later
* Those two has caused so much trouble and I need them to go away as
they make changing effects/scene stuff very difficult
[question from MArco: is it possible to rewrite the desktop grid in
the new qml api?]
* Yeah, maybe... Some people may be very vocal about the fact that the
overview ignores the desktop grid layout
* Although, as a kwin maintainer, I'm not happy about maintaining a
bunch of effects and would like to keep their number as low as
possible
* Besides the overview effect, I made dma-buf screencasting code path
in kwin more efficient

Nico
* minor visual tweak to plasma-pa:
https://invent.kde.org/plasma/plasma-pa/-/merge_requests/96
* Besides that mostly working on simplifying the KCM metadata
* Based on the new stuff Alex and I made
* And besides that mostly maintainance on craft stuff


Marco
* more work on morphingpopups on wayland, merged
* merged a solution in Plasma::Dialog side for wrong blur region behind tooltips
* fixed a drag and drop related crash in folderview
* some work on panels and multiscreen, changing how corona considers
the "primary screen"
* which led me to investigate in crashes of plasma when you close and
reopen the laptop lid. have some vague idea but definitely weird
dthings going on
* which in turn led me to investigate a kwin bug that makes it
sometimes stop drawing when the lib is reopoened
* i tried to reproduce https://bugs.kde.org/show_bug.cgi?id=445516 and
can't really reproduce... changing random svgs from old theme versions
all seems to always work
    one thing both caches (size and pixmap) now have file dates in...
the only way i can imagine things breaking,.. is devices with often
wrong clocks/dates

Reply via email to