Developing KWin, starting nested KWin

[Aleix Pol]

No, it will be the same settings as any other, as it's picked up using
the standard directories. You can probably override XDG_CONFIG_DIRS
for it or something like that.

I recommend using a nested kwin until you're somewhat confident that
the feature works. It makes for an  easier experience.

Aleix

On Thu, May 9, 2024 at 11:58 PM Gerion Entrup <gerion.entrup at flump.de> wrote:
>
> Thanks for the link, it was an interesting read!
> It, however, focuses a little bit on the libinput and DRM hacking inside KWin,
> which requires starting in a TTY, and does not so much explain a more
> complete workflow for nested KWin. A few additional questions that came
> to my mind:
> - Do virtual screens exist in a nested KWin? And how can I switch them?
> - Can I give a nested KWin other settings than the outer one? Where can I configure them?
>
> Best,
> Gerion
>
> Am Donnerstag, 9. Mai 2024, 01:11:59 MESZ schrieb Gabriel Klavans:
> > I found this post nice for some inspiration
> >
> >
> > Developing KWin Wayland – TheBlindCow
> > proli.net
> >
> >
> >
> >
> >
> > On May 8, 2024, at 6:31 PM, Gerion Entrup <gerion.entrup at flump.de> wrote:
> >
> >
> > Hi,
> >
> > I'm interested in playing around with KWin's source code (especially with the
> > built-in tiling feature). However, I find it kind of complicated to find a good
> > workflow for development (I'm on a desktop with Plasma/KWin on Wayland).
> >
> > I tried to research what is possible and see this possibilities:
> > - Replace the current running KWin. I'm pretty sure that this is not a good
> > idea, especially, when I include buggy code that segfaults, etc.
> > - Start a nested KWin. I saw this here [1] and it seems to work quite well.
> > However, I need some kind of launcher. I tried krunner but it disappears and
> > pressing the keybinding just opens the "real" krunner. A terminal emulator
> > also works but opening new windows there is not quite comfortable.
> > - Start KWin on another TTY. I did not try this but it seems quite complicated
> > to change the whole context every time to test something.
> >
> > So, what is your workflow? Is it possible to start a whole Plasma session
> > inside a nested KWin and how are keybindings captured there?
> >
> > Best,
> > Gerion
> >
> > [1] https://community.kde.org/KWin/Wayland#Starting_a_nested_KWin
>