diff --git a/Identity/Manual/repository.info.bz2 b/Identity/Manual/repository.info.bz2 index ff334db..c12942c 100644 Binary files a/Identity/Manual/repository.info.bz2 and b/Identity/Manual/repository.info.bz2 differ diff --git a/Identity/Manual/repository.pdf b/Identity/Manual/repository.pdf index b5d8d3e..91780cd 100644 Binary files a/Identity/Manual/repository.pdf and b/Identity/Manual/repository.pdf differ diff --git a/Identity/Manual/repository.txt.bz2 b/Identity/Manual/repository.txt.bz2 index 0bfe6dc..61c073b 100644 Binary files a/Identity/Manual/repository.txt.bz2 and b/Identity/Manual/repository.txt.bz2 differ diff --git a/Identity/Manual/repository.xhtml.tar.bz2 b/Identity/Manual/repository.xhtml.tar.bz2 index 3af3ae0..e96c741 100644 Binary files a/Identity/Manual/repository.xhtml.tar.bz2 and b/Identity/Manual/repository.xhtml.tar.bz2 differ diff --git a/Identity/Manual/repository.xml b/Identity/Manual/repository.xml index 19be124..5609f43 100644 --- a/Identity/Manual/repository.xml +++ b/Identity/Manual/repository.xml @@ -343,13 +343,58 @@ manual_deleteCrossReferences.sh manual_searchIndex.sh - Directories trunk Identity Icons - Directories trunk Identity Icons + Directories trunk Identity Locales + Directories trunk Identity Locales - Directories trunk Identity Release - Directories trunk Identity Release + Directories trunk Identity Locales Identity + Directories trunk Identity Locales Identity + + + + Directories trunk Identity Locales Identity Brands + Directories trunk Identity Locales Identity Brands + + + + Directories trunk Identity Locales Identity Brands Tpl + Directories trunk Identity Locales Identity Brands Tpl + + + + Directories trunk Identity Locales Identity Fonts + Directories trunk Identity Locales Identity Fonts + + + + Directories trunk Identity Locales Identity Models + Directories trunk Identity Locales Identity Models + + + + Directories trunk Identity Locales Identity Release + Directories trunk Identity Locales Identity Release + + + + Directories trunk Identity Locales Identity Themes + Directories trunk Identity Locales Identity Themes + + + + Directories trunk Identity Locales Identity Themes Backgrounds + Directories trunk Identity Locales Identity Themes Backgrounds + + + + Directories trunk Identity Locales Identity Themes Distro Anaconda Progress + Directories trunk Identity Locales Identity Themes Distro Anaconda Progress + + + + Directories trunk Identity Locales Identity Widgets + Directories trunk Identity Locales Identity Widgets @@ -503,66 +548,6 @@ manual_deleteCrossReferences.sh manual_searchIndex.sh - Directories trunk Locales - Directories trunk Locales - - - - Directories trunk Locales Identity - Directories trunk Locales Identity - - - - Directories trunk Locales Identity Brands - Directories trunk Locales Identity Brands - - - - Directories trunk Locales Identity Brands Tpl - Directories trunk Locales Identity Brands Tpl - - - - Directories trunk Locales Identity Fonts - Directories trunk Locales Identity Fonts - - - - Directories trunk Locales Identity Models - Directories trunk Locales Identity Models - - - - Directories trunk Locales Identity Release - Directories trunk Locales Identity Release - - - - Directories trunk Locales Identity Themes - Directories trunk Locales Identity Themes - - - - Directories trunk Locales Identity Themes Backgrounds - Directories trunk Locales Identity Themes Backgrounds - - - - Directories trunk Locales Identity Themes Distro Anaconda Progress - Directories trunk Locales Identity Themes Distro Anaconda Progress - - - - Directories trunk Locales Identity Widgets - Directories trunk Locales Identity Widgets - - - - Directories trunk Manual - Directories trunk Manual - - - Directories trunk Scripts Directories trunk Scripts @@ -737,7 +722,7 @@ manual_deleteCrossReferences.sh manual_searchIndex.sh Manual This section organizes the CentOS Artwork Repository Manual (i.e., the documentation manual you're reading right now). If you are interested on improving The CentOS Artwork Repository Manual, in this place you'll find the Texinfo documentation structure you need to work with. - See Directories trunk Manual, for more information. + — Removed(xref:Directories trunk Manual) —, for more information. @@ -751,7 +736,7 @@ manual_deleteCrossReferences.sh manual_searchIndex.sh Locales This section organizes production of translation messages for Identity, Documentation and Scripts. This place is perfect to consolidate The CentOS Translation SIG. If you love translating, you'll find lot of messages waiting for you to translate here. - See Directories trunk Locales, for more information. + See Directories trunk Identity Locales, for more information. @@ -968,7 +953,7 @@ centos-art render trunk/Identity/Path/To/Dir Directories trunk Identity Fonts - Directories trunk Identity Icons + Directories trunk Identity Locales Directories trunk Identity Colors Directories
@@ -1018,13 +1003,37 @@ centos-art render trunk/Identity/Path/To/Dir
- Directories trunk Identity Icons - Directories trunk Identity Release + Directories trunk Identity Locales + Directories trunk Identity Locales Identity Directories trunk Identity Fonts Directories
- The <file>trunk/Identity/Icons</file> Directory - Directories trunk Identity Icons + The <file>trunk/Identity/Locales</file> Directory + Directories trunk Identity LocalesThe trunk/Locales directory exists to store the translation messages used to produce content in different languages. + Translation messages are organized using the directory structure of the component being translated. For example, if we want to provide translation messages for trunk/Manuals/Repository, then the trunk/Locales/Manuals/Repository directory needs to be created. + Once the locale directory exists for the component we want to provide translation messages for, it is necessary to create the translation files where translation messages are. The translation files follows the concepts of xml2po and GNU gettext tools. + The basic translation process is as follow: first, translatable strings are extracted from files and a portable object template (.pot) is created or updated with the information. Using the portable object template, a portable object (.po) is created or updated for translator to locale the messages retrived. Finally, a machine object (.mo) is created from portable object to sotore the translated messages. + Inside the repository there are two ways to retrive translatable strings from files. The first one is through xml2po command and the second through xgettext command. The xml2po is used to retrive translatable strings from XML files (e.g., Scalable Vector Graphics, DocBook, etc.) and the xgettext command is used to retrive translatable strings from shell scripts files (e.g., the files that make the centos-art.sh command-line interface). + When translatable strings are retrived from XML files, using the xml2po command, there is no need to create the machine object as we do when translatable strings ar retrived from shell files, using the xgettext command. The xml2po produces a temporal machine object in order to create a translated XML file. Once the translated XML file has been created the machine object is no longer needed. On the other hand, the machine object produced by the xgettext command is required by the system in order for the show shell script localized messages. + Another difference between xml2po and xgettext we need to be aware of is the directory structure used to store machine objects. In xml2po, the machine object is created in the current working directory as .xml2po.mo and can be safetly removed once the translated XML file has been created. In the case of xgettext, the machine object needs to be stored in the $TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo file in order for the system to interpret it and should not be removed since it is the file that contain the translation messages themselves. + Automation of localization tasks is achived through the locale functionality of command-line interface. + + + Directories trunk Scripts Functions Locale + Directories trunk Scripts Functions Locale + + + +
+ + + Directories trunk Identity Locales Identity + Directories trunk Identity Locales Identity Brands + Directories trunk Identity Locales + Directories +
+ The <file>trunk/Identity/Locales/Identity</file> Directory + Directories trunk Identity Locales Identity Goals @@ -1037,63 +1046,131 @@ centos-art render trunk/Identity/Path/To/Dir Description + + • + + ... + + Usage + + • + + ... + + See also + + + + + + + + Directories trunk Identity + Directories trunk Identity + +
- Directories trunk Identity Release - Directories trunk Identity Themes - Directories trunk Identity Icons + Directories trunk Identity Locales Identity Brands + Directories trunk Identity Locales Identity Brands Tpl + Directories trunk Identity Locales Identity Directories
- The <file>trunk/Identity/Release</file> Directory - Directories trunk Identity Release + The <file>trunk/Identity/Locales/Identity/Brands</file> Directory + Directories trunk Identity Locales Identity Brands Goals • - ... + Organize brands' translation files. Description + Translation files, inside trunk/Translations/Identity/Brands translation entry, don't use default rendering translation functionality, they use the following translation pre-rendering configuration file instead: + + Inside trunk/Translations/Identity/Brands translation entry, translation files are symbolic links pointing to the common template translation structure, inside the translation template (Tpl/) directory. + Inside trunk/Translations/Identity/Brands translation entry, translation files are created using identity design templates as reference. The translation pre-rendering script creates a translation structure where the translation template (Tpl/) directory structure applies to each single design template available. + For example, if the brands' translation template (Tpl/) directory has 30 translation files, and there are 20 design templates; the brands' translation pre-rendering script creates a translation structure of symbolic links where the 30 translation files apply the 20 design templates one by one, producing 600 translation symbolic links as result. At this point, when rendering identity, the centos-art script considers translation symbolic links as translation files. + Translation file names, inside brands' translation template (Tpl) directory have special meaning: + + + Conventional file names + Translation brands file names Convenctional file names look like blue.sed, 2c-a.sed, etc. Replacement commands inside translation file are applied to design templates and translation file names are used as final image name. The image dimensions use the same dimensions that design template has. + + + + Numeric file names + Translation brands file names Numeric file names look like 300.sed, 200.sed, etc. Replacements commands inside translation files are applied to design templates, and translation file names are used as final image name. The final image is saved using an specific width defined by the number part of the translation file name. The image height is automatically scaled based on the previous width definition to maintain the designing ratio. + For example, if your design template has 400x200 pixels of dimension, and you apply a translation file named `300.sed' to it, the final image you get as result will have 300x100 pixels of dimension. The same is true if you use higher numbers like `1024.sed', `2048.sed', etc. In these cases you have bigger images proportionally. + As we are using scalable vector graphics to design identity templates, the image size you produce is not limitted in size. You can use one design template produced in 400x200 pixels to produce larger or shorter PNG images using numeric translation files as described above. + + + + Translation markers + Inside trunk/Translations/Identity/Brands/, translation files combine the following translation markers: + + + #000000 + + Specify which color to use when rendering brand images. + + Note As translation files inside trunk/Translations/Identity/Brands are symbolic links that point to template translation files, translation markers are defined inside template translation files. + + + +
+ Usage + How to render brands' translation files To render brands' translation files, use the following command: + See also + + + Directories trunk Identity Brands + Directories trunk Identity Brands + +
- Directories trunk Identity Themes - Directories trunk Identity Themes Models - Directories trunk Identity Release + Directories trunk Identity Locales Identity Brands Tpl + Directories trunk Identity Locales Identity Fonts + Directories trunk Identity Locales Identity Brands Directories
- The <file>trunk/Identity/Themes</file> Directory - Directories trunk Identity Themes + The <file>trunk/Identity/Locales/Identity/Brands/Tpl</file> Directory + Directories trunk Identity Locales Identity Brands Tpl Goals - The trunk/Identity/Themes/ directory exists to organize production of CentOS themes. @@ -1102,235 +1179,105 @@ centos-art render trunk/Identity/Path/To/Dir Usage - In this location themes are organized in “Models” —to store common information— and “Motifs”—to store unique information. At rendering time, both motifs and models are combined to produce the final CentOS themes. CentOS themes can be tagged as “Default” or “Alternative”. CentOS themes are maintained by CentOS community. - - - Directories trunk Identity Themes Models - Directories trunk Identity Themes Models - - - - Directories trunk Identity Themes Motifs - Directories trunk Identity Themes Motifs - - - See also - - Directories trunk Identity - Directories trunk Identity - - - - Directories trunk - Directories trunk - -
- Directories trunk Identity Themes Models - Directories trunk Identity Themes Models Alternative - Directories trunk Identity Themes + Directories trunk Identity Locales Identity Fonts + Directories trunk Identity Locales Identity Models + Directories trunk Identity Locales Identity Brands Tpl Directories
- The <file>trunk/Identity/Themes/Models</file> Directory - Directories trunk Identity Themes Models + The <file>trunk/Identity/Locales/Identity/Fonts</file> Directory + Directories trunk Identity Locales Identity Fonts Goals - - • - - Organize theme models. - - + This section exists to organize fonts translation files. Description - Theme models let you modeling characteristics (e.g., dimensions, translation markers, position of each element on the display area, etc.) common to all themes. Theme models let you reduce the time needed when propagating artistic motifs to different visual manifestations. - Theme models serves as a central pool of design templates for themes to use. This way you can produce themes with different artistic motifs but same characteristics. + Translation files, inside trunk/Translations/Fonts, have the following structure: + + Inside trunk/Translations/Fonts, there is one translation file for each font preview image you want to produce. This way, we create one translation file for each font-family we use somewhere inside CentOS visual identity. + + Important Do not create translation files for font-families not used somewhere inside CentOS visual identity. The identity of font entry (see Directories trunk Identity Fonts) is used as reference when someone needs to know which font-families are allowed to use inside CentOS visual identity. + + + + Translation Markers + Inside trunk/Translations/Identity/Fonts, translation files combine the following translation markers: + + + font-family:Denmark + + Specify which font family to use when rendering font preview images. + + + + font-weight:normal + + Specify which font weight to use when rendering font preview images. + + + + font-style:normal + + Specify which font style to use when rendering font preview images. + + +
+ Usage - Inside the framework location above, you find theme models organized by name. You can add your own theme models to the structure by adding a directory to the list. By default you have the `See Directories trunk Identity Themes Models DefaultDefault,' and `See Directories trunk Identity Themes Models AlternativeAlternative,' ready-to-use theme models. + How to render fonts' translation files Inside trunk/Translations/Fonts you use your favorite text editor to create translation files. Inside trunk/Translations/Fonts there is not translation template directory (Tpl/), nor translation rendering using centos-art script. For example, to create the dejavu_lgc_sans-boldoblique.sed translation file using vim editor, type the following command: + See also + + Directories trunk Identity Fonts + Directories trunk Identity Fonts + +
- Directories trunk Identity Themes Models Alternative - Directories trunk Identity Themes Models Default - Directories trunk Identity Themes Models + Directories trunk Identity Locales Identity Models + Directories trunk Identity Locales Identity Release + Directories trunk Identity Locales Identity Fonts Directories
- The <file>trunk/Identity/Themes/Models/Alternative</file> Directory - Directories trunk Identity Themes Models Alternative + The <file>trunk/Identity/Locales/Identity/Models</file> Directory + Directories trunk Identity Locales Identity Models Goals - - • - - ... - - Description - CentOS alternative theme models exist for people how want to use a different visual style on their installations of CentOS distribution. As the visual style is needed for a system already installed components like Anaconda are not required inside alternative themes. Inside alternative themes you find post-installation visual style only (i.e. Backgrounds, Display Managers, Grub, etc.). CentOS alternative themes are maintained by CentOS Community. Usage - - • - - ... - - - - - - See also - - - -
- - - Directories trunk Identity Themes Models Default - Directories trunk Identity Themes Models Default Concept - Directories trunk Identity Themes Models Alternative - Directories -
- The <file>trunk/Identity/Themes/Models/Default</file> Directory - Directories trunk Identity Themes Models Default - - Goals - Default Design Models for CentOS Themes provide design models for the following components: - - - Distribution - - Design models for CentOS Distribution (e.g., Anaconda, Firstboot, Gdm, Grub, Gsplash, Kdm, Ksplash, Rhgb and Syslinux, etc.). See Directories trunk Identity Themes Models Default Distro, for more information. - - - - Concept - - Design models to illustrate Artistic Motifs Concepts. See Directories trunk Identity Themes Models Default Concept, for more information. - - - - Promotion - - Design models for CentOS Promotion stuff (e.g., installation media, posters, etc.). See Directories trunk Identity Themes Models Default Promo, for more information. - - -
- - - - Description - This directory implements the concept of Default Design Models for CentOS Themes. Default Design Models for CentOS Themes provide the common structural information (e.g., image dimensions, translation markers, trademark position, etc.) the centos-art script uses to produce images when no other design model is specified. - Deisgn models in this directory do use the CentOS Release Brand. The CentOS Release Brand is a combination of both The CentOS Type and The CentOS Release Schema used to illustrate the major release of CentOS Distribution the image produced belongs to. — Removed(xref:Directories trunk Identity Models Tpl Brands) —, for more information. - - - - Usage - The CentOS Project maintains near to four different major releases of CentOS Distribution. Each major release of CentOS Distribution has internal differences that make them unique and, at the same time, each CentOS Distribution individually is tagged into the one unique visual manifestation (i.e., Distribution). So, how could we implement the monolithic visual structure in one visual manifestation that has internal difference? - To answer this question we broke the question in two parts and later combined the resultant answers to build a possible solution. - - - How to remark the internal differences visually? - - Merge both The CentOS Project Release Schema into The CentOS Project Trademark to build The CentOS Project Release Trademark. The CentOS Project Release Trademark remarks two things: first, it remarks the image is from The CentOS Project and second, it remarks which major release of CentOS Distribution does the image belongs to. — Removed(xref:Directories trunk Identity Models Tpl Brands) —, for more information on how to develop and improve The CentOS Project Brand. - - - - How to remark the visual resemblance? - - Use a common artistic motifs as background for all CentOS Distribution images. See Directories trunk Identity Themes Motifs, for more information. - - - - So, combining answers above, we could conclude that: - - In order to implement the CentOS Monolithic Visual Structure on CentOS Distribution visual manifestations, a CentOS Release Trademark and a background information based on one unique artistic motif should be used in all remarkable images The CentOS Distribution visual manifestation is made of. - - -
- - Important Remarking the CentOS Release Schema inside each major release of CentOS Distribution —or similar visual manifestations— takes high attention inside The CentOS Project corporate visual identity. It should be very clear for everyone which major release of CentOS Distribution is being used. - - - - - See also - - • - - Directories trunk Identity Themes - - - Directories trunk Identity Themes Models - - - Directories trunk Identity Themes Motifs - - - -
- - - Directories trunk Identity Themes Models Default Concept - Directories trunk Identity Themes Models Default Distro - Directories trunk Identity Themes Models Default - Directories -
- The <file>trunk/Identity/Themes/Models/Default/Concept</file> Directory - Directories trunk Identity Themes Models Default Concept - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - @@ -1341,116 +1288,42 @@ centos-art render trunk/Identity/Path/To/Dir
- Directories trunk Identity Themes Models Default Distro - Directories trunk Identity Themes Models Default Distro Anaconda - Directories trunk Identity Themes Models Default Concept + Directories trunk Identity Locales Identity Release + Directories trunk Identity Locales Identity Themes + Directories trunk Identity Locales Identity Models Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro</file> Directory - Directories trunk Identity Themes Models Default Distro + The <file>trunk/Identity/Locales/Identity/Release</file> Directory + Directories trunk Identity Locales Identity Release Goals - This directory provides design models to produce image files for the following CentOS Distribution components: - - - Syslinux - - Contains design models for syslinux, the program used to boot the CentOS Distribution installation media. See Directories trunk Identity Themes Models Default Distro Syslinux, for more information. - - - - Anaconda - - Contains design models for Anaconda, the program used to install CentOS Distribution. See Directories trunk Identity Themes Models Default Distro Anaconda, for more information. - - - - Firstboot - - Contains design models for the first boot program used to configure the maching onece installed. See Directories trunk Identity Themes Models Default Distro Firstboot, for more information. - - - - Rhgb - - Contains design models for CentOS Graphical Boot, the program used to show the boot process from Grub to Display Manager. See Directories trunk Identity Themes Models Default Distro Rhgb, for more information. - - - - Gdm - - Contains design models for GNOME Display Manager, the program used to log into the manchine once installed and configured. See Directories trunk Identity Themes Models Default Distro Gdm, for more information. - - - - Kdm - - Contains design models for KDE Display Manager, the program used to log into the manchine once installed and configured. See Directories trunk Identity Themes Models Default Distro Kdm, for more information. - - - - Grub - - Contains design models for GRUB (Grand Unified Boot Loader), the program used to boot the machine into an operating system. See Directories trunk Identity Themes Models Default Distro Kdm, for more information. - - - - Gsplash - - Contains design models for GNOME splash, the program used to show the progress information while user's graphical session is loading. See Directories trunk Identity Themes Models Default Distro Gsplash, for more information. - - - - Ksplash - - Contains design models for KDE splash, the program used to show the progress information while user's graphical session is loading. See Directories trunk Identity Themes Models Default Distro Ksplash, for more information. - - -
Description - 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. Usage - 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. - 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. - The procedure to follow is creatig a directory for each component using its very same name (e.g., the directory Anaconda 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 centos-art script. - 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. - 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. See also - - Directories trunk Identity Themes Models Default - Directories trunk Identity Themes Models Default - -
- Directories trunk Identity Themes Models Default Distro Anaconda - Directories trunk Identity Themes Models Default Distro Firstboot - Directories trunk Identity Themes Models Default Distro + Directories trunk Identity Locales Identity Themes + Directories trunk Identity Locales Identity Themes Backgrounds + Directories trunk Identity Locales Identity Release Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Anaconda</file> Directory - Directories trunk Identity Themes Models Default Distro Anaconda + The <file>trunk/Identity/Locales/Identity/Themes</file> Directory + Directories trunk Identity Locales Identity Themes Goals - - • - - ... - - @@ -1469,13 +1342,13 @@ centos-art render trunk/Identity/Path/To/Dir
- Directories trunk Identity Themes Models Default Distro Firstboot - Directories trunk Identity Themes Models Default Distro Gdm - Directories trunk Identity Themes Models Default Distro Anaconda + Directories trunk Identity Locales Identity Themes Backgrounds + Directories trunk Identity Locales Identity Themes Distro Anaconda Progress + Directories trunk Identity Locales Identity Themes Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Firstboot</file> Directory - Directories trunk Identity Themes Models Default Distro Firstboot + The <file>trunk/Identity/Locales/Identity/Themes/Backgrounds</file> Directory + Directories trunk Identity Locales Identity Themes Backgrounds Goals @@ -1514,103 +1387,107 @@ centos-art render trunk/Identity/Path/To/Dir
- Directories trunk Identity Themes Models Default Distro Gdm - Directories trunk Identity Themes Models Default Distro Grub - Directories trunk Identity Themes Models Default Distro Firstboot + Directories trunk Identity Locales Identity Themes Distro Anaconda Progress + Directories trunk Identity Locales Identity Widgets + Directories trunk Identity Locales Identity Themes Backgrounds Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Gdm</file> Directory - Directories trunk Identity Themes Models Default Distro Gdm + The <file>trunk/Identity/Locales/Identity/Themes/Distro/Anaconda/Progress</file> Directory + Directories trunk Identity Locales Identity Themes Distro Anaconda Progress Goals • - ... - - - - - - Description - - • - - ... + Organize Anaconda progress translation templates. - - - - - Usage - - • - ... - - - - - - See also - - - -
- - - Directories trunk Identity Themes Models Default Distro Grub - Directories trunk Identity Themes Models Default Distro Gsplash - Directories trunk Identity Themes Models Default Distro Gdm - Directories -
- The <file>trunk/Identity/Themes/Models/Default/Distro/Grub</file> Directory - Directories trunk Identity Themes Models Default Distro Grub - - Goals - - • - - ... + Organize Anaconda progress translation files in several languages and major releases of CentOS distribution. Description + Use the following command to produce translation files based: + trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +`-- Tpl + |-- en + | |-- 01-welcome.sed + | |-- 02-donate.sed + | `-- 03-yum.sed + `-- es + |-- 01-welcome.sed + |-- 02-donate.sed + `-- 03-yum.sed + In order to produce the slide images in PNG format we need to have the translation files first. So we use the following commands to create translation files for CentOS 3, 4, and 5 major releases: + centos-art render --translation --filter='3,4,5' + The above commands will produce the following translation structure: + trunk/Translations/Identity/Themes/Distro/Anaconda/Progress +|-- 3 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +|-- 4 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +|-- 5 +| |-- en +| | |-- 01-welcome.sed +| | |-- 02-donate.sed +| | `-- 03-yum.sed +| `-- es +| |-- 01-welcome.sed +| |-- 02-donate.sed +| `-- 03-yum.sed +`-- Tpl + |-- en + | |-- 01-welcome.sed + | |-- 02-donate.sed + | `-- 03-yum.sed + `-- es + |-- 01-welcome.sed + |-- 02-donate.sed + `-- 03-yum.sed + At this point we have all the translation files we need to produce Anaconda progress welcome, donate and yum slides images; in English and Spanish languages; for CentOS 3, CentOS 4, and CentOS 5. That is, a sum of 18 images around. + Now, with translation files in place, let's move to trunk/Identity structure and render them. • - ... + See Directories trunk Identity Themes Motifs Modern Distro Anaconda Progress. Usage - - • - - ... - - + Translation rendering is described in trunk/Translations documentation entry (— Removed(pxref:trunk Translations) —). See also - -
- Directories trunk Identity Themes Models Default Distro Gsplash - Directories trunk Identity Themes Models Default Distro Kdm - Directories trunk Identity Themes Models Default Distro Grub + Directories trunk Identity Locales Identity Widgets + Directories trunk Identity Themes + Directories trunk Identity Locales Identity Themes Distro Anaconda Progress Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Gsplash</file> Directory - Directories trunk Identity Themes Models Default Distro Gsplash + The <file>trunk/Identity/Locales/Identity/Widgets</file> Directory + Directories trunk Identity Locales Identity Widgets Goals @@ -1644,91 +1521,89 @@ centos-art render trunk/Identity/Path/To/Dir See also +
- Directories trunk Identity Themes Models Default Distro Kdm - Directories trunk Identity Themes Models Default Distro Ksplash - Directories trunk Identity Themes Models Default Distro Gsplash + Directories trunk Identity Themes + Directories trunk Identity Themes Models + Directories trunk Identity Locales Identity Widgets Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Kdm</file> Directory - Directories trunk Identity Themes Models Default Distro Kdm + The <file>trunk/Identity/Themes</file> Directory + Directories trunk Identity Themes Goals - - • - - ... - - + The trunk/Identity/Themes/ directory exists to organize production of CentOS themes. Description - - • - - ... - - Usage - - • - - ... - - + In this location themes are organized in “Models” —to store common information— and “Motifs”—to store unique information. At rendering time, both motifs and models are combined to produce the final CentOS themes. CentOS themes can be tagged as “Default” or “Alternative”. CentOS themes are maintained by CentOS community. + + + Directories trunk Identity Themes Models + Directories trunk Identity Themes Models + + + + Directories trunk Identity Themes Motifs + Directories trunk Identity Themes Motifs + + + See also + + Directories trunk Identity + Directories trunk Identity + + + + Directories trunk + Directories trunk + +
- Directories trunk Identity Themes Models Default Distro Ksplash - Directories trunk Identity Themes Models Default Distro Rhgb - Directories trunk Identity Themes Models Default Distro Kdm + Directories trunk Identity Themes Models + Directories trunk Identity Themes Models Alternative + Directories trunk Identity Themes Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Ksplash</file> Directory - Directories trunk Identity Themes Models Default Distro Ksplash + The <file>trunk/Identity/Themes/Models</file> Directory + Directories trunk Identity Themes Models Goals • - ... + Organize theme models. Description - - • - - ... - - + Theme models let you modeling characteristics (e.g., dimensions, translation markers, position of each element on the display area, etc.) common to all themes. Theme models let you reduce the time needed when propagating artistic motifs to different visual manifestations. + Theme models serves as a central pool of design templates for themes to use. This way you can produce themes with different artistic motifs but same characteristics. Usage - - • - - ... - - + Inside the framework location above, you find theme models organized by name. You can add your own theme models to the structure by adding a directory to the list. By default you have the `See Directories trunk Identity Themes Models DefaultDefault,' and `See Directories trunk Identity Themes Models AlternativeAlternative,' ready-to-use theme models. @@ -1739,13 +1614,13 @@ centos-art render trunk/Identity/Path/To/Dir
- Directories trunk Identity Themes Models Default Distro Rhgb - Directories trunk Identity Themes Models Default Distro Syslinux - Directories trunk Identity Themes Models Default Distro Ksplash + Directories trunk Identity Themes Models Alternative + Directories trunk Identity Themes Models Default + Directories trunk Identity Themes Models Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Rhgb</file> Directory - Directories trunk Identity Themes Models Default Distro Rhgb + The <file>trunk/Identity/Themes/Models/Alternative</file> Directory + Directories trunk Identity Themes Models Alternative Goals @@ -1758,12 +1633,7 @@ centos-art render trunk/Identity/Path/To/Dir Description - - • - - ... - - + CentOS alternative theme models exist for people how want to use a different visual style on their installations of CentOS distribution. As the visual style is needed for a system already installed components like Anaconda are not required inside alternative themes. Inside alternative themes you find post-installation visual style only (i.e. Backgrounds, Display Managers, Grub, etc.). CentOS alternative themes are maintained by CentOS Community. @@ -1784,104 +1654,98 @@ centos-art render trunk/Identity/Path/To/Dir
- Directories trunk Identity Themes Models Default Distro Syslinux - Directories trunk Identity Themes Models Default Promo - Directories trunk Identity Themes Models Default Distro Rhgb + Directories trunk Identity Themes Models Default + Directories trunk Identity Themes Models Default Concept + Directories trunk Identity Themes Models Alternative Directories
- The <file>trunk/Identity/Themes/Models/Default/Distro/Syslinux</file> Directory - Directories trunk Identity Themes Models Default Distro Syslinux + The <file>trunk/Identity/Themes/Models/Default</file> Directory + Directories trunk Identity Themes Models Default Goals - - • - - ... - - + Default Design Models for CentOS Themes provide design models for the following components: + + + Distribution + + Design models for CentOS Distribution (e.g., Anaconda, Firstboot, Gdm, Grub, Gsplash, Kdm, Ksplash, Rhgb and Syslinux, etc.). See Directories trunk Identity Themes Models Default Distro, for more information. + + + + Concept + + Design models to illustrate Artistic Motifs Concepts. See Directories trunk Identity Themes Models Default Concept, for more information. + + + + Promotion + + Design models for CentOS Promotion stuff (e.g., installation media, posters, etc.). See Directories trunk Identity Themes Models Default Promo, for more information. + + +
Description - - • - - ... - - + This directory implements the concept of Default Design Models for CentOS Themes. Default Design Models for CentOS Themes provide the common structural information (e.g., image dimensions, translation markers, trademark position, etc.) the centos-art script uses to produce images when no other design model is specified. + Deisgn models in this directory do use the CentOS Release Brand. The CentOS Release Brand is a combination of both The CentOS Type and The CentOS Release Schema used to illustrate the major release of CentOS Distribution the image produced belongs to. — Removed(xref:Directories trunk Identity Models Tpl Brands) —, for more information. Usage - - • - - ... - - - - - - See also - - - -
- - - Directories trunk Identity Themes Models Default Promo - Directories trunk Identity Themes Models Default Web - Directories trunk Identity Themes Models Default Distro Syslinux - Directories -
- The <file>trunk/Identity/Themes/Models/Default/Promo</file> Directory - Directories trunk Identity Themes Models Default Promo - - Goals - - • - - ... - - + The CentOS Project maintains near to four different major releases of CentOS Distribution. Each major release of CentOS Distribution has internal differences that make them unique and, at the same time, each CentOS Distribution individually is tagged into the one unique visual manifestation (i.e., Distribution). So, how could we implement the monolithic visual structure in one visual manifestation that has internal difference? + To answer this question we broke the question in two parts and later combined the resultant answers to build a possible solution. + + + How to remark the internal differences visually? + + Merge both The CentOS Project Release Schema into The CentOS Project Trademark to build The CentOS Project Release Trademark. The CentOS Project Release Trademark remarks two things: first, it remarks the image is from The CentOS Project and second, it remarks which major release of CentOS Distribution does the image belongs to. — Removed(xref:Directories trunk Identity Models Tpl Brands) —, for more information on how to develop and improve The CentOS Project Brand. + + + + How to remark the visual resemblance? + + Use a common artistic motifs as background for all CentOS Distribution images. See Directories trunk Identity Themes Motifs, for more information. + + + + So, combining answers above, we could conclude that: + + In order to implement the CentOS Monolithic Visual Structure on CentOS Distribution visual manifestations, a CentOS Release Trademark and a background information based on one unique artistic motif should be used in all remarkable images The CentOS Distribution visual manifestation is made of. + + +
+ + Important Remarking the CentOS Release Schema inside each major release of CentOS Distribution —or similar visual manifestations— takes high attention inside The CentOS Project corporate visual identity. It should be very clear for everyone which major release of CentOS Distribution is being used. + - Description - It applies to all tangible and non tangible items CentOS uses to promote its existence. Clothes, posters, installation media, stationery, release countdown images, banners, stickers, are all examples of promotion designs. + See also • - ... + Directories trunk Identity Themes - - - - - Usage - - • - ... + Directories trunk Identity Themes Models + + + Directories trunk Identity Themes Motifs - - - See also - - -
- Directories trunk Identity Themes Models Default Web - Directories trunk Identity Themes Motifs - Directories trunk Identity Themes Models Default Promo + Directories trunk Identity Themes Models Default Concept + Directories trunk Identity Themes Models Default Distro + Directories trunk Identity Themes Models Default Directories
- The <file>trunk/Identity/Themes/Models/Default/Web</file> Directory - Directories trunk Identity Themes Models Default Web + The <file>trunk/Identity/Themes/Models/Default/Concept</file> Directory + Directories trunk Identity Themes Models Default Concept Goals @@ -1894,7 +1758,6 @@ centos-art render trunk/Identity/Path/To/Dir Description - It applies to all web applications CentOS uses to handle its needs (Ex. Portals, Wikis, Forums, Blogs, Bug Tracker). Anything involving HTML standards should be consider here. • @@ -1921,112 +1784,94 @@ centos-art render trunk/Identity/Path/To/Dir
- Directories trunk Identity Themes Motifs - Directories trunk Identity Themes Motifs Flame - Directories trunk Identity Themes Models Default Web + Directories trunk Identity Themes Models Default Distro + Directories trunk Identity Themes Models Default Distro Anaconda + Directories trunk Identity Themes Models Default Concept Directories
- The <file>trunk/Identity/Themes/Motifs</file> Directory - Directories trunk Identity Themes Motifs + The <file>trunk/Identity/Themes/Models/Default/Distro</file> Directory + Directories trunk Identity Themes Models Default Distro Goals - The trunk/Identity/Themes/Motifs directory exists to: - - • - - Organize CentOS themes' artistic motifs. - - - - - - Description - The artistic motif of theme is a graphic design component that provides the visual style of themes, it is used as pattern to connect all visual manifestations inside one unique theme. - Artistic motifs are based on conceptual ideas. Conceptual ideas bring the motivation, they are fuel for the engines of human imagination. Good conceptual ideas may produce good motivation to produce almost anything, and art works don't escape from it. + This directory provides design models to produce image files for the following CentOS Distribution components: - TreeFlower + Syslinux - CentOS like trees, has roots, trunk, branches, leaves and flowers. Day by day they work together in freedom, ruled by the laws of nature and open standards, to show the beauty of its existence. + Contains design models for syslinux, the program used to boot the CentOS Distribution installation media. See Directories trunk Identity Themes Models Default Distro Syslinux, for more information. - Modern + Anaconda - Modern, squares and circles flowing up. + Contains design models for Anaconda, the program used to install CentOS Distribution. See Directories trunk Identity Themes Models Default Distro Anaconda, for more information. + + + + Firstboot + + Contains design models for the first boot program used to configure the maching onece installed. See Directories trunk Identity Themes Models Default Distro Firstboot, for more information. + + + + Rhgb + + Contains design models for CentOS Graphical Boot, the program used to show the boot process from Grub to Display Manager. See Directories trunk Identity Themes Models Default Distro Rhgb, for more information. + + + + Gdm + + Contains design models for GNOME Display Manager, the program used to log into the manchine once installed and configured. See Directories trunk Identity Themes Models Default Distro Gdm, for more information. + + + + Kdm + + Contains design models for KDE Display Manager, the program used to log into the manchine once installed and configured. See Directories trunk Identity Themes Models Default Distro Kdm, for more information. + + + + Grub + + Contains design models for GRUB (Grand Unified Boot Loader), the program used to boot the machine into an operating system. See Directories trunk Identity Themes Models Default Distro Kdm, for more information. + + + + Gsplash + + Contains design models for GNOME splash, the program used to show the progress information while user's graphical session is loading. See Directories trunk Identity Themes Models Default Distro Gsplash, for more information. + + + + Ksplash + + Contains design models for KDE splash, the program used to show the progress information while user's graphical session is loading. See Directories trunk Identity Themes Models Default Distro Ksplash, for more information.
- If you have new conceptual ideas for CentOS, then you can say that you want to create a new artistic motif for CentOS. To create a new artistic motif you need to create a directory under Identity/Themes/Motifs/ using a name coherent with your conceptual idea. That name will be the name of your artistic motif. If possible, when creating new conceptual ideas for CentOS, think about what CentOS means for you, what does it makes you feel, take your time, think deep, and share; you can improve the idea as time goes on. - Once you have defined a name for your theme, you need to create the motif structure of your theme. The motif structure is the basic direcotry structure you'll use to work your ideas. Here is where you organize your graphic design projects. - To add a new motif structure to CentOS Artwork Repository, you need to use the centos-art command line in the Identity/Themes/Motifs/ directory as described below: - centos-art add --motif=ThemeName - The previous command will create the basic structure of themes for you. The basic structure produced by centos-art command is illustrated in the following figure: - trunk/Identity/Themes/Motifs/$ThemeName/ -|-- Backgrounds -| |-- Img -| `-- Tpl -|-- Info -| |-- Img -| `-- Tpl -|-- Palettes -`-- Screenshots + + + + Description + 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. Usage - When designing artistic motifs for CentOS, consider the following recommendations: - - • - - Give a unique (case-sensitive) name to your Motif. This name is used as value wherever theme variable ($THEME) or translation marker (=THEME=) is. Optionally, you can add a description about inspiration and concepts behind your work. - - - Use the location trunk/Identity/Themes/Motifs/$THEME/ to store your work. If it doesn't exist create it. Note that this require you to have previous commit access in CentOS Artwork Repository. - - - The CentOS Project is using the blue color (#204c8d) as base color for its corporate visual identity. Use such base corporate color information as much as possible in your artistic motif designs. - - - Try to make your design fit one of the theme models. - - - Feel free to make your art enterprise-level and beautiful. - - - Add the following information on your artwork (both in a visible design area and document metadata): - - • - - The name (or logo) of your artistic motif. - - - The copyright sentence: Copyright (C) YEAR YOURNAME - - - The license under which the work is released. All CentOS Art works are released under http://creativecommons.org/licenses/by-sa/3.0/Creative Common Share-Alike License 3.0 (http://creativecommons.org/licenses/by-sa/3.0/). - - - - + 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. + 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. + The procedure to follow is creatig a directory for each component using its very same name (e.g., the directory Anaconda 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 centos-art script. + 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. + 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. See also - Directories trunk Identity Themes - Directories trunk Identity Themes - - - - Directories trunk Identity - Directories trunk Identity - - - - Directories trunk - Directories trunk + Directories trunk Identity Themes Models Default + Directories trunk Identity Themes Models Default @@ -2034,115 +1879,64 @@ centos-art render trunk/Identity/Path/To/Dir
- Directories trunk Identity Themes Motifs Flame - Directories trunk Identity Themes Motifs Modern - Directories trunk Identity Themes Motifs + Directories trunk Identity Themes Models Default Distro Anaconda + Directories trunk Identity Themes Models Default Distro Firstboot + Directories trunk Identity Themes Models Default Distro Directories
- The <file>trunk/Identity/Themes/Motifs/Flame</file> Directory - Directories trunk Identity Themes Motifs Flame + The <file>trunk/Identity/Themes/Models/Default/Distro/Anaconda</file> Directory + Directories trunk Identity Themes Models Default Distro Anaconda Goals - This section describes the steps we followed to construct the Flame artistic motif. This section may be useful for anyone interested in reproducing the Flame artistic motif, or in creating new artistic motifs for The CentOS Project corporate visual identity (see Directories trunk Identity). + + • + + ... + + Description - The Flame artistic motif was built using the flame filter of Gimp 2.2 in CentOS 5.5. - 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 centos-art.sh script (see Directories trunk Scripts) inside the CentOS Artwork Repository. - 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. - 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. - 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. - 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 centos-art.sh script. - With the combination of both CentOS Artwork Repository and centos-art.sh 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. - From a monolithic corporate visual identity point of view, notice that we are producing a new visual style for the same theme (i.e., Flame). 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. - 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). - 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. - Due to the “randomly generated” nature of Flame filter, we find that Flame pattern is not always the same when we use Flame filter interface. - 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. - - Important 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. - - In order for us to reproduce the same flame pattern always, Flame filter interface provides the Save and Open options. The Save 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 Open option brings up a file selector that allows you to open a previously saved Flame settings file. - The Flame settings we used in our example are saved in the file: - - Construction - - Step 1: Set image size - Create an empty image and fill the Background layer with black (000000) 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). - - - - Step 2: Add base color and pattern information - Create a new layer named Base, place it over Background layer and fill it with the base color (7800ff) you want to have your background image set in. Add a mask to Base 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. - Duplicate Base layer and name it Paper. Place Paper layer over Base layer. Remove content of Paper layer and fill it with Paper (100x100) pattern. Once you've done with black radial degradation, reduce the Paper layer opacity to 20%. - 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. - Duplicate Paper layer and rename it Stripes. Remove paper pattern from Stripes layer. Fill Stripes layer with Stripes (48x48) pattern and reduce the Stripes layer opacity to 15%. - - - - Step 3: Add flame motif - Create a new layer named Flame. Set the foreground (003cff) and background (0084ff) colors to the gradient you want to build the flame motif. - To build flame motif, use the flame filter (Filters > Render > Nature > Flame...) on Flame layer. We used a layer mask, with a radial gradient on it to control the boundaries of flame motif on Flame layer. - Duplicate Flame layer and rename it `Flame Blur'. Place `Flame Blur' below Flame layer. Apply Gussian blur filter (Filters > Blur > Gussian Blur...) until reaching the desiered effect. - The opacity value, in Flame 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 Flame layer opacity set at 100% but Flame Blur 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. - - - - Step 4: Add foreground color - Create a new layer named Color, place it on top of all visible layers and fill it with plain color (4c005a). Reduce Color layer opacity to 20%. You can use the Color layer to control the right side color information you want to produce the image for. - Duplicate Flame layer and create a new layer named Color#1. Place Color#1 layer on top of layer named Color. Remove the mask information from Color#1 layer and recreate a new one using an inverted alpha channel as reference. Remove Color#1 layer content and fill it back with plain black (000000) color. Reduce Color#1 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. - 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. - 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. - - + Usage + See also - - Directories trunk Identity Themes Motifs - Directories trunk Identity Themes Motifs - - - - Directories trunk Identity Themes - Directories trunk Identity Themes - - - - Directories trunk Identity - Directories trunk Identity - - - - Directories trunk - Directories trunk - -
- Directories trunk Identity Themes Motifs Modern - Directories trunk Identity Themes Motifs Modern Backgrounds - Directories trunk Identity Themes Motifs Flame + Directories trunk Identity Themes Models Default Distro Firstboot + Directories trunk Identity Themes Models Default Distro Gdm + Directories trunk Identity Themes Models Default Distro Anaconda Directories
- The <file>trunk/Identity/Themes/Motifs/Modern</file> Directory - Directories trunk Identity Themes Motifs Modern + The <file>trunk/Identity/Themes/Models/Default/Distro/Firstboot</file> Directory + Directories trunk Identity Themes Models Default Distro Firstboot - Presentation + Goals + + • + + ... + + - Construction + Description + + • + + ... + + @@ -2163,92 +1957,58 @@ trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def
- Directories trunk Identity Themes Motifs Modern Backgrounds - Directories trunk Identity Themes Motifs Modern Backgrounds Img - Directories trunk Identity Themes Motifs Modern + Directories trunk Identity Themes Models Default Distro Gdm + Directories trunk Identity Themes Models Default Distro Grub + Directories trunk Identity Themes Models Default Distro Firstboot Directories
- The <file>trunk/Identity/Themes/Motifs/Modern/Backgrounds</file> Directory - Directories trunk Identity Themes Motifs Modern Backgrounds + The <file>trunk/Identity/Themes/Models/Default/Distro/Gdm</file> Directory + Directories trunk Identity Themes Models Default Distro Gdm Goals • - Organize background images for Modern theme. + ... Description - Inside Motifs directory, the Backgrounds/ directory is used to create vectorial designs using Inkscape and background images using Gimp. Later, you can export background images as .png and load them in your vectorial design project using the import feautre of Inkscape. - You may need to repeat this technic for different screen resoluions. In that case you need to create one file for each screen resolution and do the appropriate linking inside .svg to .png files. For example if you need to produce background images in 800x600 you need to create the following file: - xcf/800x600.xcf - to produce the background image: - img/800x600-bg.png - which is loaded in: - svg/800x600.svg - to produce the final background image: - img/800x600.png - The img/800x600.png background image is produced automatically by means of rendering scripts. - In other cases (e.g. Anaconda), it is possible that you need to make some variations to one background image that don't want to appear on regular background images of the same resolution. In this case you need to create a new and specific background image for that art component. For example, if you need to produce the background image used by Anconda (800x600) art works you create the file: - xcf/800x600-anaconda.xcf - to produce the background image: - img/800x600-anaconda-bg.png - which is loaded in: - svg/800x600-anaconda.svg - to produce the file: - img/800x600-anaconda.png - The 800x600-anaconda.png file is used by all Anaconda art works sharing a common 800x600 screen resolution (e.g., Header, Progress, Splash, Firstboot, etc.). The Anaconda Prompt is indexed to 16 colors and 640x480 pixels so you need to create a 640x480 background image for it, and take the color limitation into account when designing it. - Background images without artistic motif are generally used as based to build the Background images that do contain the theme artistic motif. - Background images are linked (using the import feature of Inkscape) inside almost all theme art works. This structure let you make centralized changes on the visual identity and propagate them quickly to other areas. - In this structure you design background images for different screen resolutions based on the theme artistic motif. - You may create different artistic motifs propositions based on the same conceptual idea. The conceptual idea is what defines a theme. Artistic motifs are interpretations of that idea. - Inside this directory artistic motifs are organized by name (e.g., TreeFlower, Modern, etc.). - Each artistic motif directory represents just one unique artistic motif. - The artistic motif is graphic design used as common pattern to connect all visual manifestations inside one unique theme. The artistic motif is based on a conceptual idea. Artistic motifs provide visual style to themes. - Designing artistic motifs is for anyone interested in creating beautiful themes for CentOS. When building a theme for CentOS, the first design you need to define is the artistic motif. - Inside CentOS Artwork Repository, theme visual styles (Motifs) and theme visual structures (Models) are two different working lines. When you design an artistic motif for CentOS you concentrate on its visual style, and eventualy, use the centos-art command line interface to render the visual style, you are currently producing, against an already-made theme model in order to produce the final result. Final images are stored under Motifs/ directory using the model name, and the model directory structure as reference. - The artistic motif base structure is used by centos-art to produce images automatically. This section describes each directory of CentOS artistic motif base structure. + + • + + ... + + Usage - The Backgrounds/ directory is probably the core component, inside Motifs/ directory structure. Inside Backgrounds/ directory you produce background images used by almost all theme models (e.g., Distribution, Websites, Promotion, etc.). The Backgrounds/ directory can contain subdirectories to help you organize the design process. + + • + + ... + + See also - - Directories trunk Identity Themes Motifs Modern Backgrounds Img - Directories trunk Identity Themes Motifs Modern Backgrounds Img - - - - Directories trunk Identity Themes Motifs Modern Backgrounds Tpl - Directories trunk Identity Themes Motifs Modern Backgrounds Tpl - - - - Directories trunk Identity Themes Motifs Modern Backgrounds Xcf - Directories trunk Identity Themes Motifs Modern Backgrounds Xcf - - -
- Directories trunk Identity Themes Motifs Modern Backgrounds Img - Directories trunk Identity Themes Motifs Modern Backgrounds Tpl - Directories trunk Identity Themes Motifs Modern Backgrounds + Directories trunk Identity Themes Models Default Distro Grub + Directories trunk Identity Themes Models Default Distro Gsplash + Directories trunk Identity Themes Models Default Distro Gdm Directories
- The <file>trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img</file> Directory - Directories trunk Identity Themes Motifs Modern Backgrounds Img + The <file>trunk/Identity/Themes/Models/Default/Distro/Grub</file> Directory + Directories trunk Identity Themes Models Default Distro Grub Goals @@ -2261,11 +2021,22 @@ trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def Description + + • + + ... + + Usage - In this directory is where you store all background images (e.g., .png, .jpg, .xpm, etc.). This directory is required by centos-art command line interface. + + • + + ... + + @@ -2276,13 +2047,13 @@ trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def
- Directories trunk Identity Themes Motifs Modern Backgrounds Tpl - Directories trunk Identity Themes Motifs Modern Backgrounds Xcf - Directories trunk Identity Themes Motifs Modern Backgrounds Img + Directories trunk Identity Themes Models Default Distro Gsplash + Directories trunk Identity Themes Models Default Distro Kdm + Directories trunk Identity Themes Models Default Distro Grub Directories
- The <file>trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl</file> Directory - Directories trunk Identity Themes Motifs Modern Backgrounds Tpl + The <file>trunk/Identity/Themes/Models/Default/Distro/Gsplash</file> Directory + Directories trunk Identity Themes Models Default Distro Gsplash Goals @@ -2295,11 +2066,22 @@ trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def Description + + • + + ... + + Usage - In this directory is where you store all the scalable vector graphics (e.g., .svg) files. This directory is required by centos-art command line interface. + + • + + ... + + @@ -2310,13 +2092,13 @@ trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def
- Directories trunk Identity Themes Motifs Modern Backgrounds Xcf - Directories trunk Identity Themes Motifs Modern Distro Anaconda Progress - Directories trunk Identity Themes Motifs Modern Backgrounds Tpl + Directories trunk Identity Themes Models Default Distro Kdm + Directories trunk Identity Themes Models Default Distro Ksplash + Directories trunk Identity Themes Models Default Distro Gsplash Directories
- The <file>trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf</file> Directory - Directories trunk Identity Themes Motifs Modern Backgrounds Xcf + The <file>trunk/Identity/Themes/Models/Default/Distro/Kdm</file> Directory + Directories trunk Identity Themes Models Default Distro Kdm Goals @@ -2339,7 +2121,12 @@ trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def Usage - In this directory is where you store the project files (e.g, .xcf) of Gimp. This directory is not required by centos-art command line interface. If you can create a beautiful background images using scalable vector graphics only, then there is no need to use the Xcf/ directory to store background projects. Of course, you can merge both Gimp and Inkscape power to produce images based on them. In this last case you need the Xcf/ directory. + + • + + ... + + @@ -2350,13 +2137,13 @@ trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def
- Directories trunk Identity Themes Motifs Modern Distro Anaconda Progress - Directories trunk Identity Themes Motifs Modern Palettes - Directories trunk Identity Themes Motifs Modern Backgrounds Xcf + Directories trunk Identity Themes Models Default Distro Ksplash + Directories trunk Identity Themes Models Default Distro Rhgb + Directories trunk Identity Themes Models Default Distro Kdm Directories
- The <file>trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress</file> Directory - Directories trunk Identity Themes Motifs Modern Distro Anaconda Progress + The <file>trunk/Identity/Themes/Models/Default/Distro/Ksplash</file> Directory + Directories trunk Identity Themes Models Default Distro Ksplash Goals @@ -2369,42 +2156,22 @@ trunk/Identity/Themes/Motifs/Flame/Backgrounds/Xcf/800x600.xcf-flame.def Description + + • + + ... + + Usage - To render Anaconda progress slide images using the Modern artistic motif design, the Default theme model, and available translation files (— Removed(pxref:trunk Translations Identity Themes Distro Anaconda Progress) —); use the following commands: - cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ -centos-art render --identity - The above command will create the following structure: - trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress -|-- 3 -| |-- en -| | |-- 01-welcome.png -| | |-- 02-donate.png -| | `-- 03-yum.png -| `-- es -| |-- 01-welcome.png -| |-- 02-donate.png -| `-- 03-yum.png -|-- 4 -| |-- en -| | |-- 01-welcome.png -| | |-- 02-donate.png -| | `-- 03-yum.png -| `-- es -| |-- 01-welcome.png -| |-- 02-donate.png -| `-- 03-yum.png -`-- 5 - |-- en - | |-- 01-welcome.png - | |-- 02-donate.png - | `-- 03-yum.png - `-- es - |-- 01-welcome.png - |-- 02-donate.png - `-- 03-yum.png + + • + + ... + + @@ -2415,30 +2182,41 @@ centos-art render --identity
- Directories trunk Identity Themes Motifs Modern Palettes - Directories trunk Identity Themes Motifs TreeFlower - Directories trunk Identity Themes Motifs Modern Distro Anaconda Progress + Directories trunk Identity Themes Models Default Distro Rhgb + Directories trunk Identity Themes Models Default Distro Syslinux + Directories trunk Identity Themes Models Default Distro Ksplash Directories
- The <file>trunk/Identity/Themes/Motifs/Modern/Palettes</file> Directory - Directories trunk Identity Themes Motifs Modern Palettes + The <file>trunk/Identity/Themes/Models/Default/Distro/Rhgb</file> Directory + Directories trunk Identity Themes Models Default Distro Rhgb Goals • - Organize palette files for Modern theme. + ... Description + + • + + ... + + Usage - Here is where graphic designers define theme palettes for color-limited art works. Theme palettes contain the color information that rendering functions need, in order to produce images with color limitations. Theme palettes contain the unique color information required by theme. + + • + + ... + + @@ -2449,13 +2227,13 @@ centos-art render --identity
- Directories trunk Identity Themes Motifs TreeFlower - Directories trunk Identity Themes Motifs TreeFlower Backgrounds - Directories trunk Identity Themes Motifs Modern Palettes + Directories trunk Identity Themes Models Default Distro Syslinux + Directories trunk Identity Themes Models Default Promo + Directories trunk Identity Themes Models Default Distro Rhgb Directories
- The <file>trunk/Identity/Themes/Motifs/TreeFlower</file> Directory - Directories trunk Identity Themes Motifs TreeFlower + The <file>trunk/Identity/Themes/Models/Default/Distro/Syslinux</file> Directory + Directories trunk Identity Themes Models Default Distro Syslinux Goals @@ -2468,10 +2246,22 @@ centos-art render --identity Description + + • + + ... + + Usage + + • + + ... + + @@ -2482,227 +2272,184 @@ centos-art render --identity
- Directories trunk Identity Themes Motifs TreeFlower Backgrounds - Directories trunk Identity Webenv - Directories trunk Identity Themes Motifs TreeFlower + Directories trunk Identity Themes Models Default Promo + Directories trunk Identity Themes Models Default Web + Directories trunk Identity Themes Models Default Distro Syslinux Directories
- The <file>trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds</file> Directory - Directories trunk Identity Themes Motifs TreeFlower Backgrounds + The <file>trunk/Identity/Themes/Models/Default/Promo</file> Directory + Directories trunk Identity Themes Models Default Promo Goals - This section exists to orgnize backgrounds of TreeFlower artistic motif. + + • + + ... + + Description - - Desktop background - Once you have defined the vectorial artistic motif design, use the centos-art.sh script (as described in usage section below) to produce the png version of it. With the png version of your vectorial design do the following: - Open the png version with GIMP. - Save the png version as a project of GIMP inside trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Xcf directory, using the same name of your vectorial design but with the .xcf extension. - Now use GIMP to improve your design. Here you may add one layer for pattern, another for colors, and so on until you find yourself confortable with your artwork. For example, the following layer distribution (from bottom to top) was used to build revision 285 of file 1360x768.xcf using TreeFlower artistic motif at revision 241. - - - Layer 1: Background - - The first thing we did with GIMP was to create a layer named Background to store the artistic motif (File > Open as layer). This layer is the lowest layer in the image. Later, we started to create layers one upon another to change the artistic motif visual style. - - - - Layer 2: Shadow#1 - - This layer is above Background and contains a linear gradient from left (000000) to right (transparent) covering the whole image. This layer masks the artistic motif to avoid the effect of linear gradient. This layer is 100% of opacity. - - - - Layer 3: Shadow#2 - - This layer is above Shadow#1 and contains a linear gradient from left (000000) to right (transparent) covering just the 70% of the whole image aproximatly. This layer doesn't mask the artistic motif which make the left part of it fall into the dark of linear gradient. This layer is 100% of opacity. - - - - Layer 4: Pattern (Paper) - - This layer is above Shadow#2 an contains the paper pattern shipped with GIMP 2.2. This layer doesn't mask the artistic motif so the pattern is applied over the whole image. This layer is set to 15% of opacity. - - - - Layer 5: Pattern (Stripes) + It applies to all tangible and non tangible items CentOS uses to promote its existence. Clothes, posters, installation media, stationery, release countdown images, banners, stickers, are all examples of promotion designs. + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + + + + + Directories trunk Identity Themes Models Default Web + Directories trunk Identity Themes Motifs + Directories trunk Identity Themes Models Default Promo + Directories +
+ The <file>trunk/Identity/Themes/Models/Default/Web</file> Directory + Directories trunk Identity Themes Models Default Web + + Goals + + • + + ... + + + + + + Description + It applies to all web applications CentOS uses to handle its needs (Ex. Portals, Wikis, Forums, Blogs, Bug Tracker). Anything involving HTML standards should be consider here. + + • + + ... + + + + + + Usage + + • + + ... + + + + + + See also + + + +
+ + + Directories trunk Identity Themes Motifs + Directories trunk Identity Themes Motifs Flame + Directories trunk Identity Themes Models Default Web + Directories +
+ The <file>trunk/Identity/Themes/Motifs</file> Directory + Directories trunk Identity Themes Motifs + + Goals + The trunk/Identity/Themes/Motifs directory exists to: + + • + + Organize CentOS themes' artistic motifs. + + + + + + Description + The artistic motif of theme is a graphic design component that provides the visual style of themes, it is used as pattern to connect all visual manifestations inside one unique theme. + Artistic motifs are based on conceptual ideas. Conceptual ideas bring the motivation, they are fuel for the engines of human imagination. Good conceptual ideas may produce good motivation to produce almost anything, and art works don't escape from it. +
+ + TreeFlower + + CentOS like trees, has roots, trunk, branches, leaves and flowers. Day by day they work together in freedom, ruled by the laws of nature and open standards, to show the beauty of its existence. + + + + Modern + + Modern, squares and circles flowing up. + + +
+ If you have new conceptual ideas for CentOS, then you can say that you want to create a new artistic motif for CentOS. To create a new artistic motif you need to create a directory under Identity/Themes/Motifs/ using a name coherent with your conceptual idea. That name will be the name of your artistic motif. If possible, when creating new conceptual ideas for CentOS, think about what CentOS means for you, what does it makes you feel, take your time, think deep, and share; you can improve the idea as time goes on. + Once you have defined a name for your theme, you need to create the motif structure of your theme. The motif structure is the basic direcotry structure you'll use to work your ideas. Here is where you organize your graphic design projects. + To add a new motif structure to CentOS Artwork Repository, you need to use the centos-art command line in the Identity/Themes/Motifs/ directory as described below: + centos-art add --motif=ThemeName + The previous command will create the basic structure of themes for you. The basic structure produced by centos-art command is illustrated in the following figure: + trunk/Identity/Themes/Motifs/$ThemeName/ +|-- Backgrounds +| |-- Img +| `-- Tpl +|-- Info +| |-- Img +| `-- Tpl +|-- Palettes +`-- Screenshots + + + + Usage + When designing artistic motifs for CentOS, consider the following recommendations: + + • + + Give a unique (case-sensitive) name to your Motif. This name is used as value wherever theme variable ($THEME) or translation marker (=THEME=) is. Optionally, you can add a description about inspiration and concepts behind your work. + + + Use the location trunk/Identity/Themes/Motifs/$THEME/ to store your work. If it doesn't exist create it. Note that this require you to have previous commit access in CentOS Artwork Repository. + + + The CentOS Project is using the blue color (#204c8d) as base color for its corporate visual identity. Use such base corporate color information as much as possible in your artistic motif designs. + + + Try to make your design fit one of the theme models. + + + Feel free to make your art enterprise-level and beautiful. + + + Add the following information on your artwork (both in a visible design area and document metadata): + + • - This layer is above Pattern (Paper) and contains the stripes used over the artistic motif. This layer do masks the artistic motif so the stripes are only applied to it. This layer is set to 10% of opacity. + The name (or logo) of your artistic motif. - - - Layer 6: Shadow#3 - This layer is above Pattern (Stripes) and contains a linear gradient from right (6600ff) to left (transparent). This layer masks the artistic motif so the linear gradient doesn't affect it. This layer is set to 15% of opacity. + The copyright sentence: Copyright (C) YEAR YOURNAME - - - Layer 7: Shadow#4 - This layer is above Shadow#3 and contains a linear gradient from left (000000) to right (transparent). This layer do masks the artistic motif so the linear gradient doesn't affect it. This layer is set to 10% of opacity. + The license under which the work is released. All CentOS Art works are released under http://creativecommons.org/licenses/by-sa/3.0/Creative Common Share-Alike License 3.0 (http://creativecommons.org/licenses/by-sa/3.0/). - - - Layer 8: Color#1 - - This layer is above Shadow#4 and is filled with orange (ffae00) color over the whole image. This layer is set to 10% of opacity. - - - - Layer 9: Color#2 - - This layer is above Color#1 and is filled with blue (010a88) color over the whole image. This layer is set to 10% of opacity. - - - - - Note There is no definite combination. To get the appropriate visual design is a matter of constant testing and personal taste. - - Finally, use Save as copy ... option to export the final design. To export the final design use the same name of your vectorial design plus -final.png extension. - You can repeat these steps to create images for other screen resolutions. - - - - Anaconda Prompt (syslinux) background - When building syslinux backgrounds it is needed to take into account that the final image is reduced to 16 colors. In desktop background there is no color limitation but syslinux does have. The goal of this section is achieving a final syslinux background as close as possible to desktop backgrounds using 16 colors only. - Another point to consider is the forground and background definition used by syslinux. The syslinux documentation says that the color set in position 0 is the background and color set in position 7 is the forground. The final palette of color used by our background will match that specification. For great contrast we'll use black as background and white as forground. At this poing we have black (000000) and white (ffffff) colors in our syslinux palette, which left us with 14 colors to play with. - Let's begin with Xcf/640x300.xcf layer distribution from bottom to top: - - - Layer 1: Background - - This layer is the lowest layer in the image composition and contains the artistic motif image rendered for the same resolution (i.e., Img/Png/640x300.png). This layer is set to 100% of opacity. - - - - Layer 2: Pattern (Paper) - - This layer is placed above Background layer and contains the paper pattern shipped with GIMP 2.2. This layer doesn't mask the artistic motif. This layer is set to 30% of opacity. - - - - Layer 3: Pattern (Stripes) - - This layer is placed above Pattern (Paper) layer and contains the stripes pattern shipped with GIMP 2.2. This layer does mask the artistic motif in order to apply the stripes over it only. The background is not affected by the stripes pattern just the artistic motif. This layer is set to 20% of opacity. - - - - Layer 4: Shadow#1 - - This layer is placed above Pattern (Stripes) layer and fills the entire layer area with violet (6600ff) color. This layer do mask the artistic motif in order to applied the violet color to the background area outside the artistic motif only. This layer is set to 15% of opacity. - - - - Layer 5: Color#1 - - This layer is above Shadow#1 and is filled with orange (ffae00) color to cover the whole image. This layer is set to 10% of opacity. - - - - Layer 6: Color#2 - - This layer is above Color#1 and is filled with blue (010a88) color to cover the whole image. This layer is set to 10% of opacity. - - - - Layer 7: Shadow#2 - - This layer is above Color#1 and contains a linear gradient from left (000000) to right (transparent) covering 70% of the image approximately. - - -
- At this point we have the composition and should look like the desktop backgrounds. Compared with desktop backgrounds there are some differences in opacity. This is because in our testings the final color information found with this composition produces an acceptable 16 color image. Of course this is something we haven't seen yet. - To define the color information of our current coposition, save the syslinux background composition we've done using File > Save as Copy ... option in the following location: - - Now, create the final png version of syslinux backgrounds using the following command: - - This command will create syslinux-splash final images for all major releases of CentOS distribution the repository has been configured to. The important files here are syslinux-splash.png, other files may contain the wrong information because we haven't defined yet the correct color information to use. - Open one syslinux-splash.png file with GIMP and use the Image > Mode > Indexed to reduce image colors up to 16 colors, using the Generate optimum palette feature of GIMP. If the image looks aceptable after reducing colors, use the Palettes menu (Ctrl+P) of GIMP to import a new palette from file and name it CentOS-TreeFlower-Syslinux. Once you've saved the palette, the color information is stored at: - - You need to edit CentOS-TreeFlower-Syslinux.gpl file in order to set the appropriate order of colors. Remember black (000000) in position 0, and white (ffffff) in position 7. Other positions are irrelevant. When editing this file you may find that color reduction did not set black and white colors to their respective values exactly. Change that manually. For example, consider the following palette: - - Update the Palettes menu to get the new color positions from the file you just edited and open the palette with double click. - Update the syslinux.gpl file copying the following file: - - to - - With the CentOS-TreeFlower-Syslinux palette opened in the Palette Editor, open (Ctrl+O) the following file: - - and replace its color information with that one in CentOS-TreeFlower-Syslinux palette. When you are replacing color information inside syslilnux.ppm, remember to keep the order of colors just as they are in the CentOS-TreeFlower-Palette palette. - The syslinux.ppm file is 16 pixels width and 1 pixel height, so you probably need to zoom it a bit to set the color information in their place when using the pen tool with the brush Circle (01) (1 x 1). - Once you've updated the syslinux.ppm file, it is time to update the following file: - - The syslinux.hex file contains the color information in hexadecimal notation. The color information in hexadecimal notation is required by ppmtolss16 command. The ppmtolss16 command produces the final LSS16 image format that is used by syslinux program inside CentOS distribution. - The color information inside syslinux.hex must match the one in syslinux.ppm and syslinux.gpl. For example, based on CentOS-TreeFlower-Syslinux palette of colors above, consider the following syslinux.hex file: - - - - - Grub background - - - - - Usage - - • - - ... + @@ -2710,254 +2457,135 @@ trunk/Identity/Themes/Motifs/TreeFlower/Colors/syslinux.hex See also + + Directories trunk Identity Themes + Directories trunk Identity Themes + + + + Directories trunk Identity + Directories trunk Identity + + + + Directories trunk + Directories trunk + +
- Directories trunk Identity Webenv - Directories trunk Identity Widgets - Directories trunk Identity Themes Motifs TreeFlower Backgrounds + Directories trunk Identity Themes Motifs Flame + Directories trunk Identity Themes Motifs Modern + Directories trunk Identity Themes Motifs Directories
- The <file>trunk/Identity/Webenv</file> Directory - Directories trunk Identity Webenv + The <file>trunk/Identity/Themes/Motifs/Flame</file> Directory + Directories trunk Identity Themes Motifs Flame Goals - - • - - ... - - + This section describes the steps we followed to construct the Flame artistic motif. This section may be useful for anyone interested in reproducing the Flame artistic motif, or in creating new artistic motifs for The CentOS Project corporate visual identity (see Directories trunk Identity). Description - The CentOS web environment is formed by a central web application —to cover base needs (e.g., per-major release information like release notes, lifetime, downloads, documentation, support, security advisories, bugs, etc.)— and many different free web applications —to cover specific needs (e.g., wiki, mailing lists, etc.)—. - The CentOS web environment is addressed to solve the following issues: - - • - - One unique name and one unique visual style to all web applications used inside the web environment. - - - One-step navigation to web applications inside the environment. - - - High degree of customization to change the visual style of all web applications with few changes (e.g, updating just two or three images plus common style sheet [CSS] definitions). - - - The CentOS project is attached to a monolithic corporate visual identity (see Directories trunk Identity), where all visual manifestations have one unique name and one unique visual style. This way, the CentOS web environment has one unique name (the CentOS brand) and one unique visual style (the CentOS default theme) for all its visual manifestations, the web applications in this case. - Since a maintainance point of view, achiving the one unique visual style inside CentOS web environment is not a simple task. The CentOS web environment is built upon many different web applications which have different visual styles and different internal ways to customize their own visual styles. For example: MoinMoin, the web application used to support the CentOS wiki (http://wiki.centos.org/) is highly customizable but Mailman (in its 2.x.x serie), the web application used to support the CentOS mailing list, doesn't supportThe theme support of Mailman may be introduced in mailman-3.x.x release. a customization system that separates presentation from logic, similar to that used by MoinMoin. - This visual style diversity complicates our goal of one unique visual style for all web applications. So, if we want one unique visual style for all web applications used, it is innevitable to modify the web applications in order to implement the CentOS one unique visual style customization in them. Direct modification of upstream applications is not convenient because upstream applications come with their one visual style and administrators take the risk of loosing all customization changes the next time the application be updated (since not all upstream web applications, used in CentOS web environment, separate presentation from logic). - To solve the “one unique visual style” issue, installation and actualization of web applications —used inside CentOS web environment— need to be independent from upstream web applications development line; in a way that CentOS web environment administrators can install and update web applications freely without risk of loosing the one unique visual style customization changes. - At the surface of this issue we can see the need of one specific yum repository to store CentOS web environment customized web applications. + The Flame artistic motif was built using the flame filter of Gimp 2.2 in CentOS 5.5. + 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 centos-art.sh script (see Directories trunk Scripts) inside the CentOS Artwork Repository. + 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. + 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. + 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. + 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 centos-art.sh script. + With the combination of both CentOS Artwork Repository and centos-art.sh 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. + From a monolithic corporate visual identity point of view, notice that we are producing a new visual style for the same theme (i.e., Flame). 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. + 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). + 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. + Due to the “randomly generated” nature of Flame filter, we find that Flame pattern is not always the same when we use Flame filter interface. + 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. + + Important 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. + + In order for us to reproduce the same flame pattern always, Flame filter interface provides the Save and Open options. The Save 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 Open option brings up a file selector that allows you to open a previously saved Flame settings file. + The Flame settings we used in our example are saved in the file: + + + + Construction - Design model (without ads) + Step 1: Set image size + Create an empty image and fill the Background layer with black (000000) 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). - Design model (with ads) + Step 2: Add base color and pattern information + Create a new layer named Base, place it over Background layer and fill it with the base color (7800ff) you want to have your background image set in. Add a mask to Base 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. + Duplicate Base layer and name it Paper. Place Paper layer over Base layer. Remove content of Paper layer and fill it with Paper (100x100) pattern. Once you've done with black radial degradation, reduce the Paper layer opacity to 20%. + 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. + Duplicate Paper layer and rename it Stripes. Remove paper pattern from Stripes layer. Fill Stripes layer with Stripes (48x48) pattern and reduce the Stripes layer opacity to 15%. - HTML definitions + Step 3: Add flame motif + Create a new layer named Flame. Set the foreground (003cff) and background (0084ff) colors to the gradient you want to build the flame motif. + To build flame motif, use the flame filter (Filters > Render > Nature > Flame...) on Flame layer. We used a layer mask, with a radial gradient on it to control the boundaries of flame motif on Flame layer. + Duplicate Flame layer and rename it `Flame Blur'. Place `Flame Blur' below Flame layer. Apply Gussian blur filter (Filters > Blur > Gussian Blur...) until reaching the desiered effect. + The opacity value, in Flame 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 Flame layer opacity set at 100% but Flame Blur 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. - Controlling visual style - Inside CentOS web environment, the visual style is controlled by the following compenents: - - - Webenv header background - - - - - - CSS definitions - - - - -
- - - - Producing visual style - The visual style of CentOS web environment is defined in the following files: - - As graphic designer you use 1024x250.xcf file to produce 1024x250-bg.png file. Later, inside 1024x250.svg file, you use the 1024x250-bg.png file as background layer to draw your vectorial design. When you consider you artwork ready, use the centos-art.sh script, as described below, to produce the visual style controller images of CentOS web environment. - - Once you have rendered required image files, changing the visual style of CentOS web environment is a matter of replacing old image files with new ones, inside webenv repository file system structure. The visual style changes will take effect the next time customization line of CentOS web applications be packaged, uploded, and installed from [webenv] or [webenv-test] repositories. - - - - Navigation - Inside CentOS web environment, the one-step navegation between web applications is addressed using the web environment navigation bar. The web environment navigation bar contains links to main applications and is always visible no matter where you are inside the web environment. - - - - Development and release cycle - The CentOS web environment development and relase cycle is described below: - - - Download - - The first action is download the source code of web applications we want to use inside CentOS web environment. - - Important The source location from which web application are downloaded is very important. Use SRPMs from CentOS [base] and [updates] repositories as first choise, and third party repositories (e.g. RPMForge, EPEL, etc.) as last resource. - - - - - Prepare - - Once web application source code has been downloaded, our duty is organize its files inside webenv version controlled repository. - When preparing the structure keep in mind that different web applications have different visual styles, and also different ways to implement it. A convenient way to organize the file system structure would be create one development line for each web application we use inside CentOS web environment. For example, consider the following file system structure: - - - - - Customize - - Once web applications have been organized inside the version controlled repository file system, use subversion to create the CentOS customization development line of web applications source code. For example, using the above file system structure, you can create the customization development line of webapp1-0.0.1/ with the following command: - - The command above creates the following structure: - - In the above structure, the webapp1-0.0.1-webenv/ directory is the place where you customize the visual style of webapp1-0.0.1/ web application. - - Tip Use the diff command of Subversion between CentOS customization and upstream development lines to know what you are changing exactly. - - - - - Build packages - - When web application has been customized, build the web application RPM and SRPM using the source location with -webenv prefix. - - - - - Release for testing - - When the customized web application has been packaged, make packages available for testing and quality assurance. This can be achives using a [webenv-test] yum repository. - - Note The [webenv-test] repository is not shipped inside CentOS distribution default yum configuraiton. In order to use [webenv-test] repository you need to configure it first. - - If some problem is found to install/update/use the customized version of web application, the problem is notified somewhere (a bugtracker maybe) and the customization face is repated in order to fix the problem. To release the new package add a number after -webenv prefix. For example, if some problem is found in webapp1-0.0.1-webenv.rpm, when it be fixed the new package will be named webapp1-0.0.1-webenv-1.rpm. If a problem is found in webapp1-0.0.1-webenv-1.rpm, when it be fixed the new package will be named webapp1-0.0.1-webenv-2.rpm, and so on. - The “customization — release for testing” process is repeated until CentOS quality assurance team considers the package is ready for production. - - - - Release for production - - When customized web application packages are considered ready for production they are moved from [webenv-test] to [webenv] repository. This action is commited by CentOS quality assurance team. - - Note The [webenv] repository is not shipped inside CentOS distribution default yum configuraiton. In order to use [webenv] repository you need to configure it first. - - - -
- - - - The [webenv-test] repository - - + Step 4: Add foreground color + Create a new layer named Color, place it on top of all visible layers and fill it with plain color (4c005a). Reduce Color layer opacity to 20%. You can use the Color layer to control the right side color information you want to produce the image for. + Duplicate Flame layer and create a new layer named Color#1. Place Color#1 layer on top of layer named Color. Remove the mask information from Color#1 layer and recreate a new one using an inverted alpha channel as reference. Remove Color#1 layer content and fill it back with plain black (000000) color. Reduce Color#1 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. + 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. + 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. + - - The [webenv] repository - - - + + See also + + + Directories trunk Identity Themes Motifs + Directories trunk Identity Themes Motifs + + + + Directories trunk Identity Themes + Directories trunk Identity Themes + + + + Directories trunk Identity + Directories trunk Identity + + + + Directories trunk + Directories trunk + + + + +
+ + + Directories trunk Identity Themes Motifs Modern + Directories trunk Identity Themes Motifs Modern Backgrounds + Directories trunk Identity Themes Motifs Flame + Directories +
+ The <file>trunk/Identity/Themes/Motifs/Modern</file> Directory + Directories trunk Identity Themes Motifs Modern + + Presentation + - - Priority configuration - Both [webenv] and [webenv-test] repositories update packages inside CentOS [base] and CentOS [updates] repositories. - + + Construction @@ -2978,215 +2606,109 @@ priority=10
- Directories trunk Identity Widgets - Directories trunk Locales - Directories trunk Identity Webenv + Directories trunk Identity Themes Motifs Modern Backgrounds + Directories trunk Identity Themes Motifs Modern Backgrounds Img + Directories trunk Identity Themes Motifs Modern Directories
- The <file>trunk/Identity/Widgets</file> Directory - Directories trunk Identity Widgets + The <file>trunk/Identity/Themes/Motifs/Modern/Backgrounds</file> Directory + Directories trunk Identity Themes Motifs Modern Backgrounds Goals • - ... + Organize background images for Modern theme. Description + Inside Motifs directory, the Backgrounds/ directory is used to create vectorial designs using Inkscape and background images using Gimp. Later, you can export background images as .png and load them in your vectorial design project using the import feautre of Inkscape. + You may need to repeat this technic for different screen resoluions. In that case you need to create one file for each screen resolution and do the appropriate linking inside .svg to .png files. For example if you need to produce background images in 800x600 you need to create the following file: + xcf/800x600.xcf + to produce the background image: + img/800x600-bg.png + which is loaded in: + svg/800x600.svg + to produce the final background image: + img/800x600.png + The img/800x600.png background image is produced automatically by means of rendering scripts. + In other cases (e.g. Anaconda), it is possible that you need to make some variations to one background image that don't want to appear on regular background images of the same resolution. In this case you need to create a new and specific background image for that art component. For example, if you need to produce the background image used by Anconda (800x600) art works you create the file: + xcf/800x600-anaconda.xcf + to produce the background image: + img/800x600-anaconda-bg.png + which is loaded in: + svg/800x600-anaconda.svg + to produce the file: + img/800x600-anaconda.png + The 800x600-anaconda.png file is used by all Anaconda art works sharing a common 800x600 screen resolution (e.g., Header, Progress, Splash, Firstboot, etc.). The Anaconda Prompt is indexed to 16 colors and 640x480 pixels so you need to create a 640x480 background image for it, and take the color limitation into account when designing it. + Background images without artistic motif are generally used as based to build the Background images that do contain the theme artistic motif. + Background images are linked (using the import feature of Inkscape) inside almost all theme art works. This structure let you make centralized changes on the visual identity and propagate them quickly to other areas. + In this structure you design background images for different screen resolutions based on the theme artistic motif. + You may create different artistic motifs propositions based on the same conceptual idea. The conceptual idea is what defines a theme. Artistic motifs are interpretations of that idea. + Inside this directory artistic motifs are organized by name (e.g., TreeFlower, Modern, etc.). + Each artistic motif directory represents just one unique artistic motif. + The artistic motif is graphic design used as common pattern to connect all visual manifestations inside one unique theme. The artistic motif is based on a conceptual idea. Artistic motifs provide visual style to themes. + Designing artistic motifs is for anyone interested in creating beautiful themes for CentOS. When building a theme for CentOS, the first design you need to define is the artistic motif. + Inside CentOS Artwork Repository, theme visual styles (Motifs) and theme visual structures (Models) are two different working lines. When you design an artistic motif for CentOS you concentrate on its visual style, and eventualy, use the centos-art command line interface to render the visual style, you are currently producing, against an already-made theme model in order to produce the final result. Final images are stored under Motifs/ directory using the model name, and the model directory structure as reference. + The artistic motif base structure is used by centos-art to produce images automatically. This section describes each directory of CentOS artistic motif base structure. Usage + The Backgrounds/ directory is probably the core component, inside Motifs/ directory structure. Inside Backgrounds/ directory you produce background images used by almost all theme models (e.g., Distribution, Websites, Promotion, etc.). The Backgrounds/ directory can contain subdirectories to help you organize the design process. See also - - -
- - - Directories trunk Locales - Directories trunk Locales Identity - Directories trunk Identity Widgets - Directories -
- The <file>trunk/Locales</file> Directory - Directories trunk LocalesThe trunk/Locales directory exists to store the translation messages used to produce content in different languages. - Translation messages are organized using the directory structure of the component being translated. For example, if we want to provide translation messages for trunk/Manuals/Repository, then the trunk/Locales/Manuals/Repository directory needs to be created. - Once the locale directory exists for the component we want to provide translation messages for, it is necessary to create the translation files where translation messages are. The translation files follows the concepts of xml2po and GNU gettext tools. - The basic translation process is as follow: first, translatable strings are extracted from files and a portable object template (.pot) is created or updated with the information. Using the portable object template, a portable object (.po) is created or updated for translator to locale the messages retrived. Finally, a machine object (.mo) is created from portable object to sotore the translated messages. - Inside the repository there are two ways to retrive translatable strings from files. The first one is through xml2po command and the second through xgettext command. The xml2po is used to retrive translatable strings from XML files (e.g., Scalable Vector Graphics, DocBook, etc.) and the xgettext command is used to retrive translatable strings from shell scripts files (e.g., the files that make the centos-art.sh command-line interface). - When translatable strings are retrived from XML files, using the xml2po command, there is no need to create the machine object as we do when translatable strings ar retrived from shell files, using the xgettext command. The xml2po produces a temporal machine object in order to create a translated XML file. Once the translated XML file has been created the machine object is no longer needed. On the other hand, the machine object produced by the xgettext command is required by the system in order for the show shell script localized messages. - Another difference between xml2po and xgettext we need to be aware of is the directory structure used to store machine objects. In xml2po, the machine object is created in the current working directory as .xml2po.mo and can be safetly removed once the translated XML file has been created. In the case of xgettext, the machine object needs to be stored in the $TEXTDOMAIN/$LOCALE/LL_MESSAGES/$TEXTDOMAIN.mo file in order for the system to interpret it and should not be removed since it is the file that contain the translation messages themselves. - Automation of localization tasks is achived through the locale functionality of command-line interface. - - - Directories trunk Scripts Functions Locale - Directories trunk Scripts Functions Locale - - - -
- - - Directories trunk Locales Identity - Directories trunk Locales Identity Brands - Directories trunk Locales - Directories -
- The <file>trunk/Locales/Identity</file> Directory - Directories trunk Locales Identity - - Goals - - • - - ... - - - - - - Description - - • - - ... - - - - - - Usage - - • - - ... - - - - - - See also - - - - - - - - Directories trunk Identity - Directories trunk Identity + Directories trunk Identity Themes Motifs Modern Backgrounds Img + Directories trunk Identity Themes Motifs Modern Backgrounds Img + + + + Directories trunk Identity Themes Motifs Modern Backgrounds Tpl + Directories trunk Identity Themes Motifs Modern Backgrounds Tpl + + Directories trunk Identity Themes Motifs Modern Backgrounds Xcf + Directories trunk Identity Themes Motifs Modern Backgrounds Xcf + + +
- Directories trunk Locales Identity Brands - Directories trunk Locales Identity Brands Tpl - Directories trunk Locales Identity + Directories trunk Identity Themes Motifs Modern Backgrounds Img + Directories trunk Identity Themes Motifs Modern Backgrounds Tpl + Directories trunk Identity Themes Motifs Modern Backgrounds Directories
- The <file>trunk/Locales/Identity/Brands</file> Directory - Directories trunk Locales Identity Brands + The <file>trunk/Identity/Themes/Motifs/Modern/Backgrounds/Img</file> Directory + Directories trunk Identity Themes Motifs Modern Backgrounds Img Goals • - Organize brands' translation files. + ... Description - Translation files, inside trunk/Translations/Identity/Brands translation entry, don't use default rendering translation functionality, they use the following translation pre-rendering configuration file instead: - - Inside trunk/Translations/Identity/Brands translation entry, translation files are symbolic links pointing to the common template translation structure, inside the translation template (Tpl/) directory. - Inside trunk/Translations/Identity/Brands translation entry, translation files are created using identity design templates as reference. The translation pre-rendering script creates a translation structure where the translation template (Tpl/) directory structure applies to each single design template available. - For example, if the brands' translation template (Tpl/) directory has 30 translation files, and there are 20 design templates; the brands' translation pre-rendering script creates a translation structure of symbolic links where the 30 translation files apply the 20 design templates one by one, producing 600 translation symbolic links as result. At this point, when rendering identity, the centos-art script considers translation symbolic links as translation files. - Translation file names, inside brands' translation template (Tpl) directory have special meaning: - - - Conventional file names - Translation brands file names Convenctional file names look like blue.sed, 2c-a.sed, etc. Replacement commands inside translation file are applied to design templates and translation file names are used as final image name. The image dimensions use the same dimensions that design template has. - - - - Numeric file names - Translation brands file names Numeric file names look like 300.sed, 200.sed, etc. Replacements commands inside translation files are applied to design templates, and translation file names are used as final image name. The final image is saved using an specific width defined by the number part of the translation file name. The image height is automatically scaled based on the previous width definition to maintain the designing ratio. - For example, if your design template has 400x200 pixels of dimension, and you apply a translation file named `300.sed' to it, the final image you get as result will have 300x100 pixels of dimension. The same is true if you use higher numbers like `1024.sed', `2048.sed', etc. In these cases you have bigger images proportionally. - As we are using scalable vector graphics to design identity templates, the image size you produce is not limitted in size. You can use one design template produced in 400x200 pixels to produce larger or shorter PNG images using numeric translation files as described above. - - - - Translation markers - Inside trunk/Translations/Identity/Brands/, translation files combine the following translation markers: - - - #000000 - - Specify which color to use when rendering brand images. - - Note As translation files inside trunk/Translations/Identity/Brands are symbolic links that point to template translation files, translation markers are defined inside template translation files. - - - -
- - - - - Usage - How to render brands' translation files To render brands' translation files, use the following command: - - - - - See also - - - - Directories trunk Identity Brands - Directories trunk Identity Brands - - - - -
- - - Directories trunk Locales Identity Brands Tpl - Directories trunk Locales Identity Fonts - Directories trunk Locales Identity Brands - Directories -
- The <file>trunk/Locales/Identity/Brands/Tpl</file> Directory - Directories trunk Locales Identity Brands Tpl - - Goals - - - - Description Usage + In this directory is where you store all background images (e.g., .png, .jpg, .xpm, etc.). This directory is required by centos-art command line interface. @@ -3197,95 +2719,70 @@ centos-art render --translation=/home/centos/artwork/trunk/Translations/Identity
- Directories trunk Locales Identity Fonts - Directories trunk Locales Identity Models - Directories trunk Locales Identity Brands Tpl + Directories trunk Identity Themes Motifs Modern Backgrounds Tpl + Directories trunk Identity Themes Motifs Modern Backgrounds Xcf + Directories trunk Identity Themes Motifs Modern Backgrounds Img Directories
- The <file>trunk/Locales/Identity/Fonts</file> Directory - Directories trunk Locales Identity Fonts + The <file>trunk/Identity/Themes/Motifs/Modern/Backgrounds/Tpl</file> Directory + Directories trunk Identity Themes Motifs Modern Backgrounds Tpl Goals - This section exists to organize fonts translation files. + + • + + ... + + Description - Translation files, inside trunk/Translations/Fonts, have the following structure: - - Inside trunk/Translations/Fonts, there is one translation file for each font preview image you want to produce. This way, we create one translation file for each font-family we use somewhere inside CentOS visual identity. - - Important Do not create translation files for font-families not used somewhere inside CentOS visual identity. The identity of font entry (see Directories trunk Identity Fonts) is used as reference when someone needs to know which font-families are allowed to use inside CentOS visual identity. - - - - Translation Markers - Inside trunk/Translations/Identity/Fonts, translation files combine the following translation markers: - - - font-family:Denmark - - Specify which font family to use when rendering font preview images. - - - - font-weight:normal - - Specify which font weight to use when rendering font preview images. - - - - font-style:normal - - Specify which font style to use when rendering font preview images. - - -
- Usage - How to render fonts' translation files Inside trunk/Translations/Fonts you use your favorite text editor to create translation files. Inside trunk/Translations/Fonts there is not translation template directory (Tpl/), nor translation rendering using centos-art script. For example, to create the dejavu_lgc_sans-boldoblique.sed translation file using vim editor, type the following command: - + In this directory is where you store all the scalable vector graphics (e.g., .svg) files. This directory is required by centos-art command line interface. See also - - Directories trunk Identity Fonts - Directories trunk Identity Fonts - -
- Directories trunk Locales Identity Models - Directories trunk Locales Identity Release - Directories trunk Locales Identity Fonts + Directories trunk Identity Themes Motifs Modern Backgrounds Xcf + Directories trunk Identity Themes Motifs Modern Distro Anaconda Progress + Directories trunk Identity Themes Motifs Modern Backgrounds Tpl Directories
- The <file>trunk/Locales/Identity/Models</file> Directory - Directories trunk Locales Identity Models + The <file>trunk/Identity/Themes/Motifs/Modern/Backgrounds/Xcf</file> Directory + Directories trunk Identity Themes Motifs Modern Backgrounds Xcf Goals + + • + + ... + + Description + + • + + ... + + Usage + In this directory is where you store the project files (e.g, .xcf) of Gimp. This directory is not required by centos-art command line interface. If you can create a beautiful background images using scalable vector graphics only, then there is no need to use the Xcf/ directory to store background projects. Of course, you can merge both Gimp and Inkscape power to produce images based on them. In this last case you need the Xcf/ directory. @@ -3296,15 +2793,21 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se
- Directories trunk Locales Identity Release - Directories trunk Locales Identity Themes - Directories trunk Locales Identity Models + Directories trunk Identity Themes Motifs Modern Distro Anaconda Progress + Directories trunk Identity Themes Motifs Modern Palettes + Directories trunk Identity Themes Motifs Modern Backgrounds Xcf Directories
- The <file>trunk/Locales/Identity/Release</file> Directory - Directories trunk Locales Identity Release + The <file>trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress</file> Directory + Directories trunk Identity Themes Motifs Modern Distro Anaconda Progress Goals + + • + + ... + + @@ -3313,7 +2816,39 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se Usage - + To render Anaconda progress slide images using the Modern artistic motif design, the Default theme model, and available translation files (— Removed(pxref:trunk Translations Identity Themes Distro Anaconda Progress) —); use the following commands: + cd /home/centos/artwork/trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress/ +centos-art render --identity + The above command will create the following structure: + trunk/Identity/Themes/Motifs/Modern/Distro/Anaconda/Progress +|-- 3 +| |-- en +| | |-- 01-welcome.png +| | |-- 02-donate.png +| | `-- 03-yum.png +| `-- es +| |-- 01-welcome.png +| |-- 02-donate.png +| `-- 03-yum.png +|-- 4 +| |-- en +| | |-- 01-welcome.png +| | |-- 02-donate.png +| | `-- 03-yum.png +| `-- es +| |-- 01-welcome.png +| |-- 02-donate.png +| `-- 03-yum.png +`-- 5 + |-- en + | |-- 01-welcome.png + | |-- 02-donate.png + | `-- 03-yum.png + `-- es + |-- 01-welcome.png + |-- 02-donate.png + `-- 03-yum.png + See also @@ -3323,15 +2858,21 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se
- Directories trunk Locales Identity Themes - Directories trunk Locales Identity Themes Backgrounds - Directories trunk Locales Identity Release + Directories trunk Identity Themes Motifs Modern Palettes + Directories trunk Identity Themes Motifs TreeFlower + Directories trunk Identity Themes Motifs Modern Distro Anaconda Progress Directories
- The <file>trunk/Locales/Identity/Themes</file> Directory - Directories trunk Locales Identity Themes + The <file>trunk/Identity/Themes/Motifs/Modern/Palettes</file> Directory + Directories trunk Identity Themes Motifs Modern Palettes Goals + + • + + Organize palette files for Modern theme. + + @@ -3340,6 +2881,7 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se Usage + Here is where graphic designers define theme palettes for color-limited art works. Theme palettes contain the color information that rendering functions need, in order to produce images with color limitations. Theme palettes contain the unique color information required by theme. @@ -3350,13 +2892,13 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se
- Directories trunk Locales Identity Themes Backgrounds - Directories trunk Locales Identity Themes Distro Anaconda Progress - Directories trunk Locales Identity Themes + Directories trunk Identity Themes Motifs TreeFlower + Directories trunk Identity Themes Motifs TreeFlower Backgrounds + Directories trunk Identity Themes Motifs Modern Palettes Directories
- The <file>trunk/Locales/Identity/Themes/Backgrounds</file> Directory - Directories trunk Locales Identity Themes Backgrounds + The <file>trunk/Identity/Themes/Motifs/TreeFlower</file> Directory + Directories trunk Identity Themes Motifs TreeFlower Goals @@ -3369,22 +2911,10 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se Description - - • - - ... - - Usage - - • - - ... - - @@ -3395,107 +2925,246 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se
- Directories trunk Locales Identity Themes Distro Anaconda Progress - Directories trunk Locales Identity Widgets - Directories trunk Locales Identity Themes Backgrounds + Directories trunk Identity Themes Motifs TreeFlower Backgrounds + Directories trunk Identity Webenv + Directories trunk Identity Themes Motifs TreeFlower Directories
- The <file>trunk/Locales/Identity/Themes/Distro/Anaconda/Progress</file> Directory - Directories trunk Locales Identity Themes Distro Anaconda Progress + The <file>trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds</file> Directory + Directories trunk Identity Themes Motifs TreeFlower Backgrounds Goals - - • - - Organize Anaconda progress translation templates. - - - Organize Anaconda progress translation files in several languages and major releases of CentOS distribution. - - + This section exists to orgnize backgrounds of TreeFlower artistic motif. Description - Use the following command to produce translation files based: - trunk/Translations/Identity/Themes/Distro/Anaconda/Progress -`-- Tpl - |-- en - | |-- 01-welcome.sed - | |-- 02-donate.sed - | `-- 03-yum.sed - `-- es - |-- 01-welcome.sed - |-- 02-donate.sed - `-- 03-yum.sed - In order to produce the slide images in PNG format we need to have the translation files first. So we use the following commands to create translation files for CentOS 3, 4, and 5 major releases: - centos-art render --translation --filter='3,4,5' - The above commands will produce the following translation structure: - trunk/Translations/Identity/Themes/Distro/Anaconda/Progress -|-- 3 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -|-- 4 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -|-- 5 -| |-- en -| | |-- 01-welcome.sed -| | |-- 02-donate.sed -| | `-- 03-yum.sed -| `-- es -| |-- 01-welcome.sed -| |-- 02-donate.sed -| `-- 03-yum.sed -`-- Tpl - |-- en - | |-- 01-welcome.sed - | |-- 02-donate.sed - | `-- 03-yum.sed - `-- es - |-- 01-welcome.sed - |-- 02-donate.sed - `-- 03-yum.sed - At this point we have all the translation files we need to produce Anaconda progress welcome, donate and yum slides images; in English and Spanish languages; for CentOS 3, CentOS 4, and CentOS 5. That is, a sum of 18 images around. - Now, with translation files in place, let's move to trunk/Identity structure and render them. + + Desktop background + Once you have defined the vectorial artistic motif design, use the centos-art.sh script (as described in usage section below) to produce the png version of it. With the png version of your vectorial design do the following: + Open the png version with GIMP. + Save the png version as a project of GIMP inside trunk/Identity/Themes/Motifs/TreeFlower/Backgrounds/Xcf directory, using the same name of your vectorial design but with the .xcf extension. + Now use GIMP to improve your design. Here you may add one layer for pattern, another for colors, and so on until you find yourself confortable with your artwork. For example, the following layer distribution (from bottom to top) was used to build revision 285 of file 1360x768.xcf using TreeFlower artistic motif at revision 241. + + + Layer 1: Background + + The first thing we did with GIMP was to create a layer named Background to store the artistic motif (File > Open as layer). This layer is the lowest layer in the image. Later, we started to create layers one upon another to change the artistic motif visual style. + + + + Layer 2: Shadow#1 + + This layer is above Background and contains a linear gradient from left (000000) to right (transparent) covering the whole image. This layer masks the artistic motif to avoid the effect of linear gradient. This layer is 100% of opacity. + + + + Layer 3: Shadow#2 + + This layer is above Shadow#1 and contains a linear gradient from left (000000) to right (transparent) covering just the 70% of the whole image aproximatly. This layer doesn't mask the artistic motif which make the left part of it fall into the dark of linear gradient. This layer is 100% of opacity. + + + + Layer 4: Pattern (Paper) + + This layer is above Shadow#2 an contains the paper pattern shipped with GIMP 2.2. This layer doesn't mask the artistic motif so the pattern is applied over the whole image. This layer is set to 15% of opacity. + + + + Layer 5: Pattern (Stripes) + + This layer is above Pattern (Paper) and contains the stripes used over the artistic motif. This layer do masks the artistic motif so the stripes are only applied to it. This layer is set to 10% of opacity. + + + + Layer 6: Shadow#3 + + This layer is above Pattern (Stripes) and contains a linear gradient from right (6600ff) to left (transparent). This layer masks the artistic motif so the linear gradient doesn't affect it. This layer is set to 15% of opacity. + + + + Layer 7: Shadow#4 + + This layer is above Shadow#3 and contains a linear gradient from left (000000) to right (transparent). This layer do masks the artistic motif so the linear gradient doesn't affect it. This layer is set to 10% of opacity. + + + + Layer 8: Color#1 + + This layer is above Shadow#4 and is filled with orange (ffae00) color over the whole image. This layer is set to 10% of opacity. + + + + Layer 9: Color#2 + + This layer is above Color#1 and is filled with blue (010a88) color over the whole image. This layer is set to 10% of opacity. + + +
+ + Note There is no definite combination. To get the appropriate visual design is a matter of constant testing and personal taste. + + Finally, use Save as copy ... option to export the final design. To export the final design use the same name of your vectorial design plus -final.png extension. + You can repeat these steps to create images for other screen resolutions. + + + + Anaconda Prompt (syslinux) background + When building syslinux backgrounds it is needed to take into account that the final image is reduced to 16 colors. In desktop background there is no color limitation but syslinux does have. The goal of this section is achieving a final syslinux background as close as possible to desktop backgrounds using 16 colors only. + Another point to consider is the forground and background definition used by syslinux. The syslinux documentation says that the color set in position 0 is the background and color set in position 7 is the forground. The final palette of color used by our background will match that specification. For great contrast we'll use black as background and white as forground. At this poing we have black (000000) and white (ffffff) colors in our syslinux palette, which left us with 14 colors to play with. + Let's begin with Xcf/640x300.xcf layer distribution from bottom to top: + + + Layer 1: Background + + This layer is the lowest layer in the image composition and contains the artistic motif image rendered for the same resolution (i.e., Img/Png/640x300.png). This layer is set to 100% of opacity. + + + + Layer 2: Pattern (Paper) + + This layer is placed above Background layer and contains the paper pattern shipped with GIMP 2.2. This layer doesn't mask the artistic motif. This layer is set to 30% of opacity. + + + + Layer 3: Pattern (Stripes) + + This layer is placed above Pattern (Paper) layer and contains the stripes pattern shipped with GIMP 2.2. This layer does mask the artistic motif in order to apply the stripes over it only. The background is not affected by the stripes pattern just the artistic motif. This layer is set to 20% of opacity. + + + + Layer 4: Shadow#1 + + This layer is placed above Pattern (Stripes) layer and fills the entire layer area with violet (6600ff) color. This layer do mask the artistic motif in order to applied the violet color to the background area outside the artistic motif only. This layer is set to 15% of opacity. + + + + Layer 5: Color#1 + + This layer is above Shadow#1 and is filled with orange (ffae00) color to cover the whole image. This layer is set to 10% of opacity. + + + + Layer 6: Color#2 + + This layer is above Color#1 and is filled with blue (010a88) color to cover the whole image. This layer is set to 10% of opacity. + + + + Layer 7: Shadow#2 + + This layer is above Color#1 and contains a linear gradient from left (000000) to right (transparent) covering 70% of the image approximately. + + +
+ At this point we have the composition and should look like the desktop backgrounds. Compared with desktop backgrounds there are some differences in opacity. This is because in our testings the final color information found with this composition produces an acceptable 16 color image. Of course this is something we haven't seen yet. + To define the color information of our current coposition, save the syslinux background composition we've done using File > Save as Copy ... option in the following location: + + Now, create the final png version of syslinux backgrounds using the following command: + + This command will create syslinux-splash final images for all major releases of CentOS distribution the repository has been configured to. The important files here are syslinux-splash.png, other files may contain the wrong information because we haven't defined yet the correct color information to use. + Open one syslinux-splash.png file with GIMP and use the Image > Mode > Indexed to reduce image colors up to 16 colors, using the Generate optimum palette feature of GIMP. If the image looks aceptable after reducing colors, use the Palettes menu (Ctrl+P) of GIMP to import a new palette from file and name it CentOS-TreeFlower-Syslinux. Once you've saved the palette, the color information is stored at: + + You need to edit CentOS-TreeFlower-Syslinux.gpl file in order to set the appropriate order of colors. Remember black (000000) in position 0, and white (ffffff) in position 7. Other positions are irrelevant. When editing this file you may find that color reduction did not set black and white colors to their respective values exactly. Change that manually. For example, consider the following palette: + + Update the Palettes menu to get the new color positions from the file you just edited and open the palette with double click. + Update the syslinux.gpl file copying the following file: + + to + + With the CentOS-TreeFlower-Syslinux palette opened in the Palette Editor, open (Ctrl+O) the following file: + + and replace its color information with that one in CentOS-TreeFlower-Syslinux palette. When you are replacing color information inside syslilnux.ppm, remember to keep the order of colors just as they are in the CentOS-TreeFlower-Palette palette. + The syslinux.ppm file is 16 pixels width and 1 pixel height, so you probably need to zoom it a bit to set the color information in their place when using the pen tool with the brush Circle (01) (1 x 1). + Once you've updated the syslinux.ppm file, it is time to update the following file: + + The syslinux.hex file contains the color information in hexadecimal notation. The color information in hexadecimal notation is required by ppmtolss16 command. The ppmtolss16 command produces the final LSS16 image format that is used by syslinux program inside CentOS distribution. + The color information inside syslinux.hex must match the one in syslinux.ppm and syslinux.gpl. For example, based on CentOS-TreeFlower-Syslinux palette of colors above, consider the following syslinux.hex file: + + + + + Grub background + + + + + Usage • - See Directories trunk Identity Themes Motifs Modern Distro Anaconda Progress. + ... - Usage - Translation rendering is described in trunk/Translations documentation entry (— Removed(pxref:trunk Translations) —). - - - See also + +
- Directories trunk Locales Identity Widgets - Directories trunk Manual - Directories trunk Locales Identity Themes Distro Anaconda Progress + Directories trunk Identity Webenv + Directories trunk Identity Widgets + Directories trunk Identity Themes Motifs TreeFlower Backgrounds Directories
- The <file>trunk/Locales/Identity/Widgets</file> Directory - Directories trunk Locales Identity Widgets + The <file>trunk/Identity/Webenv</file> Directory + Directories trunk Identity Webenv Goals @@ -3508,12 +3177,230 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se Description + The CentOS web environment is formed by a central web application —to cover base needs (e.g., per-major release information like release notes, lifetime, downloads, documentation, support, security advisories, bugs, etc.)— and many different free web applications —to cover specific needs (e.g., wiki, mailing lists, etc.)—. + The CentOS web environment is addressed to solve the following issues: • - ... + One unique name and one unique visual style to all web applications used inside the web environment. + + + One-step navigation to web applications inside the environment. + + + High degree of customization to change the visual style of all web applications with few changes (e.g, updating just two or three images plus common style sheet [CSS] definitions). + The CentOS project is attached to a monolithic corporate visual identity (see Directories trunk Identity), where all visual manifestations have one unique name and one unique visual style. This way, the CentOS web environment has one unique name (the CentOS brand) and one unique visual style (the CentOS default theme) for all its visual manifestations, the web applications in this case. + Since a maintainance point of view, achiving the one unique visual style inside CentOS web environment is not a simple task. The CentOS web environment is built upon many different web applications which have different visual styles and different internal ways to customize their own visual styles. For example: MoinMoin, the web application used to support the CentOS wiki (http://wiki.centos.org/) is highly customizable but Mailman (in its 2.x.x serie), the web application used to support the CentOS mailing list, doesn't supportThe theme support of Mailman may be introduced in mailman-3.x.x release. a customization system that separates presentation from logic, similar to that used by MoinMoin. + This visual style diversity complicates our goal of one unique visual style for all web applications. So, if we want one unique visual style for all web applications used, it is innevitable to modify the web applications in order to implement the CentOS one unique visual style customization in them. Direct modification of upstream applications is not convenient because upstream applications come with their one visual style and administrators take the risk of loosing all customization changes the next time the application be updated (since not all upstream web applications, used in CentOS web environment, separate presentation from logic). + To solve the “one unique visual style” issue, installation and actualization of web applications —used inside CentOS web environment— need to be independent from upstream web applications development line; in a way that CentOS web environment administrators can install and update web applications freely without risk of loosing the one unique visual style customization changes. + At the surface of this issue we can see the need of one specific yum repository to store CentOS web environment customized web applications. + + + Design model (without ads) + + + + Design model (with ads) + + + + HTML definitions + + + + Controlling visual style + Inside CentOS web environment, the visual style is controlled by the following compenents: + + + Webenv header background + + + + + + CSS definitions + + + + +
+ + + + Producing visual style + The visual style of CentOS web environment is defined in the following files: + + As graphic designer you use 1024x250.xcf file to produce 1024x250-bg.png file. Later, inside 1024x250.svg file, you use the 1024x250-bg.png file as background layer to draw your vectorial design. When you consider you artwork ready, use the centos-art.sh script, as described below, to produce the visual style controller images of CentOS web environment. + + Once you have rendered required image files, changing the visual style of CentOS web environment is a matter of replacing old image files with new ones, inside webenv repository file system structure. The visual style changes will take effect the next time customization line of CentOS web applications be packaged, uploded, and installed from [webenv] or [webenv-test] repositories. + + + + Navigation + Inside CentOS web environment, the one-step navegation between web applications is addressed using the web environment navigation bar. The web environment navigation bar contains links to main applications and is always visible no matter where you are inside the web environment. + + + + Development and release cycle + The CentOS web environment development and relase cycle is described below: + + + Download + + The first action is download the source code of web applications we want to use inside CentOS web environment. + + Important The source location from which web application are downloaded is very important. Use SRPMs from CentOS [base] and [updates] repositories as first choise, and third party repositories (e.g. RPMForge, EPEL, etc.) as last resource. + + + + + Prepare + + Once web application source code has been downloaded, our duty is organize its files inside webenv version controlled repository. + When preparing the structure keep in mind that different web applications have different visual styles, and also different ways to implement it. A convenient way to organize the file system structure would be create one development line for each web application we use inside CentOS web environment. For example, consider the following file system structure: + + + + + Customize + + Once web applications have been organized inside the version controlled repository file system, use subversion to create the CentOS customization development line of web applications source code. For example, using the above file system structure, you can create the customization development line of webapp1-0.0.1/ with the following command: + + The command above creates the following structure: + + In the above structure, the webapp1-0.0.1-webenv/ directory is the place where you customize the visual style of webapp1-0.0.1/ web application. + + Tip Use the diff command of Subversion between CentOS customization and upstream development lines to know what you are changing exactly. + + + + + Build packages + + When web application has been customized, build the web application RPM and SRPM using the source location with -webenv prefix. + + + + + Release for testing + + When the customized web application has been packaged, make packages available for testing and quality assurance. This can be achives using a [webenv-test] yum repository. + + Note The [webenv-test] repository is not shipped inside CentOS distribution default yum configuraiton. In order to use [webenv-test] repository you need to configure it first. + + If some problem is found to install/update/use the customized version of web application, the problem is notified somewhere (a bugtracker maybe) and the customization face is repated in order to fix the problem. To release the new package add a number after -webenv prefix. For example, if some problem is found in webapp1-0.0.1-webenv.rpm, when it be fixed the new package will be named webapp1-0.0.1-webenv-1.rpm. If a problem is found in webapp1-0.0.1-webenv-1.rpm, when it be fixed the new package will be named webapp1-0.0.1-webenv-2.rpm, and so on. + The “customization — release for testing” process is repeated until CentOS quality assurance team considers the package is ready for production. + + + + Release for production + + When customized web application packages are considered ready for production they are moved from [webenv-test] to [webenv] repository. This action is commited by CentOS quality assurance team. + + Note The [webenv] repository is not shipped inside CentOS distribution default yum configuraiton. In order to use [webenv] repository you need to configure it first. + + + +
+ + + + The [webenv-test] repository + + + + + + The [webenv] repository + + + + + + Priority configuration + Both [webenv] and [webenv-test] repositories update packages inside CentOS [base] and CentOS [updates] repositories. + @@ -3529,19 +3416,18 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se See also -
- Directories trunk Manual + Directories trunk Identity Widgets Directories trunk Scripts - Directories trunk Locales Identity Widgets + Directories trunk Identity Webenv Directories
- The <file>trunk/Manual</file> Directory - Directories trunk Manual + The <file>trunk/Identity/Widgets</file> Directory + Directories trunk Identity Widgets Goals @@ -3554,22 +3440,10 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se Description - - • - - ... - - Usage - - • - - ... - - @@ -3582,7 +3456,7 @@ vim /home/centos/artwork/trunk/Translations/Fonts/dejavu_lgc_sans-boldoblique.se Directories trunk Scripts Directories trunk Scripts Functions - Directories trunk Manual + Directories trunk Identity Widgets Directories
The <file>trunk/Scripts</file> Directory