Blob Blame History Raw
<?xml version="1.0"?>
<!DOCTYPE html
    PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>

    <title>CentOS Artwork Repository: 2.24 The trunk/Identity/Themes/Models/Default/Distro Directory</title>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
    <meta name="description" content="CentOS Artwork Repository: 2.24 The trunk/Identity/Themes/Models/Default/Distro Directory" />
    <meta name="keywords" content="CentOS Artwork Repository: 2.24 The trunk/Identity/Themes/Models/Default/Distro Directory" />
    <meta name="resource-type" content="document" />
    <meta name="distribution" content="global" />
    <meta name="generator" content="texi2html 1.76" />
    <meta name="copyright" content="2009-2011 Alain Reguera Delgado" />

    <link href="/home/centos/artwork/trunk/Identity/Manual/repository.css" rel="stylesheet" type="text/css" media="screen projection" />

</head>

<body>

<a name="top" />

<div id="wrap">

    <div id="page-body">

        <div id="content">

<!-- Created on March, 30 2011 by texi2html 1.76 -->
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="repository_30.xhtml#SEC141" title="Previous section in reading order"> &lt; </a>]</td>
<td valign="middle" align="left">[<a href="#SEC143" title="Next section in reading order"> &gt; </a>]</td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left">[<a href="repository_7.xhtml#SEC12" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
<td valign="middle" align="left">[<a href="repository_7.xhtml#SEC12" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_80.xhtml#SEC416" title="Next chapter"> &gt;&gt; </a>]</td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left">[<a href="repository.xhtml#SEC_Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="repository_toc.xhtml#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="repository_80.xhtml#SEC416" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="repository_abt.xhtml#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Directories-trunk-Identity-Themes-Models-Default-Distro"></a>
<a name="SEC142"></a>
<h2 class="section"> 2.24 The <tt>`trunk/Identity/Themes/Models/Default/Distro'</tt> Directory </h2>

<div class="page-line white"><hr style="display:none;" /></div>
<a name="SEC143"></a>
<h3 class="subsection"> 2.24.1 Goals </h3>

<p>This directory provides design models to produce image files for the
following CentOS Distribution components:
</p>
<dl compact="compact">
<dt> <strong>Syslinux</strong></dt>
<dd><p>Contains design models for syslinux, the program used to boot the
CentOS Distribution installation media. See section <a href="repository_40.xhtml#SEC187">The <tt>`trunk/Identity/Themes/Models/Default/Distro/Syslinux'</tt> Directory</a>, for more information.
</p>
</dd>
<dt> <strong>Anaconda</strong>  </dt>
<dd><p>Contains design models for Anaconda, the program used to install
CentOS Distribution.  See section <a href="repository_32.xhtml#SEC147">The <tt>`trunk/Identity/Themes/Models/Default/Distro/Anaconda'</tt> Directory</a>, for more information.
</p>
</dd>
<dt> <strong>Firstboot</strong>  </dt>
<dd><p>Contains design models for the first boot program used to configure
the maching onece installed.  See section <a href="repository_33.xhtml#SEC152">The <tt>`trunk/Identity/Themes/Models/Default/Distro/Firstboot'</tt> Directory</a>, for more information.
</p>
</dd>
<dt> <strong>Rhgb</strong></dt>
<dd><p>Contains design models for CentOS Graphical Boot, the program used to
show the boot process from Grub to Display Manager.  See section <a href="repository_39.xhtml#SEC182">The <tt>`trunk/Identity/Themes/Models/Default/Distro/Rhgb'</tt> Directory</a>, for more
information.
</p>
</dd>
<dt> <strong>Gdm</strong>  </dt>
<dd><p>Contains design models for GNOME Display Manager, the program used to
log into the manchine once installed and configured. See section <a href="repository_34.xhtml#SEC157">The <tt>`trunk/Identity/Themes/Models/Default/Distro/Gdm'</tt> Directory</a>, for more
information.
</p>
</dd>
<dt> <strong>Kdm</strong>  </dt>
<dd><p>Contains design models for KDE Display Manager, the program used to
log into the manchine once installed and configured. See section <a href="repository_37.xhtml#SEC172">The <tt>`trunk/Identity/Themes/Models/Default/Distro/Kdm'</tt> Directory</a>, for more
information.
</p>
</dd>
<dt> <strong>Grub</strong> </dt>
<dd><p>Contains design models for GRUB (Grand Unified Boot Loader), the
program used to boot the machine into an operating system.
See section <a href="repository_37.xhtml#SEC172">The <tt>`trunk/Identity/Themes/Models/Default/Distro/Kdm'</tt> Directory</a>, for
more information.
</p>
</dd>
<dt> <strong>Gsplash</strong> </dt>
<dd><p>Contains design models for GNOME splash, the program used to show the
progress information while user's graphical session is loading.
See section <a href="repository_36.xhtml#SEC167">The <tt>`trunk/Identity/Themes/Models/Default/Distro/Gsplash'</tt> Directory</a>,
for more information.
</p>
</dd>
<dt> <strong>Ksplash</strong>  </dt>
<dd><p>Contains design models for KDE splash, the program used to show the
progress information while user's graphical session is loading.
See section <a href="repository_38.xhtml#SEC177">The <tt>`trunk/Identity/Themes/Models/Default/Distro/Ksplash'</tt> Directory</a>,
for more information.
</p></dd>
</dl>
<div class="page-line white"><hr style="display:none;" /></div>
<a name="SEC144"></a>
<h3 class="subsection"> 2.24.2 Description </h3>

<p>The CentOS Distribution visual style is controlled by image files.
These image files are packaged inside The CentOS Distribution and made
visible once such packages are installed and executed. The way to go
for changing The CentOS Distribution visual style is changing all
those image files to add the desired visual style first and later,
repackage them to make them available inside the final iso files of
CentOS Distribution.
</p>
<div class="page-line white"><hr style="display:none;" /></div>
<a name="SEC145"></a>
<h3 class="subsection"> 2.24.3 Usage </h3>

<p>This directory provides organizationl structure to store default
design models for CentOS Themes of CentOS Distribution and so it
should be considered to be used.
</p>
<p>When a new component is added to CentOS Distribution, this is the
directory you need to go for specifying design models for image files
inside such component. 
</p>
<p>The procedure to follow is creatig a directory for each component
using its very same name (e.g., the directory <tt>`Anaconda'</tt> stores
image files for Anaconda component, the installer program). Inside the
directory, you need to create one scalable vector graphic for each
image file inside the component you want to produce images for. This,
in order to set image dimensions, image file-name, position of
trademarks in the final image, translation markers and whatever common
information you need to have specified in them when rendered by
<code>centos-art</code> script.
</p>
<p>Sometimes, between major releases, image files inside packages can be
added, removed or just change their names. In order to describe such
image files variations, the design models directory structure is
organized in the same way the file variations are introduced (i.e.,
through The CentOS Project Release Schema).  So, each major release of
CentOS Distribution does have its own design model directory structure
in this directory.
</p>
<p>When a whole package is removed from one or all CentOS Distribution
major releases, the design models directory structure releated to it
is no longer used.  However it could be very useful for historical
reasons.  Also, someone could feel motivated enough to keep himself
documenting it or supporting it for whatever reason.
</p>
<div class="page-line white"><hr style="display:none;" /></div>
<a name="SEC146"></a>
<h3 class="subsection"> 2.24.4 See also </h3>

<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="repository_29.xhtml#SEC132">2.22 The <tt>`trunk/Identity/Themes/Models/Default'</tt> Directory</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
</td></tr>
</table>

<div class="page-line white"><hr style="display:none;" /></div>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#SEC145" title="Previous section in reading order"> &lt; </a>]</td>
<td valign="middle" align="left">[<a href="repository_32.xhtml#SEC147" title="Next section in reading order"> &gt; </a>]</td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left">[<a href="repository_7.xhtml#SEC12" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
<td valign="middle" align="left">[<a href="#SEC142" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_80.xhtml#SEC416" title="Next chapter"> &gt;&gt; </a>]</td>
</tr></table>

            <div class="page-line"><hr style="display:none;" /></div>

        </div>

    </div>

    <div class="page-line white"><hr style="display:none;" /></div>

</div>

</body>

</html>