Branch: refs/heads/ta/png-default
Home: https://github.com/fvwmorg/fvwm
Commit: 199f0b23156a3bf9c9d44d4b91c962b6f853247f
https://github.com/fvwmorg/fvwm/commit/199f0b23156a3bf9c9d44d4b91c962b6f853247f
Author: Thomas Adam <tho...@xteddy.org>
Date: 2016-10-16 (Sun, 16 Oct 2016)
Changed paths:
M bin/Makefile.am
M configure.ac
M fvwm/Makefile.am
M fvwm/fvwm.c
M libs/Makefile.am
M modules/FvwmAnimate/Makefile.am
M modules/FvwmBanner/Makefile.am
M modules/FvwmButtons/Makefile.am
M modules/FvwmIdent/Makefile.am
M modules/FvwmPager/Makefile.am
M modules/FvwmProxy/Makefile.am
M modules/FvwmScript/Makefile.am
Log Message:
-----------
Make PNG support mandatory
Traditionally, FVWM has always had the option of not linking to any image
renderer at all.
But, the entire world has moved on, and support for images is becoming more
important, especially with third-party applications. Indeed, FVWM itself will
have a new default configuration soon which will make use of PNGs. It's a
good idea to support this out of the box.
Choosing the default image library is not easy -- and although there's a sway
towards SVGs (which FVWM supports), PNGs are quite common still, so use that.
