Well, as @DevNul mentnioned here and @Bryanpwo mentioned here we should start a new topic on making i3wm for EOS.
That’s my favorite WM so far, and I would like to get involved in creating configs, but I wan’t to mention that I’m not the best in ricing i3 - I’m used to very raw form of this WM. So much to learn for me.
So I think in the beginning we should discuss the overview of how it should look like. In my opinion, we should stick close to what has been accomplished with XFCE - very simple, understandable for newbie, yet beautiful and modern enough that will not scare newcomers.
So I think:
no aggressive colours (grays maybe?)
nice icon set
i3lock with blurring
wifi, sound, power control plugins/icon sets
basic shortcut set with cheat sheet displayed at desktop background (idea from manjaro)
some program starting manager - I use rofi
Anything else which I forgot to mention from basic set?
I was going to recommend polybar for it is easy to use the same config on another window manager if one is interested to try - instead of learning how to script dzen2 But no aur pkg’s so poly is out of the question
Make some nice terminal color scheme - https://terminal.sexy
maybe staying close to EOS colors with the theme
Go with a couple lightweight terminal programs and let 'em install the rest on their own. Basically I think a new user need a browser and file manager and the rest is to each his own.
Some nice color scheme ideas can be found with Archlabs/Bunsenlabs. They both have some dark themes with grey or muted colors for accents. Very soothing for my aging eyes I think that having a few options written into the configs would be helpful for those new to i3. Appearance and compositing choices that can be commented in or out as the user chooses. One of the hardest things in learning a new WM is seeing that stock is not all there is and how to implement changes.
An example would be whether or not to have title bars on windows or a choice of i3bar/polybar/tint2. (Polybar with jgmenu is my choice.)
Beyond that, I have changed the keybinds to be more logical to me so my configuration ideas may detract from an “original” i3 experience. I do love this idea, though. There are a lot of Openbox distros in the world to learn from, but not so much for tiling WMs.
Hey @patryk, great topic. Thanks for creating that. Great suggestions so far.
I hope I can contribute in some way. That said I have a lot to learn regarding dotfiles and how they interact with each other.
i3-gaps is in the repositories and gives that little extra touch so I personally would prefer that over stock i3, but that’s just my opinion.
Speaking of colors… would pywal be an option? It changes the colors on the fly but that’s maybe to comlplicated for an easy setup? A color scheme based on the EOS-logo would be pretty awesome.
As @Bryanpwo mentioned maybe one or two AUR-packages would be possible? Or as an alternative to Polybar maybe i3blocks?
Just to mention it, there is compton for some eyecandy but it would be a little to much for this setup.
What I like about i3 is the efficient use of screenspace so I would prefer no titlebars.
Some good readable fonts for the terminal are quite important as for the graphical parts. Lxappearance to change the theme maybe?
Personal opinion offcourse i would choose for a basic i3wm. basicly most from repo.
eyecandy is nice, but personal is just how to configure in function introductions that people can help go intoo i3wm, with a good base that works. i think for now to start from a base for the net-installer. From there evolve to a higher level since net-install relative is young.
One thing community also needs to choose is which packages wants, like terminal, file manager and text editor.
I3-wm doesn’t come with any of them, so deciding on having the same than xfce4 or adopt a more minimalistic approach etc. It’s your choice!
So true, but I think we have to find that sweetspot between usability out-of-the-box and people’s choice. Definately @ringo list of software is way too large, and should be shrunk to absolute minimum (I’m talking about the list in GitHub repo).
Best would be first-run script asking user for his software of choice and suggesting community choice for those who don’t have their favourite programs yet, and then after making choices install them so the system won’t be bloated by default.