Maybe it would be a good idea to add this as a static method to KWayland somwehere?

Can this be done differently - the splash is also used as a part of StartActive which is not a SplashApp?

nah, if at all to KWindowSystem.

What's "StartActive"?

Ok, to KWindowSystem then. It could be a method with inner cached static result so that the consecutive calls to it do not need to perform any string comparisons.

This is not really a nice thing to have in all the places copy-pasted.

Maybe a enum-returning thing such as { Unknown = 0, X11 = 1, Wayland = 2, ForExtensibility = 255 }

We had a systemd-like startkde replacement in Plasma Active called StartActive, and sebas recently told me that it was agreed it should be revived (no idea ho was in that meeting :) ). And... it is revived.

And it shares the code with ksplashqml - the splash is integrated.

yes that's on my todo list since last Akademy... - in pretty much exactly the way you just outlined here.

well tricky then. I need to get to the kwayland integration done in KSplashApp. I need a way to get to that. And if it's not using KSplashApp that needs to be done somewhere else. If you have ideas how to solve this problem, please tell.

I don't know how start active is working and how it's integrating the code, but as a session controller I would assume it's getting started before the Wayland server is started. So the whole thing becomes mood anyway.

Anyway we had so many contenders for replacing ksmserver over the last years that I'm not going to consider hypothetical problems with possible contenders. Sorry.

It is not a ksmserver replacement, just a startkde replacement.

You can ignore this for now. Since we are now mostly in bug fixing mode, and 5.8 is LTS, startplasma (startactive) is not going to replace startkde just yet. I'll see what to do about it later then.

Please do, I have grepped plasma codebases, and we have platformName() calls in quite a few places.