Mats Lidell writes:
>>>>> Michael Sperber <sperber(a)deinprogramm.de>
> I'd feel just fine about that.
I don't have a problem with it. Unless somebody speaks up to say that
GTK2 is native on their platform, I also have no problem with just
dropping (rather than #ifdef'ing) the GTK2 support as you modernize.
(Note that we may still go with dropping as far as I'm concerned, it's
just that if somebody actually wants it because GTK3 isn't installed
but GTK2 is installed, it becomes debatable.)
＠Jeff: Strategically, don't worry about dropping it for the moment,
just drop. If within a thousand lines of changes or so somebody
decides they care, *and* we decide to go with #ifdefs, I'll help with
getting that done. "Good VCS means never having to say, 'Oh, shit, I
deleted that!'" :-)
By the way, what is the status of GTK with XEmacs?
Pretty much the same as everything else: nobody's working on it so
it's wherever somebody last left off, incomplete and almost usable.
I had more or less given up in it since no one was working on it
and I realized that I could not put in enough effort to contribute
to it either. i.e. could it be a solution for the 21.5 problems
with xft-fonts etc?
No. I detest the GTK "look and feel" for one thing. :-) If you use
GNOME (at least, I don't know about GTK 3 itself), you've got yet
another font configuration syntax to support. It is possible that we
could use something lower-level (such as pango, which Jeff has
mentioned before and Aidan prefers, I think). Also, I'm thinking
about a Cairo display type.
Note that AFAICT GTK does *not* solve the font problems. GTK
applications also exhibit broken clipping and overwriting behavior the
same as XEmacs, just much less frequently.
 Eg, Mac OS X MacPorts doesn't qualify because Aqua is native, not
GTK, and GTK3 is as easily available as GTK2.
 At least those of GNU Emacs, Inkscape, and *Office.
XEmacs-Beta mailing list