On Mon, Oct 17, 2016 at 10:30:37PM +0100, Thomas Adam wrote:
> On Mon, Oct 17, 2016 at 10:05:04PM +0100, Dominik Vogt wrote:
> > The intention of having a show off or default config using PNG is
> > a good idea, but one can still have an option "--disable-png" and
> > tell people:
>
> [...]
>
> O
On Mon, Oct 17, 2016 at 10:05:04PM +0100, Dominik Vogt wrote:
> The intention of having a show off or default config using PNG is
> a good idea, but one can still have an option "--disable-png" and
> tell people:
[...]
OK -- so what if we do that, but it defaults to using PNG if it's on the
syste
On Mon, Oct 17, 2016 at 08:19:20PM +0100, Thomas Adam wrote:
> On Mon, Oct 17, 2016 at 08:10:00PM +0100, Dominik Vogt wrote:
> > Then what is the gain of making it mandatory if every distro has
> > it anyway? With that line of argumwnt the only effect of making
> > it mandatory is making fvwm hard
On Mon, Oct 17, 2016 at 08:10:00PM +0100, Dominik Vogt wrote:
> Then what is the gain of making it mandatory if every distro has
> it anyway? With that line of argumwnt the only effect of making
> it mandatory is making fvwm harder to build for some people.
Harder to build, how? We've just ruled
On Mon, Oct 17, 2016 at 07:36:28PM +0100, Thomas Adam wrote:
> On Mon, Oct 17, 2016 at 07:01:52PM +0100, Dominik Vogt wrote:
> I'm saying that as an image format used in the wild, all of the projects
> I can see don't support XPMs. I'm not saying it's being removed at all. It's
> an example showi
On Mon, Oct 17, 2016 at 07:01:52PM +0100, Dominik Vogt wrote:
> And the logical consequence of this statement is to hard code
> image formats and remove the library code, no?
No. The logic stops in saying that out-of-the-box, PNG image support is
available. At a minimum. Other renderers are ava
On Mon, Oct 17, 2016 at 02:04:54AM +0100, Dominik Vogt wrote:
> On Mon, Oct 17, 2016 at 01:58:10AM +0100, Dominik Vogt wrote:
> > This may have gotten a bit out of hand (fvwm-2.6.7):
> >
> > $ ./configure --disable-nls --disable-mandoc --disable-sm --disable-shape
> > --disable-shm --disable-xr
On Mon, Oct 17, 2016 at 07:53:17AM +0100, Thomas Adam wrote:
> On Mon, Oct 17, 2016 at 01:58:10AM +0100, Dominik Vogt wrote:
> > But keep small and/or embedded systems in mind. It's still
> > possible to use just the core without any libraries and modules
> > and have a very small WM that can even
On Mon, Oct 17, 2016 at 01:58:10AM +0100, Dominik Vogt wrote:
> But keep small and/or embedded systems in mind. It's still
> possible to use just the core without any libraries and modules
> and have a very small WM that can even draw basic window
> decoration and some graphical effects.
Of cours
On Mon, Oct 17, 2016 at 01:58:10AM +0100, Dominik Vogt wrote:
> This may have gotten a bit out of hand (fvwm-2.6.7):
>
> $ ./configure --disable-nls --disable-mandoc --disable-sm --disable-shape
> --disable-shm --disable-xrender --disable-xinerama --disable-iconv
> --disable-xft --disable-bidi
On Mon, Oct 17, 2016 at 12:50:53AM +0100, Thomas Adam wrote:
> On Mon, Oct 17, 2016 at 12:01:14AM +0100, Dominik Vogt wrote:
> > On Sun, Oct 16, 2016 at 05:09:57PM +0100, Thomas Adam wrote:
> > > On Sun, Oct 16, 2016 at 04:48:34PM +0100, Dominik Vogt wrote:
> > > > Maybe it's a silly question, but
On Mon, Oct 17, 2016 at 12:01:14AM +0100, Dominik Vogt wrote:
> On Sun, Oct 16, 2016 at 05:09:57PM +0100, Thomas Adam wrote:
> > On Sun, Oct 16, 2016 at 04:48:34PM +0100, Dominik Vogt wrote:
> > > Maybe it's a silly question, but *why* does fvwm need mandatory
> > > image support at all? Arent's i
On Sun, Oct 16, 2016 at 05:36:51PM -0600, Jaimos Skriletz wrote:
> What about having libpng be default but having a --disable-libpng
> ./configure option to disable? Have it set up to error out if libpng and
> that option are not present with an error that says building without libpng
> may affect
On Sun, Oct 16, 2016 at 5:01 PM, Dominik Vogt wrote:
> On Sun, Oct 16, 2016 at 05:09:57PM +0100, Thomas Adam wrote:
> > On Sun, Oct 16, 2016 at 04:48:34PM +0100, Dominik Vogt wrote:
> > > Maybe it's a silly question, but *why* does fvwm need mandatory
> > > image support at all? Arent's images i
On Sun, Oct 16, 2016 at 05:09:57PM +0100, Thomas Adam wrote:
> On Sun, Oct 16, 2016 at 04:48:34PM +0100, Dominik Vogt wrote:
> > Maybe it's a silly question, but *why* does fvwm need mandatory
> > image support at all? Arent's images in a window manager just
> > gimmicks?
>
> It's not a silly que
On Sun, Oct 16, 2016 at 04:48:34PM +0100, Dominik Vogt wrote:
> Maybe it's a silly question, but *why* does fvwm need mandatory
> image support at all? Arent's images in a window manager just
> gimmicks?
It's not a silly question, but I'd hoped the commit message said enough.
Gimmick is a matter
On Sun, Oct 16, 2016 at 08:19:59AM -0700, GitHub wrote:
> 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 thir
Branch: refs/heads/ta/png-default
Home: https://github.com/fvwmorg/fvwm
Commit: d304791e3600e3180c22418356dcd9bc45bb3a22
https://github.com/fvwmorg/fvwm/commit/d304791e3600e3180c22418356dcd9bc45bb3a22
Author: Thomas Adam
Date: 2016-10-16 (Sun, 16 Oct 2016)
Changed paths:
18 matches
Mail list logo