Relevant output,
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
Nov 10 2018
Nov 9 2018
Nov 3 2018
Oct 31 2018
@nicolasfella Thank you for pointing me to that mistake, seems like I added the translation of icons by accident :)
A few minor notes, tested on Nexus 5x (edge):
Yes, using the edge image.
Thank you very much for testing!
The resolution setting in the drawer actually works with my webcam, so maybe that's a hardware adaption problem.
With my webcam it looks like this, and switching the resolution also works:
I tested it on a Nexus 5x with the bionic PM. Looks great!
QZXing (https://github.com/ftylitak/qzxing) could be a helpful library as well.
I finished the initial port of the application to kirigami on my jbb/kirigami branch. The app should probably still be tested on a real device, but so far it worked fine with different webcams (also switching between multiple cameras works).
Oct 26 2018
Here you can find the wip calendar work. Currently, it consumes plasma-framework calendar models. If possible, we may try to change model dependencies and create some kirigami calendar ui components.
In T8899#146103, @abetts wrote:Can other possible apps be added to this list? I feel there can be a few others that are very useful to have by default:
- Notes
- Calendar
Oct 3 2018
Sep 20 2018
Your help would be appreciated.
I'd like to help with this. I have experience working with Qt 5. It's been a couple of years, but I'll manage to get back into it in no time. I currently have about one full work day per week that I could dedicate to it.
Aug 25 2018
Anyone who is interested in moving forward the KDE Connect approach can talk to me or @sredman about it
Aug 1 2018
Jul 12 2018
Jul 5 2018
Jul 1 2018
Proof of concept repository can be found here.
Jun 27 2018
@nickre awesome work, Just as sidenote, I learned that @alex-l from VDG and @tcanabrava form dev side is working on re-designed KTimer, See M130 for reference. Maybe you can join forces with them :-)
Jun 26 2018
@dkardarakos Here is my code: https://gitlab.com/nickre/kirigamiclock. Currently it is in a mockup state. Should I also submit a mockup to Pholio?
also check with @kossebau which is the current maintainer of the weather plasmoid
Jun 25 2018
I have made a mockup https://phabricator.kde.org/M129
Any feedback is appreciated.
Unfortunately, for new plasma mobile applications, no relative phabricator place exists for the review to take place. So, for the first reviews and before the new app code reaches KDE repository, we cannot avoid using an external code hosting provider (e.g. gitlab). It is an important issue that we will discuss at Akademy BoF. @nickre if this is not a problem for you, could you please put your code there and put the relative link here so as our devs to review it?
In T8904#148721, @nickre wrote:I would like to contribute to this application. I have already started working on it, but where should I submit the code for review?
It's best to use arcanist to upload patches to phabricator. https://community.kde.org/Infrastructure/Phabricator
I would like to contribute to this application. I have already started working on it, but where should I submit the code for review?
Jun 24 2018
I think for alarms cron could be used, so the clock itself doesn't need be a daemon. But is/will cron be included in the images?
Jun 21 2018
@dkardarakos You bet I am. I have been reading the HIG this whole time. I'll check out the other two resources.
Well, explaining how the weather applet and -in particular- how the data engine code works is more than valuable :)
Jun 20 2018
@dkardarakos Hi, "your" = "mine"? :) I sadly cannot give valuable feedback other than explaining how the current plasma weather applet & dataengine code works. I have no insight in the application model concepts with Plasma Mobile and where it thus is different from what we have with widgets in the Plasma Desktop shell.
Let me kindly request for your feedback on this issue. Since @BrokenMutant has expressed his intention to contribute to plasma mobile weather app, it would be nice if we devised an approach either based on the suggestion made above or consider alternatives so as to facilitate the creation of the app :)
Jun 11 2018
Jun 8 2018
This task belongs to a series of tasks we created after a discussion with @bshah trying to offer to Plasma Mobile users the features of the existing mobile platforms. Since mobile users expect such an application, we think that offering a standalone application we will fulfill user needs and make PlaMo ecosystem more complete.
Jun 7 2018
The most visible performance pitfall is in non-Qt XWayland apps, e.g. Chromium. They are mostly built with desktop OpenGL, so they fall back to software rendering. I also think some X components use software rendering where normally things are accelerated, but I haven't researched yet.
Quick first reply:
The Weather Report widget from kdeplasma-addons makes use of the Plasma weather dataengine from plasma-workspace (whose logic dates from early Plasma times, myself only responsible for porting 1:1 to Plasma5, never touched the concepts even if I have some ideas resp. see some needs for improvements ;) ).
Now this makes me curious on what API/service plasma widget uses? @kossebau can you shed some light on it?
Yep. I was going to use that. I had previously made a kinda weather app for Android, and used OpenWeather. It's neat.
Jun 6 2018
If you search for a weather provider, I would suggest you OpenWeatherMap. Their weather data is freely licensed under CC BY-SA 4.0, they have a clean and easy to use api and they allow 60 calls per minute in the free plan.
Thanks. I'll take a look at it and start working soon.
Here are the resources you may need:
Thanks. I will then work on the application. This will be my first time contributing to KDE. Are there some rules/steps I should know about?
Hello and welcome :)
What do I need to do if I want to contribute?
Jun 5 2018
That sounds like a good plan for the future, but currently, the functionality is split. Koversation provides IRC and Matrix capabilities, Kaidan is used for XMPP, Telegram is supported by the official app, and there is a basic app for telephony.
It seems to me that this area intersects with the PIM one. Are we sure we want applications organized this way? It may sound more difficult to implement but I think the most logical design would be the following:
Note KAlgebra already has a Kirigami front-end, maybe it would make sense to make it usable for the simple calculator use case.
Jun 4 2018
In T8899#146105, @IlyaBizyaev wrote:I think for photos, we already have a basic gallery. Vvave can be used as a music player.
For the rest, tasks seem to exist already: https://phabricator.kde.org/project/view/28/
I think for photos, we already have a basic gallery. Vvave can be used as a music player.
For the rest, tasks seem to exist already: https://phabricator.kde.org/project/view/28/
Can other possible apps be added to this list? I feel there can be a few others that are very useful to have by default:
Jun 2 2018
May 30 2018
An amazing addition would be to also help make use of additional device buttons (e.g. physical home and Bixby buttons on Samsung phones, virtual back-home-recent keys on ASUS, Alcatel and other devices).
A related project might be Prison, which is a KDE Framework for barcode generation.
May 29 2018
Detailed instructions to create a Plasma Mobile emulated environment with: