<html><body dir="auto" role="textbox" aria-label="Message Body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><div dir="ltr"><div style="display: block;" class=""><div style="-webkit-user-select: all; -webkit-user-drag: element; display: inline-block;" class="apple-rich-link" draggable="true" role="link" data-url="https://www.proli.net/2020/04/03/developing-kwin-wayland/"><a style="border-radius:10px;font-family:-apple-system, Helvetica, Arial, sans-serif;display:block;-webkit-user-select:none;width:300px;user-select:none;-webkit-user-modify:read-only;user-modify:read-only;overflow:hidden;text-decoration:none;" class="lp-rich-link" rel="nofollow" href="https://www.proli.net/2020/04/03/developing-kwin-wayland/" dir="ltr" role="button" draggable="false" width="300"><table style="table-layout:fixed;border-collapse:collapse;width:300px;background-color:#E9E9EB;font-family:-apple-system, Helvetica, Arial, sans-serif;" class="lp-rich-link-emailBaseTable" cellpadding="0" cellspacing="0" border="0" width="300"><tbody><tr><td vertical-align="center"><table bgcolor="#E9E9EB" cellpadding="0" cellspacing="0" width="300" style="font-family:-apple-system, Helvetica, Arial, sans-serif;table-layout:fixed;background-color:rgba(233, 233, 235, 1);" class="lp-rich-link-captionBar"><tbody><tr><td style="padding:6px 12px 6px 0px;" class="lp-rich-link-captionBar-rightIconItem" width="36"><a rel="nofollow" href="https://www.proli.net/2020/04/03/developing-kwin-wayland/" draggable="false"></a></td></tr></tbody></table></td></tr></tbody></table></a></div></div><br></div><div dir="ltr"><br><blockquote type="cite">On May 8, 2024, at 6:31 PM, Gerion Entrup <gerion.entrup@flump.de> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Hi,</span><br><span></span><br><span>I'm interested in playing around with KWin's source code (especially with the </span><br><span>built-in tiling feature). However, I find it kind of complicated to find a good </span><br><span>workflow for development (I'm on a desktop with Plasma/KWin on Wayland).</span><br><span></span><br><span>I tried to research what is possible and see this possibilities:</span><br><span>- Replace the current running KWin. I'm pretty sure that this is not a good </span><br><span>idea, especially, when I include buggy code that segfaults, etc.</span><br><span>- Start a nested KWin. I saw this here [1] and it seems to work quite well. </span><br><span>However, I need some kind of launcher. I tried krunner but it disappears and </span><br><span>pressing the keybinding just opens the "real" krunner. A terminal emulator </span><br><span>also works but opening new windows there is not quite comfortable.</span><br><span>- Start KWin on another TTY. I did not try this but it seems quite complicated </span><br><span>to change the whole context every time to test something.</span><br><span></span><br><span>So, what is your workflow? Is it possible to start a whole Plasma session </span><br><span>inside a nested KWin and how are keybindings captured there?</span><br><span></span><br><span>Best,</span><br><span>Gerion</span><br><span></span><br><span>[1] https://community.kde.org/KWin/Wayland#Starting_a_nested_KWin </span></div></blockquote></body></html>