Ollie 🇪🇺🏳️🌈🏳️⚧️🇵🇸🇺🇦Look what I get to use!
Beautiful. Simple. Usable.
#fvwm2 #Slackware #rxvt #NetscapeCommunicator #xv #screenshot #desktop
grndprnzp
Soliman Hindy@LaurentFr j’avoue j’étais utilisateur de #fvwm2 avant de passer à #kde
#CDE tu l’utilisais à l’école ?
Monoka@bkuhn I remember exactly the revolution when the Kool Desktop Environment #KDE was announced by #MatthiasEttrich and shortly after the GNU Network Object Model Environment #GNOME by @Migueldeicaza and @federicomena . KDE seemed to be far ahead in the beginning. Most distributions moved from #fvwm2 (?) to KDE shortly after. The object-oriented approach of Gnome was very intriguing, inspired by #BeOS and #NeXT, but I don't know how much is left of that idea.
michiThings to discover on [email protected]: https://blogdron.github.io/classic-fvwm.css/ - a CSS theme based on the #fvwm2 look of OpenBSD,
github: https://github.com/nerfur/classic-fvwm.css
github: https://github.com/nerfur/classic-fvwm.css
CaioA pauta sobre easter eggs da #SegundaFicha cobre apenas jogos? Como um usuário #Linux da velha guarda, gostaria de resgatar o easter egg das antigas versões do Red Hat (incluindo o #Conectiva Red Hat Linux), que exibiam um chapéu giratório se uma determinada região do `timetool` (aplicativo para ajuste de data e hora) era clicada. Não achei captura de tela, então, precisei eu mesmo fazer uma (emulador PCem, distribuição Conectiva Red Hat Linux Marumbi).
🏷️ Etiquetas adicionais: #retrocomputing #redhat #fvwm #fvwm2 #anotherlevel #tcltk #emulacao #emulation
reindeerphoto
Andreas Scherbaum
Seán FenianUpdated fvwm major release package is now available.
OK, #update #fvwm2 to #fvwm3.
96% of fvwm2 configuration Just Works in fvwm3 with no changes.
Syntax to specify location of pixmaps seems to have changed. OK, simple fix. Now 97% working.
Menu background pattern definition has changed. It's done in Colorsets now. OK, a little bit of fiddling around, and that's fixed. Now 98% working.
FvwmPerl geometry precalculation isn't working. At all. That turns out to be a syntax change somewhere down the line. Apply the change. Now 99% working.
That just leaves dynamic positioning of some popups. And ... WTF?
OK, how about .... Nope.
Perhaps...? Nope.
Should that flag be there? Let's try without it. Nope.
Does this one help? Nope.
Oops, that one's not supposed to be there at all. Let's disable that ... Nope.
"Try removing this flag and using this one." Aha! Now we're getting somewhere. Update the math in that precalculation, because it's stale because the preprocessing has been broken so long and my monitor resolution is twice what it was when it last worked. Now everything works.
But what's with those changed positioning flags? It's been that way for so long. How did this EVER work?!?
OK, #update #fvwm2 to #fvwm3.
96% of fvwm2 configuration Just Works in fvwm3 with no changes.
Syntax to specify location of pixmaps seems to have changed. OK, simple fix. Now 97% working.
Menu background pattern definition has changed. It's done in Colorsets now. OK, a little bit of fiddling around, and that's fixed. Now 98% working.
FvwmPerl geometry precalculation isn't working. At all. That turns out to be a syntax change somewhere down the line. Apply the change. Now 99% working.
That just leaves dynamic positioning of some popups. And ... WTF?
OK, how about .... Nope.
Perhaps...? Nope.
Should that flag be there? Let's try without it. Nope.
Does this one help? Nope.
Oops, that one's not supposed to be there at all. Let's disable that ... Nope.
"Try removing this flag and using this one." Aha! Now we're getting somewhere. Update the math in that precalculation, because it's stale because the preprocessing has been broken so long and my monitor resolution is twice what it was when it last worked. Now everything works.
But what's with those changed positioning flags? It's been that way for so long. How did this EVER work?!?
Felix Palmen 📯@thindil @thomasadam How exactly would that work? I mean, I *did* use #fvwm2 "inside" #KDE a long time ago, but scripted the ~/.xsession for that manually ...
So, if there's some .desktop file for #fvwm3 with "Type=XSession", would e.g. sddm offer me a session "Plasma+FVWM3" or something like that when plasma is installed as well? 🤔