This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 256x256 px icons


On Aug 13 21:35, Andy Koppe wrote:
> On 13 August 2011 08:58, Corinna Vinschen wrote:
> > On Aug 12 20:37, Andy Koppe wrote:
> >> > There's no rush. ÂEven if I check in the current icons to the setup
> >> > repository, we're not quite finished anyway. ÂAndy was trying to take
> >> > another stab at the smaller icon sizes 24x24 and 16x16.
> >>
> >> I hope to get 'round to this this weekend.
> >
> > I'm looking forward. ÂI have a hard time to see how you can get a
> > recognizable result at 16x16.
> 
> I wasn't going to attempt that. (I now tried it anyway, and the result
> indeed isn't pretty.)
> 
> No, what I was going to try was using Warren's bevelled Cygwin logo
> with the wider stroke to create the standalone logo at 16 and 24 and
> the logo-in-terminal at 32, 48, and 64.
> 
> Resulting cygwin-terminal.ico attached, with the 256x256 taken from
> the current one. I think it's an improvement, particularly at 32x32.

Your attempts at 16x16, 24x24, and 32x32 definitely look better than
mine.  Also, somehow I seem to have broken the terminal frame in 32x32.
I didn't notice that before, but in direct comparison with your 32x32
it's quite obvious.

As for 48x48 and 64x64, it seems the thicker original stroke results in
a washed-out looking stroke in the inner part of the C, just below the
wedge.  Can you get rid of that washed-out look?  If yes, I just take
all of them.

> > Maybe a terminal or a setup box with just a green wedge?
> 
> Hmm, interesting idea. Attempt attached, with wedge-in-terminal
> instead of the standalone logo at 16x16 and 24x24. I think I prefer
> the logo though.

What?  They a cute!  I like them a lot.  I'd like do the same with the
setup icon.

> >> I think it would be best to do that as concurrently as possible,
> >> including the removal of the mintty postinstall and preremove scripts
> >> for creating and removing the 'mintty' start menu entry. That's to
> >> avoid an intermediate phase where the mintty entry appears in people's
> >> start menus without them asking for it, only for it to disappear again
> >> soon after.
> >
> > ACK
> 
> On second thoughts, the move of mintty to the Base category (but not
> the removal of the postinstall/preremove scripts) should probably be
> done a day before uploading the new setup.exe, to make sure it's got
> to the mirrors before setup.exe starts depending on it.

Still ACK.

> >> http://mintty.googlecode.com/svn/tags/1.0.1-2/cygport/setup.hint
> >
> > Erm... do you still need the dependency to cygutils?
> 
> No, thanks for spotting that. And actually the bash dependency isn't
> needed anymore either, following the removal of the
> postinstall/preremove scripts. Hence I dropped the 'requires' line
> completely (after checking that there are other packages without a
> 'requires' line).

Yup, makes sense.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]