[fvwmorg/fvwm] 9703d6: Make PNG support mandatory
Branch: refs/heads/master Home: https://github.com/fvwmorg/fvwm Commit: 9703d649aa91c74dde1ac92caedc3145fa1d6f53 https://github.com/fvwmorg/fvwm/commit/9703d649aa91c74dde1ac92caedc3145fa1d6f53 Author: Thomas Adam Date: 2016-10-16 (Sun, 16 Oct 2016) Changed paths: M configure.ac M fvwm/fvwm.c 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.
[fvwmorg/fvwm] 9703d6: Make PNG support mandatory
Branch: refs/heads/ta/png-default Home: https://github.com/fvwmorg/fvwm Commit: 9703d649aa91c74dde1ac92caedc3145fa1d6f53 https://github.com/fvwmorg/fvwm/commit/9703d649aa91c74dde1ac92caedc3145fa1d6f53 Author: Thomas Adam Date: 2016-10-16 (Sun, 16 Oct 2016) Changed paths: M configure.ac M fvwm/fvwm.c 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.
