From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: Antialiased text on X11
Date: Fri, 11 Mar 2005 16:13:58 +0100 [thread overview]
Message-ID: <0e2137042bdc3df8a67c1cbe128b4197@swipnet.se> (raw)
In-Reply-To: <xfezmxa8ro7.fsf@dubya.devel.cmedltd.com>
>
> I'll stick my hand in the air here and say that I would favour people
> putting effort into Cairo support rather than Xft.
>
> Isn't Cairo being used in Gtk now? Could we get Cairo for free by
> porting the buffer to Gtk?
GTK 2.6 does not use Cairo, the development version might. As for
"porting the buffer", I assume you mean that we should leave all
redisplay to Gtk, by using for example the text widget? Unfortunately
the redisplay in that widget is crude and simple, and is only suitable
for the most simple text editing tasks.
Getting Emacs to use Xft for all X ports is much more realistic. Cairo
is a moving target, and from what I have seen, we still need font
metrics and the like to be able to handle redisplay. Cairo only gives
simple drawing primitives, this is not good enough. I haven't seen the
latest Cairo sources, so this might have changed.
But if we get font metrics from Cairo or Xft does not matter much, the
porting work is roughly the same, so Xft is a much better target. The
drawing stuff is trivial in both cases.
Jan D.
prev parent reply other threads:[~2005-03-11 15:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 21:45 Antialiased text on X11 James Cloos
2005-03-10 22:25 ` Stefan Monnier
2005-03-10 23:15 ` Han Boetes
2005-03-11 4:58 ` Jan D.
2005-03-18 21:21 ` Ali Ijaz Sheikh
2005-03-18 22:39 ` Drew Adams
2005-03-19 22:45 ` The WHY of Xft [was: Re: Antialiased text on X11] James Cloos
2005-03-19 23:47 ` Miles Bader
2005-03-20 16:49 ` The WHY of Xft James Cloos
2005-03-20 22:30 ` Miles Bader
2005-03-21 14:24 ` David Hansen
2005-03-21 16:12 ` James Cloos
2005-03-21 0:32 ` Kenichi Handa
2005-03-19 0:59 ` Antialiased text on X11 Miles Bader
2005-03-19 6:27 ` Jan D.
2005-03-19 7:39 ` Miles Bader
2005-03-19 16:31 ` Stefan Monnier
2005-03-19 16:53 ` Han Boetes
2005-03-20 11:51 ` Jan D.
2005-03-19 21:41 ` Miles Bader
2005-03-20 13:15 ` Jan D.
2005-03-20 22:51 ` Jan D.
2005-03-22 23:44 ` Miles Bader
2005-03-23 2:30 ` Miles Bader
2005-03-23 17:50 ` Jan D.
2005-03-25 21:40 ` Miles Bader
2005-03-26 8:13 ` Jan D.
2005-03-29 10:52 ` Geoffrey J. Teale
2005-03-29 11:28 ` Miles Bader
2005-03-29 12:24 ` Geoffrey J. Teale
2005-03-29 18:24 ` Henrik Enberg
2005-03-29 22:50 ` Miles Bader
2005-03-31 2:42 ` James Cloos
2005-03-31 4:22 ` Miles Bader
2005-03-29 19:28 ` Jan D.
2005-04-01 8:15 ` Miles Bader
2005-04-01 16:09 ` Jan D.
2005-03-22 12:45 ` Oliver Scholz
2005-03-22 14:21 ` Stefan
2005-03-22 14:29 ` Oliver Scholz
2005-03-22 15:17 ` David Kastrup
2005-03-10 23:19 ` James Cloos
2005-03-11 9:20 ` Geoffrey J. Teale
2005-03-11 15:13 ` Jan D. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e2137042bdc3df8a67c1cbe128b4197@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).