--000000000000acefed05701b3aca
Content-Type: text/plain; charset="UTF-8"

>
> Ideally this needs to be standardized so that it does not only work with
> our applications but with any.
>

Even within just KDE apps, we have code like QDesktopServices spawning
links in code we can't manipulate. Anything non standard, simply isn't
worth merging.

But I don't think standardising anything would be too hard.

Effectively we want something like xdg-foreign which exists. The difference
is that it lasts temporarily and it's not manipulating parents.

There are two interesting questions:

Do we want/need to support wayland window sending activating an xwayland
window?

Would we need a serial of the user event (xdg_popup style)? It would which
kinda matches the X event timestamps?
It's trickier as you'd need a protocol to generate a UUID for both that and
the surface to sidechannel, but it's not impossible.

---

The other potential solution that I was wondering about, that's waaay
simpler, definitely waaay crappier, but possibly simple enough to just work
without really having issues.

Could client A just release focus (somehow) when spawning an app? If
nothing has focus and toplevel B appears, it seems sensible that kwin would
focus it.

--000000000000acefed05701b3aca
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
Ideally this needs to be standardized so that it does not only work with ou=
r applications but with any.<br></blockquote><div><br></div><div>Even withi=
n just KDE apps, we have code like QDesktopServices spawning links in code =
we can&#39;t manipulate. Anything non standard, simply isn&#39;t worth merg=
ing.<br></div></div><div class=3D"gmail_quote"><br></div><div class=3D"gmai=
l_quote">But I don&#39;t think standardising anything would be too hard.</d=
iv><div class=3D"gmail_quote"><br></div><div class=3D"gmail_extra">Effectiv=
ely we want something like xdg-foreign which exists. The difference is that=
 it lasts temporarily and it&#39;s not manipulating parents.</div><div clas=
s=3D"gmail_extra"><br><div class=3D"gmail_quote">There are two interesting =
questions:</div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_qu=
ote"><div>Do we want/need to support wayland window sending activating an x=
wayland window?</div><div><br></div><div>Would we need a serial of the user=
 event (xdg_popup style)? It would which  kinda matches the X event timesta=
mps?</div><div> It&#39;s trickier as you&#39;d need a protocol to generate =
a UUID for both that and the surface to sidechannel, but it&#39;s not impos=
sible.<br></div></div><div class=3D"gmail_quote"><div><br></div><div>---</d=
iv><div><br></div><div>The other potential solution that I was wondering ab=
out, that&#39;s waaay simpler, definitely waaay crappier, but possibly simp=
le enough to just work without really having issues.<br></div><div><br></di=
v><div>Could client A just release focus (somehow) when spawning an app? If=
 nothing has focus and toplevel B appears, it seems sensible that kwin woul=
d focus it.<br></div><div><br></div><div><br></div><div><br></div></div></d=
iv></div></div>

--000000000000acefed05701b3aca--