KLV-Spectr-RT with full real-time kernel 6.1.38-rt13c

[geo_c]

In fact @rockedge , here they are:
.
.
Placed in /root/spectwm.conf (note the program pavucontrol is already defined, just add the binding):

Spectr-keybindings-config.fake.gz

(3.38 KiB) Downloaded 38 times

.
.
gtkdialog cheat sheet:

Spectr-keybindings-DPi7.fake.gz

(2.29 KiB) Downloaded 53 times

[Sofiya]

As for the bars and opening the browser on the full screen and so that the panel is not visible, I will tell you what to do. first create a script
"xdotool" dependency

in ~/.config/spectrwm/scripts/fullscreen-toggle.sh

Code: Select all

#!/bin/sh
xdotool key super+b
polybar-msg cmd toggle

in ~/.spectrwm.conf write down

Code: Select all

 program[toggle_bars] = ~/.config/spectrwm/scripts/fullscreen-toggle.sh
 bind[toggle_bars] = MOD+Shift+f

The MOD+b hotkey shouldn't have anything to do - this is a standard key to show/hide the spectrwm bar. So @geo_c don't use standard keys
restart MOD+shift+r

pressing MOD+Shift+f will hide our polybar
and super+b will hide the spectrwm bar

-----------------------------------------------
also, when watching a movie in full screen mode, the browser opens to the entire window without a polybar when you press MOD+Shift+f
That's all I can do for you

[Sofiya]

I just have a busy head and I forget to provide you with some things in full
watching a movie in full screen mode

[rockedge]

@Sofiya the configuration works much better on bare metal. I have it running on a DELL PowerEdge R210 II rack server and the desktop is correct.

I'll have to make some screenshots

[Sofiya]

@Sofiya the configuration works much better on bare metal. I have it running on a DELL PowerEdge R210 II rack server and the desktop is correct.

I'll have to make some screenshots

yes, I just forget to mention that Qemu distorts the sizes of windows and takes them to the side even for a regular window manager

[Sofiya]

I hope nothing else escaped my little head, and I provided everything to you

[geo_c]

I hope nothing else escaped my little head, and I provided everything to you

You have made this OS the most enjoyable computing environment I've ever experienced!

@rockedge if you try and use that gtkdialog script for the keybindings, you may have to reduce the font size, because I made that script on a high resolution display.

I just copied this squashed version, made from a PFI build of beta2 with two extra layers of upper_changes incorporating all @Sofiya's additions, onto another laptop, and man does it look nice! This HP laptop always looks crappy because of the display, which is just not high res or particularly nice on the color side. But this Spectr looks gorgeous on it. Airedale with Xfce never looks good on this machine.

Anyway loads of fun so far.

[Sofiya]

[rockedge]

here's 4.4 just before upgrading to 4.5:

2023-10-14-202752_1280x1024_scrot.png (126.21 KiB) Viewed 4002 times

2023-10-14-204022_1280x1024_scrot.png (111.82 KiB) Viewed 4000 times

[geo_c]

I've been bouncing back and forth between Spectr and Bspwm, and I definitely have a sweet spot for Spectr. Maybe tweaked a little bit Bspwm would be about the same with a few more keybindings, etc.

I like how in Bspwm the windows within a tree can be resized, but all in all Spectr seems easier to get the workflow once comfortable with resizing the master/stack ratio and shufflng windows around. Awesome also has it's strengths and feels like it rides the fence between a traditional tiling wm and floating wm.

Though all of these KLVs are fast and efficient, even with Xfce Airedale is very responsive, Spectr still wins for me.

Next on my list is take a crack at @wiak's Swayland. That looks like another I could build with a script instead of using an iso or PFI.

So far the only one I built from a script is Bspwm.

[Sofiya]

to lock screen

Code: Select all

 program[i3lock]            = i3lock -c 000000   # i3lock -i /root/Pictures/*.png  /  i3lock -c 000000 
 bind[i3lock]               = MOD1+l             # MOD1 key - alt
 

[rockedge]

Next on my list is take a crack at @wiak's Swayland. That looks like another I could build with a script instead of using an iso or PFI.

So far the only one I built from a script is Bspwm.

I have built a few using the build script/PLUG and then made like 20 instances of it using KL-multi. Really fun and cutting edge stuff. Great platform to get some expereince with tiling WM's, Wayland, Pipewire

[rockedge]

@Sofiya @geo_c I have an error on the Spectrwm bar that I have never seen before. Just appeared in the latest version I but together with most of the additions from this thread.

Code: Select all

total exceptions:1, first exception; could not find touchpad_toggle

[Sofiya]

@Sofiya @geo_c I have an error on the Spectrwm bar that I have never seen before. Just appeared in the latest version I but together with most of the additions from this thread.

Code: Select all

total exceptions:1, first exception; could not find touchpad_toggle

in /usr/local/bin/

[rockedge]

@geo_c we need a binding to activate the control cheat-sheet script. With perhaps a dedicated floating position

2023-10-15_1920x1080.png (54.66 KiB) Viewed 3911 times

[geo_c]

@geo_c we need a binding to activate the control cheat-sheet script. With perhaps a dedicated floating position
2023-10-15_1920x1080.png

I'll see what I can do on the window position. I believe I can put that in the gtkdialog script as I've used scripts with coordinates after the gtkdialog command. The real question is font size, as there is a lot to fit on the screen, but on higher resolution monitors the text gets really small. if set to fit lower resolution monitors.

Also, what I experience is when the window opens the text has a lot of space between it and the top of the window, but once floated and dragged the text falls into postition.

I'll do some experimenting.

[Sofiya]

What we managed to achieve with our program GTK3: gtkdialog-splash , you forget that we have such a program. especially since we have it /usr/local/bin/mksplash
viewtopic.php?t=6855
my resolution is 1366x768 you can try to position the text differently and make it pop up in the center by pressing a hotkey
close by left mouse click

[Sofiya]

Me and@Fredx181 worked really hard on it and to be honest it’s a shame that you don’t use it

[rockedge]

@Sofiya I like mksplash a lot. Use it on KLV-Airedale to make all kinds of splash screens and info boxes.

Good stuff. I like the cheet sheet splash. Going to use it in the rootfs and once we know what packages need to be installed during the initial build we can fix up the PLUG file for KLV-Spectr

[Sofiya]

The most normal font and the correct lines with it are "Monospace"

[geo_c]

Me and@Fredx181 worked really hard on it and to be honest it’s a shame that you don’t use it

Yes, I only don't use it because I'm dense and unaware. I could tell you all about it, but then this would become more like a therapy forum. So I'll spare you....

I'm using it now, and it's so much easier than what I was trying to do.

I'm about to post my edits, and yes, I already figured out to change the font to mono.

[geo_c]

Here are my edits, I'm leaving the font size at 9, though on the this machine which is something like 1920x1080, it comes out really small. None of my other machines are like that though.

If I wasn't already neglecting my day job, I would try and write a script that greps the monitor size and chooses the correct fontsize, HA! Yeah, that would take me about 7 months to figure out how to do.

I'm including my program/binding definitions, and the gtksplash script. I'm not working with @Sofiya's latest changes that allowed full screen video viewing.

The splash screen still comes out on the left, I'm not sure it should be centered but you can see that I included a keybinding to open the splash screen [MOD+MOD1+k] and at the top of the list included the keys to drag the window around.

So here they are:

Spectr-keybindings-config.fake.gz

(4.6 KiB) Downloaded 37 times

Spectr-hotkeys.sh.fake.gz

(2.53 KiB) Downloaded 52 times

[rockedge]

To test out a quick example I set MOD+z for the key bindings splash. I will try out @geo_c 's configuration as well

2023-10-15-190312_500px.png (240.04 KiB) Viewed 3860 times

[geo_c]

To test out a quick example I set MOD+z for the key bindings splash. I will try out @geo_c 's configuration as well
2023-10-15-190312_500px.png

It occured to me that I don't have the i3lock keybinding listed in the splash, but I do have it included in the config file. Whether or not it should be included in the list is good for me either way. Easy enough to type into the script.

Code: Select all

 bind[i3lock]               = MOD1+l             # MOD1 key - alt 

[rockedge]

in the vastness of Github I came across darls-10.0.84, which is somewhat similar to our Spectrwm
production @dimkr

Yes, dimkr referred me to it so I could look it over and perhaps borrow some ideas from it!

[wiak]

Yes, dimkr referred me to it so I could look it over and perhaps borrow some ideas from it!

I see it is a variant of Vanilla Dpup, so not a KL, but uses dwl for Wayland (like dwm for X) so the configs would be relevant.

But here is my view overall:

If you looked in build_firstrib_rootfs code you'd see the following variable assigning code plus comment to determine f_ plugin(s) being used and the two plugins that will then be sourced automatically during build:

Code: Select all

firstribplugin="f_00.plug"			# contains extra commandlines to execute in chroot during build
									# e.g. xbps-install -y package_whatever (for Void flavour)
									# e.g. apt install -y package_whatever (for deb-based flavour)
									# e.g. pacman -Sy package_whatever (for Arch-Linux-based flavour)
[ "$4" ] && firstribplugin="$4"		# optional fourth parameter specifies alternative f_00 plugin name
firstribplugin01="f_01.plug"		# This second plugin will be sourced immediately after main firstribplugin has finished its work
[ "$5" ] && firstribplugin01="$5"	# optional fifth parameter specifies alternative f_01 plugin name

It is very apparent to me that a lot of KLV-related building has been going on, and for the most part the main KLV distro is built using exactly the same early f_plug code. The extra is pretty much always to do with different window manager being tested (or wayland compositor) and whatever extra apps prove useful in that scenario. Hence it is easy to use second plugfile f_01 per the above, since that is also auto-used during chroot main build. However:

There are some very strong reasons for NOT going for an absolutely in-common f_00 initial plug nevertheless; for one thing, there is always a likely tendency to put more in it that the more frugal-minded amongst us would like, hence I resisted the idea of splitting the f_plug for KLV-Swayland into two or three separate plug files (reason for three plug files would be that user setup via /etc/skel generally comes at the very end and could be arranged since any file named f_whatever auto gets copied into firstrib/tmp directory prior to main chroot build and can thus be sourced by any other main plug file via ". /tmp/f_whatever"). However, I did carefully try to collect main KLV code we all basically use into the top section of my f_00 plugin since that provides me with a general template for easier other type of wm/compositor builds should I do these later).

[wiak]

Though I have in documentation sometime back recommended using special filename format to identify author and revision information, I never wanted (and don't) want to over formalise any build conventions unless particularly useful. Best is to always keep as simple/general-purpose as possible, which is also why the FR initrd proves so versatile in booting so many alternative root filesystem types. So we all know, the FIrstRib build system has only a few formal requirements:

1. Build plug files must be named with first two characters being f_
2. Kernel boot parameters all start with first two characters w_ (the w somewhat being taken as first letter from wiak, but also historic since initrd booting distro was previously called WeeDog as a hat tip to this forum, but since the name 'Dog' resulted in confusion with other distros here it was a mistake so reverted to original name FirstRib.
3. Addon modules (compressed as sfs or normal directories) are all named with two numeric digits signifying their overlayfs layer
4. 'Most' FirstRib utilities I've created are named to start with first two letters wd, which are usually placed in /usr/local/bin and a list of them thus found simply by entering wd followed by tab key in a terminal. A few annoying-to-me early exceptions to that naming convention is mount_chroot.sh, umount_chroot.sh, modify_initrd.sh, and wiakwifi; these came very early when development was so fast I didn't have time to streamline all naming conventions though f_ and w_ and double_digit were already set in stone. I chose not to rename the likes of mount_chroot because they are now used in other scripts so would be a menace; that is always the problem with trying to ensure backward compatibility as development proceeds - hindsight is a great thing. Fortunately, most early decisions have proven to be very sound.

[geo_c]

Just wanted to say that Nitrogen is a fantastic background setter. It allows you to choose directories or choose a directory recursively and loads thumbnails lightning fast. So much easier than Xfce background setter for instance.

[Sofiya]

[geo_c]

I cleaned up this hotkey splash screen quite a bit, corrected some typos, added all the key bindings that are in my 4.4 system, and made a few variations of colors, all with DejaVu Mono bold 9. Attached is an actual .gz with the files, including the keybinding-config

One more note, my keybinding to launch the splash screen ( MOD+MOD1+k) is configured in spectrwm.conf to look for /root/Startup/Spectr-hotkeys.sh

If you don't want the splash in startup but still want to launch it with MOD+MOD1+k, just change the path to your location.

Spectr-hotkeys-colors.tar.gz

(2.52 KiB) Downloaded 25 times