Right, as of a about a month ago, I think I can finally say that I've switched permanently to #Wayland from #X11. I've tinkered with Wayland for several years but always came back to #X since there were too many glitches, or things in development, which made for a shaky experience when compared to the #XDesktop. Although there are still some minor things, like, say #Birdtray for #Thunderbired not quite working as it should, everything else is at least as good now for the stuff I do.
so... yesterday...
i got my #wminizer script working.
today, i intend to do a proper write up of it.
this is not that write up.
this is just me spouting a little victory song and dance. (and may get some passages for copypasta to the proper write up if i just let my fingers fly over the keyboard while thinking about it...)
wminizer is to wmrotate as wmrotate is to wm.
wmrotate has a while loop with a list of window managers to run in sequence. -- (why? wmrotate lets you cycle through window managers without losing your entire current Xwindows gui session and all programs currently running. cool huh?)
wminizer has a while loop with a list of wmrotate scripts to run in sequence.
why?
wmrotate is stuck on the one unchangeable list for the xsession. so if you want to add another wm to the list, or remove one, or change their sequence, you have to wait for a restart of the X11 server.
wminizer, allows the sequence to be changed.
wmrotate, to switch to the next window manager, simply kill the current window manager, and the next loads instantly.
wmrotate still works the same in wminizer. kill one wm to move to the next.
to implement a new list of wm, without losing your x session and all running programs, just kill the wmrotate script currently on.
in the initial default configuration, wminizer uses just wmrotate1 and wmrotate2, but you could have more elaborate arrangements.
just having 2 wmrotate scripts is sufficient to be able to switch between them to enable a live config change.
the two do not even have to be evolving versions of the same to toggle to.
one could be your main sequence that you edit, and the other, just a fallback to bounce past when refreshing the main one to be active with new edits.
as in, make edits to your wmrotate1, kill wmrotate1 so you're in wmrotate2 then, which might just have openbox/dwm/twm in it, which you're only in for a second before killing it, to get into the new wmrotate1.
or could be both the same, just one catching up with the other, edit by edit.
also... wminizer's just the/ a first increment more advanced than wmrotate.
all kinds more conditionals and syntactical conveniences and more elaborate arrangements of which window managers starting when or how, specifying, all sorts of if-else'ing possible...
but for now, for my bash-fu, this is accomplishment enough, for me. ;D ... more will come in due course.
so... i may as well point out the parts here in this ramble...
example wmrotate1 script:
#!/bin/bash
while true
do
icewm
dwm
herbstluftwm
dwm
spectrwm
dwm
done
example wmrotate2 script:
```#!/bin/bash
while true
do
dwm
spectrwm
openbox
i3
done
````
either of which can be used as a standard wmrotate on its own.
example wminizer script:
```#!/bin/bash
while true
do
wmrotate1
wmrotate2
done
```
and then of course have it be launched from some kind of Xsession or xinitrc or whatever other way you startx or whatever and it reads the right thing...
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/Xresources
sysmodmap=/etc/X11/xinit/Xmodmap
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f "$userresources" ]; then
xrdb -merge "$userresources"
fi
if [ -f "$usermodmap" ]; then
xmodmap "$usermodmap"
fi
if [ -n "`/etc/X11/chooser.sh`" ]; then
command="`/etc/X11/chooser.sh`"
else
failsafe="yes"
fi
if [ -d /etc/X11/xinit/xinitrc.d ] ; then
for f in /etc/X11/xinit/xinitrc.d/?* ; do
[ -x "$f" ] && . "$f"
done
unset f
fi
if [ -n "$failsafe" ]; then
wminizer
xclock -geometry 50x50-1+1 &
xterm -geometry 80x38+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login
else
exec $command
fi
export PATH=$PATH:/home/digit/bin
wmrotate & wmpid=$
wait $wmpid
(note that's basically just like a defualt devuan Xsession/xinitrc thingy, with twm in the fallback section replaced with wminizer, and the wmrotate and wmpid stuff added at the end. ... remember, my bash-fu no good, this was just the first working jank. can be cleaned up more yet. ... and should be for the "proper" write up. but for now, this is what you get from me. heh.)
okay, that'll do for now.
this twig snapped in the forest,
and now some can hear it.
so it definitely happened.
;)
yeah, i'll get wminizer cleaned up and put in a public hosted git repo with a helpful readme.md and nice accoutrements and things.
"soon".
;)
and then further development on the more elaborate arrangements can proceed.
https://bbs.archlinux.org/viewtopic.php?pid=320776#p320776 was the original inspiration for wmrotate. props to gazj and the others who helped in that thread, from all those years ago.
ps, i was at first going to call it wminator... then the whimsy of the name wminizer struck and stuck. get it? sounds like womaniser. :3 ... not there's no valid reason or connection, to womanising... but wminizing, i guess is a facilitation of promiscuity when comes to window managers. ... yeah, it fits. lol.
#windowmanager #windowmanagers #desktop #geekings #scripts #wmrotate #wminizer #foss #X11 #xinit
https://linuxnews.de/fedora-workstation-41-definitiv-ohne-x11/ #fedora #x11 #Wayland
Fedora Workstation 41 definitiv ohne X11 - LinuxNews.de
@studi0
♲ David Revoy - 2024-05-30 15:46:25 GMT
Here is my new GNU/Linux distribution guide about Debian KDE 12, the right GNU/Linux distribution for professional digital painting in 2024! Also about three major problems with GNU/Linux distros that will drive away all professional artists, IMO, and how I got kicked out of the Fedora KDE ecosystem with F40, which imposed Plasma6 and Wayland. I hope it helps other artists here!Blog post: https://www.davidrevoy.com/article1030/debian-12-kde-plasma-2024-install-guide
It looks like the #cube is back.
https://www.phoronix.com/review/wayland-nv-amd-2023
I heard (regarding other aspects) wayland has changed a lot in the past couple months.
anyone know where rolling benchmark comparisons or more recent comparisons (perhaps even across more hardware) ma be?
#freesoftware
#wayland #vs #x11 #waylandvsx11
#performance #bechmark #performancebenchmark
https://linuxnews.de/vorschlag-fedora-kde-plasma-6-ohne-x11/
#Fedora #kde #x11
Try enabling gfx.x11-egl.force-enabled in about:config to force the use of EGL1 and then restart the web browser.
If this works, enabling layers.acceleration.force-enabled can boost your performance even more by enabling OpenGL alongside EGL. 2
This also works on Flatpak if the security permissions are correct (use Flatseal3 if needed).
Tags: #linux #gnulinux #sysadmin #gpu #gpu-linux #gpuacceleration #egl #opengl #x11 #xorg #mozilla #firefox #hack #flatpak #flatseal
https://www.khronos.org/egl/
https://flathub.org/apps/details/com.github.tchx84.Flatseal
https://linuxreviews.org/HOWTO_Make_Mozilla_Firefox_Blazing_Fast_On_Linux
I'm still on the journey to using #Wayland rather than #X11 but there are a few issues which I'm not sure how to resolve.
Here's the scenario that I'm currently looking at. I have a separate #touchscreen which I can attach to my #laptop via an #HDMI connection. I can configure it to extend the usual monitor, say to the right. However, when I touch the touchscreen, it registers movement on the laptop's monitor even though I'm touching a location which should be to the right of it. With an X window set up, I can remap things using #xinput so that the touch is registered correctly but I haven't figured out a way of doing the same in Wayland. Does anybody have any ideas?
I wonder why in the latest update of #KDE #Plasma, the #DesktopSwitching #Animation no longer allows the #Cube effect. I quite liked that piece of #EyeCandy even though it's no big deal that it seems to have disappeared.
I've been looking at improving the usefulness of my separate #touchscreen when using a #program like #xournalpp for making sketches and writing on a display for other to see. It works OK with #X11 but the response to touches of the #stylus on the screen is a bit frustrating. However, with #Wayland, it seems to be so much better, which means the #hardware is fine and it's the #software that is not very sensitive.
The only issue I have now is that I can only get it work as a clone of the laptop display and not as a separate screen. This works with X11 though I have to adjust things a bit with #xinput. But in Wayland, touches on the screen as configured "to the right" of the main display map back to the #mouse #cursor on the main screen and not on the touchscreen itself. Does anyone have any ideas about a possible solution?
old/iophk: #x11 has to go. it is past time for removal. the question is whether there will someday be something to replace it. wayland seems stalled http://theinvisiblethings.blogspot.com/2011/04/linux-security-circus-on-gui-isolation.html
Today I had to give two different presentations in two entirely different places, neither of which had an #HDMI connection, which is the only #video output I have on my #laptop. Both still had #VGA, which is pretty ancient these days. Luckily, a few years ago, I bought an HMDI-to-VGA #adaptor but initially I had difficulty with using it, perhaps because of lack of full support in #KDE. Colours were sometimes different or flashed or gave some odd artefacts on the projected image. Happily, now things have been sorted out and everything worked really well. I was also using an extra #touchscreen and an #HDMI duplicator to send the signal to two outputs at once. Thanks to all the #FreeSoftware hackers who made this possible.
"Another tick in the box for #Wayland to eventually properly replace #X11 for all workloads, as the work on DRM lease protocol support aimed at VR has been merged in." https://www.gamingonlinux.com/2021/08/wayland-gets-drm-lease-protocol-support-to-help-vr-on-linux
