From 099889fcf540cf5e73d2a2711f944bebc95b2a0d Mon Sep 17 00:00:00 2001 From: Eugene O'Connor Date: Fri, 24 Jan 2003 18:52:38 +0000 Subject: New files for GNOME 2.2 System Admin Guide V2.1. --- gnome2-system-admin-guide/C/appendixa.xml | 231 +++++++ .../C/gnome2.2-system-admin-guide.pdf | Bin 0 -> 569131 bytes gnome2-system-admin-guide/C/mimetypes.xml | 719 +++++++++++++++++++++ gnome2-system-admin-guide/C/performance.xml | 591 +++++++++++++++++ gnome2-system-admin-guide/C/screensavers.xml | 124 ++++ gnome2-system-admin-guide/C/sessions.xml | 114 ++++ gnome2-system-admin-guide/C/themes.xml | 236 +++++++ 7 files changed, 2015 insertions(+) create mode 100644 gnome2-system-admin-guide/C/appendixa.xml create mode 100644 gnome2-system-admin-guide/C/gnome2.2-system-admin-guide.pdf create mode 100644 gnome2-system-admin-guide/C/mimetypes.xml create mode 100644 gnome2-system-admin-guide/C/performance.xml create mode 100644 gnome2-system-admin-guide/C/screensavers.xml create mode 100644 gnome2-system-admin-guide/C/sessions.xml create mode 100644 gnome2-system-admin-guide/C/themes.xml (limited to 'gnome2-system-admin-guide') 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 @@ + + + + Hidden Directories + + This appendix describes the hidden directories that the +GNOME desktop adds to the home directories of users. + + + hidden directories + + + .* directories + hidden directories + + A hidden +directory is a directory that has a name that begins with a period (.). describes the hidden directories that the GNOME +desktop adds to the home directories of users. + + Hidden Directories in User Home Directories + + + + + + + Directory + + + Description + + + + + + + + .esd_auth + + + + Contains the authentication cookie for the GNOME +sound daemon. The GNOME sound daemon is the Enlightened Sound Daemon (ESD). + + + + + + .gconf + + + + Contains the GConf configuration +source for the user. When the user sets a preference, the new preference information +is added to this location. + + + + + + .gconfd + + + + Contains the following GConf +daemon details: + + + Configuration information. + + + Lock information for objects that are referenced by an Interoperable Object Reference (IOR). + + + State information for objects that are referenced by an IOR. + + + + + + + + .gnome + + + + Contains user-specific application data that is +not stored in the GConf repository. For example, +this directory contains MIME type information and session information for +the user. + + + + + + .gnome-desktop + + + + The Nautilus file manager +contains a preference that enables users to use Nautilus +to manage the desktop background. If the user selects this option, this directory +contains the objects that are on the Nautilus desktop +background of the user. This directory contains the following: + + + Objects on the desktop background, for example, the Home object, the Trash object, and other launchers. +The objects appear in the directory as desktop entry files. For example, the starthere.desktop file contains a link to the Start Here location. + + + Removable media volumes that are mounted. + + + The file manager also contains a preference that enables +users to use the home directory as the desktop background directory, instead +of .gnome-desktop. If a user selects this +option, the contents of the home directory are displayed as desktop background +objects. + + + + + + .gnome2 + + + + Contains user-specific application data that is +not stored in the GConf repository. For example, +this directory contains the following: + + + Keyboard shortcut information. + + + Window location information. + + + Desktop entry files for panel launchers. + + + This directory also contains user-specific menu data. +If a user modifies menus, the details are stored here. + + + + + + .gnome2-private + + + + Ignore this directory. This directory has no function +at the time of publication of this guide. + + + + + + .metacity + + + + Contains session data for the Metacity window manager. + + + + + + .nautilus + + + + Contains file manager data that is specific to the +user. For example, this directory can contain the following: + + + Metadata for the directories with which the user works. + + + Nautilus themes that the user adds. + + + Nautilus emblems that the user +adds. + + + Nautilus desktop background images. + + + + + + + + .themes + + + + Contains desktop themes and window frame themes +that the user adds. The user can add themes from the Themes +preference tool. + + + + + + .thumbnails + + + + 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. + + + + + + .xscreensaver + + + + Contains +screensaver configuration data and screensaver preference data. + + + + +
+ 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 new file mode 100644 index 0000000..58e896a Binary files /dev/null and b/gnome2-system-admin-guide/C/gnome2.2-system-admin-guide.pdf differ 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 @@ + + + MIME Types + + This chapter describes how applications detect MIME types, +how to register MIME types, and how to add applications to the GNOME desktop. + + + Introduction + + MIME types + introduction + + A Multipurpose Internet Mail Extension +(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. + In the GNOME desktop, the Nautilus 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: + + + Open the file in an appropriate application. + + + Display a string that describes the type of file. + + + Display an appropriate icon to represent the file. + + + Display a list of other applications that can open the file. + + + 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. + 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. + + + Detecting the MIME Type for a File + + MIME types + detecting + + + detecting MIME types + + Applications can detect the MIME type of a file as follows: + + + The application uses file content sniffers +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. + + + If file content sniffers do not identify the MIME type, then +the application can check the filename. The application checks the filename +against the MIME type registry. 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. + + + The following sections provide further information on file content sniffers +and the MIME type registry. + + File Content Sniffers + + MIME types + file content sniffers + + + file content sniffers + + File content sniffers are specified in the file /usr/gnome/etc/gnome-vfs-mime-magic. The following is an example of a file content sniffer: + 0 string \x89PNG image/png + The syntax for file content sniffers is as follows: + offset_start[:offset_end] pattern_type pattern [&pattern_mask] type + describes the fields in a file content +sniffer. + + Fields in a File Content Sniffer + + + + + + + Field + + + Description + + + + + + + + offset_start + + + + Specifies the number of characters to ignore in +the file before searching for a text pattern. + + + + + + pattern_type + + + + Specifies the type of pattern to search for. The string pattern type is the only pattern type that is supported at +the time of publication of this guide. + + + + + + pattern + + + + Specifies the pattern to search for. + + + + + + pattern_mask + + + + Specifies a pattern mask, +in hexadecimal format. For more information on pattern masks, see the next +section. + This field is optional. This field is not present in +the example. + + + + + + type + + + + Specifies the MIME type to associate with files that match +this entry. + + + + +
+ + Pattern Masks + + MIME types + pattern mask + + + pattern mask + + 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: + 0 string BMxxxx\000\000 &0xffff00000000ffff image/bmp + The pattern and mask in the example are as follows: + + + + + + + + + + + + + + + Pattern + + + + B + + + + + M + + + + + x + + + + + x + + + + + x + + + + + x + + + + + \000 + + + + + \000 + + + + + + Mask + + + + ff + + + + + ff + + + + + 00 + + + + + 00 + + + + + 00 + + + + + 00 + + + + + ff + + + + + ff + + + + + + + The pattern and mask specify a file with the following characteristics: + + + The file begins with BM. + + + BM is followed by four bytes with any values. + + + The four bytes are followed by \000\000. + + + The file content sniffer specifies that the MIME type of files that +match the pattern and mask is image/bmp. + + + + MIME Type Registry + + MIME types + MIME type registry + + The MIME type registry is located in /usr/gnome/share/mime-info. The MIME type registry contains the following files: + + + + + + + + File + + + Filename Extension + + + + + + + MIME information file + + + + .mime + + + + + + MIME keys file + + + + .keys + + + + + + + The following sections describe MIME information files and MIME keys +files. + + MIME Information Files + + MIME types + MIME information files + + MIME information files +associate MIME types with one or both of the following: + + + Filename extensions + + + Filename patterns + + + 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. + In MIME information files, the filename pattern to search for is written +as a regular expression. + The format of MIME type entries in MIME information files is as follows: + MIME_type + ext[,priority]: list_of_extensions + regex[,priority]: list_of_regular_expressions + 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 1 +to the .gz extension, and assign a higher priority of 2 to the .tar.gz extension. In this case, the +file abc.tar.gz takes the MIME type for .tar.gz. + + You must indent the ext field and the regex field with a tab character (\t). + + The following MIME type entries are samples from the gnome-vfs.mime MIME information file: + 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.* + + 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 abc.mime and def.mime, the MIME type in abc.mime is used. + + + + MIME Keys Files + + MIME types + MIME keys files + + MIME keys file 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. + The following is a sample from a MIME keys file: + 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 + + You must indent the keys in a MIME keys file with a tab character +(\t). + + describes the most important keys in +MIME keys files. Typically, the description key and the category key are localized. + + Keys in MIME Keys Files + + + + + + + Key + + + Description + + + + + + + + can_be_executable + + + + Specifies whether files of this MIME type +can be executed. + + + + + + description + + + + Describes the MIME type. This description can be +displayed in the file manager and other applications. + + + + + + icon_filename + + + + Specifies the filename of an icon to represent the +MIME type. Does not specify the path to the filename, or the filename extension. + This icon can be displayed in the file manager and other applications. + + + + + + default_action_type + + + + Specifies the category of action to take when a +file of this MIME type is opened by the user. Enter application +for this MIME type for most applications. + + + + + + short_list_application_ids + _for_novice_user_level + + + + 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. + + + + + + category + + + + Specifies a category for the MIME type. The value +of this key determines the location of the MIME type in the File Types and Programs preference tool. + + + + +
+ + + + + Registering Applications for MIME Types + + MIME types + registering applications +for + + + applications + registry + + The application registry 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: + + + The command to use to start the application. + + + MIME types to associate with the application. + + + An application registration file can contain one or more application +registrations. Application registration files have a .applications extension. + The location of the application registry is /usr/share/gnome/application-registry. This directory contains a default application registration file +that is called gnome-vfs.applications. + To register an application, add a registration file for the application +to the application registry. + The following is an example of an application registration: + 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 + describes the keys in application registration +files. + + Keys for an Application Registration + + + + + + + Key + + + Description + + + + + + + Application identifier + + + 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. + + + + + + command + + + + Specifies the command to use to start the application, +and any options to use with the command. + + + + + + name + + + + Specifies a name for the application. The name is used +in the user interface. For example, the name is used in the Open +With submenu in the file manager. + + + + + + can_open_multiple_files + + + + Specifies whether the application can open several +files at the same time. + + + + + + expects_uris + + + + Specifies whether the application can process URIs. +If the value of this key is true, the application registration +entry must also contain a supported_uri_schemes key. + + + + + + supported_uri_schemes + + + + Specifies +the URI schemes that the application can process. + + + + + + requires_terminal + + + + Specifies whether to run the application in a terminal +window. Enter true for this field for an application that +does not create a window in which to run. + + + + + + mime_types + + + + Specifies the MIME types that the application can +use. + + + + +
+ + + Adding an Application to the GNOME Desktop + + MIME types + adding applications + + + applications + adding + + To add an application to the GNOME desktop, perform the +following steps: + + + Add a menu item for the application. For more information +on how to add an item to a menu, see . + + + Add an icon for the application to /usr/gnome/share/icons/theme_name/icon_size/apps. +For more information on icons and themes, see Installing Themes. + + + 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 . + + + 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 . + + + Add a MIME keys file for the application to the MIME type +registry. For more information on MIME keys files, see . + + + If the application uses a new MIME type, add an icon for the +MIME type to /usr/gnome/share/icons/theme_name/icon_size/mimetypes. For more information on icons +and themes, see Installing Themes. + + + 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 . + + + + 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 @@ + + + Improving Performance + + This chapter describes how to improve the performance of +the GNOME desktop. + + + Introduction + + performance, improving + introduction + + This chapter lists several preferences whose +settings you can change to improve the performance of the GNOME desktop. You +can use the gconftool-2 command to set values for preferences +for users. The example commands in this chapter show how to set values in +the user configuration source. + You can also use the --direct and --config-source options to set mandatory values or default values for preferences. +You can also use the gconftool-2 command in a script to +set the values of many preferences. For more information on the gconftool-2 command and the options that are available with the +command, see Using GConf. + + + Reducing CPU Usage + + performance, improving + reducing CPU +usage + + + reducing + CPU usage + + + CPU usage + reducing + + This section describes preferences that +you can set to reduce CPU usage by the GNOME desktop. + + To Use Themes Which Require Less CPU Resources + + themes + and CPU usage + + Some window frame themes load image files to draw the window frame. +Other themes use simpler techniques to draw the window frame. + 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: + + + Atlanta + + + Esco + + + The following window frame themes also use less CPU resources than Crux: + + + AgingGorilla + + + Bright + + + Metabox + + + + Metabox does not work well with inverse desktop themes such as +HighContrastInverse. Use Atlanta with inverse desktop themes. + + + themes + changing + + To change the window frame theme, run the following command: + # gconftool-2 --type string +--set /apps/metacity/general/theme theme_name + For example, to use Atlanta, run the following command: + # gconftool-2 --type string +--set /apps/metacity/general/theme Atlanta + Alternatively, users can choose ApplicationsDesktop PreferencesThemes, then select the appropriate theme. + + You can use the Metacity Theme Viewer +to measure the performance of a window frame theme, and to preview the theme. +To start Metacity Theme Viewer, use the following +command: + # metacity-theme-viewer theme_name + For example, to measure the performance of Atlanta and preview Atlanta, +run the following command: + # metacity-theme-viewer +Atlanta + + + + To Reduce CPU Usage by Turning Off Display of Icons in Menus + + icons, in menus + menu icons + + + menu icons + and CPU usage + + Some items in menus display an icon beside the item. To +turn off this feature, run the following command: + + menu icons + turning off + + # gconftool-2 +--type bool --set /desktop/gnome/interface/menus_have_icons false + Alternatively, users can choose ApplicationsDesktop PreferencesMenus & Toolbars, then deselect the Show icons in menus option. + + + To Reduce CPU Usage by Turning On Wireframe Mode + + wireframe mode + and CPU usage + + 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. + + wireframe mode + turning on + + To turn on wireframe mode, run the following command: + # gconftool-2 --type bool +--set /apps/metacity/general/wireframe_move_resize true + + + To Reduce CPU Usage by Turning Off the Splash Screen + + splash screen + and CPU usage + + 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. + + splash screen + turning off + + To turn off the splash screen, run the following command: + # gconftool-2 --type bool +--set /apps/gnome-session/options/show_splash_screen false + Alternatively, users can choose ApplicationsDesktop PreferencesAdvancedSessions, +then deselect the Show splash screen on login option. + + + To Reduce CPU Usage by Turning Off Panel Animation + + panels + animation, turning off + + 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: + # gconftool-2 --type bool +--set /apps/panel/global/enable_animations false + Alternatively, users can choose ApplicationsDesktop PreferencesAdvancedThemes, +then deselect the Animation option. + + + Improving File Manager Performance + + Nautilus + file manager + + The Nautilus file manager includes some features +that you can modify to improve performance. + + To Modify Performance Preferences + + file manager + modifying performance +preferences + + The file manager includes performance-related +preferences. Each performance preference can take one of three values. The +values are described in the following table: + + + + + + + + Value + + + Description + + + + + + + + always + + + + Performs +the action for both local files, and files on other file systems. + + + + + + local_only + + + + Performs the action for local files only. When you +set a performance preference to local_only, the CPU usage +is reduced. + + + + + + never + + + + Never performs the action. When you set a performance preference +to never, the CPU usage and the network traffic are reduced. + + + + + + The following table describes the performance preferences for the file +manager. For the fastest performance, set the value of the preferences to never. + + + + + + + + Preference + + + Description + + + + + + + + show_icon_text + + + + 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: + # gconftool-2 --type string --set /apps/nautilus/preferences/show_icon_text +never + Alternatively, users can perform the following +steps: + + + Choose EditPreferences from a file manager window, then choose Performance. + + + Select an option for the Show Text in Icons +preference. + + + + + + + + show_directory_item_counts + + + + Specifies when to show the number of items in folders. +To never show the number of items in folders, run the following command: + # gconftool-2 --type string --set /apps/nautilus/preferences/show_directory_item_counts +never + Alternatively, users can perform the following +steps: + + + Choose EditPreferences from a file manager window, then choose Performance. + + + Select an option for the Show Number of Items in +Folders preference. + + + + + + + + show_image_thumbnails + + + + Specifies when to show thumbnails of image files. +To never show thumbnails, run the following command: + # gconftool-2 --type string --set /apps/nautilus/preferences/show_image_thumbnails +never + Alternatively, users can perform the following +steps: + + + Choose EditPreferences from a file manager window, then choose Performance. + + + Select an option for the Show Thumbnails for Image +Files preference. + + + + + + + + preview_sound + + + + Specifies when to preview the content of sound files. +To never preview the content of sound files, run the following command: + # gconftool-2 --type string --set /apps/nautilus/preferences/preview_sound +never + Alternatively, users can perform the following +steps: + + + Choose EditPreferences from a file manager window, then choose Performance. + + + Select an option for the Preview Sound Files +preference. + + + + + + + + + + To Turn Off the Side Pane, Toolbar, and Location Bar + + file manager + side pane, turning off + + 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. + To turn off the side pane, run the following command: + # gconftool-2 --type bool +--set /apps/nautilus/preferences/start_with_sidebar false + Alternatively, users can choose EditPreferences from a file manager window, +then choose Windows, and then deselect the Display side pane option. The next time that users open a file +manager window, the window does not display a side pane. + + file manager + toolbar, turning off + + To turn off the toolbar, run the following command: + # gconftool-2 --type bool +--set /apps/nautilus/preferences/start_with_toolbar false + Alternatively, users can choose EditPreferences from a file manager window, +then choose Windows, and then deselect the Display toolbar option. The next time that users open a file manager +window, the window does not display a toolbar. + You can also turn off the location bar. Users can use the CtrlL keyboard shortcut to display a location bar +when required. + + file manager + location bar, turning +off + + To turn off the location bar, run the following +command: + # gconftool-2 --type bool +--set /apps/nautilus/preferences/start_with_location_bar false + Alternatively, users can choose EditPreferences from a file manager window, +then choose Windows, and then deselect the Display location bar option. The next time that users open a file +manager window, the window does not display a location bar. + + + To Turn Off the Desktop Background + + file manager + desktop background, turning +off + + + desktop background + turning off + + The file manager contains +a preference that enables users to use Nautilus +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: + + + Use the Desktop Background menu. + + + Use the file manager to change the pattern or color of the +desktop background. + + + Use the Home object and the Trash object. The Home object and the Trash object are not displayed on the desktop. + + + To disable the desktop background, run the following command: + # gconftool-2 --type bool +--set /apps/nautilus/preferences/show_desktop false + Alternatively, users can choose EditPreferences from a file manager window. +Users can then choose Desktop & Trash, and then deselect +the Use Nautilus to draw the desktop option. + + + + + Reducing X11 Network Traffic + + reducing + X11 network traffic + + + X11 network traffic, reducing + + + network traffic, reducing + + This section describes preferences that you can set to reduce X11 network +traffic on the GNOME desktop. + + To Use Themes Which Create Less Network Traffic + + themes + and network traffic + + Remote display protocols do not transfer every pixel in +a block of pixels if all pixels in the block are the same color. + To reduce X11 network traffic, use a window frame theme that uses solid +colors. That is, use one of the following window frame themes: + + + Atlanta + + + Esco + + + For information on how to change the theme, see . + + + To Reduce Network Traffic by Turning Off Display of Icons in Menus + + menu icons + and network traffic + + 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. + For information on how to turn off this feature, see . + + + To Reduce Network Traffic by Turning On Wireframe Mode + + wireframe mode + and network traffic + + If the application that displays the window +is running on a remote host, wireframe mode reduces X11 network traffic. + For more information on wireframe mode, see . + + + + Reducing Color Usage and Improving Display Quality + + reducing + color usage + + + color usage + reducing + + + display quality, improving + + 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. + The GNOME desktop uses the Netscape color palette. +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. + The following display problems might occur on systems that support 8-bit +color: + + + Windows, icons, and background images might appear grainy. + Many themes, background images, and icons use colors that are not in the Netscape 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. + + + Applications that do not use the Netscape +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. + + + Color flashing might occur when users switch between applications +that use the Netscape color palette, and applications +that do not use this palette. The applications that do not use the Netscape color palette might use a custom colormap. When the +custom colormap is used, other visual components might lose colors, then become +unviewable. + + + The following sections describe how to optimize the appearance of the +GNOME desktop for systems that support 8-bit color. + + To Use Themes That Use the Netscape Color Palette + + themes + and color usage + + 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. + For information on how to change the theme, see . + + + To Reduce Color Usage by Turning Off Display of Icons in Menus + + menu icons + and color usage + + Some items in menus display an icon beside the item. If +the icon contains colors that are not in the Netscape +color palette, this feature can increase the number of colors used. + For information on how to turn off this feature, see . + + + To Reduce Color Usage by Turning Off the Splash Screen + + splash screen + and color usage + + You can turn off the splash screen to make more colors available +for the GNOME desktop and applications. + For information on how to turn off the splash screen, see . + + + To Reduce Color Usage by Using a Solid Color for the Desktop Background + + desktop background + using solid color + + Use a solid color for the desktop background. +Use of a solid color reduces the number of colors used by the GNOME desktop. + To set a solid color for the desktop background, run the following commands: + # gconftool-2 --type string +--set /desktop/gnome/background/picture_options none + # gconftool-2 --type string +--set /desktop/gnome/background/color_shading_type solid + # gconftool-2 --type string +--set /desktop/gnome/background/primary_color \#hexadecimal_color + Alternatively, users can choose ApplicationsDesktop PreferencesBackground, then choose a solid color for the desktop +background. + + + 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 @@ + + + Setting Screensavers + + 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. + + + Introduction + + screensavers + introduction + + + XScreenSaver + screensavers + + A screensaver 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 XScreenSaver. +The following sections describe how to set preferences for the XScreenSaver application, and how to modify the displays that +are available for the screensaver. + + The XScreenSaver application does not +allow you to lock your screen if you are logged in as root. +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 su command to log in as root. + + + + Setting Screensaver Preferences + + screensavers + setting preferences + + Default screensaver preferences are stored in a file that +is called XScreenSaver. This file is stored in different +locations, depending on the platform, as follows: + + + + + + + + Platform + + + File Location + + + + + + + RedHat Linux + + + + /usr/X11R6/lib/X11/app-defaults/XScreenSaver + + + + + + Solaris Operating Environment + + + + /usr/openwin/lib/app-defaults/XScreenSaver + + + + + + + To modify screensaver application preferences, users can right-click +on the Lock button, then choose Properties. The user can then modify preferences in the XScreenSaver dialog. When a user modifies the screensaver preferences, the +preferences are stored in the home directory of the user, in the $HOME/.xscreensaver file. For information on screensaver preferences, +see GNOME 2.2 Desktop User Guide. + Users can also run the command /usr/X11R6/bin/xscreensaver-demo to open the XScreenSaver dialog. + To set default screensaver preferences for all users, modify the XScreenSaver file. You can also use the XScreenSaver dialog to create a $HOME/.xscreensaver file, +then copy the file to the location of the XScreenSaver +file. + To restore the default settings for a user, delete the $HOME/.xscreensaver file from the home directory of the user. If no $HOME/.xscreensaver file is present, the default preferences in the XScreenSaver file are used. + + The default display behavior of XScreenSaver +is to display a blank screen. The blank screen might confuse users. You might +want to change this default display behavior. + + To activate changes to the screensaver preferences, use the following +command to reload screensaver preferences: + # xscreensaver-command -restart + + The xset application does not work +with XScreenSaver at the time of publication of +this guide. To modify screensaver preferences, modify the XScreenSaver file or the $HOME/.xscreensaver file. + + + + Modifying Screensaver Displays + + screensavers + modifying screensaver +displays + + The screensaver application allows users +to choose one or more screensaver displays. 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 XScreenSaver file and in the $HOME/.xscreensaver +file. + To add a new screensaver display, copy the executable file for the display +to the /usr/X11R6/lib/xscreensaver/hacks directory. Add +the command for the screensaver display to the XScreenSaver file or the $HOME/.xscreensaver 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 -root option to display the screensaver display on the desktop. + 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 $HOME/.xscreensaver file shows a disabled Qix (solid) screensaver +display: + - "Qix (solid)" qix -root -solid -segments 100 + + 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 @@ + + + Session Management + + This chapter introduces session management, and describes +how to set session defaults. The chapter also contains information on sessions +and login scripts. + + + Introduction + + sessions + introduction + + 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 Login Manager 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. + At a minimum, the following applications run in a session: + + + The session manager, gnome-session. + + + The GConf X settings daemon, gnome-settings-daemon. + + + The gnome-panel application, which +runs the panels on the GNOME desktop. + + + The Metacity window manager. + + + + + Setting Session Defaults + + sessions + setting defaults + + The following table lists the files that contain default +session information: + + + + + + + + File + + + Description + + + + + + + + /usr/share/gnome/default.session + + + + Default session file. +Default session details are stored in this file. + + + + + + $HOME/.gnome2/session + + + + User session file. When a user modifies the session, +the details are stored in this file. + + + + + + To set default session details for all users, modify the default session +file. + 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 /usr/share/gnome/default.session +are used. + To save the current session as the default session, users can run the gnome-session-save command. + + + Login Scripts + + sessions + login scripts + + 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 Sessions preference tool. + + 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 /usr/dt/config/Xsession.d directory. Name the script as follows: + + number_greater_than_1000.name + + For example, name the script 1050.login. For more +information on the /usr/dt/config/Xsession.d file, see The XSession File in the dtlogin1 man page. + + + 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 @@ + + + Installing Themes + + 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. + + + Introduction + + themes + introduction + + 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. + The following types of theme affect different parts of the GNOME desktop: + + + Desktop themes + + + desktop +themes + themes + + 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 Widget Theme tabbed section in the Theme +preference tool. + + + + Window frame themes + + + window frame themes + themes + + Window frame +themes determine the appearance of the frames around windows only. Users can +choose a window frame theme from the Window Frames tabbed +section in the Theme preference tool. + + + + + + To Install a Desktop Theme + + themes + desktop theme, installing + + Desktop themes reside in the /usr/share/themes directory. The typical structure of a desktop theme in the file +system is as follows: + + + + + + + + Theme file + + + + /usr/share/themes/theme_name/gtk-2.0/gtkrc + + + + + + Image files + + + + /usr/share/themes/theme_name/pixmaps/*.* + + + + + + + Typically, a new desktop theme is supplied as a .tar.gz +file. To install the new desktop theme, unzip the .tar.gz +file, then untar the .tar file into the /usr/share/themes directory. + If a user adds a desktop theme, the theme is stored in the $HOME/.themes directory. + Users can install their own desktop themes. If a user installs a desktop +theme, the theme is stored in the $HOME/.themes directory. + + + To Install a Window Frame Theme + + themes + window frame theme, installing + + Window frame themes reside in the /usr/share/themes/theme_name/metacity-1 +directory. The typical structure of a window frame theme in the file system +is as follows: + + + + + + + + Theme file + + + + /usr/share/themes/theme_name/metacity-1/metacity-theme-1.xml + + + + + + Image files + + + + /usr/share/themes/theme_name/metacity-1/*.* + + + + + + + Typically, a new window frame theme is supplied as a .tar.gz file. To install the new window frame theme, unzip the .tar.gz file, then untar the .tar file into +the /usr/share/themes directory. + Users can install their own window frame themes. If a user installs +a window frame theme, the theme is stored in the $HOME/.themes +directory. + + + Installing Icons for Themes + + themes + installing icons + + 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. + 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. + When you install a new icon, create the following 48 × 48 pixel +versions of the icon: + + + Regular icon + + + Low contrast icon + + + High contrast icon + + + Inverse high contrast icon + + + If possible, create 16 × 16 pixel versions of the each of the +icons above also, for themes that do not require large print. + Install the icons to the image files location that is specified for +the theme in or . For example, +to add icons to the HighContrast theme, add the icons to the /usr/share/themes/HighContrast/pixmaps 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 /usr/share/themes/HighContrast/gtk-2.0/gtkrc +file. + The instructions above apply only to the following types of icon: + + + Icons that are used within applications in the GNOME desktop. + + + Icons that are used internally by GTK+ applications, or GTK+ +stock icons. + + + For more information on how to create icons for application launchers +and for panels, see http://www.freedesktop.org/standards/icon-theme-spec.html. + + + To Create a Custom Desktop Theme + + themes + creating custom desktop + + 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: + + + Create a directory structure for the theme in the /usr/share/themes directory. Use the same directory structure that +other themes use. For example, to create a theme that is called SmallPrint, +create the following directories: + + + + /usr/share/themes/SmallPrint/gtk-2.0 + + + + + /usr/share/themes/SmallPrint/pixmaps + + + + + + Locate the gtkrc theme file that is closest +to meeting the needs of your users. Copy the file to the gtk-2.0 directory of your new theme. + + + Open the gtkrc file in a text editor, + and modify the attributes of the interface elements as required. + + + If the new theme includes images, install the images for the +new theme in the pixmaps 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 pixmap_path entry in the gtkrc file is correct. + + + Users can now choose the new theme. + For more information on gtkrc files, see http://developer.gnome.org/doc/API/2.0/gtk/index.html. + + -- cgit