So quite excited about this.
So quite excited about this.
Recent HN discussion: https://news.ycombinator.com/item?id=14676625
I haven't tested it yet, but bookmarked the HN thread because I want to try a tiling window manager, but decided to make until there's a good one for Wayland.
I like being able to configure my computer my own way.
EDIT: Not that i3 lacks features, I've not found much I couldn't do with it. But it doesn't come packaged with a lot of other software like a DE does.
More and more i feel what is needed is not bigger DEs, but more useful, and non-DE oriented, standards.
Don’t expect too much, GNOME considers proper HiDPI out of scope and only supports 96dpi and 192dpi (and other integer multiples)
Everything inbetween is handled by rendering at 192dpi and then downscaling.
So if you have a 144dpi 4K screen, and try to run minecraft, minecraft will run at 6K resolution and be downscaled.
The result is horrible performance.
The only solution for proper HiDPI support for multiple monitors today is Qt, which supports it even on X11.
Argh. That's depressing. But still, Gnome with Wayland is the only DE I've seen that gracefully handles multiple monitors with different DPIs.
All other platforms – Windows, Android, Qt, the web – use the opposite model.
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.
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