Re: bug 385814
On 02/27/20 14:24, Stefan Champailler wrote: import org.kde.plasma.private.kicker 0.1 as Kicker Kicker is in plasma-workspace, see https://cgit.kde.org/plasma-workspace.git/tree/applets/kicker
bug 385814
Hello, I may have some time to look at this bug : https://bugs.kde.org/show_bug.cgi?id=385814 I've already tried to understan the code but without success... I've followed this : https://userbase.kde.org/Plasma/Kicker to that : https://cgit.kde.org/plasma-desktop.git/tree/applets/kicker but then, I can't figure out how a change in the favorite menu ends... I've seen this import : import org.kde.plasma.private.kicker 0.1 as Kicker in some QtQuick scripts but I can't figure out where it comes from... Any pointer ? Thkx ! stF
Re: Does KDE need a metronome?
There's also Kronometer... One could add a metronome mode to it ? stF On Tue, 11 Feb 2020 22:07:02 +0100 Tomasz Bojczuk wrote: > Hi all, > > Maybe it's something that could also make sense for Plasma Mobile, not > > just Android. > > > My only concern is will be the app work only inside Plasma Mobile or it > will be still available standalone? > > > > > Is it using Kirigami right now? > > > At first I was curious to use Kirigami but I stopped myself to use it > because it seemed to me like a canon against a fly... > In the app there are just a few standard GUI controls: drawer, a few > actions on it plus check boxes on settings dialog. > The most is custom painting. But just now, using only QML/Qt it is > probably the biggest package among all metronomes in the store. > The same situation is with Breeze icons that Kirigami comes with. Maybe two > or three can be used, the rest > But correct me if I'm too much concern about it. In other hand, due to > small controls amount it is easy to deploy Kirigami and not icons at all > yet. > Still it doesn't matter for desktop. > > Another tool-ish question emerges here. Do I need to use ECM for build? > As long as I personally prefer cmake over qmake, qmake/Qt5.14 support new > aab package type and works flawlessly with deploying/debugging to virtual > device. > So it is qmake for now. > > Anyhow, I'm open for suggestion. > > Kind regards, > Tomasz
Re: KDiff3 on macosx
Just the link in case: https://binary-factory.kde.org/job/KDiff3_Nightly_macos/ 00:44:13 error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: for: /Users/packaging/Craft/BinaryFactory/macos-64-clang/build/extragear/kdiff3/image-RelWithDebInfo-master/Users/packaging/Craft/BinaryFactory/macos-64-clang/plugins/kf5/parts/kdiff3part.so (for architecture x86_64) option "-add_rpath /Users/packaging/Craft/BinaryFactory/macos-64-clang/lib" would duplicate path, file already has LC_RPATH for: /Users/packaging/Craft/BinaryFactory/macos-64-clang/lib ... Le jeu. 27 févr. 2020 à 10:33, Michael Reeves a écrit : > > > Can someone with a working osx craft setup please look at why KDiff3 is > failing on build factory?
KDiff3 on macosx
Can someone with a working osx craft setup please look at why KDiff3 is failing on build factory?
gsoc ktoblzcheck
hello. I is a student of PetrSU (Petrozavodsk, Russia). I interested this idea. https://community.kde.org/GSoC/2020/Ideas#Project:_Provide_the_bank_data_needed_for_financial_applications_in_SQLite_format how to participate it?
