Monday meeting notes for 25/10/2021
Aleix Pol
aleixpol at kde.org
Mon Oct 25 13:30:20 BST 2021
Should we organise a call or so about wacom tablets on wayland? What
was the discussion about?
On Mon, Oct 25, 2021 at 1:07 PM Marco Martin <notmart at gmail.com> wrote:
>
> [discussion about problems in wayland wrt wacom tablets, may need more
> discussion with hanyoung and tyson tan]
>
> David E
> * We're seeing the usual mass of bugs come in after a .0 release
> * so we need to be more on top of that
> * I approved a bunch of things wrt fingerprints
> * There's some good stuff from Devin
> * and I'll merge my kscreenlocker side
> * it's currently "blocked" on letting someone merge their patch for
> custom prompts
> * and then I'll land the fingerprint stuff on top
>
> [David Redondo We broke plasmashell dbus api. d_ed I saw the mrs]
>
> Nicofe
> * One big-ish thing is implementing fdo color preference support in our portal
> https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/49
> * Fixed a relevant KCM bug
> https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1123
> * I also added API to use it from an app:
> https://invent.kde.org/frameworks/kguiaddons/-/merge_requests/27
> * On the PlaMo side I finally merged the ModemManager port of Spacebar
> And started working on fixing all the things
> Something that came out of that is
> https://invent.kde.org/frameworks/modemmanager-qt/-/merge_requests/7
>
> Carl
> * Fix pushDialogLayers
> https://invent.kde.org/frameworks/kirigami/-/merge_requests/405
> (merged) and ported Kalendar's OverlaySheets, Koko's share dialog and
> Neochat settings to it
> * Ported Qrca and the health certificate part of Itinerary to
> Kirigami.NavigationTabBar:
> https://invent.kde.org/plasma-mobile/qrca/-/merge_requests/45 (merged)
> and https://invent.kde.org/pim/itinerary/-/merge_requests/53 (merged)
> * Fix some issues with the new Sonnet QtQuick feature:
> https://invent.kde.org/frameworks/sonnet/-/merge_requests/33 (merged)
> * Kirigami doc improvements:
> https://invent.kde.org/frameworks/kirigami/-/merge_requests/406
> (merged), https://invent.kde.org/frameworks/kirigami/-/merge_requests/407
> * KCM doc improvements:
> https://invent.kde.org/documentation/develop-kde-org/-/merge_requests/151
> (merged)
>
> Arjen
> * I've been doing some work on touch support for plasma
> * I did a few MRs to set Qt.ImhNoPredictiveText on text fields that
> are used as search fields, without it the virtual keyboard will only
> cause the textEdited/textChanged signals to be fired on enter, which
> means things like krunner don't work properly with virtual keyboard
> * I wrote a kirigami MR to detect whether an input method/virtual
> keyboard is active
> https://invent.kde.org/frameworks/kirigami/-/merge_requests/398
> * but it's a bit stuck as the kwin api basically is insufficient
> * that said, the only property Qt.inputMethod has that is the same is
> the "visible" property
> * it doesn't have any information about whether an input method is
> enabled or what kind of input method is being used
> * the end goal of this was to prevent system settings from focusing
> the search field on startup when started with touch and a virtual
> keyboard is active
> * and be able to do the same in other places
> * last thing I'm working on is porting the plasma widget explorer away
> from DragArea so that it becomes easier to change the behaviour
> between mouse and touch
> * I have a draft mr
> https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/630
> * it works great with mouse
> * but touch only works sporadically
> * so far we figured out that drags are started properly, but then kwin
> doesn't seem to properly update the drags on touch motion
> [d_ed i can believe it's an untested area]
>
> Kai Uwe
> * not much from my side
> * just that p-b-i got kicked out of Mozilla store last Monday
> * fvogt did a fix and d_ed will upload it … thanks for that!
>
> Marco
> i started to port some of the code of the plasma6 prototype wrt applet
> loading i did to plasma5, as at akademy we talked about the
> possibility to have the api we liked more in plasma5alsready, so some
> plamoid could be ported in any moment..
>
>
> --
> Marco Martin
More information about the Plasma-devel
mailing list