KWindowSystem: deprecate KStartupInfoData::launchedBy, unused
ClosedPublic

Authored by dfaure on Mar 13 2020, 6:53 AM.

Details

Summary

KRun bothers with a WId in many places just to end up calling
KStartupInfoData::setLaunchedBy... and nobody uses that value anywhere.
Time to deprecate this and simplify KRun (which I'm rewriting).

Test Plan

Builds. Warns when used in KIO.

Diff Detail

Repository
R278 KWindowSystem
Branch
master
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 23641
Build 23659: arc lint + arc unit
dfaure created this revision.Mar 13 2020, 6:53 AM
Restricted Application added a project: Frameworks. · View Herald TranscriptMar 13 2020, 6:53 AM
Restricted Application added a subscriber: kde-frameworks-devel. · View Herald Transcript
dfaure requested review of this revision.Mar 13 2020, 6:53 AM

Anything WId also probably won't work on Wayland, so +1

zzag added a comment.Mar 13 2020, 8:16 AM

Do you know why LAUNCHED_BY was added? The spec [1] has no a single word about its potential use cases.

[1] https://specifications.freedesktop.org/startup-notification-spec/startup-notification-latest.txt

davidedmundson accepted this revision.Mar 19 2020, 11:27 AM

I don't 100% agree that "it doesn't seem used".

It's used in KStartupInfoData::Private::to_text() which affects what gets written out over the wire to everyone else.
At which point we can't just look internally at what we happen to use in KDE, we need to ask if anyone else in the world uses that property.

From what I can tell, kwin doesn't read it back in any form, the spec does explicitly say it's optional, and not even GTK sets it...so it's probably safe.

This revision is now accepted and ready to land.Mar 19 2020, 11:27 AM
zzag added a comment.Mar 19 2020, 12:28 PM

Maybe it would be worth to send an email to wm-spec-list proposing to deprecate LAUNCHED_BY, but on the other hand fixing X11 stuff in any way is like beating a dead horse.

dfaure closed this revision.Mar 21 2020, 9:44 AM