All tasks are resolved here

Kalk has made into Plasma-Mobile namespace.

Ideally, in Plasma environment use PowerDevil's schedule wake up system would be better. However, this can act as a fall back method in case running in non plasma DE.

I can modify the mockup I made on T12717#224840

relevant: https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/6

Is there anything left to do here?

Alarms could benefit from this sort of API, since on other platforms they typically show up in full screen to allow for easy snooze/dismiss

This could be turned into an API for all call-like apps, sort of like MPRIS but for calls.

Mockups for a mobile friendly KCM: https://invent.kde.org/plasma/bluedevil/-/issues/1

1. I don't mind having it directly in xdg-desktop-portal-kde, but if it's something that might be re-used, it might be better to put it into some framework.

2-3) Kirigami-addons will be probably my preference. It sounds like something that can be re-used so why not write it that way. Then in xdg-desktop-portal-kde we will just check if it's running on mobile and create a dialog based on that.

4. This might complicate it a bit, because you either would need to implement all the other portals which are same for both the desktop and mobile, or you would need to set different value to XDG_CURRENT_DESKTOP so xdg-desktop-portal first loads your portal implementation for some portals and then xdg-desktop-portal-kde as fallback for the rest.

@jgrulich, since you are working on xdg-desktop-portal-kde, do you have an opionion on where the mobile file picker ui should go?
Options are basically:

• everything into xdg-desktop-portal-kde
• KIO (would still need special handling in the portal)
• put actual gui code in Kirigami-addons and call it from the portal
• create a new portal for mobile

Designs: https://phabricator.kde.org/T12717#224147

No, the portal uses the KFileWidget directly. After posting this I also had the idea of implementing this in KIO directly.

@davidedmundson @jbbgameich alternate idea is to simply put the QML file dialog in the plasma-integration, AFAIU, portal ultimately ends up using the dialog in plasma-integration?

@davidedmundson I'm mentioning you here because I think you had the idea to base the PlaMo file dialog on xdg-desktop-portal. I have been working on this approach for some time. Now I wonder where to best put the code. I began by forking xdg-desktop-portal-kde, but it would be probably better to integrate it into the exisiting portal.

No. A lot of the stuff in plasma-nm is just a stub and not implemented

I suppose this is fixed with fix which landed in the plasma-nm?

yes, as of a minute ago. rotation-locked-portrait and rotation-locked-landscape

Now we do R266:48a112fb64dc

Do we have such icons somewhere?

Can the locked icon be set based on the orientation it was locked in? For example, a landscape icon when locked to landscape and a portrait icon when locked to portrait.

KDBus single instance API in every single application

I would like to do as much as possible via freedesktop sound theme spec/libcanberra. We are planning to do that for notifications anyway (T12536)

Keyboard configuration is tracked at : T12904 .

We need to think design/use-case research, and also ideally check what code we can share with the desktop power management.

Options to fix this:

• use libtaskmanager to give focus to the existing window belonging to the application
• KDBus single instance API in every single application

Other approach (using qpa): https://invent.kde.org/lnj/plasma-integration/-/tree/feature/mobile-kirigami-ui

https://phabricator.kde.org/D28509

We need to think design/use-case research, and also ideally check what code we can share with the desktop power management.

https://github.com/rilmodem/ofono/blob/master/test/get-network-time

Options to fix this:

• Add accept button to plasma-settings
• Add apply button to KCM
• always save kcms on desctruction (plasma-settings is closed, kcm is switched)

http://man7.org/linux/man-pages/man2/timerfd_create.2.html

Spacebear progress update: Thanks to the help of Anthony Fieroni, spacebear now generally works (receiving and sending), work to invoke the client when a message arrives is work in progress and not fully tested, but should work as well.

https://invent.kde.org/jbbgameich/spacebear

I was recently working on rewriting spacebar. A few things are already better tham with spacbar:

• sending messages works reliably
• no random crashes
• mapping of incomimg and outgoing conversations to contacts
• no more hacks to find the sim accoumt
• better design (imo)

Since we have basic functionality already in place, I am closing this meta-task. If there's any further improvements, we can create separate smaller tasks.