| <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd"> |
| <html> |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| <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#SEC136" title="Previous section in reading order"> < </a>]</td> |
| <td valign="middle" align="left">[<a href="#SEC138" 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#SEC361" 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#SEC361" 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="SEC137"></a> |
| <h2 class="section"> 3.23 trunk/Identity/Themes/Motifs/Flame </h2> |
| |
| <p>The <em>Flame</em> artistic motif was completly built using Gimp 2.2 in |
| CentOS 5.5. In this section we describe the steps we followed through |
| its construction. This information 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> |
| <p><img src="/home/centos/artwork/trunk/Identity/Themes/Motifs/Flame/Concept/Img/motif.jpg" alt="trunk/Identity/Themes/Motifs/Flame/Concept/Img/motif"> |
| </p> |
| |
| <a name="SEC138"></a> |
| <h3 class="subsection"> 3.23.1 Step 1: Set image size </h3> |
| |
| <p>Create an empty image and fill the Background layer with black |
| (<samp>`000000'</samp>) color. Image dimensions depends 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> |
| <p><img src="/home/centos/artwork/trunk/Identity/Themes/Motifs/Flame/Screenshots/Construction/1.jpg" alt="trunk/Identity/Themes/Motifs/Flame/Screenshots/Construction/1"> |
| </p> |
| |
| <a name="SEC139"></a> |
| <h3 class="subsection"> 3.23.2 Step 2: Add patterns </h3> |
| |
| <p>Create a new layer named <samp>`Paper'</samp>, place it over <samp>`Background'</samp> |
| layer and fill it with <samp>`Paper (100x100)'</samp> pattern. |
| </p> |
| <p>Add a mask to <samp>`Paper'</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. |
| In our image dimension, the central point of radial degradation is at |
| 430x296 approximately. Once you've done with black radial degradation, |
| reduce the <samp>`Paper'</samp> layer opacity to 20%. |
| </p> |
| <p>Duplicate <samp>`Paper'</samp> layer and rename it <samp>`Stripes'</samp> |
| --duplicating the layer helps us to be sure the layer masks will be |
| equal in both <samp>`Paper'</samp> and <samp>`Stripes'</samp> layers--. 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> |
| <p><img src="/home/centos/artwork/trunk/Identity/Themes/Motifs/Flame/Screenshots/Construction/2.jpg" alt="trunk/Identity/Themes/Motifs/Flame/Screenshots/Construction/2"> |
| </p> |
| |
| <a name="SEC140"></a> |
| <h3 class="subsection"> 3.23.3 Step 3: Add flame motif </h3> |
| |
| <p>Create a new layer named <samp>`Flame'</samp>. Set the foreground to white |
| color (<code>ffffff</code>). Use the Gimp's flame filter (<samp>`Filters > |
| Render > Nature > Flame...'</samp>) to build the flame motif on <samp>`Flame'</samp> |
| layer. |
| </p> |
| <p>The flame filter can produce stunning, randomly generated fractal |
| patterns. This feature of Gimp give us a great oportunity to grant the |
| production of new artistic motifs very quickly 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#SEC206">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 the |
| artistic motif defined, 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 knowlegde 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, you may find |
| that the same pattern is not always used each time you use the Flame |
| 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 to recreate the same flame pattern every time we may need to, |
| the Flame 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> |
| <p><img src="/home/centos/artwork/trunk/Identity/Themes/Motifs/Flame/Screenshots/Construction/3.jpg" alt="trunk/Identity/Themes/Motifs/Flame/Screenshots/Construction/3"> |
| </p> |
| <p>Ok. Now that we have created the flame motif, and also divagated a bit |
| about it, lets continue with the construction steps. |
| </p> |
| <p>Duplicate <samp>`Flame'</samp> layer and rename it `Flame Blur'. Place `Flame |
| Blur' below <samp>`Flame'</samp> layer. Add gussian blur filter (<samp>`Filters |
| > Blur > Gussian Blur...'</samp>). |
| </p> |
| <pre class="verbatim">Horizontal:10.0 |
| Vertical:10.0 |
| </pre> |
| <p>Duplicate <samp>`Flame'</samp> layer and rename it `Flame Softglow'. Place |
| `Flame Softglow' above <samp>`Flame'</samp> layer. Add Softglow filter |
| (<samp>`Filters > Artisitc > Softglow...'</samp>). |
| </p> |
| <pre class="verbatim">Glow radius: 10.00 |
| Brightness: 0.75 |
| Sharpness: 0.85 |
| </pre> |
| <p>Reduce flame layers opacity using the same value. The value used to |
| reduce flame layers opacity may vary from one image to another, |
| specifically, on the place the image will be finally placed on. For |
| example, images used as desktop background have the flame layers |
| opacity reduced to 50% in order to reduce brightness. Otherwise, the |
| background image used in anaconda progress slides has flame layers |
| opacity reduced to 20% in order to reduce brightness even more so text |
| could look clean and readable over it. |
| </p> |
| <p><img src="/home/centos/artwork/trunk/Identity/Themes/Motifs/Flame/Screenshots/Construction/4.jpg" alt="trunk/Identity/Themes/Motifs/Flame/Screenshots/Construction/4"> |
| </p> |
| |
| <a name="SEC141"></a> |
| <h3 class="subsection"> 3.23.4 Step 4: Add foreground color </h3> |
| |
| <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 10%. You can use the <samp>`Color'</samp> layer |
| to control the final color information you want to produce the image |
| for. |
| </p> |
| <p><img src="/home/centos/artwork/trunk/Identity/Themes/Motifs/Flame/Screenshots/Construction/5.jpg" alt="trunk/Identity/Themes/Motifs/Flame/Screenshots/Construction/5"> |
| </p> |
| <p>When setting color information, remember that the same artistic motif |
| needs to be reproduced in 14 and 16 colors for Grub and Syslinux |
| visual manifestations respectively. Using many different colors in the |
| artistic motif may reduce the possibility of your design to fix in all |
| different situations. 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>It is up to you to find out justice and compromise among all possible |
| variables you may face, when you propagate your artistic motif visual |
| style to different visual manifestations of CentOS Project corporate |
| visual identity. |
| </p> |
| |
| <a name="SEC142"></a> |
| <h3 class="subsection"> 3.23.5 See also </h3> |
| |
| |
| |
| <table cellpadding="1" cellspacing="1" border="0"> |
| <tr><td valign="middle" align="left">[<a href="#SEC141" title="Previous section in reading order"> < </a>]</td> |
| <td valign="middle" align="left">[<a href="repository_27.html#SEC143" 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="#SEC137" title="Up section"> Up </a>]</td> |
| <td valign="middle" align="left">[<a href="repository_64.html#SEC361" title="Next chapter"> >> </a>]</td> |
| </tr></table> |
| <p> |
| <font size="-1"> |
| This document was generated on <i>December, 4 2010</i> using <a class="www" href="http://texi2html.cvshome.org/"><i>texi2html 1.76</i></a>. |
| </font> |
| <br> |
| |
| </p> |
| </body> |
| </html> |