From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Logo Pictograph
Date: Sun, 27 Oct 2019 13:19:59 +0200 [thread overview]
Message-ID: <87sgnetoyo.fsf@tarshish> (raw)
In-Reply-To: <CAJ4jsadKhREm9r+d6RojLJ5PBZvE9A3tb1QVmq7o6DUG3kTwQg@mail.gmail.com>
Hi Thomas, Carlos, Arnout, all,
On Fri, Sep 20 2019, Carlos Santos wrote:
> On Tue, Sep 17, 2019 at 5:28 PM Arnout Vandecappelle <arnout@mind.be> wrote:
>> On 13/09/2019 22:03, Thomas Petazzoni wrote:
>> Do you mean that it seems oversimplified? I would say it is actually still much
>> more detailed/complex than the typical logo. The PNG is very high resolution, it
>> becomes better if you zoom it out a lot (like it is intended to be used).
>>
>> For me, the logo2.png looks a bit better because it simplified more. I like the
>> vertical gray line which gives structure to the image. However, it is very much
>> a large yellow blob. I think this could be improved by lowering the intensity of
>> the horizontal part of the helmet a little (which also returns a bit of the 3D
>> effect). We could even try to add a slight gradient to that part (although
>> possibly a gradient in a logo is not a good idea either).
>>
>> > I know this feeling is not very helpful as-is
>> > because it doesn't say what needs to be fixed or improved.
>> >
>> > In any case, this is not a very strong feeling, so I certainly won't
>> > oppose to this new logo just because of my vague comment, and I'll be
>> > happy to see a logo change accepted!
>>
>> +1 to that!
>>
>> Regards,
>> Arnout
>
> The yellow ones become meaningless spots when reduced to around
> 100x100 pixels. The yellow color does not help much. :-/
>
> The monochromatic ones still look like a helmet when reduced and
> bw_logo seems to have more "volume" and looks like a construction
> helmet more than bw_logo2.
Thanks for your concrete logo suggestions.
Hadas sent me another set of logo alternatives:
http://tinkie.tkos.co.il/buildroot-logo/all_buildroot_logos.pdf
What is your favorite option?
Thanks,
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2019-10-27 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 12:15 [Buildroot] Buildroot Logo Pictograph Baruch Siach
2019-09-13 13:37 ` Peter Korsgaard
2019-09-13 20:03 ` Thomas Petazzoni
2019-09-17 20:28 ` Arnout Vandecappelle
2019-09-20 14:39 ` Carlos Santos
2019-10-27 11:19 ` Baruch Siach [this message]
2019-10-27 11:38 ` Carlos Santos
2019-09-22 5:53 ` Jonathan Ben Avraham
2019-09-22 14:40 ` Arnout Vandecappelle
2019-09-23 6:40 ` Jonathan Ben Avraham
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgnetoyo.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.