MX Fluxbox Screenshots
Re: MX Fluxbox Screenshots
If I was doing these on canvas heh it'd work but altering the white center to a less eye searing in Gimp over the years never conquered that feathering the edges.
" Outside the square , inside the cube "
Re: MX Fluxbox Screenshots
upscaled this beautiful image to 1920x1280 to maintain its ratio; ultimately cut height to 1200 px
no layers added, toned down contrast - and blurred the image to kingdom come

no layers added, toned down contrast - and blurred the image to kingdom come

Sony Vaio VPCF23P (2011), Intel Core i7-2670, 6gb RAM, 240gb SSD, MX-Linux 23 based Fluxbox v/1.3.7+
Lenovo Thinkpad L560 (2016), Intel Core i5-6200, 16gb RAM, 240gb SSD, Devuan Daedalus based Fluxbox v/1.3.7+
Lenovo Thinkpad L560 (2016), Intel Core i5-6200, 16gb RAM, 240gb SSD, Devuan Daedalus based Fluxbox v/1.3.7+
Re: MX Fluxbox Screenshots
I made Ken Sunset into a single feather, Thanks for @Jerry3904 so beautiful image!

viewtopic.php?p=798769#p798769

viewtopic.php?p=798769#p798769
In the world filled desire,
I seek only essence, serve for MX.
I just needing only ideal in the art at all.
I want to protect place of rest called MX LINUX.
Sony VAIO Pro 11inch Silver (FHD) extrox (MX23)
I seek only essence, serve for MX.
I just needing only ideal in the art at all.
I want to protect place of rest called MX LINUX.

Sony VAIO Pro 11inch Silver (FHD) extrox (MX23)
Re: MX Fluxbox Screenshots
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX Fluxbox Screenshots
As usual, my wallpaper matches the current season - the gloomy mood of November and the last autumn leaves:


Desktop PC: AMD Ryzen 5 5600 3.5GHz, MSI B550M PRO-VDH, 32GB RAM, Gigabyte RX 570. Laptop: MacBook Late 2008, Core2Duo 2.0GHz, 8GB RAM. Netbook: Asus EEEPC Intel Atom 1.6GHz, 2GB RAM. System: MX23 64bit/32bit Fluxbox.
Re: MX Fluxbox Screenshots
It also matches other kinds of gloomy moods ...
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX Fluxbox Screenshots
Hi,Jerry3904 wrote: Wed Nov 20, 2024 5:57 am Hey people, nice work there and fun results.
Here's the original straight from the camera:
![]()
Not suggesting this is a marked improvement but here is a variation with gradients, blur and resized to 4K:
http://bandshed.net/images/wallpapers/4K/SkyBlur-4K.jpg
@kobaian
Excellent as always! And yes, much gloom worldwide for sure..
Re: MX Fluxbox Screenshots
Thanks, looks pretty nice!
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX Fluxbox Screenshots
I've made a comparison of memory consumption between compositors running on my fluxbox setup, i.e compton vs picom - and fluxbox' own pseudo-transparency setting.
Checks were done immediately after system startup, calling the ps_mem command in a terminal (in this case in a stjerm drop-down terminal).
Lowest memory usage is obviously obtained with pseudo-transparency, but compton comes close.
Using picom causes an increase of some 12-13 Mb -->which I find very acceptable, considering the nice effects it adds to fluxbox' appearance (both shadowing and corner-rounding).

Checks were done immediately after system startup, calling the ps_mem command in a terminal (in this case in a stjerm drop-down terminal).
Lowest memory usage is obviously obtained with pseudo-transparency, but compton comes close.
Using picom causes an increase of some 12-13 Mb -->which I find very acceptable, considering the nice effects it adds to fluxbox' appearance (both shadowing and corner-rounding).

Sony Vaio VPCF23P (2011), Intel Core i7-2670, 6gb RAM, 240gb SSD, MX-Linux 23 based Fluxbox v/1.3.7+
Lenovo Thinkpad L560 (2016), Intel Core i5-6200, 16gb RAM, 240gb SSD, Devuan Daedalus based Fluxbox v/1.3.7+
Lenovo Thinkpad L560 (2016), Intel Core i5-6200, 16gb RAM, 240gb SSD, Devuan Daedalus based Fluxbox v/1.3.7+
Re: MX Fluxbox Screenshots
ceeslans wrote: Thu Nov 21, 2024 5:24 pm I've made a comparison of memory consumption between compositors running on my fluxbox setup, i.e compton vs picom - and fluxbox' own pseudo-transparency setting.
Checks were done immediately after system startup, calling the ps_mem command in a terminal (in this case in a stjerm drop-down terminal).
Lowest memory usage is obviously obtained with pseudo-transparency, but compton comes close.
Using picom causes an increase of some 12-13 Mb -->which I find very acceptable, considering the nice effects it adds to fluxbox' appearance (both shadowing and corner-rounding).
![]()
I think for MX-25 we should switch to picom since it is still being developed.
Compton hasn't been updated for 7 years and will soon be removed.
You do not have the required permissions to view the files attached to this post.
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.