diff options
Diffstat (limited to 'gnome2-system-admin-guide/C')
-rw-r--r-- | gnome2-system-admin-guide/C/appendixa.xml | 231 | ||||
-rw-r--r-- | gnome2-system-admin-guide/C/gnome2.2-system-admin-guide.pdf | bin | 0 -> 569131 bytes | |||
-rw-r--r-- | gnome2-system-admin-guide/C/mimetypes.xml | 719 | ||||
-rw-r--r-- | gnome2-system-admin-guide/C/performance.xml | 591 | ||||
-rw-r--r-- | gnome2-system-admin-guide/C/screensavers.xml | 124 | ||||
-rw-r--r-- | gnome2-system-admin-guide/C/sessions.xml | 114 | ||||
-rw-r--r-- | gnome2-system-admin-guide/C/themes.xml | 236 |
7 files changed, 2015 insertions, 0 deletions
diff --git a/gnome2-system-admin-guide/C/appendixa.xml b/gnome2-system-admin-guide/C/appendixa.xml new file mode 100644 index 0000000..2ac858c --- /dev/null +++ b/gnome2-system-admin-guide/C/appendixa.xml @@ -0,0 +1,231 @@ +<?xml version="1.0" encoding="utf-8"?> + + <appendix id="appendixa-0"> + <title>Hidden Directories</title> + <highlights> + <para>This appendix describes the hidden directories that the +GNOME desktop adds to the home directories of users. </para> + </highlights> + <indexterm> + <primary>hidden directories</primary> + </indexterm> + <indexterm> + <primary>.* directories</primary> + <see>hidden directories</see> + </indexterm> + <para>A hidden +directory is a directory that has a name that begins with a period (.). <xref linkend="appendixa-TBL-2"/> describes the hidden directories that the GNOME +desktop adds to the home directories of users. </para> + <table frame="topbot" id="appendixa-TBL-2"> + <title>Hidden Directories in User Home Directories</title> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colname="colspec0" colwidth="50*"/> + <colspec colname="colspec1" colwidth="50*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Directory</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para> + <filename>.esd_auth</filename> + </para> + </entry> + <entry valign="top"> + <para>Contains the authentication cookie for the GNOME +sound daemon. The GNOME sound daemon is the Enlightened Sound Daemon (ESD).</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>.gconf</filename> + </para> + </entry> + <entry valign="top"> + <para>Contains the <application>GConf</application> configuration +source for the user. When the user sets a preference, the new preference information +is added to this location.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>.gconfd</filename> + </para> + </entry> + <entry valign="top"> + <para>Contains the following <application>GConf</application> +daemon details:</para> + <itemizedlist> + <listitem> + <para>Configuration information.</para> + </listitem> + <listitem> + <para>Lock information for objects that are referenced by an <firstterm>Interoperable Object Reference (IOR)</firstterm>.</para> + </listitem> + <listitem> + <para>State information for objects that are referenced by an IOR.</para> + </listitem> + </itemizedlist> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>.gnome</filename> + </para> + </entry> + <entry valign="top"> + <para>Contains user-specific application data that is +not stored in the <application>GConf</application> repository. For example, +this directory contains MIME type information and session information for +the user. </para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>.gnome-desktop</filename> + </para> + </entry> + <entry valign="top"> + <para>The <application>Nautilus</application> file manager +contains a preference that enables users to use <application>Nautilus</application> +to manage the desktop background. If the user selects this option, this directory +contains the objects that are on the <application>Nautilus</application> desktop +background of the user. This directory contains the following:</para> + <itemizedlist> + <listitem> + <para>Objects on the desktop background, for example, the <guilabel>Home</guilabel> object, the <guilabel>Trash</guilabel> object, and other launchers. +The objects appear in the directory as desktop entry files. For example, the <filename>starthere.desktop</filename> file contains a link to the <guilabel>Start Here</guilabel> location. </para> + </listitem> + <listitem> + <para>Removable media volumes that are mounted.</para> + </listitem> + </itemizedlist> + <para>The file manager also contains a preference that enables +users to use the home directory as the desktop background directory, instead +of <filename>.gnome-desktop</filename>. If a user selects this +option, the contents of the home directory are displayed as desktop background +objects.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>.gnome2</filename> + </para> + </entry> + <entry valign="top"> + <para>Contains user-specific application data that is +not stored in the <application>GConf</application> repository. For example, +this directory contains the following:</para> + <itemizedlist> + <listitem> + <para>Keyboard shortcut information.</para> + </listitem> + <listitem> + <para>Window location information.</para> + </listitem> + <listitem> + <para>Desktop entry files for panel launchers.</para> + </listitem> + </itemizedlist> + <para>This directory also contains user-specific menu data. +If a user modifies menus, the details are stored here.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>.gnome2-private</filename> + </para> + </entry> + <entry valign="top"> + <para>Ignore this directory. This directory has no function +at the time of publication of this guide.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>.metacity</filename> + </para> + </entry> + <entry valign="top"> + <para>Contains session data for the <application>Metacity</application> window manager.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>.nautilus</filename> + </para> + </entry> + <entry valign="top"> + <para>Contains file manager data that is specific to the +user. For example, this directory can contain the following: </para> + <itemizedlist> + <listitem> + <para>Metadata for the directories with which the user works.</para> + </listitem> + <listitem> + <para><application>Nautilus</application> themes that the user adds.</para> + </listitem> + <listitem> + <para><application>Nautilus</application> emblems that the user +adds.</para> + </listitem> + <listitem> + <para><application>Nautilus</application> desktop background images.</para> + </listitem> + </itemizedlist> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>.themes</filename> + </para> + </entry> + <entry valign="top"> + <para>Contains desktop themes and window frame themes +that the user adds. The user can add themes from the <application>Themes</application> +preference tool.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>.thumbnails</filename> + </para> + </entry> + <entry valign="top"> + <para>Contains image thumbnails for the user. The image +thumbnails are used in the file manager. The file manager contains a preference +that the user can select to stop generation of thumbnail images.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <filename>.xscreensaver</filename> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Contains +screensaver configuration data and screensaver preference data.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </appendix> diff --git a/gnome2-system-admin-guide/C/gnome2.2-system-admin-guide.pdf b/gnome2-system-admin-guide/C/gnome2.2-system-admin-guide.pdf Binary files differnew file mode 100644 index 0000000..58e896a --- /dev/null +++ b/gnome2-system-admin-guide/C/gnome2.2-system-admin-guide.pdf diff --git a/gnome2-system-admin-guide/C/mimetypes.xml b/gnome2-system-admin-guide/C/mimetypes.xml new file mode 100644 index 0000000..ac3ff2f --- /dev/null +++ b/gnome2-system-admin-guide/C/mimetypes.xml @@ -0,0 +1,719 @@ +<?xml version="1.0" encoding="utf-8"?> +<chapter id="mimetypes-0"> + <title>MIME Types</title> + <highlights> + <para>This chapter describes how applications detect MIME types, +how to register MIME types, and how to add applications to the GNOME desktop.</para> + </highlights> + <sect1 id="mimetypes-1"> + <title>Introduction</title> + <indexterm> + <primary>MIME types</primary> + <secondary>introduction</secondary> + </indexterm> + <para>A <firstterm>Multipurpose Internet Mail Extension</firstterm> +(MIME) type identifies the format of a file. The MIME type enables applications +to read the file. Applications such as Internet browsers and email applications +use the MIME type to handle files of different types. For example, an email +application can use the MIME type to detect what type of file is in a file +attached to an email.</para> + <para>In the GNOME desktop, the <application>Nautilus</application> file manager +uses MIME types to identify the type of a file. The file manager needs to +know the MIME type of a file to perform the following tasks:</para> + <itemizedlist> + <listitem> + <para>Open the file in an appropriate application.</para> + </listitem> + <listitem> + <para>Display a string that describes the type of file.</para> + </listitem> + <listitem> + <para>Display an appropriate icon to represent the file.</para> + </listitem> + <listitem> + <para>Display a list of other applications that can open the file.</para> + </listitem> + </itemizedlist> + <para>If you add a new application, you must ensure that other applications +can recognize the files associated with the application. You must perform +several tasks to enable other applications to detect the MIME type of the +application files.</para> + <para>This section describes how applications detect the MIME types of files, +and how applications are associated with MIME types. This chapter also describes +the procedure that you must follow to add a new application.</para> + </sect1> + <sect1 id="mimetypes-10"> + <title>Detecting the MIME Type for a File</title> + <indexterm> + <primary>MIME types</primary> + <secondary>detecting</secondary> + </indexterm> + <indexterm> + <primary>detecting MIME types</primary> + </indexterm> + <para>Applications can detect the MIME type of a file as follows:</para> + <orderedlist> + <listitem> + <para>The application uses <firstterm>file content sniffers</firstterm> +to search for a particular pattern in the file. A file content sniffer associates +a specific pattern in a file with a MIME type. If the application finds a +match for the pattern, the MIME type associated with the pattern is the MIME +type of the file.</para> + </listitem> + <listitem> + <para>If file content sniffers do not identify the MIME type, then +the application can check the filename. The application checks the filename +against the <firstterm>MIME type registry</firstterm>. The MIME type registry +associates particular filename extensions and filename patterns, with particular +MIME types. If a match for the filename is found, the MIME type associated +with the extension or pattern is the MIME type of the file.</para> + </listitem> + </orderedlist> + <para>The following sections provide further information on file content sniffers +and the MIME type registry.</para> + <sect2 id="mimetypes-2"> + <title>File Content Sniffers</title> + <indexterm> + <primary>MIME types</primary> + <secondary>file content sniffers</secondary> + </indexterm> + <indexterm> + <primary>file content sniffers</primary> + </indexterm> + <para>File content sniffers are specified in the file <filename>/usr/gnome/etc/gnome-vfs-mime-magic</filename>. The following is an example of a file content sniffer:</para> + <literallayout>0 string \x89PNG image/png</literallayout> + <para>The syntax for file content sniffers is as follows:</para> + <literallayout>offset_start[:offset_end] pattern_type pattern [&pattern_mask] type</literallayout> + <para><xref linkend="mimetypes-TBL-3"/> describes the fields in a file content +sniffer.</para> + <table frame="topbot" id="mimetypes-TBL-3"> + <title>Fields in a File Content Sniffer</title> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="29.90*"/> + <colspec colwidth="70.10*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Field</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para> + <literal>offset_start</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies the number of characters to ignore in +the file before searching for a text pattern.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>pattern_type</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies the type of pattern to search for. The <literal>string</literal> pattern type is the only pattern type that is supported at +the time of publication of this guide.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>pattern</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies the pattern to search for. </para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>pattern_mask</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies a <firstterm>pattern mask</firstterm>, +in hexadecimal format. For more information on pattern masks, see the next +section.</para> + <para>This field is optional. This field is not present in +the example.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>type</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies the MIME type to associate with files that match +this entry.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <sect3 id="mimetypes-12"> + <title>Pattern Masks</title> + <indexterm> + <primary>MIME types</primary> + <secondary>pattern mask</secondary> + </indexterm> + <indexterm> + <primary>pattern mask</primary> + </indexterm> + <para>A +pattern mask identifies bits in the pattern to ignore when searching for a +pattern in a file. The following is an example of a file content sniffer with +a pattern mask:</para> + <literallayout>0 string BMxxxx\000\000 &0xffff00000000ffff image/bmp</literallayout> + <para>The pattern and mask in the example are as follows:</para> + <informaltable frame="none"> + <tgroup cols="9" colsep="0" rowsep="0"> + <colspec colwidth="16.54*"/> + <colspec colwidth="10.21*"/> + <colspec colwidth="10.41*"/> + <colspec colwidth="10.21*"/> + <colspec colwidth="10.41*"/> + <colspec colwidth="10.21*"/> + <colspec colwidth="10.41*"/> + <colspec colwidth="10.21*"/> + <colspec colwidth="10.41*"/> + <tbody> + <row> + <entry valign="top"> + <para>Pattern</para> + </entry> + <entry valign="top"> + <para> + <literal>B</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>M</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>x</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>x</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>x</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>x</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>\000</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>\000</literal> + </para> + </entry> + </row> + <row> + <entry valign="top"> + <para>Mask</para> + </entry> + <entry valign="top"> + <para> + <literal>ff</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>ff</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>00</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>00</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>00</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>00</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>ff</literal> + </para> + </entry> + <entry valign="top"> + <para> + <literal>ff</literal> + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>The pattern and mask specify a file with the following characteristics:</para> + <orderedlist> + <listitem> + <para>The file begins with <literal>BM</literal>.</para> + </listitem> + <listitem> + <para><literal>BM</literal> is followed by four bytes with any values.</para> + </listitem> + <listitem> + <para>The four bytes are followed by <literal>\000\000</literal>.</para> + </listitem> + </orderedlist> + <para>The file content sniffer specifies that the MIME type of files that +match the pattern and mask is <literal>image/bmp</literal>.</para> + </sect3> + </sect2> + <sect2 id="mimetypes-4"> + <title>MIME Type Registry</title> + <indexterm> + <primary>MIME types</primary> + <secondary>MIME type registry</secondary> + </indexterm> + <para>The MIME type registry is located in <filename>/usr/gnome/share/mime-info</filename>. The MIME type registry contains the following files:</para> + <informaltable frame="topbot"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="50*"/> + <colspec colwidth="50*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>File</para> + </entry> + <entry valign="top"> + <para>Filename Extension</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para>MIME information file</para> + </entry> + <entry valign="top"> + <para> + <filename>.mime</filename> + </para> + </entry> + </row> + <row> + <entry valign="top"> + <para>MIME keys file</para> + </entry> + <entry valign="top"> + <para> + <filename>.keys</filename> + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>The following sections describe MIME information files and MIME keys +files.</para> + <sect3 id="mimetypes-5"> + <title>MIME Information Files</title> + <indexterm> + <primary>MIME types</primary> + <secondary>MIME information files</secondary> + </indexterm> + <para><firstterm>MIME information files</firstterm> +associate MIME types with one or both of the following:</para> + <itemizedlist> + <listitem> + <para>Filename extensions</para> + </listitem> + <listitem> + <para>Filename patterns</para> + </listitem> + </itemizedlist> + <para>When an application searches for the MIME type of a file, the application +checks the filename against the MIME information files. If a match for the +filename is found, the MIME type associated with the extension or pattern +is the MIME type of the file.</para> + <para>In MIME information files, the filename pattern to search for is written +as a regular expression.</para> + <para>The format of MIME type entries in MIME information files is as follows:</para> + <literallayout><replaceable>MIME_type</replaceable> + ext[,priority]: <replaceable>list_of_extensions</replaceable> + regex[,priority]: <replaceable>list_of_regular_expressions</replaceable></literallayout> + <para>You can specify a priority value for the filename extension and the +regular expression. You can use the priority value to differentiate composite +filenames. For example, you can assign a priority of <literal>1</literal> +to the <filename>.gz</filename> extension, and assign a higher priority of <literal>2</literal> to the <filename>.tar.gz</filename> extension. In this case, the +file <filename>abc.tar.gz</filename> takes the MIME type for <filename>.tar.gz</filename>.</para> + <note> + <para>You must indent the <literal>ext</literal> field and the <literal>regex</literal> field with a tab character (<literal>\t</literal>).</para> + </note> + <para>The following MIME type entries are samples from the <filename>gnome-vfs.mime</filename> MIME information file:</para> + <literallayout>application/x-compressed-tar + regex,2: tar\.gz$ + ext: tgz +audio/x-real-audio + ext: rm ra ram +image/jpeg + ext: jpe jpeg jpg +image/png + ext: png +text/html + ext: html htm HTML +text/plain + ext: asc txt TXT +text/x-readme + regex: README.*</literallayout> + <note> + <para>The file manager reads the MIME information files alphabetically. +The alphabetical order determines the order in which MIME types are assigned +to filename extensions or regular expressions. For example, if the same file +extension is assigned to different MIME types in the files <filename>abc.mime</filename> and <filename>def.mime</filename>, the MIME type in <filename>abc.mime</filename> is used.</para> + </note> + </sect3> + <sect3 id="mimetypes-11"> + <title>MIME Keys Files</title> + <indexterm> + <primary>MIME types</primary> + <secondary>MIME keys files</secondary> + </indexterm> + <para><firstterm>MIME keys file</firstterm> provide information +about a MIME type that is used in the user interface. For example, the MIME +keys file provides a description of a MIME type, and specifies an icon to +represent files of that MIME type.</para> + <para>The following is a sample from a MIME keys file:</para> + <literallayout>text/html + description=HTML page + icon_filename=gnome-text-html + default_action_type=application + short_list_application_ids_for_novice_user_level=mozilla,netscape,galeon + category=Documents/World Wide Web</literallayout> + <note> + <para>You must indent the keys in a MIME keys file with a tab character +(<literal>\t</literal>).</para> + </note> + <para><xref linkend="mimetypes-TBL-6"/> describes the most important keys in +MIME keys files. Typically, the <literal>description</literal> key and the <literal>category</literal> key are localized.</para> + <table frame="topbot" id="mimetypes-TBL-6"> + <title>Keys in MIME Keys Files</title> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colname="colspec0" colwidth="50*"/> + <colspec colname="colspec1" colwidth="50*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Key</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry colname="colspec0"> + <para> + <literal>can_be_executable</literal> + </para> + </entry> + <entry colname="colspec1"> + <para>Specifies whether files of this MIME type +can be executed.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>description</literal> + </para> + </entry> + <entry valign="top"> + <para>Describes the MIME type. This description can be +displayed in the file manager and other applications.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>icon_filename</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies the filename of an icon to represent the +MIME type. Does not specify the path to the filename, or the filename extension. </para> + <para>This icon can be displayed in the file manager and other applications.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>default_action_type</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies the category of action to take when a +file of this MIME type is opened by the user. Enter <literal>application</literal> +for this MIME type for most applications.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>short_list_application_ids</literal> + <literal>_for_novice_user_level</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies the application to use when a file of this MIME type is opened by +a user. Specify one or more applications, in order of priority. The applications +must also be registered in the application registry.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>category</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies a category for the MIME type. The value +of this key determines the location of the MIME type in the <application>File Types and Programs</application> preference tool.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </sect3> + </sect2> + </sect1> + <sect1 id="mimetypes-7"> + <title>Registering Applications for MIME Types</title> + <indexterm> + <primary>MIME types</primary> + <secondary>registering applications +for</secondary> + </indexterm> + <indexterm> + <primary>applications</primary> + <secondary>registry</secondary> + </indexterm> + <para>The <firstterm>application registry</firstterm> contains text files that register applications. The application +registration files contain a series of key-value pairs that specify details +for applications. For example, the application registration files contain +the following information:</para> + <itemizedlist> + <listitem> + <para>The command to use to start the application.</para> + </listitem> + <listitem> + <para>MIME types to associate with the application.</para> + </listitem> + </itemizedlist> + <para>An application registration file can contain one or more application +registrations. Application registration files have a <filename>.applications</filename> extension.</para> + <para>The location of the application registry is <filename>/usr/share/gnome/application-registry</filename>. This directory contains a default application registration file +that is called <filename>gnome-vfs.applications</filename>.</para> + <para>To register an application, add a registration file for the application +to the application registry. </para> + <para>The following is an example of an application registration:</para> + <literallayout>eog + command=eog + name=Eye of Gnome + can_open_multiple_files=true + expects_uris=false + requires_terminal=false + mime_types=image/bmp,image/gif,image/jpeg,image/png,image/tiff, +image/x-xpixmap,image/x-bmp,image/x-png,image/x-portable-anymap, +image/x-portable-bitmap,image/x-portable-graymap, +image/x-portable-pixmap</literallayout> + <para><xref linkend="mimetypes-TBL-8"/> describes the keys in application registration +files.</para> + <table frame="topbot" id="mimetypes-TBL-8"> + <title>Keys for an Application Registration</title> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colname="colspec0" colwidth="50*"/> + <colspec colname="colspec1" colwidth="50*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Key</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para>Application identifier</para> + </entry> + <entry valign="top"> + <para>Specifies a unique identifier for the application. This +identifier must be the same as the identifier in the short_list_application_ids_for_novice_user_level +key in the MIME keys file for the application.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>command</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies the command to use to start the application, +and any options to use with the command.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>name</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies a name for the application. The name is used +in the user interface. For example, the name is used in the <guimenu>Open +With</guimenu> submenu in the file manager.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>can_open_multiple_files</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies whether the application can open several +files at the same time.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>expects_uris</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies whether the application can process URIs. +If the value of this key is <literal>true</literal>, the application registration +entry must also contain a <literal>supported_uri_schemes</literal> key.</para> + </entry> + </row> + <row> + <entry colname="colspec0" valign="top"> + <para> + <literal>supported_uri_schemes</literal> + </para> + </entry> + <entry colname="colspec1" valign="top"> + <para>Specifies +the URI schemes that the application can process.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>requires_terminal</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies whether to run the application in a terminal +window. Enter <literal>true</literal> for this field for an application that +does not create a window in which to run.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>mime_types</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies the MIME types that the application can +use.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </sect1> + <sect1 id="mimetypes-9"> + <title>Adding an Application to the GNOME Desktop</title> + <indexterm> + <primary>MIME types</primary> + <secondary>adding applications</secondary> + </indexterm> + <indexterm> + <primary>applications</primary> + <secondary>adding</secondary> + </indexterm> + <para>To add an application to the GNOME desktop, perform the +following steps:</para> + <orderedlist> + <listitem> + <para>Add a menu item for the application. For more information +on how to add an item to a menu, see <xref linkend="menustructure-0"/>.</para> + </listitem> + <listitem> + <para>Add an icon for the application to <filename>/usr/gnome/share/icons/<replaceable>theme_name</replaceable>/<replaceable>icon_size</replaceable>/apps</filename>. +For more information on icons and themes, see <citetitle>Installing Themes</citetitle>. </para> + </listitem> + <listitem> + <para>If the application uses a new MIME type, add a file content +sniffer for the new MIME type. For more information on file content sniffers, +see <xref linkend="mimetypes-2"/>.</para> + </listitem> + <listitem> + <para>If the application uses a new MIME type, add a MIME information +file for the application to the MIME type registry. For more information on +MIME information files, see <xref linkend="mimetypes-5"/>.</para> + </listitem> + <listitem> + <para>Add a MIME keys file for the application to the MIME type +registry. For more information on MIME keys files, see <xref linkend="mimetypes-11"/>.</para> + </listitem> + <listitem> + <para>If the application uses a new MIME type, add an icon for the +MIME type to <filename>/usr/gnome/share/icons/<replaceable>theme_name</replaceable>/<replaceable>icon_size</replaceable>/mimetypes</filename>. For more information on icons +and themes, see <citetitle>Installing Themes</citetitle>. </para> + </listitem> + <listitem> + <para>To associate the application with a MIME type, add an application +registration file to the application registry. For more information on the +application registry, see <xref linkend="mimetypes-7"/>.</para> + </listitem> + </orderedlist> + </sect1> +</chapter> diff --git a/gnome2-system-admin-guide/C/performance.xml b/gnome2-system-admin-guide/C/performance.xml new file mode 100644 index 0000000..4d98630 --- /dev/null +++ b/gnome2-system-admin-guide/C/performance.xml @@ -0,0 +1,591 @@ +<?xml version="1.0" encoding="utf-8"?> +<chapter id="performance-0"> + <title>Improving Performance</title> + <highlights> + <para>This chapter describes how to improve the performance of +the GNOME desktop. </para> + </highlights> + <sect1 id="performance-1"> + <title>Introduction</title> + <indexterm> + <primary>performance, improving</primary> + <secondary>introduction</secondary> + </indexterm> + <para>This chapter lists several preferences whose +settings you can change to improve the performance of the GNOME desktop. You +can use the <command>gconftool-2</command> command to set values for preferences +for users. The example commands in this chapter show how to set values in +the user configuration source. </para> + <para>You can also use the <literal>--direct</literal> and <literal>--config-source</literal> options to set mandatory values or default values for preferences. +You can also use the <command>gconftool-2</command> command in a script to +set the values of many preferences. For more information on the <command>gconftool-2</command> command and the options that are available with the +command, see <citetitle>Using GConf</citetitle>.</para> + </sect1> + <sect1 id="performance-8"> + <title>Reducing CPU Usage</title> + <indexterm> + <primary>performance, improving</primary> + <secondary>reducing CPU +usage</secondary> + </indexterm> + <indexterm> + <primary>reducing</primary> + <secondary>CPU usage</secondary> + </indexterm> + <indexterm> + <primary>CPU usage</primary> + <secondary>reducing</secondary> + </indexterm> + <para>This section describes preferences that +you can set to reduce CPU usage by the GNOME desktop. </para> + <sect2 id="performance-3"> + <title>To Use Themes Which Require Less CPU Resources</title> + <indexterm> + <primary>themes</primary> + <secondary>and CPU usage</secondary> + </indexterm> + <para>Some window frame themes load image files to draw the window frame. +Other themes use simpler techniques to draw the window frame.</para> + <para>The default theme is Crux. Crux loads image files, and can be slow on +systems with limited CPU resources. To reduce CPU usage, use one of the following +window frame themes: </para> + <itemizedlist> + <listitem> + <para>Atlanta</para> + </listitem> + <listitem> + <para>Esco</para> + </listitem> + </itemizedlist> + <para>The following window frame themes also use less CPU resources than Crux:</para> + <itemizedlist> + <listitem> + <para>AgingGorilla</para> + </listitem> + <listitem> + <para>Bright</para> + </listitem> + <listitem> + <para>Metabox</para> + </listitem> + </itemizedlist> + <note> + <para>Metabox does not work well with inverse desktop themes such as +HighContrastInverse. Use Atlanta with inverse desktop themes.</para> + </note> + <indexterm> + <primary>themes</primary> + <secondary>changing</secondary> + </indexterm> + <para>To change the window frame theme, run the following command: </para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type string +--set /apps/metacity/general/theme <replaceable>theme_name</replaceable></userinput></para> + <para>For example, to use Atlanta, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type string +--set /apps/metacity/general/theme Atlanta</userinput></para> + <para>Alternatively, users can choose <menuchoice><guimenu>Applications</guimenu><guisubmenu>Desktop Preferences</guisubmenu><guimenuitem>Themes</guimenuitem></menuchoice>, then select the appropriate theme.</para> + <tip> + <para>You can use the <application>Metacity Theme Viewer</application> +to measure the performance of a window frame theme, and to preview the theme. +To start <application>Metacity Theme Viewer</application>, use the following +command:</para> + <para><computeroutput>#</computeroutput> <userinput>metacity-theme-viewer <replaceable>theme_name</replaceable></userinput></para> + <para>For example, to measure the performance of Atlanta and preview Atlanta, +run the following command: </para> + <para><computeroutput>#</computeroutput> <userinput>metacity-theme-viewer +Atlanta</userinput></para> + </tip> + </sect2> + <sect2 id="performance-2"> + <title>To Reduce CPU Usage by Turning Off Display of Icons in Menus</title> + <indexterm> + <primary>icons, in menus</primary> + <see>menu icons</see> + </indexterm> + <indexterm> + <primary>menu icons</primary> + <secondary>and CPU usage</secondary> + </indexterm> + <para>Some items in menus display an icon beside the item. To +turn off this feature, run the following command: </para> + <indexterm> + <primary>menu icons</primary> + <secondary>turning off</secondary> + </indexterm> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 +--type bool --set /desktop/gnome/interface/menus_have_icons false</userinput></para> + <para>Alternatively, users can choose <menuchoice><guimenu>Applications</guimenu><guisubmenu>Desktop Preferences</guisubmenu><guimenuitem>Menus & Toolbars</guimenuitem></menuchoice>, then deselect the <guilabel>Show icons in menus</guilabel> option.</para> + </sect2> + <sect2 id="performance-5"> + <title>To Reduce CPU Usage by Turning On Wireframe Mode</title> + <indexterm> + <primary>wireframe mode</primary> + <secondary>and CPU usage</secondary> + </indexterm> + <para>The Metacity window manager has a wireframe mode for when +you move and resize windows. When wireframe mode is turned on, only the outline +of windows is displayed when you move and resize windows. The contents of +the window do not need to be updated during the move or resize. The contents +of the window are displayed when the move or resize is complete.</para> + <indexterm> + <primary>wireframe mode</primary> + <secondary>turning on</secondary> + </indexterm> + <para>To turn on wireframe mode, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type bool +--set /apps/metacity/general/wireframe_move_resize true</userinput></para> + </sect2> + <sect2 id="performance-6"> + <title>To Reduce CPU Usage by Turning Off the Splash Screen</title> + <indexterm> + <primary>splash screen</primary> + <secondary>and CPU usage</secondary> + </indexterm> + <para>By default, when users log in to the GNOME desktop, a splash +screen is displayed. Icons are displayed on the splash screen while the user +logs in. You can turn off the splash screen to reduce CPU usage during login. </para> + <indexterm> + <primary>splash screen</primary> + <secondary>turning off</secondary> + </indexterm> + <para>To turn off the splash screen, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type bool +--set /apps/gnome-session/options/show_splash_screen false</userinput></para> + <para>Alternatively, users can choose <menuchoice><guimenu>Applications</guimenu><guisubmenu>Desktop Preferences</guisubmenu><guisubmenu>Advanced</guisubmenu><guimenuitem>Sessions</guimenuitem></menuchoice>, +then deselect the <guilabel>Show splash screen on login</guilabel> option.</para> + </sect2> + <sect2 id="performance-4"> + <title>To Reduce CPU Usage by Turning Off Panel Animation</title> + <indexterm> + <primary>panels</primary> + <secondary>animation, turning off</secondary> + </indexterm> + <para>When users show or hide panels, the panels can show or hide +in an animated style. To turn off panel animation, run the following command: </para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type bool +--set /apps/panel/global/enable_animations false</userinput></para> + <para>Alternatively, users can choose <menuchoice><guimenu>Applications</guimenu><guisubmenu>Desktop Preferences</guisubmenu><guisubmenu>Advanced</guisubmenu><guimenuitem>Themes</guimenuitem></menuchoice>, +then deselect the <guilabel>Animation</guilabel> option.</para> + </sect2> + <sect2 id="performance-7"> + <title>Improving File Manager Performance</title> + <indexterm> + <primary>Nautilus</primary> + <see>file manager</see> + </indexterm> + <para>The <application>Nautilus</application> file manager includes some features +that you can modify to improve performance.</para> + <sect3 id="performance-9"> + <title>To Modify Performance Preferences</title> + <indexterm> + <primary>file manager</primary> + <secondary>modifying performance +preferences</secondary> + </indexterm> + <para>The file manager includes performance-related +preferences. Each performance preference can take one of three values. The +values are described in the following table:</para> + <informaltable frame="topbot"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="34.46*"/> + <colspec colwidth="65.54*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Value</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para> + <literal>always</literal> + </para> + </entry> + <entry> + <para>Performs +the action for both local files, and files on other file systems.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>local_only</literal> + </para> + </entry> + <entry valign="top"> + <para>Performs the action for local files only. When you +set a performance preference to <literal>local_only</literal>, the CPU usage +is reduced.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>never</literal> + </para> + </entry> + <entry valign="top"> + <para>Never performs the action. When you set a performance preference +to never, the CPU usage and the network traffic are reduced.</para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>The following table describes the performance preferences for the file +manager. For the fastest performance, set the value of the preferences to <literal>never</literal>.</para> + <informaltable frame="topbot"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="43.34*"/> + <colspec colwidth="56.66*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Preference</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para> + <literal>show_icon_text</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies when to preview the content of text files +in the icon that represents the file. To never preview the content of text +files, run the following command: </para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type string --set /apps/nautilus/preferences/show_icon_text +never</userinput></para> + <para>Alternatively, users can perform the following +steps:</para> + <orderedlist> + <listitem> + <para>Choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window, then choose <guilabel>Performance</guilabel>.</para> + </listitem> + <listitem> + <para>Select an option for the <guilabel>Show Text in Icons</guilabel> +preference.</para> + </listitem> + </orderedlist> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>show_directory_item_counts</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies when to show the number of items in folders. +To never show the number of items in folders, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type string --set /apps/nautilus/preferences/show_directory_item_counts +never </userinput></para> + <para>Alternatively, users can perform the following +steps:</para> + <orderedlist> + <listitem> + <para>Choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window, then choose <guilabel>Performance</guilabel>.</para> + </listitem> + <listitem> + <para>Select an option for the <guilabel>Show Number of Items in +Folders</guilabel> preference.</para> + </listitem> + </orderedlist> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>show_image_thumbnails</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies when to show thumbnails of image files. +To never show thumbnails, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type string --set /apps/nautilus/preferences/show_image_thumbnails +never </userinput></para> + <para>Alternatively, users can perform the following +steps:</para> + <orderedlist> + <listitem> + <para>Choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window, then choose <guilabel>Performance</guilabel>.</para> + </listitem> + <listitem> + <para>Select an option for the <guilabel>Show Thumbnails for Image +Files</guilabel> preference.</para> + </listitem> + </orderedlist> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <literal>preview_sound</literal> + </para> + </entry> + <entry valign="top"> + <para>Specifies when to preview the content of sound files. +To never preview the content of sound files, run the following command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type string --set /apps/nautilus/preferences/preview_sound +never </userinput></para> + <para>Alternatively, users can perform the following +steps:</para> + <orderedlist> + <listitem> + <para>Choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window, then choose <guilabel>Performance</guilabel>.</para> + </listitem> + <listitem> + <para>Select an option for the <guilabel>Preview Sound Files</guilabel> +preference.</para> + </listitem> + </orderedlist> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + </sect3> + <sect3 id="performance-10"> + <title>To Turn Off the Side Pane, Toolbar, and Location Bar</title> + <indexterm> + <primary>file manager</primary> + <secondary>side pane, turning off</secondary> + </indexterm> + <para>The file manager includes preferences that enable +you to turn off the side pane and the toolbar. To improve file manager performance, +turn off the side pane and the toolbar.</para> + <para>To turn off the side pane, run the following command: </para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type bool +--set /apps/nautilus/preferences/start_with_sidebar false</userinput></para> + <para>Alternatively, users can choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window, +then choose <guilabel>Windows</guilabel>, and then deselect the <guilabel>Display side pane</guilabel> option. The next time that users open a file +manager window, the window does not display a side pane. </para> + <indexterm> + <primary>file manager</primary> + <secondary>toolbar, turning off</secondary> + </indexterm> + <para>To turn off the toolbar, run the following command: </para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type bool +--set /apps/nautilus/preferences/start_with_toolbar false</userinput></para> + <para>Alternatively, users can choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window, +then choose <guilabel>Windows</guilabel>, and then deselect the <guilabel>Display toolbar</guilabel> option. The next time that users open a file manager +window, the window does not display a toolbar. </para> + <para>You can also turn off the location bar. Users can use the <keycombo><keycap>Ctrl</keycap><keycap>L</keycap></keycombo> keyboard shortcut to display a location bar +when required. </para> + <indexterm> + <primary>file manager</primary> + <secondary>location bar, turning +off</secondary> + </indexterm> + <para>To turn off the location bar, run the following +command:</para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type bool +--set /apps/nautilus/preferences/start_with_location_bar false</userinput></para> + <para>Alternatively, users can choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window, +then choose <guilabel>Windows</guilabel>, and then deselect the <guilabel>Display location bar</guilabel> option. The next time that users open a file +manager window, the window does not display a location bar.</para> + </sect3> + <sect3 id="performance-11"> + <title>To Turn Off the Desktop Background</title> + <indexterm> + <primary>file manager</primary> + <secondary>desktop background, turning +off</secondary> + </indexterm> + <indexterm> + <primary>desktop background</primary> + <secondary>turning off</secondary> + </indexterm> + <para>The file manager contains +a preference that enables users to use <application>Nautilus</application> +to manage the desktop background. Users can disable the desktop background +to improve performance. However, if users disable the desktop background, +users cannot do the following:</para> + <itemizedlist> + <listitem> + <para>Use the <guimenu>Desktop Background</guimenu> menu.</para> + </listitem> + <listitem> + <para>Use the file manager to change the pattern or color of the +desktop background. </para> + </listitem> + <listitem> + <para>Use the <guilabel>Home</guilabel> object and the <guilabel>Trash</guilabel> object. The <guilabel>Home</guilabel> object and the <guilabel>Trash</guilabel> object are not displayed on the desktop. </para> + </listitem> + </itemizedlist> + <para>To disable the desktop background, run the following command: </para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type bool +--set /apps/nautilus/preferences/show_desktop false</userinput></para> + <para>Alternatively, users can choose <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> from a file manager window. +Users can then choose <guilabel>Desktop & Trash</guilabel>, and then deselect +the <guilabel>Use Nautilus to draw the desktop</guilabel> option. </para> + </sect3> + </sect2> + </sect1> + <sect1 id="performance-12"> + <title>Reducing X11 Network Traffic</title> + <indexterm> + <primary>reducing</primary> + <secondary>X11 network traffic</secondary> + </indexterm> + <indexterm> + <primary>X11 network traffic, reducing</primary> + </indexterm> + <indexterm> + <primary>network traffic, reducing</primary> + </indexterm> + <para>This section describes preferences that you can set to reduce X11 network +traffic on the GNOME desktop. </para> + <sect2 id="performance-14"> + <title>To Use Themes Which Create Less Network Traffic</title> + <indexterm> + <primary>themes</primary> + <secondary>and network traffic</secondary> + </indexterm> + <para>Remote display protocols do not transfer every pixel in +a block of pixels if all pixels in the block are the same color.</para> + <para>To reduce X11 network traffic, use a window frame theme that uses solid +colors. That is, use one of the following window frame themes:</para> + <itemizedlist> + <listitem> + <para>Atlanta</para> + </listitem> + <listitem> + <para>Esco</para> + </listitem> + </itemizedlist> + <para>For information on how to change the theme, see <xref linkend="performance-3"/>.</para> + </sect2> + <sect2 id="performance-15"> + <title>To Reduce Network Traffic by Turning Off Display of Icons in Menus</title> + <indexterm> + <primary>menu icons</primary> + <secondary>and network traffic</secondary> + </indexterm> + <para>Some items in menus display an icon beside the item. If +the icon is located on another file system, this feature can increase X11 +network traffic. This feature can also increase X11 network traffic if the +panels are displayed on a remote host. </para> + <para>For information on how to turn off this feature, see <xref linkend="performance-2"/>.</para> + </sect2> + <sect2 id="performance-13"> + <title>To Reduce Network Traffic by Turning On Wireframe Mode</title> + <indexterm> + <primary>wireframe mode</primary> + <secondary>and network traffic</secondary> + </indexterm> + <para>If the application that displays the window +is running on a remote host, wireframe mode reduces X11 network traffic.</para> + <para>For more information on wireframe mode, see <xref linkend="performance-5"/>.</para> + </sect2> + </sect1> + <sect1 id="performance-17"> + <title>Reducing Color Usage and Improving Display Quality</title> + <indexterm> + <primary>reducing</primary> + <secondary>color usage</secondary> + </indexterm> + <indexterm> + <primary>color usage</primary> + <secondary>reducing</secondary> + </indexterm> + <indexterm> + <primary>display quality, improving</primary> + </indexterm> + <para>Many modern computer systems support 24-bit color, that is, 16,777,216 colors. +However, many users still use systems that support 8-bit color, that is, 256 +colors. </para> + <para>The GNOME desktop uses the <firstterm>Netscape color palette</firstterm>. +This palette is a general-purpose palette of 216 colors, which is designed +to optimize the use of color on systems that support 8-bit color. However, +some visual components of the GNOME desktop are designed for systems that +support 24-bit color.</para> + <para>The following display problems might occur on systems that support 8-bit +color:</para> + <itemizedlist> + <listitem> + <para>Windows, icons, and background images might appear grainy. + Many themes, background images, and icons use colors that are not in the <application>Netscape</application> color palette. The colors that are not in the palette +are replaced with the nearest equivalent or a dithered approximation. This +use of replacement colors causes the grainy appearance.</para> + </listitem> + <listitem> + <para>Applications that do not use the <application>Netscape</application> +color palette have less colors available. Color errors might occur. Some colors +might not appear in the user interface of the application. Some applications +might crash if the application cannot allocate colors.</para> + </listitem> + <listitem> + <para>Color flashing might occur when users switch between applications +that use the <application>Netscape</application> color palette, and applications +that do not use this palette. The applications that do not use the <application>Netscape</application> color palette might use a custom colormap. When the +custom colormap is used, other visual components might lose colors, then become +unviewable.</para> + </listitem> + </itemizedlist> + <para>The following sections describe how to optimize the appearance of the +GNOME desktop for systems that support 8-bit color. </para> + <sect2 id="performance-20"> + <title>To Use Themes That Use the Netscape Color Palette</title> + <indexterm> + <primary>themes</primary> + <secondary>and color usage</secondary> + </indexterm> + <para>Some window frame themes use colors that are in the Netscape +color palette. Bright and Esco use colors from the Netscape color palette. +Bright and Esco do not have the grainy appearance of other themes on 8-bit +color displays. Use Bright or Esco for the best color display on 8-bit visual +modes. </para> + <para>For information on how to change the theme, see <xref linkend="performance-3"/>.</para> + </sect2> + <sect2 id="performance-21"> + <title>To Reduce Color Usage by Turning Off Display of Icons in Menus</title> + <indexterm> + <primary>menu icons</primary> + <secondary>and color usage</secondary> + </indexterm> + <para>Some items in menus display an icon beside the item. If +the icon contains colors that are not in the <application>Netscape</application> +color palette, this feature can increase the number of colors used.</para> + <para>For information on how to turn off this feature, see <xref linkend="performance-2"/>.</para> + </sect2> + <sect2 id="performance-18"> + <title>To Reduce Color Usage by Turning Off the Splash Screen</title> + <indexterm> + <primary>splash screen</primary> + <secondary>and color usage</secondary> + </indexterm> + <para>You can turn off the splash screen to make more colors available +for the GNOME desktop and applications.</para> + <para>For information on how to turn off the splash screen, see <xref linkend="performance-6"/>.</para> + </sect2> + <sect2 id="performance-19"> + <title>To Reduce Color Usage by Using a Solid Color for the Desktop Background</title> + <indexterm> + <primary>desktop background</primary> + <secondary>using solid color</secondary> + </indexterm> + <para>Use a solid color for the desktop background. +Use of a solid color reduces the number of colors used by the GNOME desktop. </para> + <para>To set a solid color for the desktop background, run the following commands: </para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type string +--set /desktop/gnome/background/picture_options none</userinput></para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type string +--set /desktop/gnome/background/color_shading_type solid</userinput></para> + <para><computeroutput>#</computeroutput> <userinput>gconftool-2 --type string +--set /desktop/gnome/background/primary_color \#<replaceable>hexadecimal_color</replaceable></userinput></para> + <para>Alternatively, users can choose <menuchoice><guimenu>Applications</guimenu><guisubmenu>Desktop Preferences</guisubmenu><guimenuitem>Background</guimenuitem></menuchoice>, then choose a solid color for the desktop +background.</para> + </sect2> + </sect1> +</chapter> diff --git a/gnome2-system-admin-guide/C/screensavers.xml b/gnome2-system-admin-guide/C/screensavers.xml new file mode 100644 index 0000000..53ed1f0 --- /dev/null +++ b/gnome2-system-admin-guide/C/screensavers.xml @@ -0,0 +1,124 @@ +<?xml version="1.0" encoding="utf-8"?> +<chapter id="screensavers-0"> + <title>Setting Screensavers</title> + <highlights> + <para>This chapter describes how to set preferences for the screensaver. +This chapter also provides information on how to modify the displays that +are available for the screensaver.</para> + </highlights> + <sect1 id="screensavers-1"> + <title>Introduction</title> + <indexterm> + <primary>screensavers</primary> + <secondary>introduction</secondary> + </indexterm> + <indexterm> + <primary>XScreenSaver</primary> + <see>screensavers</see> + </indexterm> + <para>A <firstterm>screensaver</firstterm> is an application that +replaces the image on a screen when the screen is not in use. The screensaver +application for the GNOME desktop is <application>XScreenSaver</application>. +The following sections describe how to set preferences for the <application>XScreenSaver</application> application, and how to modify the displays that +are available for the screensaver.</para> + <note> + <para>The <application>XScreenSaver</application> application does not +allow you to lock your screen if you are logged in as <literal>root</literal>. +If you want to be able to lock your screen, log in as a normal user. To obtain +system administrator privileges, open a terminal window, then use the <command>su</command> command to log in as <literal>root</literal>.</para> + </note> + </sect1> + <sect1 id="screensavers-2"> + <title>Setting Screensaver Preferences</title> + <indexterm> + <primary>screensavers</primary> + <secondary>setting preferences</secondary> + </indexterm> + <para>Default screensaver preferences are stored in a file that +is called <filename>XScreenSaver</filename>. This file is stored in different +locations, depending on the platform, as follows:</para> + <informaltable frame="topbot"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="43.76*"/> + <colspec colwidth="56.24*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>Platform</para> + </entry> + <entry valign="top"> + <para>File Location</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para>RedHat Linux</para> + </entry> + <entry valign="top"> + <para> + <filename>/usr/X11R6/lib/X11/app-defaults/XScreenSaver</filename> + </para> + </entry> + </row> + <row> + <entry valign="top"> + <para>Solaris Operating Environment</para> + </entry> + <entry valign="top"> + <para> + <filename>/usr/openwin/lib/app-defaults/XScreenSaver</filename> + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>To modify screensaver application preferences, users can right-click +on the <guibutton>Lock</guibutton> button, then choose <guimenuitem>Properties</guimenuitem>. The user can then modify preferences in the <guilabel>XScreenSaver</guilabel> dialog. When a user modifies the screensaver preferences, the +preferences are stored in the home directory of the user, in the <filename>$HOME/.xscreensaver</filename> file. For information on screensaver preferences, +see <citetitle>GNOME 2.2 Desktop User Guide</citetitle>.</para> + <para>Users can also run the command <command>/usr/X11R6/bin/xscreensaver-demo</command> to open the <guilabel>XScreenSaver</guilabel> dialog.</para> + <para>To set default screensaver preferences for all users, modify the <filename>XScreenSaver</filename> file. You can also use the <guilabel>XScreenSaver</guilabel> dialog to create a <filename>$HOME/.xscreensaver</filename> file, +then copy the file to the location of the <filename>XScreenSaver</filename> +file.</para> + <para>To restore the default settings for a user, delete the <filename>$HOME/.xscreensaver</filename> file from the home directory of the user. If no <filename>$HOME/.xscreensaver</filename> file is present, the default preferences in the <filename>XScreenSaver</filename> file are used. </para> + <note> + <para>The default display behavior of <application>XScreenSaver</application> +is to display a blank screen. The blank screen might confuse users. You might +want to change this default display behavior.</para> + </note> + <para>To activate changes to the screensaver preferences, use the following +command to reload screensaver preferences:</para> + <para><computeroutput>#</computeroutput> <userinput>xscreensaver-command -restart</userinput></para> + <note> + <para>The <application>xset</application> application does not work +with <application>XScreenSaver</application> at the time of publication of +this guide. To modify screensaver preferences, modify the <filename>XScreenSaver</filename> file or the <filename>$HOME/.xscreensaver</filename> file. </para> + </note> + </sect1> + <sect1 id="screensavers-3"> + <title>Modifying Screensaver Displays</title> + <indexterm> + <primary>screensavers</primary> + <secondary>modifying screensaver +displays</secondary> + </indexterm> + <para>The screensaver application allows users +to choose one or more <firstterm>screensaver displays</firstterm>. A screensaver +display is an application that displays images on the screen of the user when +the screen is not in use. The screensaver displays are listed in the <filename>XScreenSaver</filename> file and in the <filename>$HOME/.xscreensaver</filename> +file. </para> + <para>To add a new screensaver display, copy the executable file for the display +to the <filename>/usr/X11R6/lib/xscreensaver/hacks</filename> directory. Add +the command for the screensaver display to the <filename>XScreenSaver</filename> file or the <filename>$HOME/.xscreensaver</filename> file. Include +any arguments that are required to run the screensaver display on the whole +desktop, rather than in a window. For example, you might want to include the <literal>-root</literal> option to display the screensaver display on the desktop.</para> + <para>To disable a screensaver display, add +a minus sign (-) at the start of the command for the screensaver display in +the preferences file. The following excerpt from a <filename>$HOME/.xscreensaver</filename> file shows a disabled <literal>Qix (solid)</literal> screensaver +display:</para> + <literallayout>- "Qix (solid)" qix -root -solid -segments 100</literallayout> + </sect1> +</chapter> diff --git a/gnome2-system-admin-guide/C/sessions.xml b/gnome2-system-admin-guide/C/sessions.xml new file mode 100644 index 0000000..01b19eb --- /dev/null +++ b/gnome2-system-admin-guide/C/sessions.xml @@ -0,0 +1,114 @@ +<?xml version="1.0" encoding="utf-8"?> +<chapter id="sessions-0"> + <title>Session Management</title> + <highlights> + <para>This chapter introduces session management, and describes +how to set session defaults. The chapter also contains information on sessions +and login scripts.</para> + </highlights> + <sect1 id="sessions-1"> + <title>Introduction</title> + <indexterm> + <primary>sessions</primary> + <secondary>introduction</secondary> + </indexterm> + <para>A GNOME desktop session occurs between the time that a user +logs in to the GNOME desktop and the time that the user logs out. The session +manager starts after the <application>Login Manager</application> authenticates +the user. The session manager enables the user to manage the session. For +example, a user can save the state of a session and return to that session +the next time that the user logs in. </para> + <para>At a minimum, the following applications run in a session:</para> + <itemizedlist> + <listitem> + <para>The session manager, <command>gnome-session</command>.</para> + </listitem> + <listitem> + <para>The <application>GConf</application> X settings daemon, <command>gnome-settings-daemon</command>.</para> + </listitem> + <listitem> + <para>The <application>gnome-panel</application> application, which +runs the panels on the GNOME desktop.</para> + </listitem> + <listitem> + <para>The <application>Metacity</application> window manager.</para> + </listitem> + </itemizedlist> + </sect1> + <sect1 id="sessions-3"> + <title>Setting Session Defaults</title> + <indexterm> + <primary>sessions</primary> + <secondary>setting defaults</secondary> + </indexterm> + <para>The following table lists the files that contain default +session information:</para> + <informaltable frame="topbot"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="51.80*"/> + <colspec colwidth="48.20*"/> + <thead> + <row rowsep="1"> + <entry valign="top"> + <para>File</para> + </entry> + <entry valign="top"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry valign="top"> + <para> + <filename>/usr/share/gnome/default.session</filename> + </para> + </entry> + <entry valign="top"> + <para>Default session file. +Default session details are stored in this file.</para> + </entry> + </row> + <row> + <entry valign="top"> + <para> + <filename>$HOME/.gnome2/session</filename> + </para> + </entry> + <entry valign="top"> + <para>User session file. When a user modifies the session, +the details are stored in this file.</para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>To set default session details for all users, modify the default session +file. </para> + <para>To restore the default session settings for a user, delete the session +file from the home directory of the user. If no user session file is present, +the default settings in <filename>/usr/share/gnome/default.session</filename> +are used. </para> + <para>To save the current session as the default session, users can run the <command>gnome-session-save</command> command. </para> + </sect1> + <sect1 id="sessions-2"> + <title>Login Scripts</title> + <indexterm> + <primary>sessions</primary> + <secondary>login scripts</secondary> + </indexterm> + <para>The GNOME desktop does not support system-wide login scripts +or logout scripts. The session manager only allows users to configure user +sessions. Users can configure non-session-managed startup applications with +the <application>Sessions</application> preference tool.</para> + <tip> + <para>You can work around the lack of support for system-wide login scripts. +To create a system-wide login script, create the script in the <filename>/usr/dt/config/Xsession.d</filename> directory. Name the script as follows:</para> + <para> + <filename><replaceable>number_greater_than_1000</replaceable>.<replaceable>name</replaceable></filename> + </para> + <para>For example, name the script <filename>1050.login</filename>. For more +information on the <filename>/usr/dt/config/Xsession.d</filename> file, see <citetitle>The XSession File</citetitle> in the <citerefentry><refentrytitle>dtlogin</refentrytitle><manvolnum>1</manvolnum></citerefentry> man page.</para> + </tip> + </sect1> +</chapter> diff --git a/gnome2-system-admin-guide/C/themes.xml b/gnome2-system-admin-guide/C/themes.xml new file mode 100644 index 0000000..1384d8d --- /dev/null +++ b/gnome2-system-admin-guide/C/themes.xml @@ -0,0 +1,236 @@ +<?xml version="1.0" encoding="utf-8"?> +<chapter id="themes-0"> + <title>Installing Themes</title> + <highlights> + <para>This chapter describes the types of theme that are available +in the GNOME desktop, how to install themes, and how to create a custom theme.</para> + </highlights> + <sect1 id="themes-1"> + <title>Introduction</title> + <indexterm> + <primary>themes</primary> + <secondary>introduction</secondary> + </indexterm> + <para>A theme is a group of coordinated settings that specifies the visual +appearance of a part of the GNOME desktop. Users can choose themes to change +the appearance of the desktop. </para> + <para>The following types of theme affect different parts of the GNOME desktop:</para> + <variablelist> + <varlistentry> + <term>Desktop themes</term> + <listitem> + <indexterm> + <primary>desktop +themes</primary> + <see>themes</see> + </indexterm> + <para>Desktop themes determine +the visual appearance of windows, panels, and applets. Desktop themes also +determine the visual appearance of the GNOME-compliant interface items that +appear on windows, panels, and applets, such as menus, icons, and buttons. +Some of the desktop themes that are available in GNOME are designed for special +accessibility needs. Users can choose a desktop theme from the <guilabel>Widget Theme</guilabel> tabbed section in the <application>Theme</application> +preference tool.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Window frame themes</term> + <listitem> + <indexterm> + <primary>window frame themes</primary> + <see>themes</see> + </indexterm> + <para>Window frame +themes determine the appearance of the frames around windows only. Users can +choose a window frame theme from the <guilabel>Window Frames</guilabel> tabbed +section in the <application>Theme</application> preference tool.</para> + </listitem> + </varlistentry> + </variablelist> + </sect1> + <sect1 id="themes-3"> + <title>To Install a Desktop Theme</title> + <indexterm> + <primary>themes</primary> + <secondary>desktop theme, installing</secondary> + </indexterm> + <para>Desktop themes reside in the <filename>/usr/share/themes</filename> directory. The typical structure of a desktop theme in the file +system is as follows:</para> + <informaltable frame="none"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="19.19*"/> + <colspec colwidth="80.81*"/> + <tbody> + <row> + <entry valign="top"> + <para>Theme file</para> + </entry> + <entry valign="top"> + <para> + <filename>/usr/share/themes/<replaceable>theme_name</replaceable>/gtk-2.0/gtkrc</filename> + </para> + </entry> + </row> + <row> + <entry valign="top"> + <para>Image files</para> + </entry> + <entry valign="top"> + <para> + <filename>/usr/share/themes/<replaceable>theme_name</replaceable>/pixmaps/*.*</filename> + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>Typically, a new desktop theme is supplied as a <filename>.tar.gz</filename> +file. To install the new desktop theme, unzip the <filename>.tar.gz</filename> +file, then untar the <filename>.tar</filename> file into the <filename>/usr/share/themes</filename> directory.</para> + <para>If a user adds a desktop theme, the theme is stored in the <filename>$HOME/.themes</filename> directory.</para> + <para>Users can install their own desktop themes. If a user installs a desktop +theme, the theme is stored in the <filename>$HOME/.themes</filename> directory.</para> + </sect1> + <sect1 id="themes-5"> + <title>To Install a Window Frame Theme</title> + <indexterm> + <primary>themes</primary> + <secondary>window frame theme, installing</secondary> + </indexterm> + <para>Window frame themes reside in the <filename>/usr/share/themes/<replaceable>theme_name</replaceable>/metacity-1</filename> +directory. The typical structure of a window frame theme in the file system +is as follows:</para> + <informaltable frame="none"> + <tgroup cols="2" colsep="0" rowsep="0"> + <colspec colwidth="19.19*"/> + <colspec colwidth="80.81*"/> + <tbody> + <row> + <entry valign="top"> + <para>Theme file</para> + </entry> + <entry valign="top"> + <para> + <filename>/usr/share/themes/<replaceable>theme_name</replaceable>/metacity-1/metacity-theme-1.xml</filename> + </para> + </entry> + </row> + <row> + <entry valign="top"> + <para>Image files</para> + </entry> + <entry valign="top"> + <para> + <filename>/usr/share/themes/<replaceable>theme_name</replaceable>/metacity-1/*.*</filename> + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para>Typically, a new window frame theme is supplied as a <filename>.tar.gz</filename> file. To install the new window frame theme, unzip the <filename>.tar.gz</filename> file, then untar the <filename>.tar</filename> file into +the <filename>/usr/share/themes</filename> directory.</para> + <para>Users can install their own window frame themes. If a user installs +a window frame theme, the theme is stored in the <filename>$HOME/.themes</filename> +directory.</para> + </sect1> + <sect1 id="themes-11"> + <title>Installing Icons for Themes</title> + <indexterm> + <primary>themes</primary> + <secondary>installing icons</secondary> + </indexterm> + <para>The GNOME desktop provides several themes that are designed +for users with special visual needs. For example, some of the themes are designed +for users with low vision. The themes contain several versions of each icon +so that the icon can be displayed in each theme.</para> + <para>You might need to install a new icon for an application. When you install +a new icon, you must create several versions of the icon, so that the icon +displays correctly in the themes. You can create the icons in several formats, +for example Portable Network Graphic (PNG) format. The suggested size of icons +for the GNOME desktop is 48 pixels by 48 pixels. At this size, most themes +can rescale the icons.</para> + <para>When you install a new icon, create the following 48 × 48 pixel +versions of the icon:</para> + <itemizedlist> + <listitem> + <para>Regular icon</para> + </listitem> + <listitem> + <para>Low contrast icon</para> + </listitem> + <listitem> + <para>High contrast icon</para> + </listitem> + <listitem> + <para>Inverse high contrast icon</para> + </listitem> + </itemizedlist> + <para>If possible, create 16 × 16 pixel versions of the each of the +icons above also, for themes that do not require large print.</para> + <para>Install the icons to the image files location that is specified for +the theme in <xref linkend="themes-3"/> or <xref linkend="themes-5"/>. For example, +to add icons to the HighContrast theme, add the icons to the <filename>/usr/share/themes/HighContrast/pixmaps</filename> directory. Add references to the icons to the relevant theme files. +For example, to add icons to the HighContrast theme, add references to the +icons to the <filename>/usr/share/themes/HighContrast/gtk-2.0/gtkrc</filename> +file. </para> + <para>The instructions above apply only to the following types of icon:</para> + <itemizedlist> + <listitem> + <para>Icons that are used within applications in the GNOME desktop.</para> + </listitem> + <listitem> + <para>Icons that are used internally by GTK+ applications, or GTK+ +stock icons.</para> + </listitem> + </itemizedlist> + <para>For more information on how to create icons for application launchers +and for panels, see <ulink url="http://www.freedesktop.org/standards/icon-theme-spec.html">http://www.freedesktop.org/standards/icon-theme-spec.html</ulink>.</para> + </sect1> + <sect1 id="themes-15"> + <title>To Create a Custom Desktop Theme</title> + <indexterm> + <primary>themes</primary> + <secondary>creating custom desktop</secondary> + </indexterm> + <para>If the desktop themes that the GNOME desktop provides are +not suitable for the needs of your users, you can create a custom desktop +theme. To create a custom desktop theme, perform the following steps:</para> + <orderedlist> + <listitem> + <para>Create a directory structure for the theme in the <filename>/usr/share/themes</filename> directory. Use the same directory structure that +other themes use. For example, to create a theme that is called SmallPrint, +create the following directories:</para> + <itemizedlist> + <listitem> + <para> + <filename>/usr/share/themes/SmallPrint/gtk-2.0</filename> + </para> + </listitem> + <listitem> + <para> + <filename>/usr/share/themes/SmallPrint/pixmaps</filename> + </para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para>Locate the <filename>gtkrc</filename> theme file that is closest +to meeting the needs of your users. Copy the file to the <filename>gtk-2.0</filename> directory of your new theme.</para> + </listitem> + <listitem> + <para>Open the <filename>gtkrc</filename> file in a text editor, + and modify the attributes of the interface elements as required. </para> + </listitem> + <listitem> + <para>If the new theme includes images, install the images for the +new theme in the <filename>pixmaps</filename> directory of your new theme. +If the new theme uses images from another theme, you do not need to create +copies of the images for the new theme. Instead, ensure that the reference +to the images in the <literal>pixmap_path</literal> entry in the <filename>gtkrc</filename> file is correct.</para> + </listitem> + </orderedlist> + <para>Users can now choose the new theme.</para> + <para>For more information on <filename>gtkrc</filename> files, see <ulink url="http://developer.gnome.org/doc/API/2.0/gtk/index.html">http://developer.gnome.org/doc/API/2.0/gtk/index.html</ulink>.</para> + </sect1> +</chapter> |