unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Silk icon set for Gnus and synchronizing it into Emacs
Date: Thu, 24 Mar 2011 15:27:26 -0500	[thread overview]
Message-ID: <87tyes4635.fsf@lifelogs.com> (raw)
In-Reply-To: 87ipv8pcc8.fsf@stupidchicken.com

On Thu, 24 Mar 2011 15:06:47 -0400 Chong Yidong <cyd@stupidchicken.com> wrote: 

CY> So, the images that we distribute with Emacs are "the images that Emacs
CY> needs".  If Gnus or any other package in Emacs needs extra *specific*
CY> icons, by the way, we should not hesitate to add them to etc/images.

OK.

CY> If I understand you correctly, you want something different: for Emacs
CY> to provide a complete set of images that arbitrary Emacs applications
CY> might need.  While I agree that Emacs programmers might be happy with
CY> the easy availability of such icons, adding hundreds of files to the
CY> Emacs tarfile, not directly used by Emacs, strikes me as wasteful.

As I said, it can be a single image or in some other compact format
(e.g. http://www.famfamfam.com/lab/icons/silk/famfamfam_silk_icons_v013.zip
could be used directly).  So I don't think it's wasteful--if anything,
it saves a lot of work maintaining individual images.

CY> People make jokes about the Emacs operating system,

I think even more people use and rely on Emacs every day, and that's
more important :) My proposal aims to improve the Emacs platform so
applications running on it can provide a better user experience.

CY> but in truth we've placed a lot of emphasis on using existing
CY> operating system resources.  Icon sets are an operating system
CY> resource.

I disagree.  Some are provided by the platform but not in a reliable
cross-platform way, and certainly not as conveniently named as Silk's
icons.

CY> That's why I was talking about extending x-gtk-stock-map to other
CY> platforms---the idea is to provide a cross-platform solution for
CY> Emacs applications to access the operating system's icons.

I think that's useful but insufficient.  So I propose iconset.el to
manage the general "give me an icon from iconset X or from a Gnome theme
or from the OS" task.  Then iconset-silk.el for the specific Silk icons;
iconset-gnome.el to manage the Gnome themes and icons, and
iconset-gtk.el to access x-gtk-stock-map.  At the top level the API user
should be able to specify either a semantic meaning ("the best available
icon for the text/plain MIME type") or a specific icon ("the Silk
css_valid icon"), together with a priority list to specify "best."

CY> Although adding Silk as an ELPA package is tempting, but I'm not
CY> certain.  Suppose a package wants one single icon from Silk.  If it
CY> depends on the Silk package, installing it means also downloading and
CY> installing the hundreds of Silk icons, which is, again, wasteful.  Or is
CY> the idea to make Silk an optional dependency, so that the package will
CY> display icons only if Silk is installed?

Yes, I think it will be optional through iconset.el.  When the user
installs iconset-silk.el, iconset.el will automatically provide it.  So
I propose iconset.el (plus the Gnome theme/GTK glue) goes into the Emacs
core, while iconset-silk.el lives in the GNU ELPA.

Ted




  reply	other threads:[~2011-03-24 20:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 20:43 Silk icon set for Gnus and synchronizing it into Emacs Ted Zlatanov
2011-03-23 15:31 ` Ted Zlatanov
2011-03-23 17:51   ` Chong Yidong
2011-03-23 18:37     ` Ted Zlatanov
2011-03-24  9:42       ` Julien Danjou
2011-03-24 15:55         ` Ted Zlatanov
2011-03-24 17:20           ` Julien Danjou
2011-03-24 19:06       ` Chong Yidong
2011-03-24 20:27         ` Ted Zlatanov [this message]
2011-03-25 15:29           ` Chong Yidong
2011-03-25  6:17         ` Christoph Conrad
2011-03-25 16:00           ` chad
2011-03-25 16:16             ` Christoph Conrad
2011-03-25 16:47             ` Ted Zlatanov
2011-03-28 18:09               ` chad
2011-03-28 18:27                 ` Ted Zlatanov
2011-03-28 20:03                   ` chad
2011-03-28 20:37                     ` Ted Zlatanov
2011-03-28 20:35                   ` Jan Djärv
2011-03-28 20:50                     ` Ted Zlatanov

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=87tyes4635.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).