Just out of curiosity: why is this flagged as ARM related? In the arm-profiles repository we already have a Sway edition and from the discussion above I conclude that the topic is centered around making a Sway edition (ISO image) for x86/x64 PCs, isn’t it?
EDIT: don’t get me wrong I am highly interested in the work for the x86/x64 edition and hope to get some ideas or share some know how (as I was creating the arm profile for it)… but I just want to make sure that there won’t be an additional or alternative ARM profile for Sway…
I pushed iso-profiles and desktop-settings to sway branch.
Probably it makes sense now to create a sway subgroup in the packages/community group to collect greetd, greetd-gtkgreet and manjaro-sway-settings there.
iso builds including manjaro-sway-settings from my online repo
greetd is installed but does not start, maybe this is a live environment thing or is it because the buildiso does not support greetd?
I don’t know how to provide the changed /etc/greetd/config.toml, since when I try to deliver it with manjaro-sway-settings it generates an error since greetd also provides it
You might have to enable the greetd service in the ISO image. Not sure how to do this in those live CD images, but on ARM profile there was a custom section for services that should be started on boot…
Desktop settings package should only install stuff to /etc/skel for the most part. If you need to overwrite system files, you should use the desktop-overlay/etc/greetd/config.toml in the iso-profile. Note that overlay is only for overwriting files, you should avoid putting there anything that is not provided by some package.
Services are enabled in profile.conf in the iso-profile. Since greetd is not directly supported yet, set the the display manager to none and just put the greetd service to the right array.
If you need to configure autologin for the live session, do so by using the live-overlay directory.
Can you upload the PKGBUILD for the desktop settings somewhere?
Found out how I did that back then.
Wofi seems to use the gtk-theme. Since I didn’t set it, it looked strange. With the desktop-settings scheme you can set the theme. Now it looks great.
Since there already exists a manjaro sway edition for arm, we could decide to just have one style and adapt over to the already existing styling. Let me know what you think, keep existing or adapt to manjaro-arm version.
Uniformity is a positive, but not the highest goal imho. Overall it looks quite nice. Personally I would drop the powerline elements from the panel. I used to do those in bspwm edition with lemonpanel, but later felt that more simple and subtle design can be less distracting, and utility is what many tiling wm users appreciate.
Looks very nice, indeed. Any major things you did change from the Manjaro ARM Sway configuration (noticed some changes for overlay help and application launcher so far)…
I used waybar as in the arm config but made some minor changes to the style and some more things clickable. What alternative panel would you have preferred?
Overall, I dropped a bunch of GTK* tools, that I don’t think we need and replaced them with tui-applications I like more.
I took the termite config from the arm profile because I’ve got a pre OpenGL 3.x notebook (thinkpad x200) where I was testing the iso and have been annoyed by Kitty not working.
I am using man for the help-dialog, because I don’t see a big benefit in what appelgriebsch did with the custom menu - or perhaps I just don’t really understand it.
Overall I changed some things around the “look and feel” and hope they’re a bit more consistent. I never used your arm built, but what I really liked is, how “clean” everything looks. Wanted to keep that.
well, do you think its worth it? i have been using kitty in sway for ages without problem, until i was on said notebook. termite was primarily ‘already done’ for the arm sway edition.
Well, I’ve always needed to build the git version of kitty from AUR to use it at all . I don’t think terminal applications should depend on certain hardware.