PSA: KDE CI: How-To for stable branch switches being picked up

2018-07-17 Thread Friedrich W. H. Kossebau
Hi KDE project maintainers, tl;dr https://community.kde.org/Infrastructure/Continuous_Integration_System now tells how to make sure KDE CI picks up your new "stable" branch Some days ago I found that a few products on KDE CI in the "Extragear" section had not seen builds of their stable branch

Re: auto QString(Builder) considered VERY HARMFUL -> use clazy, especially before releases

2018-09-27 Thread Friedrich W. H. Kossebau
Am Donnerstag, 27. September 2018, 20:08:54 CEST schrieb Andreas Hartmetz: > Today I fixed the third or so crash in KDE software due to the following > pattern: > > const auto str = someString + anotherString; > > What happens is that the type of str ends up being QStringBuilder > instead of QStr

Re: auto QString(Builder) considered VERY HARMFUL -> use clazy /w kdevelop

2018-09-27 Thread Friedrich W. H. Kossebau
Darn, forgot some obvious promo bits... see below: Am Donnerstag, 27. September 2018, 21:01:13 CEST schrieb Friedrich W. H. Kossebau: > Am Donnerstag, 27. September 2018, 20:08:54 CEST schrieb Andreas Hartmetz: > > Please take care. > > Care can be done e.g. by deploying cl

Re: auto QString(Builder) considered VERY HARMFUL -> use clazy, especially before releases

2018-09-28 Thread Friedrich W. H. Kossebau
Am Freitag, 28. September 2018, 01:03:01 CEST schrieb Albert Astals Cid: > El dijous, 27 de setembre de 2018, a les 21:01:13 CEST, Friedrich W. H. Kossebau va escriure: > > One would recommend to run clazy over your code at least before releases, > > to catch all kind of p

PSA: how to prepare apps for non-Plasma X-based shells and their app panels

2019-02-04 Thread Friedrich W. H. Kossebau
Hi, quick heads-up for anyone maintaining applications which also target non- Plasma shells (X-based, no issue with wayland-based systems): TL;DR Make sure to have "StartupWMClass=myapp" in the (main) application desktop file if both WM_CLASS properties of the application window do _not_ match

Re: Aw: Re: setWindowIcon for QDialog

2019-03-06 Thread Friedrich W. H. Kossebau
Hi, allow me to chime in with my AFAIK, which though is confirmed by my quick look at the code: Am Dienstag, 5. März 2019, 18:21:00 CET schrieb Martin Flöser: > Hi Alexander, > > according to the xprop output the _NET_WM_ICON property is not set. The > method inside Qt responsible for this is:

Re: CI system maintainability

2019-03-28 Thread Friedrich W. H. Kossebau
Am Donnerstag, 28. März 2019, 09:29:22 CET schrieb Kevin Ottens: > Hello, > > On Thursday, 28 March 2019 09:16:11 CET Ben Cooksley wrote: > > Please note that the commits in this instance were pushed without > > review, so restrictions on merge requests wouldn't make a difference > > in this case

Re: CI system maintainability

2019-03-28 Thread Friedrich W. H. Kossebau
Am Donnerstag, 28. März 2019, 11:27:44 CET schrieb Daniel Vrátil: > I'm completely fine with mandatory code review for everything and I'd be > happy to have this in PIM. I think the biggest problem in PIM to overcome > will be finding the reviewers - I dare say I'm currently the only one who > has

Re: CI system maintainability

2019-03-28 Thread Friedrich W. H. Kossebau
Hi Laurent, Am Donnerstag, 28. März 2019, 14:33:59 CET schrieb laurent Montel: > For example I works all days on kde (pim or other) when I wake up, or at > noon after my lunch or the evening, I will not wait several days for a > review because nobody has time to do it. > > (For example I make ~ 1

Re: CI system maintainability

2019-03-28 Thread Friedrich W. H. Kossebau
Am Donnerstag, 28. März 2019, 16:04:01 CET schrieb Boudhayan Gupta: > I don't care if you lose time. I don't want the guys building my house to > cut corners mixing my concrete because it's going to save time. There is a difference here though, no? The people building your house will not live in

Re: CI system maintainability

2019-03-28 Thread Friedrich W. H. Kossebau
Thanks for reply. More below: Am Donnerstag, 28. März 2019, 16:56:33 CET schrieb laurent Montel: > Le jeudi 28 mars 2019, 16:11:12 CET Friedrich W. H. Kossebau a écrit : > > Hi Laurent, > > > > Am Donnerstag, 28. März 2019, 14:33:59 CET schrieb laurent Montel: > > >

Re: CI system maintainability

2019-03-29 Thread Friedrich W. H. Kossebau
Am Donnerstag, 28. März 2019, 23:06:17 CET schrieb laurent Montel: > Le jeudi 28 mars 2019, 18:27:42 CET Friedrich W. H. Kossebau a écrit : > > Am Donnerstag, 28. März 2019, 16:56:33 CET schrieb laurent Montel: > > > Le jeudi 28 mars 2019, 16:11:12 CET Friedrich W. H

Re: Revisiting the TechBase situation (2 proposals)

2019-04-02 Thread Friedrich W. H. Kossebau
Hi Juan, Am Dienstag, 2. April 2019, 16:20:42 CEST schrieb Juan Carlos Torres: > Greetings, > > I won't be going into history but right now we have two developer-facing > wikis: TechBase and Community. On paper, the division between the two is > clear: "external" vs "community". In addition to st

Re: Revisiting the TechBase situation (2 proposals)

2019-04-04 Thread Friedrich W. H. Kossebau
Am Donnerstag, 4. April 2019, 15:19:49 CEST schrieb David Edmundson: > >OPTION 1: Sunset TechBase, put everything in Community Wiki > > The community wiki is two things. > > * There is structured useful information about things like coding > style, or ABI compliance > > Putting this with techbas

PSA: Use newer add_test(NAME COMMAND ), check CI, esp. with min ECM >=5.38

2019-04-29 Thread Friedrich W. H. Kossebau
Hi, tl:dr In your CMake code replace all remaining add_test( ) with add_test(NAME COMMAND ) to make sure test executables are still found once you bump the minimum ECM version required >= 5.38. And check your product on KDE CI, where not found test executables are now properly reported

RFC: KDE server/service/location for public gpg keys of tarball signers & Co.

2019-08-01 Thread Friedrich W. H. Kossebau
Hi, those of you who make use of signed tarballs/binaries/other files on the consumer side: Please tell your use-case for accessing and using the public keys of the signers, and what the options are you would like to see supported on KDE side. Do so directly on the related task on Phabricator:

RFC: Apps using KF5 & deprecated API - preferred flags to disable/enable warnings and/or API?

2019-09-09 Thread Friedrich W. H. Kossebau
Hi, developer using KDE Frameworks libraries in your projects, how would you like to be able to control warnings about deprecated API in those libraries? Or control the visibility of deprecated API to your code when building? There is a prototype to enhance KDE Frameworks API, so developers bui

Re: RFC: Apps using KF5 & deprecated API - preferred flags to disable/enable warnings and/or API?

2019-09-14 Thread Friedrich W. H. Kossebau
Am Montag, 9. September 2019, 19:28:11 CEST schrieb Friedrich W. H. Kossebau: > Hi, > > developer using KDE Frameworks libraries in your projects, how would you > like to be able to control warnings about deprecated API in those > libraries? Or control the visibility of depreca

Re: RFC: Apps using KF5 & deprecated API - preferred flags to disable/enable warnings and/or API?

2019-09-15 Thread Friedrich W. H. Kossebau
Am Sonntag, 15. September 2019, 23:22:51 CEST schrieb Albert Astals Cid: > El dilluns, 9 de setembre de 2019, a les 19:28:11 CEST, Friedrich W. H. Kossebau va escriure: > > Hi, > > > > developer using KDE Frameworks libraries in your projects, how would you > >

Heads-up for developers using KF modules: how to disable visibility of & warnings about deprecated API for >= 5.64

2019-10-21 Thread Friedrich W. H. Kossebau
Hi, tldr; Please test now with git master the new available C++ macros with KF -DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0xXXYYZZ -DKF_DEPRECATED_WARNINGS_SINCE=0xXYYZZ -DKF_NO_DEPRECATED_WARNINGS -DKF_NO_DEPRECATED as well as individual specializations per library, e.g. -DK{LIB}_DISABLE_DEPRECATED_BE

QT_DEPRECATED_BEFORE/KF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x060000 considered harmful

2019-10-24 Thread Friedrich W. H. Kossebau
Hi, happy to see people starting to adapt the new deprecation macros available with KDE Frameworks (and any other library using ECMGenerateExportHeader, coming with ECM 5.64). Just, I see commits adding things like --- 8< --- add_definitions(-DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x06 --- 8<

Re: QT_DEPRECATED_BEFORE/KF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x060000 considered harmful

2019-10-24 Thread Friedrich W. H. Kossebau
Am Donnerstag, 24. Oktober 2019, 10:50:07 CEST schrieb laurent Montel: > Hi, > As discussed with David previously for QT_DEPRECATED, I am against it, > because if we fix a QT/KF_DEPRECATED version we can be sure that nobody > will work for fixing deprecated method until kf6. > If we can"t see that

Re: QT_DEPRECATED_BEFORE/KF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x060000 considered harmful

2019-10-24 Thread Friedrich W. H. Kossebau
Am Donnerstag, 24. Oktober 2019, 16:32:32 CEST schrieb Volker Krause: > On Thursday, 24 October 2019 10:50:07 CEST laurent Montel wrote: > > Hi, > > As discussed with David previously for QT_DEPRECATED, I am against it, > > because if we fix a QT/KF_DEPRECATED version we can be sure that nobody > >

Re: QT_DEPRECATED_BEFORE/KF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x060000 considered harmful

2019-10-24 Thread Friedrich W. H. Kossebau
Am Donnerstag, 24. Oktober 2019, 17:40:51 CEST schrieb laurent Montel: > Le jeudi 24 octobre 2019, 16:53:04 CEST Friedrich W. H. Kossebau a écrit : > > Am Donnerstag, 24. Oktober 2019, 16:32:32 CEST schrieb Volker Krause: > > > For master however this is less of an issue, as y

Re: QT_DEPRECATED_BEFORE/KF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x060000 considered harmful

2019-10-25 Thread Friedrich W. H. Kossebau
Am Freitag, 25. Oktober 2019, 10:00:47 CEST schrieb David Faure: > On vendredi 25 octobre 2019 08:39:24 CEST Volker Krause wrote: > > In case this ends up being activated in production builds, this would > > however require our ABI isn't changing by deactivating deprecated bits. > > Enum values and

Re: QT_DEPRECATED_BEFORE/KF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x060000 considered harmful

2019-10-25 Thread Friedrich W. H. Kossebau
Am Freitag, 25. Oktober 2019, 10:00:47 CEST schrieb David Faure: > But yeah, maybe something slipped by. Once my KF5 build with > KF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x053f00 is done > [which requires porting 13 modules, apparently), I'll see if the rest of my > Plasma session and KDE Applications

Re: QT_DEPRECATED_BEFORE/KF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x060000 considered harmful

2019-10-25 Thread Friedrich W. H. Kossebau
Am Donnerstag, 24. Oktober 2019, 18:52:34 CEST schrieb laurent Montel: > Le jeudi 24 octobre 2019, 18:22:07 CEST Friedrich W. H. Kossebau a écrit : > > Am Donnerstag, 24. Oktober 2019, 17:40:51 CEST schrieb laurent Montel: > > > Le jeudi 24 octobre 2019, 16:53:04 CEST Friedric

Re: QT_DEPRECATED_BEFORE/KF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x060000 considered harmful

2019-11-02 Thread Friedrich W. H. Kossebau
Am Donnerstag, 24. Oktober 2019, 10:50:07 CET schrieb laurent Montel: > When a compilation is broken by a new deprecated method we will fix it. First though lots of people run into the build error, and are annoyed by it. As just happened know, because I properly added the missing deprecation mark

Re: Sysadmin Load Reduction: Subversion Infrastructure

2019-11-09 Thread Friedrich W. H. Kossebau
Am Samstag, 9. November 2019, 21:22:16 CET schrieb Ben Cooksley: > On Sun, Nov 10, 2019 at 8:37 AM Albert Astals Cid wrote: > > El dissabte, 9 de novembre de 2019, a les 19:27:07 CET, Ben Cooksley va escriure: > > > On Sun, Nov 10, 2019 at 7:18 AM Alexander Potashev wrote: > > > > сб, 9 нояб. 2

Write-up of Qt i18n vs. KI18n/gettext, potential issues with Qt translations

2019-12-15 Thread Friedrich W. H. Kossebau
Hi, for those interested in magic and/or issues of the translation system in software from KDE, I just flushed some old note of mine about things I researched at the KDE meeting Randa 2016 which I never managed to turn into proper bug reports, code fixes etc. Also comes with some overview how

Recommendation: drop ProvidersUrl entry to rely on default value (was: Re: Get Hot New Stuff - Legacy Endpoints)

2020-01-30 Thread Friedrich W. H. Kossebau
Hi, as found out by discussion on irc, a good solution for everyone relying on the default GHNS storage as provided by KDE is to just not hard-code any value for ProvidersUrl, but leave it out and let KNewStuff default to what is built into the KNewStuff library as current value. So: --- 8< --

WARNING: was bad recommendation (Re: Recommendation: drop ProvidersUrl entry to rely on default value)

2020-01-30 Thread Friedrich W. H. Kossebau
schrieb Christoph Feck: > On 01/30/20 13:53, Friedrich W. H. Kossebau wrote: > > as found out by discussion on irc, a good solution for everyone relying on > > the default GHNS storage as provided by KDE is to just not hard-code any > > value for ProvidersUrl, but leave it out and

Fixing QNetworkAccessManager use for KDE services

2020-02-02 Thread Friedrich W. H. Kossebau
Hi Ben, sorry to hear about this pain you have in all the good work you do that allows us to enjoy the high reliability of the KDE services. I would like to help to reduce that pain. Am Samstag, 1. Februar 2020, 23:24:14 CET schrieb Ben Cooksley: > Hi all, > > For an extremely long time now, i

Re: Fixing QNetworkAccessManager use

2020-02-19 Thread Friedrich W. H. Kossebau
Am Mittwoch, 19. Februar 2020, 08:05:01 CET schrieb Ben Cooksley: > On Mon, Feb 3, 2020 at 7:42 AM Volker Krause wrote: > > It would also help to know where specifically we have that problem, so we > > can actually solve it, and so we can figure out why we failed to fix this > > there earlier. >

Re: Fixing QNetworkAccessManager use

2020-02-19 Thread Friedrich W. H. Kossebau
Am Mittwoch, 19. Februar 2020, 21:01:20 CET schrieb Johan Ouwerkerk: > On Wed, Feb 19, 2020 at 2:09 PM Friedrich W. H. Kossebau > > wrote: > > Personally I am still unsure what the actual issue is. Why are redirects > > needed at all. Why all the address changes all the tim

Re: Calligra fails on CI with libKF5XmlGui 5.70.0

2020-04-22 Thread Friedrich W. H. Kossebau
Hi Dag, Am Mittwoch, 22. April 2020, 08:20:25 CEST schrieb Dag: > A few days ago CI build started to fail with this message: > > /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: > /home/jenkins/install-prefix/lib64/libKF5XmlGui.so.5.70.0: undefined > reference to `QSystemL

Re: Context information needed for isolated words

2020-05-02 Thread Friedrich W. H. Kossebau
Am Samstag, 2. Mai 2020, 13:11:55 CEST schrieb Johan Ouwerkerk: > On Sat, May 2, 2020 at 12:36 PM Eloy Cuadra wrote: > > Hi, > > > > There is a widespread problem across many text strings to be translated: > > some isolated words are gender invariable in English, but not in many > > languages.>

Re: EBN Going Away

2020-05-06 Thread Friedrich W. H. Kossebau
Hi Allen. Am Mittwoch, 6. Mai 2020, 16:56:57 CEST schrieb Allen Winter: > In 2005 Adriaan and I setup a little service for improving code quality > which we named "The English Breakfast Network" (ebn.kde.org) > > Sometime soon the server that runs the EBN will be taken down > and I have no intent

Re: My first task

2020-06-11 Thread Friedrich W. H. Kossebau
Hi Piotr, Am Donnerstag, 11. Juni 2020, 20:49:57 CEST schrieb Piotr Frankowski: > Hello, > > First of all,thanks for such great piece of software, which I am using for > 15 years. I would like to make small contribution - but I need little help, > a kind of mentoring or a plan and help at begin.

Moving ring-kde to unmaintained (was: Re: Shift for parts of the CI system to Qt 5.15)

2020-06-20 Thread Friedrich W. H. Kossebau
Am Samstag, 20. Juni 2020, 12:25:42 CEST schrieb Ben Cooksley: > On Sat, Jun 20, 2020 at 8:13 PM Volker Krause wrote: > > On Saturday, 20 June 2020 08:20:18 CEST Ben Cooksley wrote: > > > - ring-kde > > > > build errors seem to be in stuff downloaded by cmake!? > > Indeed, this seems to be a bit

PSA: Qt logging category names of all KF modules have changed for KF >= 5.73 (current master)

2020-07-13 Thread Friedrich W. H. Kossebau
Hi, as of this morning, latest master branch of all KDE Frameworks modules has seen a change of all the Qt logging category names they define, to now follow standardized patterns. Those are described over at https://community.kde.org/Frameworks/Frameworks_Logging_Policy So everyone running K

Re: Dropping libkgeomap from release service 20.12 - was - Re: libkgeomap

2020-08-08 Thread Friedrich W. H. Kossebau
Am Samstag, 8. August 2020, 00:41:27 CEST schrieb Albert Astals Cid: > This needs to go to release-team which is where the dropping/adding stuff is > discussed. > > Sending there. > > Friedrich, you're the lastest one that did changes, even they are mostly > gardening ones. What's your opinion?

Grantlee latest 5.2.0 and deprecated QString enums in its API

2020-12-28 Thread Friedrich W. H. Kossebau
Hi Steve & all Grantlee consumers, TL;DR Current last release 5.2.0 of Grantlee blocks applications from using QT_DISABLE_DEPRECATED_BEFORE=0x050F00., Please let's have a new release 5.3.0/5.2.1 of Grantlee with a fix for that (MR 70 up as proposal) Some of us have hit the issue that Grantlee

RFC: suffix ".in" instead of ".cmake" for template files to substitution processing

2021-01-03 Thread Friedrich W. H. Kossebau
Hi, [replies only to kde-devel@kde.org, please] tl;dr This is a proposal to standardize on the suffix ".in" for input/ template files passed to cmake's configure_file() in KDE projects. When it comes to naming the files used as templates for build-time generation of source/data files by subs

PSA: Please do not use KDEFrameworkCompilerSettings for non-KF projects

2021-01-19 Thread Friedrich W. H. Kossebau
Hi, the docs of the module tell us: "KDEFrameworkCompilerSettings - Set stricter compile and link flags for KDE Frameworks modules." https://api.kde.org/ecm/kde-module/KDEFrameworkCompilerSettings.html And it has been meant that way. E.g. because extending those settings with more strict settin

Re: PSA: Please do not use KDEFrameworkCompilerSettings for non-KF projects

2021-01-20 Thread Friedrich W. H. Kossebau
Am Mittwoch, 20. Januar 2021, 16:51:54 CET schrieb Volker Krause: > How about we try to come up with an alternative solution for what looks like > a wide-spread demand for centrally maintained high-quality compiler > settings instead then? That might also make any kind of enforcement to not > use t

Re: PSA: Please do not use KDEFrameworkCompilerSettings for non-KF projects

2021-01-31 Thread Friedrich W. H. Kossebau
Am Mittwoch, 20. Januar 2021, 17:10:03 CET schrieb Friedrich W. H. Kossebau: > Am Mittwoch, 20. Januar 2021, 16:51:54 CET schrieb Volker Krause: > > How about we try to come up with an alternative solution for what looks > > like a wide-spread demand for centrally maintained high-q

Re: C and C++ compiler extensions disabled in extra-cmake-modules

2021-06-28 Thread Friedrich W. H. Kossebau
Am Montag, 28. Juni 2021, 01:05:37 CEST schrieb Albert Astals Cid: > With > https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/145 > we have disabled the C and C++ specific compiler extensions. > > This has already let to some code failing to build that was using C > extensions

[REVERTED] Re: C and C++ compiler extensions disabled in extra-cmake-modules

2021-06-28 Thread Friedrich W. H. Kossebau
Am Montag, 28. Juni 2021, 01:05:37 CEST schrieb Albert Astals Cid: > With > https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/145 > we have disabled the C and C++ specific compiler extensions. > > This has already let to some code failing to build that was using C > extensions

ECM 5.85: introducing KDE_COMPILERSETTINGS_LEVEL concept

2021-08-14 Thread Friedrich W. H. Kossebau
Hi, ((kde-core-devel as CC:, please reply only to kde-devel) TL;DR Starting with ECM 5.85 KDECompilerSettings will provide some stricter settings, which you can control on the toplevel by KDE_COMPILERSETTINGS_LEVEL and then again per settings category, for a stable set of settings matching you

Re: How do you label code to be deleted in KF6?

2021-11-09 Thread Friedrich W. H. Kossebau
Am Dienstag, 9. November 2021, 03:33:44 CET schrieb Glen Ditchfield: > I would like to have some members of KCalendarCore's incidence classes > removed during the transition from KF5 to KF6, and I'd like to be sure > that the changes won't be missed in the excitement. > > Do you have some preferre

Re: Merge stable to master vs cherry-picking

2021-12-08 Thread Friedrich W. H. Kossebau
Am Mittwoch, 8. Dezember 2021, 07:44:32 CET schrieb Ben Cooksley: > This is why I have been pushing for people to use @stable in their > .kde-ci.yml files - even for the 'master' branch. > It is much simpler for people if you can use stable/released dependencies > when conducting development. Othe

Re: Merge stable to master vs cherry-picking

2021-12-09 Thread Friedrich W. H. Kossebau
Am Donnerstag, 9. Dezember 2021, 11:08:01 CET schrieb Ben Cooksley: > On Wed, Dec 8, 2021 at 10:38 PM Friedrich W. H. Kossebau > > wrote: > > Am Mittwoch, 8. Dezember 2021, 07:44:32 CET schrieb Ben Cooksley: > > > This is why I have been pushing for people to use @st

SPDX and docbook documentation, how to do properly?

2022-01-05 Thread Friedrich W. H. Kossebau
Hi, the section "License Statements in Non-Source-Code Files" at https://community.kde.org/Guidelines_and_HOWTOs/ Licensing#License_Statements_in_Non-Source-Code_Files currently does not hold an example how to add SPDX tags. And by a quick look it seems not many docbook files in KDE repos cu

Re: SPDX and docbook documentation, how to do properly?

2022-01-10 Thread Friedrich W. H. Kossebau
Am Mittwoch, 5. Januar 2022, 15:21:24 CET schrieb Luigi Toscano: > Harald Sitter ha scritto: > > On Wed, Jan 5, 2022 at 1:45 PM Friedrich W. H. Kossebau > > > > wrote: > >> Hi, > >> > >> the section "License Statements in Non-Source-Co

Developer setups for user D-Bus service files?

2022-01-11 Thread Friedrich W. H. Kossebau
Hi, (plasma-devel as CC: for heads-up, please reply only to kde-devel to keep discussion in one place) at least with systemd controlled start (but possibly also before) of the session D-Bus (based on what I understood so far, please correct me) for a user is not possible just by editing their

Re: Developer setups for user D-Bus service files?

2022-01-11 Thread Friedrich W. H. Kossebau
Am Dienstag, 11. Januar 2022, 19:38:09 CET schrieb Friedrich W. H. Kossebau: > YOUR INPUT NEEDED > So, what standard approach should we take as developers here? Ideally we all > do something similar, so any issues hit are more easy to > understand/reproduce when we discuss them. And

Re: Developer setups for user D-Bus service files?

2022-01-11 Thread Friedrich W. H. Kossebau
Am Dienstag, 11. Januar 2022, 22:49:47 CET schrieb David Edmundson: > >at least with systemd controlled start (but possibly also before > > Since forever. Okay, guessed so, as I had found decade old queries trying to solve similar challenges, though systemd also is that age, thus was not that su

Re: Developer setups for user D-Bus service files?

2022-01-11 Thread Friedrich W. H. Kossebau
Am Dienstag, 11. Januar 2022, 22:49:47 CET schrieb David Edmundson: > I did start another idea. > > If you populate the dev session environment variables *really* early > must we even go through pam you can set your XDG_DATA_DIRS before DBus > daemon has loaded it will then have the right stuff. >

Re: Developer setups for user D-Bus service files?

2022-01-12 Thread Friedrich W. H. Kossebau
Am Mittwoch, 12. Januar 2022, 11:49:26 CET schrieb David Edmundson: > > This triggered yet another idea with me, and I came across > > https://www.freedesktop.org/software/systemd/man/environment.d.html > > upon which I tried to add a file > > /home/mydevuser/.config/environment.d/60-test.conf > >

Reminder: When requiring ECM 5.85 or newer, be aware of KDE_COMPILERSETTINGS_LEVEL concept

2022-02-14 Thread Friedrich W. H. Kossebau
Hi, ((kde-core-devel as CC:, please reply only to kde-devel) Time for a quick reminder after half a year, given this is not daily business but people might more & more require newer ECM and run into this. Quoting the important bit below, for the full initial email, please see https://marc.in

Challenge: adding new method overloads when existing consumers use {} with args

2022-07-23 Thread Friedrich W. H. Kossebau
Hi, (cc: kde-frameworks-devel for heads-up, please reply to kde-devel only) given a class C with a method foo(A a): --- 8< --- class C { public: void foo(A a); }; --- 8< --- Now you want to add an overload, to serve further use-cases as requested by API consumers: --- 8<

Re: Challenge: adding new method overloads when existing consumers use {} with args

2022-07-25 Thread Friedrich W. H. Kossebau
Am Montag, 25. Juli 2022, 10:19:39 CEST schrieb David Redondo: > Am Samstag, 23. Juli 2022, 17:20:08 CEST schrieb Friedrich W. H. Kossebau: > Adding such an overload as in your example is source incompatible > regardless. See also our guidelines. > https://community.kde.

Re: Challenge: adding new method overloads when existing consumers use {} with args

2022-07-27 Thread Friedrich W. H. Kossebau
Am Montag, 25. Juli 2022, 15:21:43 CEST schrieb Arjen Hiemstra: > On Monday, 25 July 2022 14:22:45 CEST Friedrich W. H. Kossebau wrote: > > Am Montag, 25. Juli 2022, 10:19:39 CEST schrieb David Redondo: > > > Am Samstag, 23. Juli 2022, 17:20:08 CEST schrieb Friedrich W.

Re: Challenge: adding new method overloads when existing consumers use {} with args

2022-07-27 Thread Friedrich W. H. Kossebau
(David, somehow your emails do not make it from the mailinglist to my inbox sadly, no idea yet why. Saw your email by chance on the list web interface, and tosky forwarded it manually to me, so I can reply now here. So might miss out more :() Am Samstag, 23. Juli 2022, 20:26:47 CEST schrieb Dav

Re: Challenge: adding new method overloads when existing consumers use {} with args

2022-07-27 Thread Friedrich W. H. Kossebau
Am Mittwoch, 27. Juli 2022, 13:51:48 CEST schrieb Friedrich W. H. Kossebau: > Am Montag, 25. Juli 2022, 15:21:43 CEST schrieb Arjen Hiemstra: > > You could try using SFINAE: > > > > ``` > > struct Test { > > > > void foo() { } &g

Re: Challenge: adding new method overloads when existing consumers use {} with args

2022-07-28 Thread Friedrich W. H. Kossebau
Am Donnerstag, 28. Juli 2022, 01:50:28 CEST schrieb Thiago Macieira: > [cross-posting to Qt dev ML - dunno if it'll arrive because I'm subscribed > with different addresses] > > On Wednesday, 27 July 2022 14:54:55 PDT Friedrich W. H. Kossebau wrote: > > And has n

Re: Challenge: adding new method overloads when existing consumers use {} with args

2022-08-15 Thread Friedrich W. H. Kossebau
Am Donnerstag, 28. Juli 2022, 14:38:38 CEST schrieb Friedrich W. H. Kossebau: > Am Donnerstag, 28. Juli 2022, 01:50:28 CEST schrieb Thiago Macieira: > > But {} is particularly special, so I don't know how we'd deal with it. I > > don't think this has come up for us

Cleaning up cdash.org integration, what to do, or any hidden usage still?

2022-09-02 Thread Friedrich W. H. Kossebau
Hi, (cc: kde-devel for heads-up, please reply only to kde-core-devel). we stumbled over some CTestConfig.cmake files in some of the KDE git repositories. Which seem to originate from a time where people worked on integration with cdash.org, that is a decade ago :) It seems though this integrat

Re: "Configure Language" option

2022-10-25 Thread Friedrich W. H. Kossebau
Am Montag, 24. Oktober 2022, 23:38:15 CEST schrieb Stefan Gerlach: > i noticed that several KDE apps lack the ability to switch the UI language > when using the "Configure Language" dialog. The .mo files are correctly > installed, all the languages are in the selection box and the configuration > i

Re: "Configure Language" option

2022-10-25 Thread Friedrich W. H. Kossebau
Am Dienstag, 25. Oktober 2022, 17:16:15 CEST schrieb Friedrich W. H. Kossebau: > Am Montag, 24. Oktober 2022, 23:38:15 CEST schrieb Stefan Gerlach: > > i noticed that several KDE apps lack the ability to switch the UI language > > when using the "Configure Language"

Helper for porting from deprecated KMessageBox Yes/No API

2022-11-02 Thread Friedrich W. H. Kossebau
Hi, while as "culprit" for those API changes (HIG-matching rename of *YesNo* methods) I have seen to do the needed porting in some repos, there are more which need someone else to do that sadly. Especially for those projects with many calls perhaps the approach we now developed for KDevelop mi

RFC: KF (& other lib) consumers: want KFOO_VERSION macro definitions automagically available?

2023-02-28 Thread Friedrich W. H. Kossebau
Hi, (cc:kde-core-devel only for heads-up, any reply please only to kde-devel) TL;DR Would you fancy not having to always explicitly include a version header of a KFoo module to have the KFOO_VERSION variable available in your code? So is it worth it to add support for that on the KF side? (KF6

Re: RFC: KF (& other lib) consumers: want KFOO_VERSION macro definitions automagically available?

2023-03-09 Thread Friedrich W. H. Kossebau
(cc:kde-core-devel only for heads-up, any reply please only to kde-devel) Am Dienstag, 28. Februar 2023, 15:20:11 CET schrieb Friedrich W. H. Kossebau: > TL;DR Would you fancy not having to always explicitly include a version > header of a KFoo module to have the KFOO_VERSION variable ava

Re: Usage of KF5/KF6 in targets and CMake config files outside of Frameworks

2023-03-09 Thread Friedrich W. H. Kossebau
Am Donnerstag, 9. März 2023, 18:03:17 CET schrieb Ingo Klöcker: > On Donnerstag, 9. März 2023 16:58:40 CET Heiko Becker wrote: > > while looking at a MR for libkcddb (part of Gear) I wondered if the > > transition > > from Qt5/KF5 to Qt6/KF6 could be used to get rid of the KF5/6 prefix in > > targe

Re: Tellico failing CI with exiv2 error

2023-07-06 Thread Friedrich W. H. Kossebau
Am Donnerstag, 6. Juli 2023, 18:43:50 CEST schrieb Kai Uwe Broulik: > > Probably libexiv2 on the CI host was updated to libexiv2 0.28, but > > KFileMetaData was not rebuilt. Automatic dependency tracking for > > artifacts > > > from the CI system is obviously incomplete (or likely nonexistent)

PSA: Qt6-based KDE software builds: drop EXCLUDE_DEPRECATED_BEFORE_AND_AT override now

2023-07-26 Thread Friedrich W. H. Kossebau
Hi, a quick heads-up: if you already package or otherwise do any Qt6-based KDE software builds and have in the set of manual flags passed to cmake any "-DEXCLUDE_DEPRECATED_BEFORE_AND_AT=x.y.z" override, please remove that override completely now. All KDE sources should now set the proper d

RFC: switching games released with KDE Gear to Qt6/KF6-only in master branch next?

2023-09-13 Thread Friedrich W. H. Kossebau
Hi, (cc: kde-devel for heads-up, please reply only to kde-games-devel) QUESTION Would anyone have issues with switching all the games and game libraries released with KDE Gear to be Qt6/KF6 only in the master branch (once some conditions are met, see below)? MOTIVATION Having brushed over ma

Re: RFC: switching games released with KDE Gear to Qt6/KF6-only in master branch next?

2023-09-24 Thread Friedrich W. H. Kossebau
Am Mittwoch, 13. September 2023, 22:34:16 CEST schrieb Friedrich W. H. Kossebau: > (cc: kde-devel for heads-up, please reply only to kde-games-devel) > > QUESTION > > Would anyone have issues with switching all the games and game libraries > released with KDE Gear to be Q

KDE Gear "6.0" status update: all 40 games & 2 libs now Qt6-only in master

2023-10-01 Thread Friedrich W. H. Kossebau
Hi, just a quick heads-up to keep more people in the loop: all the 40 game apps & 2 game libs covered by KDE Gear starting today are now Qt6-only in their master branches. And thus can/will be released based on Qt6/ KF6 in the KDE Gear "6.0" 24.02 release. So the section "Games" can be checked

Re: fix for KConfigPrivate::groupList (kconfig.cpp)

2023-12-29 Thread Friedrich W. H. Kossebau
Am Freitag, 29. Dezember 2023, 10:53:45 CET schrieb Tommaso Massimi: > running plasma-systemmonitor with valgring a lot of problems are declared, > I'm trying to check them out. > > I'm not sure if this is the best way to communicate with the development > team, > so I'm writing this mail also to

Re: fix for KConfigPrivate::groupList (kconfig.cpp)

2023-12-29 Thread Friedrich W. H. Kossebau
Hi, Am Freitag, 29. Dezember 2023, 10:53:45 CET schrieb Tommaso Massimi: > running plasma-systemmonitor with valgring a lot of problems are declared, > I'm trying to check them out. > > I'm not sure if this is the best way to communicate with the development > team, > so I'm writing this mail als

Re: fix for KConfigPrivate::groupList (kconfig.cpp)

2023-12-29 Thread Friedrich W. H. Kossebau
Am Freitag, 29. Dezember 2023, 16:36:41 CET schrieb Tommaso Massimi: > On Fri, Dec 29, 2023 at 3:35 PM Friedrich W. H. Kossebau > wrote: [snip} > > After a more close look I would partially disagree and point to another > > > possible cause: > correct, my analisys was

Re: KDE Gear projects with failing CI (release/24.02) (6 February 2024)

2024-02-07 Thread Friedrich W. H. Kossebau
Am Mittwoch, 7. Februar 2024, 11:48:57 CET schrieb Ben Cooksley: > All of the Games Flatpak failures are caused by > https://invent.kde.org/games/libkdegames/-/commit/023d1a7b173f9d28453a0268e9 > 1ad1ccb47054b9 I intend to revert that commit in 24 hours unless a suitable > explaination can be provi

flathub now supports tag, but which id to use for KDE? (was: Re: Defining a developer name for our applications metadata)

2024-02-22 Thread Friedrich W. H. Kossebau
Am Dienstag, 30. Januar 2024, 18:34:46 CET schrieb Timothée Ravier: > Hi folks, > > Flathub is now requiring that applications define a "developer_name" tag in > their metadata (see [1], [2]). > > What do folks think would be a good value for our application there? > > Based on the suggestion in

Re: flathub now supports tag, but which id to use for KDE? (was: Re: Defining a developer name for our applications metadata)

2024-02-26 Thread Friedrich W. H. Kossebau
Am Donnerstag, 22. Februar 2024, 15:58:53 CET schrieb Friedrich W. H. Kossebau: > Am Dienstag, 30. Januar 2024, 18:34:46 CET schrieb Timothée Ravier: > > Hi folks, > > > > Flathub is now requiring that applications define a "developer_name" tag > &g

Re: KDE Gear projects with failing CI (master) (9 April 2024)

2024-04-10 Thread Friedrich W. H. Kossebau
Am Mittwoch, 10. April 2024, 13:04:47 CEST schrieb Ingo Klöcker: > On Mittwoch, 10. April 2024 09:21:34 CEST Ben Cooksley wrote: > > On Wed, Apr 10, 2024 at 9:51 AM Ingo Klöcker wrote: > > > On Dienstag, 9. April 2024 23:26:32 CEST Albert Astals Cid wrote: > > > > ktrip - NEW > > > > > > > > * h

Re: KDE Gear projects with failing CI (master) (9 April 2024)

2024-04-10 Thread Friedrich W. H. Kossebau
Am Mittwoch, 10. April 2024, 14:29:37 CEST schrieb Ingo Klöcker: > On Mittwoch, 10. April 2024 13:33:46 CEST Friedrich W. H. Kossebau wrote: > > Am Mittwoch, 10. April 2024, 13:04:47 CEST schrieb Ingo Klöcker: > > > On Mittwoch, 10. April 2024 09:21:34 CEST Ben Cooksley wrote: &

Re: Application-specific color settings

2015-06-08 Thread Friedrich W. H. Kossebau
Am Montag, 8. Juni 2015, 17:22:26 schrieb Milian Wolff: > Hey all, > > sometimes I need to run applications that do not work properly with a dark > system color scheme. Is there a way to set a different (bright) color scheme > for /some/ applications? > > If not, where would such a feature need t

RFC: names of icons related to tables, paths, animation, text & more

2015-11-17 Thread Friedrich W. H. Kossebau
Hi, the Breeze iconset currently gets further icons, as needed by the different Calligra apps and plugins. And that are many icons. Given these icons are then in the public namespace (without any calligra prefix) and ideally also can be reused by any apps, we need to ensure there are no icon n

Re: How to make QImageIOPlugins work with KDE applications?

2016-02-18 Thread Friedrich W. H. Kossebau
Hi Sebastian, Am Donnerstag, 18. Februar 2016, 16:17:51 CET schrieb Sebastian Wahl: > Hi guys, > > I was developing a QImageIOPlugin for FLIF (Free Lossless Image > Format, http://flif.info/) and was quite disappointed to not being > able to find any application which would use it. > Well, that w

Re: How to make QImageIOPlugins work with KDE applications?

2016-02-18 Thread Friedrich W. H. Kossebau
Am Freitag, 19. Februar 2016, 00:28:04 CET schrieb Friedrich W. H. Kossebau: > Install a file "imagethumbnail.desktop" with this: Forgot to adapt the name of the file, "imagethumbnail.desktop" of course is already taken :) So use e.g. "flifthumbnail.desktop". Cheers Friedich

Re: How to make QImageIOPlugins work with KDE applications?

2016-02-19 Thread Friedrich W. H. Kossebau
Curious question at the begin: what mimetype are you using for flif? Am Freitag, 19. Februar 2016, 18:54:09 CET schrieb Sebastian Wahl: > > The WebP image format is already noted in the shared-mime-info database, > > that is how Gwenview & Co. treat such files as image files (surely even > > more

Re:

2016-03-03 Thread Friedrich W. H. Kossebau
Hi Alex, Am Donnerstag, 3. März 2016, 20:13:59 CET schrieb Alex Mourtziapis: > Hi, > > Sorry for spamming... > I wanted to ask if there's a possible way to work on Krita repo without > messing with the whole Calligra Suite. > (my connection is not that good as you can imagine, it ll take a lotta

Separating in-source translations from */messages into own */srcmessages (or similar)

2016-06-17 Thread Friedrich W. H. Kossebau
Hi, PROBLEM: garbage po and mo files in packages currently many of the scripts used for creating release tarballs of KDE software accidentally also add those po files to the tarballs whose translations are already fed back directly into the sources by scripty (with data files like appdata, des

Re: Separating in-source translations from */messages into own */srcmessages (or similar)

2016-06-20 Thread Friedrich W. H. Kossebau
Am Montag, 20. Juni 2016, 00:50:12 CEST schrieb Luigi Toscano: > Albert Astals Cid ha scritto: > > El divendres, 17 de juny de 2016, a les 12:30:00 CEST, Luigi Toscano va > > > > escriure: > >> On Friday 17 of June 2016 12:10:41 Friedrich W. H. Kossebau wrote:

Re: Does kxmleditor or khexedit still exist or can they be compiled with build options?

2016-11-09 Thread Friedrich W. H. Kossebau
Am Mittwoch, 9. November 2016, 19:13:37 CET schrieb Albert Astals Cid: > El dimecres, 9 de novembre de 2016, a les 11:48:02 > > CET, David C. Rankin va escriure: > > I'm also trying to locate khexedit. > > khexedit was renamed to okteta. For the record, Okteta was written from scratch for KDE

Re: Detecting appstream scheme support ; end-user-oriented "About AppStream" page (was: Re: Add "Install via AppStream" links to applications on kde.org)

2016-12-18 Thread Friedrich W. H. Kossebau
then give your comments/2 cents :) Am Montag, 19. Dezember 2016, 01:30:39 CET schrieb Matthias Klumpp: > 2016-12-19 1:00 GMT+01:00 Friedrich W. H. Kossebau : > > Am Sonntag, 18. Dezember 2016, 22:50:23 CET schrieb Albert Astals Cid: > >> El dissabte, 17 de desembre de 2016, a les

Re: okteta 4.5.4 fails to build

2010-12-28 Thread Friedrich W. H. Kossebau
Hi Erik, Dimanche, le 26 december 2010, à 22:25, Erik a écrit: > 2010-12-24 03:11, Erik skrev: > > steps to reproduce: > > 1. tar jxvf /usr/portage/distfiles/kdeutils-4.5.4.tar.bz2 > > 2. cd kdeutils-4.5.4 > > 3. mkdir build > > 4. cd build > > 5. cmake -DKDE4_ENABLE_FINAL=ON .. > > 6. make okteta

Re: Improving onscreen keyboard features 4 disabled

2011-04-15 Thread Friedrich W. H. Kossebau
Hi Kyle, Vrendredi, le 15 avril 2011, à 22:03, Kyle Pablo a écrit: > Hello All, > > Can we implement a word completion feature for a new onscreen > keyboard? > The accessibility tools are limited and having an onscreen keyboard > that is > similar to Windows 7's in features and design w

  1   2   >