Some comments, I’ll be mostly listing negatives to save time even though this looks awesome:
The fzf-based app launcher leaves unnecessary terminal windows behind when launching some apps like pamac-manager. Have you tried wofi et al? This seems rather limited in features. You might be interested to see what bspwm edition did with rofi. You can put execution, app launching and window switching in combi mode and then put file search in another script: Rofi-finder - YouTube
Both firefox and qutebrowser? I would use firefox and add a plugin for keyboard driven usage
Quite a lot of affects, they perform poorly in a vm. That transparency blink when window focus changes is super distracting, but probably better if it performs better outside of a vm. I would consider toning this down
Top panel is well executed
Firewalld is a nice touch
Lack mouse based option to close windows. Have you considered adding some option? (no is a valid option, but know that it is not the only one)
No gui filemanager. Interesting choice. Ranger is always nice. Did you have some kind of volume mounting solution selected?
Wallpaper gets cropped on low resolution display. Not sure if anything can be done about that.
The iso is surprisingly big considering how little apps are shipped. You might want to consider focusing on a single toolkit (qt or more likely gtk)
Printing support is enabled. You may want to drop that from the minimal version
Image previews don’t seem to work in ranger
This looks very promising, but you might want to consider what is your target audience? Is this aimed at minimalists? You can get meeaningfully more minimal if you want. Or should this be accessible to newcomers? If yes, you might want to develop the mouse support further and maybe add a gui filemanager. And maybe add micro in addition to or in place of neovim.
I think the reason is, that there is no desktop entry for pamac. /usr/share/applications/org.manjaro.pamac.manager.desktop only contains:
not really. you’re not the first to favor wofi, so probably I need to take a look
ok. have not been using firefox for years, can you recommend an addon?
I think it is only one and yes, depending on the vm it seems distracting. will tone flashfocus down a notch.
haven’t considered and been using i3 for a long time without ever asking myself if that is possible. what are you referring to?
I didn’t think of that. Will have a look.
I think it is already marked as “extra”, but I’m just only building the full image atm.
I think this only applies to very low res (1024*768) - would ignore that…
for me one of the only pains working with sway/wayland was, that I couldn’t just install stuff and it worked out of the box, but had to follow rabbitholes of threads with people dealing with the different stuff you have to install and env variables to set. my aim was to not have that, but things to “just work” - therefor I added qt libraries too.
I mean: it foremost is aimed at myself so what you see here mainly is how I use my OS.
I think neovim I added just because either the arm or Simons branch already had it and I thought: “neat”. I didn’t know that before and I don’t know micro. I used those text editors only for commit messages/tinkering with configs, so I never really cared. So I’m depending on external opinions there…
I don’t use Firefox that way, so can’t definitively recommend, but this had good reviews:
In bspwm I added a global close button to the top panel, and added a desktop menu that contained an item for closing windows. Something akin to a shortcut for xkill in top panel could work too. Or three finger downward swipe? Those kinds of things. I3/sway has built-in actions with it’s titlebars, but you aren’t using those so that’s not available.
Excellent reasoning, you also get ootb theming that way!
Just installed. Latched me straight onto my network without me needing to config anything, which is cool. No problems to report thus far. I’ll carry on customizing and adding apps etc and see what transpires.
It even comes with those see-thru window jobbies outta the box. Nice.
Some remarks that I’ve also mentioned in the other post on the beginning of the Sway edition for x86/64…
Some alignment has taken place between the look’n’feel of both Sway editions; also the Sway ARM edition has been improved by work done here; so I’m really quite happy to see both evolve and learn from each other.
On the Sway ARM edition we sometimes have a different selection of default tools - e.g. we went with the Wofi launcher from the beginning. Also the default themes (matcha-green, matcha-blue) are a bit more aligned to the look’n’feel of the other Manjaro (ARM) editions (with having me figure out color values from screenshots back in the days). This is not a big obstacle and might be also aligned between both editions after some discussion…
One thing that is quite different is the packaging (and distribution) of the manjaro-sway-settings. In the ARM edition we decided a couple of months ago to not have a dedicated package for the default settings, which has the challenge that updates to the default theme doesn’t reach users automatically. But on the other hand we also solved the issues with overwriting customization a user might have done on it… so both approaches have their pros and cons and I would like have a common understanding here, which might also easy converging the Sway editions moving forward…
In theory, any settings package, should not change anything in an existing users /home.
I have always preferred using overlays, because it’s easier to test and quicker to get into production when creating images and new installs, than a settings package is.
A settings package first needs to be packaged, then uploaded to the repo and then tested with a new image created. Also, some settings packages might contain changes to certain files that another package actually own, making it conflict. The overlay, just overwrites that file.
The idea of the settings package is that you can test the new settings without building an image by just creating a new, temporary user account. But yes, in practice, overlay is quicker and doesn’t require occasional pushing packages straight to stable branch.
If they do, that is just a mismanaged package. In x86, the policy is to use the overlay for the files owned by other packages, and settings package for the rest. All files outside /home should be owned by some package.
This might be a limitation of the terminal emulator used. In ARM edition we use termite as it is less on system requirements, but may also lack some of the advanced feats. When using a more modern terminal emulator such as alacritty or kitty image preview should work out-of-the-box…
There I’m also a bit on/off with the choice in the ARM edition. The most lightweight solution would be pcmanfm, but this offers not much additional features and also seems to have some issues with opening files in default applications (e.g. pdf) in my installation. So I went with the thunar application, which is a bit more advanced. Nemo / Nautilus have a bunch of additional (cinnamon/gnome) dependencies they need to get working… not sure if that still fits the idea of such a lightweight desktop edition…
Any suggestions for default apps are welcomed though. I usually tried to provide a CLI and UI variant for the most important utilities on a desktop.
This is the tiniest niggling thing, but might be worth considering as a default.
What’s the information you are most likely to want to see the most often? At least for me, it’s the clock and my eyes (well in my opinion) should be guided to it. So…I simply added in the style sheet, background-color: darkblue;
Again, almost anyone that dares to run a tiling based environment should be able to do that, but if you feel my theorem is correct, why should everyone have to do it?
Let me reiterate…I am so happy someone is finally making a spin/distro with sway!