Do we still need hardware for the booth, other than the rpi? I can bring some but it would be good some hindsight.
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
Jan 31 2024
Jan 29 2024
Nov 7 2023
I created this matrix room to coordinate this with the people I know they're coming, please join if you want to come. https://matrix.to/#/#kde-qtws-2023:kde.org
Feb 22 2023
Feb 7 2023
Separate repositories make sense, yes. I don't really see how it fits in KNewStuff. From a feature offering perspective, it seems to me it's a bit weird how it kind of overlaps with Purpose but not entirely. I don't know what to make of it though.
Jan 10 2023
Sep 12 2022
No. I meant the camera, microphone and gps.
Sep 11 2022
First make sure to start working on one of the 3 listed. I guess it depends on which you prefer we can start looking into.
Jul 11 2022
It was originally developed for bigscreen but it doesn't really have much bigscreen specific. I recommend you give it a try.
Have you seen this? https://invent.kde.org/plasma-bigscreen/plasma-remotecontrollers/
Jun 20 2022
If an issue you reported isn't a problem anymore, it's usually helpful to mark it as resolved so that we don't need to triage it later on.
Mar 5 2022
plasmoid/contents/ui/PasteMenuItem.qml:8:import org.kde.plasma.components 2.0 as PlasmaComponents for MenuItem
plasmoid/contents/ui/ShareDialog.qml:10:import org.kde.plasma.components 2.0 as PlasmaComponents for Highlight and ListItem
TODO
package/contents/ui/IconItem.qml:9:import org.kde.plasma.components 2.0 as PlasmaComponents // for ContextMenu+MenuItem
TODO:
package/contents/ui/main.qml:12:import org.kde.plasma.components 2.0 as PlasmaComponents // for Menu+MenuItem
Still todo:
contents/ui/BarcodePage.qml:10:import org.kde.plasma.components 2.0 as PlasmaComponents For ContextMenu
contents/ui/ClipboardItemDelegate.qml:13:import org.kde.plasma.components 2.0 as PlasmaComponents2
contents/ui/Menu.qml:11:import org.kde.plasma.components 2.0 as PlasmaComponents For Highlight
Oct 29 2021
Sorry, I wasn't clear enough. I meant we can move the KFileItemActions integration. Or maybe even into plasma-integration and this way it rolls with Plasma, although changing release cycles has some problems.
An idea would be to move this into the frameworkintegration repository.
Oct 25 2021
+1 please ping me, I'll be around.
Oct 5 2021
Sure, if it's the 14th note we already have the fireside chat at some point of the day.
Sep 21 2021
It could make sense to provide façade interfaces to do the common things the different plugin types allow.
Sep 13 2021
It's supposed to be something similar to Android's intents.
Aug 27 2021
In D18758#678706, @arrowd wrote:So, do we want to get this in?
Short recap:
- Project::open() executes KIO jobs synchronously at the moment.
- To make the code asynchronous we need some 3rd-party library implementing futures, like QtPromise.
- The original bug that made me work on this is fixed already.
Should we abandon this?
Aug 4 2021
My comment was mostly aimed at the plasmashell profiling (i.e. plasmoids) we did for the pinebook. KCM delays should be less stressful to performance because we don't trigger it as the system is starting up.
Jul 28 2021
In T14752#261083, @paulb wrote:@apol, can you confirm these are KDE patrons?
Canonical, Google, SUSE, The Qt Company, Blue Systems, Haute Couture Enioka, Slimbook and PINE64
Jul 26 2021
https://develop.kde.org/hig/ < let's not reinvent the wheel. Whatever is there can be addressed if it doesn't fit. If an application doesn't fit the HIG it can definitely be addressed.
May 29 2021
Would it maybe make sense to style it into Plasma rather than like an application?
Apr 25 2021
Adjust the voting structure:
Apr 20 2021
I agree with the overall goal, some details follow.
Nov 10 2020
Like we said to the last few, feel free to work on it. I haven't seen much activity happen around the topic. Maybe you would like to explain how you'd like to start working on it?
Oct 19 2020
In T8187#243082, @elvisangelaccio wrote:Just my 2 cents: we have telemetry now, so we can actually check whether people prefer single or double click.
Sep 13 2020
@cubix tell us if you don't know where to start from or if you have any questions. :)
Makes sense to me too, but I've seen many projects that have taken ownership of the flatpak recipe to let it degrade over time. We need ways to make sure it doesn't happen.
Aug 26 2020
IIRC the patch was stopped with the concern that it would bring a QtQml dependency that isn't always necessary. I'd say it should be fine though.
Aug 2 2020
We have moved to gitlab, now patches should be uploaded here: https://invent.kde.org/frameworks/networkmanager-qt
Jul 26 2020
Rebased to master into https://invent.kde.org/plasma/kwin/-/merge_requests/145.
Jul 23 2020
I'd love to merge it.
Should be working on Wayland as of Plasma 5.18 with improvements in 5.19.
Jul 11 2020
Jun 26 2020
Moved to invent for kwayland-server
Jun 15 2020
Did you like the format? Anything we can improve upon?
Jun 10 2020
Jun 8 2020
Jun 6 2020
Jun 3 2020
Jun 2 2020
Jun 1 2020
May 31 2020
May 25 2020
The biggest problem with sharing the dmabuf buffers it that its memory management becomes quite complex (and I'm unsure it's really doable).
PipeWire has mechanisms to create the buffers it's going to need, juggling this with passing the buffer from the app/output and making sure it stays relevant feels messy and error-prone.
Copying from dmabuf->dmabuf shouldn't be very expensive though, as it shouldn't go through the buses (AFAIK, that is).
May 23 2020
May 22 2020
hmmm. Ping @mart. :) what do you suggest we do?
I don't feel like the world needs this.
Should I understand this is not desired and that I should abandon it?
Ping?