|
 |
ee1f37 |
|
|
|
ee1f37 |
<html>
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
Permission is granted to copy, distribute and/or modify this document
|
|
|
ee1f37 |
under the terms of the GNU Free Documentation License, Version 1.2 or
|
|
|
ee1f37 |
any later version published by the Free Software Foundation; with no
|
|
|
ee1f37 |
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
|
|
|
ee1f37 |
copy of the license is included in the section entitled GNU Free
|
|
|
ee1f37 |
Documentation License.
|
|
|
ee1f37 |
-->
|
|
|
406f69 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
|
|
|
ee1f37 |
Karl Berry <karl@freefriends.org>
|
|
|
ee1f37 |
Olaf Bachmann <obachman@mathematik.uni-kl.de>
|
|
|
ee1f37 |
and many others.
|
|
|
ee1f37 |
Maintained by: Many creative people <dev@texi2html.cvshome.org>
|
|
|
ee1f37 |
Send bugs and suggestions to <users@texi2html.cvshome.org>
|
|
|
ee1f37 |
|
|
|
ee1f37 |
-->
|
|
|
ee1f37 |
<head>
|
|
|
f66721 |
<title>CentOS Artwork Repository: 2.26 The trunk/Identity/Themes/Motifs/Flame Directory</title>
|
|
|
ee1f37 |
|
|
|
f66721 |
<meta name="description" content="CentOS Artwork Repository: 2.26 The trunk/Identity/Themes/Motifs/Flame Directory">
|
|
|
f66721 |
<meta name="keywords" content="CentOS Artwork Repository: 2.26 The trunk/Identity/Themes/Motifs/Flame Directory">
|
|
|
ee1f37 |
<meta name="resource-type" content="document">
|
|
|
ee1f37 |
<meta name="distribution" content="global">
|
|
|
ee1f37 |
<meta name="Generator" content="texi2html 1.76">
|
|
|
ee1f37 |
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
|
|
ee1f37 |
<style type="text/css">
|
|
|
ee1f37 |
|
|
|
ee1f37 |
@import "/home/centos/artwork/trunk/Identity/Models/Css/Texi2html/common.css";
|
|
|
ee1f37 |
|
|
|
ee1f37 |
a.summary-letter {text-decoration: none}
|
|
|
ee1f37 |
pre.display {font-family: serif}
|
|
|
ee1f37 |
pre.format {font-family: serif}
|
|
|
ee1f37 |
pre.menu-comment {font-family: serif}
|
|
|
ee1f37 |
pre.menu-preformatted {font-family: serif}
|
|
|
ee1f37 |
pre.smalldisplay {font-family: serif; font-size: smaller}
|
|
|
ee1f37 |
pre.smallexample {font-size: smaller}
|
|
|
ee1f37 |
pre.smallformat {font-family: serif; font-size: smaller}
|
|
|
ee1f37 |
pre.smalllisp {font-size: smaller}
|
|
|
ee1f37 |
span.sansserif {font-family:sans-serif; font-weight:normal;}
|
|
|
ee1f37 |
ul.toc {list-style: none}
|
|
|
ee1f37 |
-->
|
|
|
ee1f37 |
</style>
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
</head>
|
|
|
ee1f37 |
|
|
|
ee1f37 |
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
063806 |
[ < ]
|
|
|
063806 |
[ > ]
|
|
|
ee1f37 |
|
|
|
f66721 |
[ << ]
|
|
|
f66721 |
[ Up ]
|
|
|
f66721 |
[ >> ]
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
56a476 |
[Top]
|
|
|
56a476 |
[Contents]
|
|
|
f66721 |
[Index]
|
|
|
56a476 |
[ ? ]
|
|
|
ee1f37 |
|
|
|
f66721 |
|
|
|
063806 |
|
|
|
f66721 |
2.26 The <tt>`trunk/Identity/Themes/Motifs/Flame'</tt> Directory
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
063806 |
|
|
|
f66721 |
2.26.1 Goals
|
|
|
ee1f37 |
|
|
|
f66721 |
This section describes the steps we followed to construct the
|
|
|
f66721 |
Flame artistic motif. This section may be useful for anyone
|
|
|
f66721 |
interested in reproducing the Flame artistic motif, or in
|
|
|
f66721 |
creating new artistic motifs for The CentOS Project corporate visual
|
|
|
f66721 |
identity (see section The <tt>`trunk/Identity'</tt> Directory).
|
|
|
f66721 |
|
|
|
ee1f37 |
|
|
|
063806 |
|
|
|
f66721 |
2.26.2 Description
|
|
|
ee1f37 |
|
|
|
f66721 |
The Flame artistic motif was built using the flame filter of
|
|
|
f66721 |
Gimp 2.2 in CentOS 5.5.
|
|
|
f66721 |
|
|
|
f66721 |
The flame filter of Gimp can produce stunning, randomly generated
|
|
|
f66721 |
fractal patterns. The flame filter of Gimp gives us a great oportunity
|
|
|
f66721 |
to reduce the time used to produce new artistic motifs, because of its
|
|
|
f66721 |
"randomly generated" nature. Once the artistic motif be created, it
|
|
|
f66721 |
is propagated through all visual manifestations of CentOS Project
|
|
|
f66721 |
corporate visual identity using the <tt>`centos-art.sh'</tt> script
|
|
|
f66721 |
(see section The <tt>`trunk/Scripts/Bash'</tt> Directory) inside the CentOS Artwork Repository.
|
|
|
f66721 |
|
|
|
f66721 |
To set the time intervals between each new visual style production, we
|
|
|
f66721 |
could reuse the CentOS distribution major release schema. I.e., we
|
|
|
f66721 |
could produce a new visual style, every two years, based on a new
|
|
|
f66721 |
"randomly generated" flame pattern, and publish the whole corporate
|
|
|
f66721 |
visual identity (i.e., distribution stuff, promotion stuff, websites
|
|
|
f66721 |
stuff, etc.) with the new major release of CentOS distribution all
|
|
|
f66721 |
together at once.
|
|
|
f66721 |
|
|
|
f66721 |
Producing a new visual style is not one day's task. Once we have
|
|
|
f66721 |
defined the artistic motif, we need to propagate it through all visual
|
|
|
f66721 |
manifestations of The CentOS Project corporate visual identity. When
|
|
|
f66721 |
we say that we could produce one new visual style every two years we
|
|
|
f66721 |
really mean: to work two years long in order to propagate a new visual
|
|
|
f66721 |
style to all visual manifestations of The CentOS Project corporate
|
|
|
f66721 |
visual identity.
|
|
|
f66721 |
|
|
|
f66721 |
Obviously, in order to propagate one visual style to all different
|
|
|
f66721 |
visual manifestations of The CentOS Project corporate visual identity,
|
|
|
f66721 |
we need first to know which the visual manifestations are. To define
|
|
|
f66721 |
which visual manifestations are inside The CentOS Project corporate
|
|
|
f66721 |
visual identity is one of the goals the CentOS Artwork Repository and
|
|
|
f66721 |
this documentation manual are both aimed to satisfy.
|
|
|
f66721 |
|
|
|
f66721 |
Once we define which the visual manifestation are, it is possible to
|
|
|
f66721 |
define how to produce them, and this way, organize the automation
|
|
|
f66721 |
process. Such automation process is one of the goals of
|
|
|
f66721 |
<tt>`centos-art.sh'</tt> script.
|
|
|
f66721 |
|
|
|
f66721 |
With the combination of both CentOS Artwork Repository and
|
|
|
f66721 |
<tt>`centos-art.sh'</tt> scripts we define work lines where translators,
|
|
|
f66721 |
programmers, and graphic designers work together to distribute and
|
|
|
f66721 |
reduce the amount of time employed to produce The CentOS Project
|
|
|
f66721 |
monolithic corporate identity.
|
|
|
f66721 |
|
|
|
f66721 |
From a monolithic corporate visual identity point of view, notice that
|
|
|
f66721 |
we are producing a new visual style for the same theme (i.e.,
|
|
|
f66721 |
Flame). It would be another flame design but still a flame
|
|
|
f66721 |
design. This idea is very important to be aware of, because we are
|
|
|
f66721 |
somehow "refreshing" the theme, not changing it at all.
|
|
|
f66721 |
|
|
|
f66721 |
This way, as we are "refreshing" the theme, we still keep oursleves
|
|
|
f66721 |
inside the monolithic conception we are trying to be attached to
|
|
|
f66721 |
(i.e., one unique name, and one unique visual style for all visual
|
|
|
f66721 |
manifestations).
|
|
|
f66721 |
|
|
|
f66721 |
Producing artistic motifs is a creative process that may consume long
|
|
|
f66721 |
time, specially for people without experienced knowledge on graphic
|
|
|
f66721 |
design land. Using "randomly generated" conception to produce
|
|
|
f66721 |
artistic motifs could be, practically, a way for anyone to follow in
|
|
|
f66721 |
order to produce maintainable artistic motifs in few steps.
|
|
|
f66721 |
|
|
|
f66721 |
Due to the "randomly generated" nature of Flame filter, we find that
|
|
|
f66721 |
Flame pattern is not always the same when we use Flame
|
|
|
f66721 |
filter interface.
|
|
|
f66721 |
|
|
|
f66721 |
Using the same pattern design for each visual manifestation is
|
|
|
f66721 |
essential in order to maintain the visual connection among all visual
|
|
|
f66721 |
manifestations inside the same theme. Occasionally, we may introduce
|
|
|
f66721 |
pattern variations in opacity, size, or even position but never change
|
|
|
f66721 |
the pattern design itself, nor the color information used by images
|
|
|
f66721 |
considered part of the same theme.
|
|
|
f66721 |
|
|
|
f66721 |
 Important
|
|
|
f66721 |
When we design background images, which are considered part of the
|
|
|
f66721 |
same theme, it is essential to use the same design pattern always.
|
|
|
f66721 |
This is what makes theme images to be visually connected among
|
|
|
f66721 |
themeselves, and so, the reason we use to define the word "theme"
|
|
|
f66721 |
as: a set of images visually connected among themeselves.
|
|
|
f66721 |
|
|
|
aaf678 |
|
|
|
f66721 |
In order for us to reproduce the same flame pattern always,
|
|
|
f66721 |
Flame filter interface provides the <samp>`Save'</samp> and <samp>`Open'</samp>
|
|
|
f66721 |
options. The <samp>`Save'</samp> option brings up a file save dialog that
|
|
|
f66721 |
allows you to save the current Flame settings for the plug-in, so that
|
|
|
f66721 |
you can recreate them later. The <samp>`Open'</samp> option brings up a file
|
|
|
f66721 |
selector that allows you to open a previously saved Flame settings
|
|
|
f66721 |
file.
|
|
|
f66721 |
|
|
|
f66721 |
The Flame settings we used in our example are saved in the file:
|
|
|
f66721 |
|
|
|
f66721 |
trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def
|
|
|
f66721 |
|
|
|
aaf678 |
|
|
|
f66721 |
|
|
|
f66721 |
2.26.3 Construction
|
|
|
ee1f37 |
|
|
|
b9dbd3 |
|
|
|
063806 |
|
|
|
f66721 |
2.26.3.1 Step 1: Set image size
|
|
|
f66721 |
|
|
|
f66721 |
Create an empty image and fill the <samp>`Background'</samp> layer with black
|
|
|
f66721 |
(000000) color. Image dimensions depend on the final
|
|
|
f66721 |
destination you plan to use the image for. For the sake of our
|
|
|
f66721 |
construction example we used an image of 640x480 pixels and 300 pixels
|
|
|
f66721 |
per inch (ppi).
|
|
|
f66721 |
|
|
|
f66721 |
|
|
|
f66721 |
|
|
|
f66721 |
2.26.3.2 Step 2: Add base color and pattern information
|
|
|
f66721 |
|
|
|
f66721 |
Create a new layer named <samp>`Base'</samp>, place it over <samp>`Background'</samp>
|
|
|
f66721 |
layer and fill it with the base color (7800ff) you want to have
|
|
|
f66721 |
your background image set in. Add a mask to <samp>`Base'</samp> layer using
|
|
|
f66721 |
radial gradient and blur it. You may need to repeat this step more
|
|
|
f66721 |
than once in order to achieve a confortable black radial degradation
|
|
|
f66721 |
on the right side of your design.
|
|
|
f66721 |
|
|
|
f66721 |
Duplicate <samp>`Base'</samp> layer and name it <samp>`Paper'</samp>. Place
|
|
|
f66721 |
<samp>`Paper'</samp> layer over <samp>`Base'</samp> layer. Remove content of
|
|
|
f66721 |
<samp>`Paper'</samp> layer and fill it with <samp>`Paper (100x100)'</samp> pattern.
|
|
|
f66721 |
Once you've done with black radial degradation, reduce the
|
|
|
f66721 |
<samp>`Paper'</samp> layer opacity to 20%.
|
|
|
f66721 |
|
|
|
f66721 |
Notice that when we duplicate one layer, the mask information related
|
|
|
f66721 |
to layer is preserved from previous to next layer. This saves us some
|
|
|
f66721 |
of the time required to produce different layers with the same mask
|
|
|
f66721 |
information on them.
|
|
|
f66721 |
|
|
|
f66721 |
Duplicate <samp>`Paper'</samp> layer and rename it <samp>`Stripes'</samp>. Remove
|
|
|
f66721 |
paper pattern from <samp>`Stripes'</samp> layer. Fill <samp>`Stripes'</samp> layer
|
|
|
f66721 |
with <samp>`Stripes (48x48)'</samp> pattern and reduce the <samp>`Stripes'</samp>
|
|
|
f66721 |
layer opacity to 15%.
|
|
|
f66721 |
|
|
|
f66721 |
|
|
|
f66721 |
|
|
|
f66721 |
2.26.3.3 Step 3: Add flame motif
|
|
|
f66721 |
|
|
|
f66721 |
Create a new layer named <samp>`Flame'</samp>. Set the foreground
|
|
|
f66721 |
(003cff) and background (0084ff) colors to the gradient
|
|
|
f66721 |
you want to build the flame motif.
|
|
|
f66721 |
|
|
|
f66721 |
To build flame motif, use the flame filter (<samp>`Filters > Render >
|
|
|
f66721 |
Nature > Flame...'</samp>) on <samp>`Flame'</samp> layer. We used a layer mask, with
|
|
|
f66721 |
a radial gradient on it to control the boundaries of flame motif on
|
|
|
f66721 |
<samp>`Flame'</samp> layer.
|
|
|
f66721 |
|
|
|
f66721 |
Duplicate <samp>`Flame'</samp> layer and rename it `Flame Blur'. Place `Flame
|
|
|
f66721 |
Blur' below <samp>`Flame'</samp> layer. Apply Gussian blur filter
|
|
|
f66721 |
(<samp>`Filters > Blur > Gussian Blur...'</samp>) until reaching the desiered
|
|
|
f66721 |
effect.
|
|
|
f66721 |
|
|
|
f66721 |
The opacity value, in <samp>`Flame'</samp> layers, may vary from one image to
|
|
|
f66721 |
another based on the place the image will be finally placed on. For
|
|
|
f66721 |
example, images used as desktop background have the <samp>`Flame'</samp> layer
|
|
|
f66721 |
opacity set at 100% but <samp>`Flame Blur'</samp> is set to 70%. However, you
|
|
|
f66721 |
may find that background images used in anaconda progress slides have
|
|
|
f66721 |
opacity reduced differently, in order to reduce brightness in a way
|
|
|
f66721 |
that texts could look clean and readable over it.
|
|
|
f66721 |
|
|
|
f66721 |
|
|
|
f66721 |
|
|
|
f66721 |
2.26.3.4 Step 4: Add foreground color
|
|
|
f66721 |
|
|
|
f66721 |
Create a new layer named <samp>`Color'</samp>, place it on top of all visible
|
|
|
f66721 |
layers and fill it with plain color (4c005a). Reduce
|
|
|
f66721 |
<samp>`Color'</samp> layer opacity to 20%. You can use the <samp>`Color'</samp> layer
|
|
|
f66721 |
to control the right side color information you want to produce the
|
|
|
f66721 |
image for.
|
|
|
f66721 |
|
|
|
f66721 |
Duplicate <samp>`Flame'</samp> layer and create a new layer named
|
|
|
f66721 |
<samp>`Color#1'</samp>. Place <samp>`Color#1'</samp> layer on top of layer named
|
|
|
f66721 |
<samp>`Color'</samp>. Remove the mask information from <samp>`Color#1'</samp> layer
|
|
|
f66721 |
and recreate a new one using an inverted alpha channel as reference.
|
|
|
f66721 |
Remove <samp>`Color#1'</samp> layer content and fill it back with plain black
|
|
|
f66721 |
(000000) color. Reduce <samp>`Color#1'</samp> opacity to 20%. In this
|
|
|
f66721 |
step we created a mask to protect the flame artistic motif from black
|
|
|
f66721 |
color, so when we decrement or increment the opacity of layer, the
|
|
|
f66721 |
flame artistic motif wouldn't be affected, just the environment
|
|
|
f66721 |
suround it.
|
|
|
f66721 |
|
|
|
f66721 |
When you set color information, remember that the same artistic motif
|
|
|
f66721 |
needs to be indexed to 14 and 16 colors, in order to produce Grub and
|
|
|
f66721 |
Syslinux visual manifestations respectively. Using many different
|
|
|
f66721 |
colors in the artistic motif may reduce the possibility of your design
|
|
|
f66721 |
to fix all different situations in. Likewise, using more colors in
|
|
|
f66721 |
one design, and less colors in another design will reduce the
|
|
|
f66721 |
connectivity among your designs, since color information is relevant
|
|
|
f66721 |
to visual identity.
|
|
|
f66721 |
|
|
|
f66721 |
When you propagate your artistic motif visual style to different
|
|
|
f66721 |
visual manifestations of CentOS Project corporate visual identity, it
|
|
|
f66721 |
is up to you to find out justice and compromise among all possible
|
|
|
f66721 |
variables you may face.
|
|
|
f66721 |
|
|
|
f66721 |
|
|
|
f66721 |
|
|
|
f66721 |
2.26.4 See also
|
|
|
ee1f37 |
|
|
|
f66721 |
|
|
|
f66721 |
2.25 The <tt>`trunk/Identity/Themes/Motifs'</tt> Directory
|
|
|
f66721 |
|
|
|
f66721 |
2.17 The <tt>`trunk/Identity/Themes'</tt> Directory
|
|
|
f66721 |
|
|
|
f66721 |
2.4 The <tt>`trunk/Identity'</tt> Directory
|
|
|
f66721 |
|
|
|
f66721 |
2.3 The <tt>`trunk'</tt> Directory
|
|
|
f66721 |
|
|
|
f66721 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
f66721 |
[ < ]
|
|
|
f66721 |
[ > ]
|
|
|
ee1f37 |
|
|
|
f66721 |
[ << ]
|
|
|
063806 |
[ Up ]
|
|
|
f66721 |
[ >> ]
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
<font size="-1">
|
|
|
406f69 |
This document was generated on March, 1 2011 using texi2html 1.76.
|
|
|
ee1f37 |
</font>
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
|
|
|
ee1f37 |
</body>
|
|
|
ee1f37 |
</html>
|