[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Can we go GTK-only?
From: |
Eli Zaretskii |
Subject: |
Re: Can we go GTK-only? |
Date: |
Fri, 28 Oct 2016 10:13:55 +0300 |
> Date: Thu, 27 Oct 2016 19:15:02 -0400
> From: "Perry E. Metzger" <address@hidden>
> Cc: Daniel Colascione <address@hidden>,
> Emacs developers <address@hidden>
>
> On Thu, 27 Oct 2016 13:32:14 -0700 Paul Eggert <address@hidden>
> wrote:
> > Alternatively, how about if we change the GTK port to be more like
> > the NS port? That is, we leave xterm.o, xfns.c, xselect.c etc.
> > alone (except for removing the GTK-related parts), and have new
> > source files gtkterm.c, gtkfns.c, gtkselect.c etc. as needed to
> > support GTK. The GTK port would no longer define HAVE_X_WINDOWS.
> > That way, the no-toolkit, Motif, and Athena configurations would
> > still work, without getting in the way of GTK.
>
> This seems like a good idea. Emacs already has multiple front ends.
> Having a distinct GTK front end seems like a good, clean sort of
> segregation. The legacy code can be left in and alone for now for the
> benefit of those who use it.
It's not as trivial as it sounds, because our experience shows that
such a separation causes duplication of code. Minimizing code
duplication makes the job harder.
- Can we go GTK-only?, Daniel Colascione, 2016/10/27
- Re: Can we go GTK-only?, Frank Haun, 2016/10/27
- Re: Can we go GTK-only?, Paul Eggert, 2016/10/27
- Re: Can we go GTK-only?, Richard Stallman, 2016/10/27
- Re: Can we go GTK-only?, Eli Zaretskii, 2016/10/28
- Re: Can we go GTK-only?, Stefan Monnier, 2016/10/28