Labwc by default does not have a power manager daemon. KDE does. astyle when I tried KDE under Wayland I also had problems with the power management, in my case I found the keyboard unresponsive and I had to power cycle my system. Not to mention that I have not been able to get it working with any DM.
I'm more interested at this time in seeing if power management is working under KDE Wayland... And info I'm seeing these days suggests that it's a hit and miss. Some ppl say it's not a problem for them (but those ppl also have stuff compiled, have the very latest versions, and a lot of other details lined up), and some say that they're having problems with power management, too.
Something like turning off the display after 5 minutes of idle?
That was a good UI. Hate Microsoft as much as you want but you can't deny that Windows 95's design was very well thought out and perfect. Today's "Modern" GUI's and styles are terrible. They are slow, bloated, and have poor function/user experience. All for the sake of wanting to change because some UI designer wants to be different and radical. Even worse is how the engines behind those GUI's are all HTML, CSS, and JavaScript.
The solution is to port toolkits to Xt (X intrinsics toolkits). Motif was compatible with so much, in part because it used Xt. However, Motif was difficult to program for. GDK which Gtk2 & Gtk 3 use, needs to be ported to Xt.
Excuse the dumb ignorant question here, but why have things like X11 or Wayland in the first place? I see during FreeBSD boot and pre-X11 environment on UEFI platforms, a nice graphics capable low latency fast frame buffer. Couldn't libraries be built to make use of that instead?
Idk, but wouldn't that be considered a more basic display server? Whatever it is, X client will be made to work on any such display server.
Correct. My problem is frankly session restore, and having the DE respond adequately to those 5 minutes of idle... I don't want my session crashing after 5 minutes of idle. What if I have something in Konsole or Firefox? This is where Pipewire comes in.
I don't expect the DE to control that stuff, but displaying the info in a nice layout - now that's nice to have.
Xorg/X11 are the libs that build on that basic graphics capability in the first place. In simple terms, the graphics that are provided by BIOS andUEFI are at the bottom of the graphics stack, then come the GPU drivers like amdgpu/nv/i915, and then Xorg on top of that. There's a reason it's called a graphics stack... Wayland is an alternative to the aging Xorg/X11.
Pipewire handles both audio and video: https://pipewire.org/
Its a good question. Underneath most Xorg (and Wayland compositor) drivers is libdrm.
I couldn't stand Win95 when came out! My first GUI was GEM, then classic MacOS (called just System 6/7 back then) and on PC's I was very happy with W4WG 3.11 with Central Point Desktop. I used to know almost all Win3 .ini's by heart, and passionately hated W95 Registry (still do). I switched to W95 only because of Macromedia Freehand, when they stop supporting Win3 (AFAIR v7). BTW, Win95 was barely usable and horribly unstable OS, Win98SE was the first version that worked well.
At least it wasn't full of ads, SaaSS crap, and didn't take up 60gb for what should probably be accomplishable in 6.
Until AOL became available shortly after the launch of win95...At least it wasn't full of ads, SaaSS crap, and didn't take up 60gb for what should probably be accomplishable in 6.
Oh, and we came full circle since. 
Not having session restore could be played-off as Plasma being so stable it isn't expected to crash
(sounds questionable for enterprise wanting stability though)Come on... under Xorg, I can walk away for 5 minutes to grab lunch... same is possible under Windows, MacOS, you name it. So why not Wayland? I do want feature and capability parity here. I am sold on Wayland, I do see technical benefits. 'Energy efficiency' is irrelevant here, sorry. I should be able to set time limits for the screen to turn itself off when I walk away or go to sleep myself... and I expect Wayland to behave accordingly (just like Xorg does).Not having session restore could be played-off as Plasma being so stable it isn't expected to crash
But not being able to do something simple like blank a screen is wild; is Wayland that important? Technical aside, it could be argued Plasma on Wayland might be less energy-efficient, use more power, and have higher energy costs
I'm only surprised that you never tried to automate that 'lolcat' thingy. IDK about zsh, but in bash this will work:
exec > >(while IFS= read -d '' -r line; do if [[ -n $line ]]; then echo; printf "%s\n" "$line" | lolcat; fi; done); PROMPT_COMMAND='printf "\0"'
vmisev said:Seriously now, my only contact with Fluxbox was way back ~'06 in the first FreeBSD based distro I ever touched - .ua made FrenzyBSD LiveCD. Fluxbox was very usable, nicely configured and more than enough for LiveCD based OS. BTW, FrenzyBSD is "guilty" that I fell in love for life with FreeBSD. Soon after Frenzy, when I decided to go with actual FreeBSD on bare metal, I went with KDE because that's what I knew from my previous Mandrake use, and since then it's only console (vt, of course) or KDE
In the FreeBSD Foundation article "Graphical Installer for FreeBSD" they stated that new graphical installer will be based on gbsddialog(1) which is based on Gtk+
My guess is, that you were hinting at this all along. There's also graphics of an image through using Lua for the FreeBSD logo on the start up terminal.
It would have to work for VT now.
Well, that blog entry has no date, and the Github link (provided by the author) is dead... And FreeBSD is supposed to be a professional OS for professionals...
This looks harsh, but somebody at the Foundation needs to get their act together.
