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