I Use This!
Very High Activity


Analyzed 12 days ago. based on code collected 2 months ago.
Posted over 1 year ago by Kate
Ever since I started contributing to Kate there has been one feature request that was being requested in almost every blog post or discussion about kate: multiple cursor support. I am happy to say that after 3 or 4 days of really pushing myself to ... [More] implement this and address all the issues we just merged it (KDE Frameworks 5.92)! It will be available not only for Kate users, but for KDevelop, KWrite and any application that uses KTextEditor as its editor component. Short tutorial on using multiple cursors To create them via mouse, use Alt + Click To create via keyboard, Ctrl + Alt + Down / Up To create cursors out of a selection, first select some text and then press Alt + Shift + I What features are supported? Right now we probably miss a lot of things and we need the community’s help and ideas to make this feature awesome! But here’s what’s supported Basic text insertion and removal Auto completion Text transforms (upper/lower case, commenting, removing lines etc.) Movements (word, line, single character movement) multi select copy/cut Did I miss some feature that you were really hoping for? Let us know, that’s the only way it will get added. We really need the community’s help in test and stabilizing this feature as we want things to be stable before the release which is in about 25 days. So, if you feel like giving a hand feel free to come by the repo and say hi! [Less]
Posted over 1 year ago by KDE Dot News
Say Hello To KDE Eco by Joseph P. De Veaugh-Geiss Creative Commons Attribution-ShareAlike 4.0 International Public License Software is immaterial, but it determines the energy consumption of hardware. The ICT sector is reported to ... [More] contribute as much CO2 as the aviation industry, and the numbers continue to rise. Making software efficient is crucial. Let's build energy-efficient Free Software together! Dot Categories:  General [Less]
Posted over 1 year ago by Mellow Clamour | flyingcakes - planet-kde
Hello! This is my fourth status update for Season of KDE 2022. In my last post I told how packaging was almost done and I was looking out to automate updates. Finalizing the checker data There are multiple backends that can be used with Flatpak ... [More] External Data Checker. I initially planned to use the HTML checker, for it seemed logical at that time. But by the time I finalized it, I was already gravitating towards Anitya Release Monitoring. Since Anitya already has version tracking for most packages, it seemed a bit easier than the HTML checker. With Anitya, all I need to know is the project id, which is just a simple search on their website. The packages that don't exist on Anitya are quite easy to submit. A Fedora account is all it takes. (you can use any Open ID). For example, I added Falkon on Anitya. Roadblocks There are certain corner cases where FEDC didn't work as expected. GPGME is the first example. The download server for GPGME is incorrectly setting Content-Encoding as text/*, which FEDC discards, as it could be an error page. The right way out will be to get GPGME developers in the loop and inform them of this issue. Another package, SQLite, uses the current year in its URL, making it difficult to predict via a script. Experimenting with GitHub Actions I made a test repository to demonstrate the working of FEDC via a GitHub action. We were planning to get an access token added to KDE repos on Flathub GitHub organization so that we could utilize our GitHub Action. One of my submissions had erroneous checker data. It went unnoticed, until the Flathub bot made an unexpected pull request on a repo. That made us realise that we don't actually need to add an access token. Flathub runs the updater and makes pull requests automatically. Happy accident! So, all I am required to do is to add checker data to as many manifests as possible. The update for 21.12.3 was done manually, but the updates next month should be mostly automated! Links to all my pull requests are at end of this post. Next steps I plan to add checker data to all the remaining applications (~80) in the next 2-to 3 days. I'm also parallelly looking over to use FEDC on KDE Invent to automatically update non KDE dependencies on master manifest repo. Links to pull requests Adding checker data Akregator : https://github.com/flathub/org.kde.akregator/pull/5 Artikulate : https://github.com/flathub/org.kde.artikulate/pull/9 Blinken : https://github.com/flathub/org.kde.blinken/pull/22 Bomber : https://github.com/flathub/org.kde.bomber/pull/17 Bovo : https://github.com/flathub/org.kde.bovo/pull/18 Falkon : https://github.com/flathub/org.kde.falkon/pull/3 Granatier : https://github.com/flathub/org.kde.granatier/pull/16 Filelight : https://github.com/flathub/org.kde.filelight/pull/2 KColorChooser : https://github.com/flathub/org.kde.kcolorchooser/pull/3 Kalzium : https://github.com/flathub/org.kde.kalzium/pull/44 Kamoso : https://github.com/flathub/org.kde.kamoso/pull/5 Kanagram : https://github.com/flathub/org.kde.kanagram/pull/21 Kapman : https://github.com/flathub/org.kde.kapman/pull/42 KAtomic : https://github.com/flathub/org.kde.katomic/pull/41 KBlackbox : https://github.com/flathub/org.kde.kblackbox/pull/17 KBlocks : https://github.com/flathub/org.kde.kblocks/pull/42 KBounce : https://github.com/flathub/org.kde.kbounce/pull/43 KBreakout : https://github.com/flathub/org.kde.kbreakout/pull/2 KBruch : https://github.com/flathub/org.kde.kbruch/pull/40 KDF : https://github.com/flathub/org.kde.kdf/pull/2 Updates for 21.12.3 KGeoTag : https://github.com/flathub/org.kde.kgeotag/pull/1 Akregator : https://github.com/flathub/org.kde.akregator/pull/4 KRuler : https://github.com/flathub/org.kde.kruler/pull/2 KFind : https://github.com/flathub/org.kde.kfind/pull/2 KDevelop : https://github.com/flathub/org.kde.kdevelop/pull/16 KUIViewer : https://github.com/flathub/org.kde.kuiviewer/pull/1 KRDC : https://github.com/flathub/org.kde.krdc/pull/1 KColorChooser : https://github.com/flathub/org.kde.kcolorchooser/pull/2 KGet : https://github.com/flathub/org.kde.kget/pull/3 KDF : https://github.com/flathub/org.kde.kdf/pull/1 Koko : https://github.com/flathub/org.kde.koko/pull/3 GwenView : https://github.com/flathub/org.kde.gwenview/pull/24 Kdenline : https://github.com/flathub/org.kde.kdenlive/pull/168 Okular : https://github.com/flathub/org.kde.okular/pull/144 Itineary : https://github.com/flathub/org.kde.itinerary/pull/8 KTorrent : https://github.com/flathub/org.kde.ktorrent/pull/29 KTuberling : https://github.com/flathub/org.kde.ktuberling/pull/53 Konversation : https://github.com/flathub/org.kde.konversation/pull/22 Kontact : https://github.com/flathub/org.kde.kontact/pull/61 KCalc : https://github.com/flathub/org.kde.kcalc/pull/22 Ark : https://github.com/flathub/org.kde.ark/pull/38 Kontrast : https://github.com/flathub/org.kde.kontrast/pull/17 Kamoso : https://github.com/flathub/org.kde.kamoso/pull/4 Elisa : https://github.com/flathub/org.kde.elisa/pull/57 Dolphin : https://github.com/flathub/org.kde.dolphin/pull/72 Filelight : https://github.com/flathub/org.kde.filelight/pull/1 I will see you in next post with more updates! [Less]
Posted over 1 year ago by Kubuntu News
We are pleased to announce that Plasma 5.24.3 is now available in our backports PPA for Kubuntu 21.10 (Impish Indri). The release announcement detailing the new features and improvements in Plasma 5.24.3 can be found here. To upgrade: Add the ... [More] following repository to your software sources list: ppa:kubuntu-ppa/backports or if it is already added, the updates should become available via your preferred update method. The PPA can be added manually in the Konsole terminal with the command: sudo add-apt-repository ppa:kubuntu-ppa/backports and packages then updated with sudo apt full-upgrade IMPORTANT Please note that more bugfix releases are scheduled by KDE for Plasma 5.24, so while we feel these backports will be beneficial to enthusiastic adopters, users wanting to use a Plasma release with more rounds of stabilisation/bugfixes ‘baked in’ may find it advisable to stay with Plasma 5.22 as included in the original 21.10 (Impish Indri) release. The Kubuntu Backports PPA for 21.10 also currently contains newer versions of KDE Gear (formerly Applications) and other KDE software. The PPA will also continue to receive updated versions of KDE packages other than Plasma, for example KDE Frameworks. Issues with Plasma itself can be reported on the KDE bugtracker [1]. In the case of packaging or other issues, please provide feedback on our mailing list [2], IRC [3], and/or file a bug against our PPA packages [4]. 1. KDE bugtracker: https://bugs.kde.org2. Kubuntu-devel mailing list: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel3. Kubuntu IRC channels: #kubuntu & #kubuntu-devel on irc.libera.chat4. Kubuntu ppa bugs: https://bugs.launchpad.net/kubuntu-ppa [Less]
Posted over 1 year ago by KDE Community
Tuesday, 8 March 2022. Today KDE releases a bugfix update to KDE Plasma 5, versioned 5.24.3. Plasma 5.24 was released in February 2022 with many feature refinements and new modules to complete the desktop experience. This release adds two weeks' ... [More] worth of new translations and fixes from KDE's contributors. The bugfixes are typically small but important and include: Kcms/colors: fix spacing between radio buttons and content. Commit. SDDM theme: stop eliding people’s names so aggressively. Commit. Fixes bug #450673 Powerdevil: Improved backlight devices selection. Commit. Fixes bug #399646 View full changelog [Less]
Posted over 1 year ago by Albert Astals Cid
This is a continuation of https://tsdgeos.blogspot.com/2022/02/okular-signature-verification-user.htmlIn that blog what was introduced was the new user interface to be able to see digital signatures in the mobile interface (i.e. the one that uses ... [More] Kirigami instead of QWidgets).You can use the Okular mobile interface anywhere you want, it's not really mobile-only, it's really mobile-optimized, so you can try it (though you'll have to build it manually since most distributions don't build it by default) on desktop Linux too.Anyway, in that previous blog I talked about introducing the new user interface to be able to see digital signatures, and that worked out of the box in places that provide NSS like desktop Linux or Plasma Phone distributions (Aleix tried on the PinePhone and confirmed it works), but for Android it still did not work.What was needed was something very similar to what we did for Windows https://tsdgeos.blogspot.com/2022/02/okular-signature-support-now-works-on.html but this time for Android.I added a way for Craft to build NSS for Android and told it to not disable NSS when building poppler for Android that should have been all.But things are never simple enough...For Android we use a tool called androiddeployqt, it is a tool that gathers everything needed for your project and creates the APK file for it. Unfortunately it has a documented limitation with runtime plugins, it has no way to know they are needed so they are not packaged. NSS unfortunately has plugins, so after some "why is this crashing?" hours of scratching my head and debugging i realized the problem was the missing plugins were not being "installed".The workaround to make androiddeployqt work for plugins is basically linking the plugins to your binary, this way the plugin is a clear dependency and gets packaged, but did I say things are never simple enough?In KDE we have binary-factory continuous integration for Android and we also have gitlab continuous integration for Android, unfortunately they use different ways of building, the first uses Craft, the second does not. This means that in gitlab CI the NSS library is not available, so I can't link to it, but i need to link to it so that Craft on the binary-factory CI creates the APK files correctly.To try to resolve that I came up with a patch that tried to differentiate if we were building inside Craft or the gitlab CI unfortunately while that worked on my local setup it did not work on the KDE servers, so at the end I resolved for a much more pedestrian way, there's an option to enable the extra libraries and Craft enables that option when building OkularSo after that, yes, it works as you can see in the screenshot below :) Signature Properties User Interface If you want you can download the Okular APK from https://binary-factory.kde.org/job/Okular_Nightly_android-arm64/ but beware there are still some limitations that don't make Okular usable day-to-day for Android, so we've created a Google Summer of Code potential project for that, maybe you're interested? [Less]
Posted over 1 year ago by Kdenlive
The last maintenance release of the 21.12 cycle is out with lots of usability polishing of keyframes, subtitles and proxy clips. Audio thumbnails on high zoom levels got a major performance optimization. This version also fixes 5 crashes ... [More] including Wayland layout switching, time remapping module among others. With this release we switched our AppImage building to KDE Craft that is already in use for our Windows and macOS builds. With this step our packages become more consistent in regard of bundled dependency versions across all platforms. Also the maintenance becomes less time consuming giving developers more time to focus on coding rather than packaging. We encourage users to reset their configurations to avoid any possible issues by going to menu Help -> Reset Configuration. If you encounter any issues please report them and don’t forget to checkout the trouble shooting tips.   Full log Fix tests and resize issue. Commit. [Effect Keyframes] Fix “apply current value” uses wrong position. Commit. [Effect Keyframes] Fix “copy current value to selected” crash. Commit. [Effect Keyframes] Fix wrong keyframes shown as selected. Commit. Fix tags corrupting audio/video icons in bin. Commit. Fix audio thumb speed not correctly initialized (broke monitor thumbs). Commit. Fix audio thumbs for clips with speed effect. Commit. Fix crash cutting a grouped subtitle. Commit. Fix 1 pixel offset at some zoom factors. Commit. Correctly update add/remove keyframe button on undo/redo and active keyframe on speed change. Commit. Fix possible crash in extract zone. Commit. Fix thumbnails for playlist clips having a different resolution than project profile. Commit. Fix crash updating speed before/after in time remap. Commit. Fix proxy clips not correctly disabled on rendering. Commit. Fix sometimes cannot resize clip when there is a 1 frame gap. Commit. Various fixes for remove space in subtitle track. Commit. Fix same track transitions sometimes broken by clip resize. Commit. Fix 1 frame offset in subtitles when removing space. Commit. Show clip labels as soon as there is one letter width. Commit. Fix marker thumbnail size. Commit. Don’t show clip thumbs on when clip is too small (<16 pixels). Commit. Missing change from last commit (fix remove space). Commit. Fix “remove space” not working on 1 frame space. Commit. Only create proxy clips automatically if requested. Commit. Fix audio wave for non stereo clips. Commit. Fix qml binding loop warning. Commit. Fix clip thumbnails extending past clip length. Commit. Fix adjust to original size using proxy resolution. Commit. Try to fix ghost icons on Windows. Commit. Major speedup in audio thumbs drawing on high zoom levels. Commit. Fix clip name not scrolling anymore. Commit. Fix unusable bin icon for audio/video drag. Commit. Fix Wayland crash on layout switch. Commit. Minor optimization for audio thumbs drawing. Commit. Fix .ass subtitle files not correctly read. Commit. Ensure processes are in the path before starting an executable. Commit. Fix timeline keyframes sometimes disappearing from view. Commit. Fix wrong comparison of current settings and settings stored in the project settings dialog. Commit. Fix again VPx quality: use constrained quality (bitrate>0). Commit. [Spot Remover effect] Add xml ui to fix initalization (and other minor. Commit. [Extract Frame] Fix wrong frame exported when using source resolution. Commit. The post Kdenlive 21.12.3 released appeared first on Kdenlive. [Less]
Posted over 1 year ago by Albert Astals Cid
KDE produces amazing software, but sometimes not everyone can use it.One of the reasons that can happen is because it's not translated to a language they understand.For that we are calling for translators, specially for the languages listed below ... [More] which had not had a single translation update in the last year [*].Committing to help means that you will do some work every now and then, not just translate a few texts only.We will help you learn the tools needed and hopefully if you know more people that can help you can grow a team :)If you're interested please email me at aacid@kde.orgAfrikaansArmenianAssameseBengaliBosnianBretonChhattisgarhiCrimean TatarCroatianEsperantoFarsiFrisianGalicianGeorgianGujaratiHausaHebrewIrish GaelicKabyleKannadaKashubianKazakhKhmerKinyarwandaKurdishLow SaxonLuxembourgishMacedonianMaithiliMalayMalteseMarathiNepaliNorthern SothoOccitanOriyaPashtoScottish GaelicSinhalaTatarTeluguThaiTswanaUyghurUzbekWalloonWelshXhosa[*] apologies if indeed there were translations and my script failed for some reason [Less]
Posted over 1 year ago by Stef's Blog
Hello, This is my first blogpost for KDE SoK 2022. What I’m working on. My work centres around alerts in KDE Connect iOS app. As it’s under development, a lot of information is communicated to the user using system alerts. iOS is limited to ... [More] displaying only one alert at a time and doesn’t have any native system for queuing them. Sample Alert: Progress During last month I learned a lot about swift. Getting familiar with the code took me a while. I started by implementing a basic alert queue. After consulting it with my Mentors, I got the data types right. struct AlertContent{ let title: LocalizedStringKey let content: Text? let buttons: () -> AlertActionBuilder.Buttons } Buttons also got me stuck as they are created using a custom iOS 14 compatibility view. But eventually, I wrapped my head around this too. Before my changes, every message was a separate alert. Now there is a single alert with content that changes dynamically. .alert(alertManager.currentAlert.title,isPresented: alertsBind, actions: alertManager.currentAlert.buttons){ alertManager.currentAlert.content } It uses a custom binding alertsBind that detects when the alert is dismissed and, if available, pushes the next alert in. Overall I spent some time figuring out some of swift’s quirks. It differs from languages that I’m more familiar with, like Python / JS / C++. The result can be seen here - queued alerts being shown one after another. Next steps Switch alerts in app to use this new system. Clean up the code You can see my current progress in the merge request I created. [Less]
Posted over 1 year ago by Srirupa's Blog
Overview This is my third blogpost for SoK 2022. If you have been following my earlier blogposts, you would know that I’ve been working on adding the Perspective Ellipse Assistant Tool in Krita. My Progress so far Created a Merge Request Here’s the ... [More] link to my Merge Request, you can check if you want to! Creating the Insrcibed Ellipse Two weeks back this is what my tool looked like. Then I spent almost a week scratching my head over the mathematics required to transform a circle inscribed inside a unit square to an ellipse inscribed inside my quadrilateral. Dmitry suggested a nice tutorial on projection matrices and geomtery. Going through a few lessons made all the mathematical code less intimidating. Since I already had a four cornered assistant, all I needed to do was to add it’s inscribed ellipse. This is roughly what’s done: The transformation matrix is set for the canvas. A unit square is added to path, which on being drawn on the canvas gets converted to the transformed quadrilateral. The inscribed circle for the unit square, as expected, gets converted to the inscribed ellipse for our quadrilateral. A bit of code… Here’s a little bit of code demonstrating the above procedure. Anyone not familiar with Krita’s codebase can skip directly to the animation! First, inside the PerspectiveEllipseAssistant::drawAssistant(), the transformation matrix of the canvas is set using: gc.setTransform(converter->documentToWidgetTransform()); Now, the following code draws a valid four cornered assistant. QPainterPath path; for (int y = 0; y <= 1; ++y) { QLineF line = QLineF(QPointF(0.0, y), QPointF(1.0, y)); KisAlgebra2D::cropLineToRect(line, gc.window(), false, false); path.moveTo(line.p1()); path.lineTo(line.p2()); } for (int x = 0; x <= 1; ++x) { QLineF line = QLineF(QPointF(x, 0.0), QPointF(x, 1.0)); KisAlgebra2D::cropLineToRect(line, gc.window(), false, false); path.moveTo(line.p1()); path.lineTo(line.p2()); } And finally, once I draw the circle inside the unit square, I have my Perspective Ellipse! All I had to do was to add this piece of code: path.addEllipse(QPointF(0.5, 0.5), 0.5, 0.5); And here’s a small animation demonstrating the current Perspective Ellipse Assistant Tool! Next Steps I would spend the next few weeks working on drawing and snapping related code. That should hopefully complete my assistant! [Less]