FVWM myExt collection

[oops]

One suggestion, you can optimize all yours bigs .png files with (size divided by 2 or more):
pngquant -f --ext .png --quality 70-95 MyPicture.png

Thanks, this is great. I have been avoiding adding many png (wallpaper) images due to the large size.

Your welcome.
you can do this recusively for all .png by:

Code: Select all

cd /the-baseDir
find . -name '*.png' -exec pngquant -f --ext .png --quality 70-95 {} \;

PS: Maybe you can also provide a custom config for eepc (with small screen like: 1024x600 )

[rasat]

PS: Maybe you can also provide a custom config for eepc (with small screen like: 1024x600 )

Yes, for sure. This annoyance of odd-looking wallpaper of large resolution on a small screen can now be solved. There will be a similar script that adjusts panels and buttons as per screen resolution.
https://github.com/rasatpc/FVWM3-myEXT/ ... osition.sh

FVWM myEXT GitHub:
https://github.com/rasatpc/FVWM3-myEXT

[oops]

Thanks Rasat, I didn't know.

[pianokeyjoe]

Thanks, this is great. I have been avoiding adding many png (wallpaper) images due to the large size.

Your welcome.
you can do this recusively for all .png by:

Code: Select all

cd /the-baseDir
find . -name '*.png' -exec pngquant -f --ext .png --quality 70-95 {} \;

PS: Maybe you can also provide a custom config for eepc (with small screen like: 1024x600 )

Installed pngquant and experimented with the compression ratios. I wish there was a GUI version to preview the results of the different compression ratios but it all worked eitherway!

[oops]

Hello,
I have tested a little bit more (the memory side) , and fvmw3 is in the middle range (beetween IceWM and XFCE4 DE), FvwmButtons consumes some extra memory.

All AMD64

20520KB - fvwm3
18936KB - FvwmScript
18844KB - FvwmButtons
18700KB - FvwmButtons
16872KB - FvwmButtons
16816KB - FvwmButtons
16752KB - FvwmButtons
13040KB - FvwmButtons
12908KB - FvwmButtons
12808KB - FvwmButtons
12596KB - FvwmPager
9312KB - FvwmIconMan
652KB - FvwmEvent
648KB - FvwmEvent
648KB - FvwmEvent
------------------------------------
190052KB: Memory used by user 'autre-mx'

//////////////////////////////////////////////////////
------------- bspwm-----------------------
3196KB - bspwm_help.sh
2444KB - bspwm
2336KB - sxhkd
------------------------------------
7976KB: Memory used by user 'autre-mx'

-----------JWM x32-------------------------
26020KB - jwm
------------------------------------
26020KB: Memory used by user 'user-mx'

----------- icewm-session 64bits-------------------------
24896KB - icewm
1960KB - icewm-session
------------------------------------
26856KB: Memory used by user 'autre-mx'
-----------icewm-session 32bits-------------------------
19132KB - icewm
1668KB - icewm-session
------------------------------------
20800KB: Memory used by user autre-mx'

------------I3------------------------
17356KB - i3
15192KB - i3bar
6668KB - i3status
------------------------------------
39216KB: Memory used by user 'autre-mx'

-------------only fluxbox - amd64-----------------------
15920KB - fluxbox
------------------------------------
15920KB: Memory used by user 'autre-mx'
------------fluxbox X32------------------------
29428KB - tint2
25508KB - wmalauncher
24544KB - wmalauncher
24524KB - wmalauncher
24476KB - wmalauncher
24420KB - wmalauncher
24384KB - wmalauncher
24352KB - wmalauncher
24324KB - wmalauncher
24256KB - wmalauncher
19964KB - wmalauncher
10240KB - fluxbox
------------------------------------
280420KB: Memory used by user 'user-mx'


------------XFCE4 with xfwm4 ------------------------
90920KB - xfwm4
52660KB - xfce4-panel
47960KB - xfce4-clipman
31016KB - xfce4-session
27212KB - xfce4-power-man
24772KB - xfce4-notifyd
2060KB - xfce-superkey
------------------------------------
276600KB: Memory used by user 'autre-mx'

------------XFCE4 with compiz (only)------------------------
147596KB - compiz
------------------------------------
147596KB: Memory used by user 'user-mx'

[rasat]

FvwmButtons consumes some extra memory.

Can you identify which FvwmButtons?

[oops]

... Yes I guess from:
/home/user/.fvwm/extraEXT/MODULES/DashToDock/dashToD.sys

[rasat]

... Yes I guess from:
/home/user/.fvwm/extraEXT/MODULES/DashToDock/dashToD.sys

So, you compared the memory usage with the extensions? Do the test with the default Fvwm3.... empty .fvwm folder.

[oops]

... Yes I guess from:
/home/user/.fvwm/extraEXT/MODULES/DashToDock/dashToD.sys

So, you compared the memory usage with the extensions? Do the test with the default Fvwm3.... empty .fvwm folder.

Yes, without this extension (dock like or buttons), fvwm has the ~ same footprint as Icewm, or Fluxbox (without dock too by default), or I3.
It is nice, it was just to advise (with only tint2 the footprint is better).

[rasat]

Yes, without this extension (dock like or buttons), fvwm has the ~ same footprint as Icewm, or Fluxbox (without dock too by default), or I3.

This means optimizing the extensions for lower memory usage.

About the wallpaper of different screen resolutions. At last, after breaking my head in creating a script, I found the solution.... tiled wallpaper. The default Fvwm wallpapers (480x480) are tiled.

With Gimp you can create your own seamless images.
https://www.linuxtopia.org/online_books ... ode83.html

Click menu bar: Filters → Map → Tile Seamless

I did a test on .fvwm/images/background/myExt-1920x1080.png
https://rasatpc.net/screenshot/myExt/Ti ... 00x675.png

Tiled image (seamless) 900x506 that will work well on a screen 3840x2160 and 1024x600.
https://rasatpc.net/screenshot/myExt/Ti ... 00x506.png

Another method of creating a wallpaper is with xsetroot by using different numbers. For example, run this in terminal:

Code: Select all

xsetroot -bg \#555555 -mod 4 4