While dialer doesn't work on the Nexus 5X due to the ofono version being used is not compatible with rild implementation, dialer now works reasonably well on Plasma Mobile on pinephone and Librem 5. Closing this.

This looks like the upstream qtvirtualkeyboard bug, and nothing to do with "Shell functions".

This now works as expected, still not perfect, but works

@nicolasfella I am unsetting PM 1.0 milestone from this, and adding this to general Plasma Mobile board.

Let's mark this task as resolved, we already have a Discover app store, if any further improvements are needed they can be separate tasks.

I started Kalk, a Kirigami-based calculator app, by forking Liri Calculator.

While we can try to flatpak Dekko 2, we should also disscuss with the kube upstream maintainers whether porting back to Kirigami is an option for them now.
We are already utilizing their sink backend for nextcloud synchronization.

@jbbgameich said that Dekko 2 (https://gitlab.com/dekkan/dekko and https://open-store.io/app/dekko2.dekkoproject) could be reused

Probably we can't, because the power button is not a key modifier.

Maybe we could use the well-known key shortcuts from other mobile operating systems like Android:

• double press power button: Start camera
• power button and volume down: Take sceenshot

Gestures could also (optionally) be used for replacing the navigation bar at the bottom to save space.

Basics are done, but there's a KWin bug (at least on the pinephone) that only saves a quarter of the screen - probably some dpi issue

Initial implementation: https://invent.kde.org/jbbgameich/voicememo

You can test it on the desktop

Hey @dkardarakos, can I build and run the source code on my system (KDE neon) first and then test the changes I make later in the emulated environment?
Or do I have to do everything in the emulated environment only?
Thanks,

Welcome @sassycode ! I would start by looking into the code of kirigamiclock in invent, which I think is still a personal project of @nickre, find some area that needs improvement or a missing feature, forking the repository and submitting a merge request.

Hello, I am Sashmita Raghav, from India. I am very much interested in contributing to this application.
I have some experience working with Qt, C++ and QML. I would be greatful if someone could tell me where I could start 😄

Hi,
I am Sushma unnibhavi. I am a third year undergrad student studying
Information Science at Nitte Meenakshi Institute Of Technology. I am
interested in participating in the Season of KDE 2020. I am interested
in working on Plasma phonebook. Can anybody tell me how to
proceed with the application process?

For the alarm clock, we may adopt an approach like calindac of Calindori.

The KDE PIM team has expressed interest in co-locating a sprint to talk about mobile PIM topics

Application store, discover allows installing, updating and uninstalling applications from the store, supposedly in flatpak format, or as native packages

As for the application, Discover works well on mobile.

We agreed that https://cgit.kde.org/spacebar.git is our way forward.

https://invent.kde.org/kde/plasma-phonebook has basic functionality working, moving to 'Done'

Since basic functionality is working I'm moving this to 'Done'

Taking screenshots with a key combo is also important, e.g. vol down & power for a few seconds like it's done in Android

@nicolasfella I added license headers and uploaded it to Invent.

For now you can find screenshots on https://www.plasma-mobile.org/screenshots/. I'll look into adding them to the appstream metadata and README.

@nickre This is really nice work! I'd like to move this forward and bring it to a KDE repository. However, I see that your files don't have any license information/headers. Would you please clarify this by adding license headers according to https://community.kde.org/Policies/Licensing_Policy so we don't "steal" your work?

Another update:

Works quite nicely already. I still have some changes to the design in mind, so I will propose my changes in a merge request some time soon.

OK, I just finished fully working basic calculator. Scientific calculator and Programmer calculator don't work yet. Unfortunately, my code is very unreadable because I'm not experienced in team programming ... I also don't know what to write in the about section. The help button redirects to the KDE FAQ page.

@jbbgameich just a friendly request for us lurkers that like to keep an eye on Plasma Mobile development: would it be possible to add screenshots to the applications you host on invent so we can take a peak into how they look? =D thanks, and keep up the awesome work!

Great work! @jbbgameich

Work in progress: https://invent.kde.org/jbbgameich/plasma-phonebook

Nowadays angelfish is mostly usable as a daily driver web browser. The task could probably be marked as done.

Implemented in https://invent.kde.org/jbbgameich/qrca

As an explanation: Strictly speaking the dialer wasn't written as an application but part of the Plasma Mobile shell. Only shell parts should use PlasmaCore stuff nowadays, Kirigami should work for everything else.

I saw that the dialer application gets colors from PlasmaCore ... I won't be able to build a calculator application next week, so I won't fix it right away.

PlasmaCore is not the correct way to get colors. As said, please use Kirigami.Theme. values.

Any colors the user may wish to use. You have to use colors provided by the theme and not hardcode them.

What exactly colors does plasma mobile use? ( rgb )

Nice that you are working on it.
I noticed two things:

• Text is not readable due to the background Rectangles on the buttons. I'd suggest to use ToolButtons so you don't have to make them flat on your own.
• The design is currently very colorful, which won't look to good with all system color themes (breeze dark / breeze lite etc.) Instead you could use Kirigami.Theme.* colors which adapt to it.

I have created an application GUI for now. Could anyone check it on a mobile device?

https://docs.plasma-mobile.org/AppDevelopment.html should provide a good general starting point for app development. Any Qt / c++ libraries should be fine for the backend, the ui should use QtQuick Controls 2 and Kirigami.
Maybe https://github.com/AsteroidOS/asteroid-calculator could be ported to Kirigami and rebased on the Plasma Mobile app template.

If I'm interested in, what exactly should I do? What libraries can I use? Are there any additional guidelines on the code?

Short update:
you need to install two additional packages ofono-qt and telepathy-ofono and then starting calls works

This turned out to be a missing dependency problem and should/does work for some while now. Basically we added an explicit dependency from kwin-wayland-backend-hwcomposer to the precise build version number of kwin

In T6942#177703, @IlyaBizyaev wrote:

Great! :)
If you need visual feedback:

1. Card names and date in the details view are misaligned

In T6942#177731, @nicolasfella wrote:

I see that you are using KCalCore::Todo for storing tasks. For the usual calendar KCalCore::Event would be more suitable IMHO. Should we change that or would you rather support both types (TODOs and Events)?

I see that you are using KCalCore::Todo for storing tasks. For the usual calendar KCalCore::Event would be more suitable IMHO. Should we change that or would you rather support both types (TODOs and Events)?

Great! :)
If you need visual feedback:

1. Card names and date in the details view are misaligned
2. The time picker looks a bit overwhelming, and I'm not sure how it would work with 24h format.

Android, for instance, does it this way:

Screenshots added, feedback welcome.

mb would be useful for this app
https://github.com/nu-book/zxing-cpp - C++ zxing rewrite with modern c++
https://github.com/swex/QZXingNu - mine QZXing-like wrapper around zxing-cpp

Neon doesn't actually have a kwin-wayland-backend-hwcomposer package, so renaming is not a solution. apt-pinning seems to be the right approach.

The current state of angelfish can be found here (https://invent.kde.org/jbbgameich/plasma-angelfish). It should be merged back into the main repository and migrated to invent.kde.org.
Still missing features:

• search engine configuration
• Tab closing (WIP)

Thank you for the pointers. I'll go through the documents and get back to
you if I have any questions.

Hello @smishipills,
This application has not been written yet, but you are welcome to start writing it. I'd suggest you do some research on projects with which we can share code.
Then you can use our app development guide (https://docs.plasma-mobile.org/AppDevelopment.html)

Hey all! I am new to Open source and I have tried submitting fixing some bugs in KCalc desktop. I would like to know more about this application. I too worked on a calculator using Qml/ Qt(https://github.com/smritipillai/CalculatorUsingQml) so I would like to know the status of this app so that I too can contribute to it in some way possible and work on it as a part of SoK program.

Welcome Marko!

Should basic phone functionality (dialer, SMS, contact book) be maintained in the plasma-phone-components repository or should the dialer be split into its own repository?

Thank you for working on this! You can use our app development documentation and app template as a starting point. The existing dialer application will probably be helpful as well.

I can start working on this task. I have experience in QT and C++ and CMake as I using it for some of mine and some floss projects. Not that much experience in QML but I'm learning it for one more floss project too.
Do we have some basic source code for this up which should be improved or it need to be developed from scratch? I will study API's and QML now and please answer with should I start developing this and if some more resources are needed please refer me to proper addresses.
Thanks
Marko Pavlovic

Would it be possible to build something directly on libqofono? It seems to have a QML api.

If you want, you can go to the KDE VDG Channel and request some design help as you go along. The app is shaping up nicely.

Project's code is now available at Calindori repository.

ok

I tried using the QZXing live demo app on the latest edge image (2018-11-12) and currently Qml Video Filters are broken: https://git.merproject.org/mer-core/nemo-qtmultimedia-plugins/merge_requests/2

Thanks for your feedback and for taking the time to draw your ideas!

Looks really nice already!
I'm not a designer, but I'd suggest making the calender fill the whole page.

Calendar tasks functionality added. VDG feedback is welcome.

An idea that came around was to add barcode scanning to Purpose so that applications that use barcode scanning don't need to implement it themselves. This way one could have multiple "sources" of barcodes such as the local camera or the camera of a device connected via KDE Connect.

*should* be fixed in master