From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5653 invoked by alias); 2 Aug 2011 15:25:13 -0000 Received: (qmail 5268 invoked by uid 22791); 2 Aug 2011 15:24:49 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.83/v0.83-20-g38e4449) with ESMTP; Tue, 02 Aug 2011 15:24:31 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 4A67A2CB0C2; Tue, 2 Aug 2011 17:24:28 +0200 (CEST) Date: Tue, 02 Aug 2011 15:25:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: 256x256 px icons Message-ID: <20110802152428.GC8652@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <4E327A08.108@etr-usa.com> <20110729094239.GD19240@calimero.vinschen.de> <4E32BFA8.2080907@etr-usa.com> <20110730183646.GM26203@calimero.vinschen.de> <20110801080730.GT26203@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2011-08/txt/msg00016.txt.bz2 On Aug 2 15:49, Andy Koppe wrote: > On 1 August 2011 21:05, Andy Koppe wrote: > > On 1 August 2011 09:07, Corinna Vinschen wrote: > >> On Jul 31 21:21, Andy Koppe wrote: > >>> On 30 July 2011 21:22, Andy Koppe wrote: > >>> > On 30 July 2011 19:36, Corinna Vinschen wrote: > >>> >> On Jul 29 21:29, Andy Koppe wrote: > >>> >>> Attached is my take on this, with 64x64, 48x48, 32x32 showing > >>> >>> fatbuttlarry's Cygwin symbol inside the Konsole icon, and 16x16 > >>> >>> showing the Cygwin symbol only. > >>> >> > >>> >> Not bad, but the green border around the C is too dark to set the > >>> >> C apart from the background.  The border needs some light grey which > >>> >> allows to recognize the C. > >>> > > >>> > I'm not sure how to do that, but the attached attempt turn up the > >>> > saturation of the green outline. > >>> > > >>> > It also reduces the blurriness of the whole thing a bit. Apparently > >>> > it's better to convert an SVG to a high-res bitmap and resize that > >>> > down with a bitmap program such as Paint.net instead of converting the > >>> > SVG straight to the target bitmap sizes (at least when using > >>> > InkScape). > >>> > > >>> > The two attached icons differ at size 32: cygwin-terminal2.ico has the > >>> > Cygwin-in-terminal there, whereas cygwin-terminal3.ico has just the > >>> > Cygwin symbol. Size 32 shows up in the Windows 7 taskbar. > >>> > >>> Further to those two, here's one with the glowy Cygwin symbol all the > >>> way from size 16 to 64. It's a "remastered" version of the one in > >>> cygutils; a bit bigger and with the aforementioned brighter green > >>> outline around the "C". > >> > >> Thanks.  But, hmm.  The longer I play with it, the less I like the green > >> glow.  It adds an eerie touch to the C > > > > Now what's wrong with that? Cygwin - mean and a bit eerie. ;) > > > >> and it still doesn't set the C > >> really apart on dark backgrounds. > > > > I disagree, looking at a desktop with a darkish picture and dark grey > > taskbar and window borders. > > > >> I think we should go with a grey outline. > > > > I did eventually work out how to turn the outline of fatbuttlarry's > > icon grey. See attachments. > > Having used both variants for a while, I agree that a grey outline > does look better. I tried your icons on my desktop and the standalone icon looks good. In the terminal icons the beveled C looks better than the fatbuttlarry C, cleaner, crisper. It's also easier to distinguish from the dark background, but that's probably just because you used a darker shade of grey for the frame. In the terminal window, a lighter grey really doesn't hurt. Generally it looks like your C's are a pixel or two smaller, except in the smallest sizes. Gimp shows that you're always leaving a transparent frame of at least one pixel. Any reason for that? I guess we're getting close to the end result now. The question is just, should we use fatbuttlarry's bubbly C, or Warrens beveled C? I like both. The beveled C exists in 256x256, too. I like the beveled C better in the terminal frame, but I like the bubbly C better standalone. Maybe we can just use both in this combination? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat