Despite the fact that I have been staying in KDE for 2 or 3 months now, I am just discovering little by little what this environment has.
One of the options offered, or at least some forum programmers on esdebian, and some other forums commented on being indispensable, is tiling, which according to some times I read, is only offered by managers such as openbox and some others that I do not remember their name , but always making that distinction, I don't switch to KDE for not being able to offer me that function.
Today, exploring the configuration options, I came to the following:
System Preferences> Window Behavior
Within
window behavior, advanced tab, select enable mozaico
and the result is:
For those of us who did not know about this function, here it is, it seems useful to me since the windows are arranged automatically.
regards
Interesting, I didn't know 😀
In the next version they will remove it: /
Completing your information:
- Openbox is not a tiling manager, there are manuals where you can achieve something similar by configuring certain parameters but it is not tiling.
- Here you have a list of tiling managers in the archwiki .
regards
Openbox does not bring it by default, if you can add it but it is not an option included, it is brought by managers such as xmonad, wmfs2, musca, subtle, wmii and obviously the dynamic managers, on KDE, it is not something new, it has it from versions previous ones and I think that aesthetically it looks bad and I think it is a good idea that they will remove it as I see vicky's comment.
Greetings.
Note: Mosaic appears as a mozaic. Check to see if this appears in KDE, or is it a misspelling.
regards
Indeed, it is a spelling error, it is mosaic, I did not know how to correct it.
regards
Setting the environment variables so that the applications look good -that is, with KDE theming- I think that dwm or Awesome3 (or wmii, musca, scrotWM, Ratpoison, i3 or any other WM) are a much better option to use an oriented environment to tiles than KDE, with how heavy it is 🙂
It is true, in the next version or I think that in 4.10 it will disappear, because the code has not been maintained, but as I read it is expected to be reimplemented later as a plugin for kwin easier to maintain. All that info is on Martin Graesslin's blog.