I use it because the Ubuntu UI uses so much resources (from my experience) and my computers are generally trash.
That's why it's fast, but badly coded applications can be less stable.
Yeah I mean I don't think it's a perfect division of say if your laptop/screen has 1920x1080 and you want to divide that by some known resolutions.
Good to know about being able to define layouts. Would be cool to just call it in another tab (number bottom of screen)
Because it's the terminology used by i3. You define "placeholders", and which criteria i3 should use to decide which placeholder a given window should open in. Here are more details [1]
> Good to know about being able to define layouts. Would be cool to just call it in another tab (number bottom of screen)
I'm not sure what you mean. You can switch workspaces in a key definition, so you certainly can bring up a layout on whatever workspace you want with a given keypress.
If I could have the predefined tiles and bind it to a key combo and then they would open up in a new panel (like 2)
Anyway thanks for the links/explanation
Regarding i3-wm is there such a thing as pre-defined resolution tiling for the sake of UI testing? That would be pretty neat.
Imagine a bunch of windows that were tiled (think mosaic) according to known device resolutions like 320x680 (or something like that for mobile devices) then you could have say a browser open in each tile (with local dev url) and refresh/shows the UI as displayed on every resolution that would be impressive.