From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Logo Pictograph
Date: Wed, 11 Sep 2019 15:15:03 +0300 [thread overview]
Message-ID: <87tv9jrpvc.fsf@tarshish> (raw)
Hi Buildroot developers,
We have a nice recognizable logo that illustrates what Buildroot is
about. Being far from expert (or even amateur) in graphic design, I find it
perfect. But when Hadas Cohen, SolidRun's graphic designer, considered using
the Buildroot logo in a brochure, she noticed a problem. It turns out that a
realistic picture is no go for logo design. As a result she could not use the
logo as is, because it looks markedly different than other logos in the
brochure.
Hadas referred me to this professional looking explanation of why photograph
is not a good choice for a logo:
https://forums.adobe.com/thread/1270284
Hadas also collected a few hundred random logos to demonstrate the point:
http://tinkie.tkos.co.il/buildroot-logo/2616906744_a238697a95_b.jpg
SolidRun management agreed to let Hadas design an iconic pictograph version of
the Buildroot logo. Here is the result.
Two colored logo alternatives:
http://tinkie.tkos.co.il/buildroot-logo/colored_logo.png
http://tinkie.tkos.co.il/buildroot-logo/colored_logo2.png
Two monochromatic alternatives:
http://tinkie.tkos.co.il/buildroot-logo/bw_logo.png
http://tinkie.tkos.co.il/buildroot-logo/bw_logo2.png
Hadas can provide the vectorized SVG and PDF sources of these raster images.
What do you think?
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 reply other threads:[~2019-09-11 12:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 12:15 Baruch Siach [this message]
2019-09-13 13:37 ` [Buildroot] Buildroot Logo Pictograph 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
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=87tv9jrpvc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox