unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kai Ma <justksqsf@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Text shadows
Date: Sun, 12 Mar 2023 19:49:40 +0800	[thread overview]
Message-ID: <9F5BA7F8-BB8A-4FF0-AC23-E249C7D471B5@gmail.com> (raw)
In-Reply-To: <838rg2urub.fsf@gnu.org>



> On Mar 12, 2023, at 19:33, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Kai Ma <justksqsf@gmail.com>
>> Date: Sun, 12 Mar 2023 17:55:01 +0800
>> Cc: emacs-devel@gnu.org
>> 
>> At worst, perhaps it would be good enough not to support blurring on
>> some platforms, or support it by some minor modification of the color?
>> Or maybe we could implement the equivalent of gaussian_blur in our
>> code?
>> 
>> This is already the case: Cairo does not provide a Gaussian blurring function, so I wrote one (named
>> gaussian_blur) in xcairo.c.  It is an approximation, not the “True Gaussian Blur”, like Moz2D’s
>> implementation.  It only uses one CPU core, but is fast enough for me.
> 
> I thought you said gaussian_blur required some Cairo-only extension?
> That's why I wrote the above.

Sorry if my words were misleading.  I didn’t intend to say that.

gaussian_blur right now only works on Cairo surfaces, but it’s easy to change.




  reply	other threads:[~2023-03-12 11:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12  4:06 Text shadows Kai Ma
2023-03-12  4:18 ` Kai Ma
2023-03-12  7:12 ` Eli Zaretskii
2023-03-12  8:24   ` Kai Ma
2023-03-12  8:46     ` Po Lu
2023-03-12  9:23       ` Kai Ma
2023-03-12 10:33         ` Po Lu
2023-03-12  9:14     ` Eli Zaretskii
2023-03-12  9:55       ` Kai Ma
2023-03-12 11:33         ` Eli Zaretskii
2023-03-12 11:49           ` Kai Ma [this message]
2023-03-12 12:36             ` Eli Zaretskii

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=9F5BA7F8-BB8A-4FF0-AC23-E249C7D471B5@gmail.com \
    --to=justksqsf@gmail.com \
    --cc=eliz@gnu.org \
    --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).