diff options
Diffstat (limited to 'user-guide/C')
62 files changed, 2716 insertions, 0 deletions
diff --git a/user-guide/C/img/ch1-README.png b/user-guide/C/img/ch1-README.png Binary files differnew file mode 100644 index 000000000..8c4a3a282 --- /dev/null +++ b/user-guide/C/img/ch1-README.png diff --git a/user-guide/C/img/ch1-cnn.png b/user-guide/C/img/ch1-cnn.png Binary files differnew file mode 100644 index 000000000..022c280de --- /dev/null +++ b/user-guide/C/img/ch1-cnn.png diff --git a/user-guide/C/img/ch1-complex-search.png b/user-guide/C/img/ch1-complex-search.png Binary files differnew file mode 100644 index 000000000..d56fe9ee9 --- /dev/null +++ b/user-guide/C/img/ch1-complex-search.png diff --git a/user-guide/C/img/ch1-connect.png b/user-guide/C/img/ch1-connect.png Binary files differnew file mode 100644 index 000000000..9daad6061 --- /dev/null +++ b/user-guide/C/img/ch1-connect.png diff --git a/user-guide/C/img/ch1-duplicate.png b/user-guide/C/img/ch1-duplicate.png Binary files differnew file mode 100644 index 000000000..e356c35ce --- /dev/null +++ b/user-guide/C/img/ch1-duplicate.png diff --git a/user-guide/C/img/ch1-google.png b/user-guide/C/img/ch1-google.png Binary files differnew file mode 100644 index 000000000..af56b613b --- /dev/null +++ b/user-guide/C/img/ch1-google.png diff --git a/user-guide/C/img/ch1-hardware.png b/user-guide/C/img/ch1-hardware.png Binary files differnew file mode 100644 index 000000000..32d9ea8f6 --- /dev/null +++ b/user-guide/C/img/ch1-hardware.png diff --git a/user-guide/C/img/ch1-history.png b/user-guide/C/img/ch1-history.png Binary files differnew file mode 100644 index 000000000..f47381ede --- /dev/null +++ b/user-guide/C/img/ch1-history.png diff --git a/user-guide/C/img/ch1-home-john.png b/user-guide/C/img/ch1-home-john.png Binary files differnew file mode 100644 index 000000000..6ccb107cd --- /dev/null +++ b/user-guide/C/img/ch1-home-john.png diff --git a/user-guide/C/img/ch1-home.png b/user-guide/C/img/ch1-home.png Binary files differnew file mode 100644 index 000000000..e4082f37f --- /dev/null +++ b/user-guide/C/img/ch1-home.png diff --git a/user-guide/C/img/ch1-icon-view-150.png b/user-guide/C/img/ch1-icon-view-150.png Binary files differnew file mode 100644 index 000000000..c556b44e5 --- /dev/null +++ b/user-guide/C/img/ch1-icon-view-150.png diff --git a/user-guide/C/img/ch1-icon-view-demo.png b/user-guide/C/img/ch1-icon-view-demo.png Binary files differnew file mode 100644 index 000000000..9e79fef17 --- /dev/null +++ b/user-guide/C/img/ch1-icon-view-demo.png diff --git a/user-guide/C/img/ch1-inadequate-permissions.png b/user-guide/C/img/ch1-inadequate-permissions.png Binary files differnew file mode 100644 index 000000000..9db7d0b45 --- /dev/null +++ b/user-guide/C/img/ch1-inadequate-permissions.png diff --git a/user-guide/C/img/ch1-list-mydoc.png b/user-guide/C/img/ch1-list-mydoc.png Binary files differnew file mode 100644 index 000000000..6b2ed455f --- /dev/null +++ b/user-guide/C/img/ch1-list-mydoc.png diff --git a/user-guide/C/img/ch1-music-control.png b/user-guide/C/img/ch1-music-control.png Binary files differnew file mode 100644 index 000000000..61a4aa7d1 --- /dev/null +++ b/user-guide/C/img/ch1-music-control.png diff --git a/user-guide/C/img/ch1-nautiluslogo.png b/user-guide/C/img/ch1-nautiluslogo.png Binary files differnew file mode 100644 index 000000000..be1973f92 --- /dev/null +++ b/user-guide/C/img/ch1-nautiluslogo.png diff --git a/user-guide/C/img/ch1-new-window.png b/user-guide/C/img/ch1-new-window.png Binary files differnew file mode 100644 index 000000000..3de1ace8e --- /dev/null +++ b/user-guide/C/img/ch1-new-window.png diff --git a/user-guide/C/img/ch1-open-with.png b/user-guide/C/img/ch1-open-with.png Binary files differnew file mode 100644 index 000000000..f594bc174 --- /dev/null +++ b/user-guide/C/img/ch1-open-with.png diff --git a/user-guide/C/img/ch1-panel.png b/user-guide/C/img/ch1-panel.png Binary files differnew file mode 100644 index 000000000..6427677bb --- /dev/null +++ b/user-guide/C/img/ch1-panel.png diff --git a/user-guide/C/img/ch1-permissions.png b/user-guide/C/img/ch1-permissions.png Binary files differnew file mode 100644 index 000000000..822a81a04 --- /dev/null +++ b/user-guide/C/img/ch1-permissions.png diff --git a/user-guide/C/img/ch1-pluck.png b/user-guide/C/img/ch1-pluck.png Binary files differnew file mode 100644 index 000000000..36f5e27c2 --- /dev/null +++ b/user-guide/C/img/ch1-pluck.png diff --git a/user-guide/C/img/ch1-samba.png b/user-guide/C/img/ch1-samba.png Binary files differnew file mode 100644 index 000000000..8d08b6df9 --- /dev/null +++ b/user-guide/C/img/ch1-samba.png diff --git a/user-guide/C/img/ch1-slash.png b/user-guide/C/img/ch1-slash.png Binary files differnew file mode 100644 index 000000000..30de5702c --- /dev/null +++ b/user-guide/C/img/ch1-slash.png diff --git a/user-guide/C/img/ch1-toolbar.png b/user-guide/C/img/ch1-toolbar.png Binary files differnew file mode 100644 index 000000000..e63a07324 --- /dev/null +++ b/user-guide/C/img/ch1-toolbar.png diff --git a/user-guide/C/img/ch1-toshiba.png b/user-guide/C/img/ch1-toshiba.png Binary files differnew file mode 100644 index 000000000..3e8fe69c2 --- /dev/null +++ b/user-guide/C/img/ch1-toshiba.png diff --git a/user-guide/C/img/ch1-tree-demo.png b/user-guide/C/img/ch1-tree-demo.png Binary files differnew file mode 100644 index 000000000..7f017a9b1 --- /dev/null +++ b/user-guide/C/img/ch1-tree-demo.png diff --git a/user-guide/C/img/ch1-tree-doc-1.png b/user-guide/C/img/ch1-tree-doc-1.png Binary files differnew file mode 100644 index 000000000..715742c3b --- /dev/null +++ b/user-guide/C/img/ch1-tree-doc-1.png diff --git a/user-guide/C/img/ch1-tree-doc.png b/user-guide/C/img/ch1-tree-doc.png Binary files differnew file mode 100644 index 000000000..9f9b9e5c8 --- /dev/null +++ b/user-guide/C/img/ch1-tree-doc.png diff --git a/user-guide/C/img/ch1-tree-etc.png b/user-guide/C/img/ch1-tree-etc.png Binary files differnew file mode 100644 index 000000000..ebf24e220 --- /dev/null +++ b/user-guide/C/img/ch1-tree-etc.png diff --git a/user-guide/C/img/ch1-tree-slash.png b/user-guide/C/img/ch1-tree-slash.png Binary files differnew file mode 100644 index 000000000..68b1d67a6 --- /dev/null +++ b/user-guide/C/img/ch1-tree-slash.png diff --git a/user-guide/C/img/ch1-view-as.png b/user-guide/C/img/ch1-view-as.png Binary files differnew file mode 100644 index 000000000..294cd1705 --- /dev/null +++ b/user-guide/C/img/ch1-view-as.png diff --git a/user-guide/C/img/ch1-zoom-control.png b/user-guide/C/img/ch1-zoom-control.png Binary files differnew file mode 100644 index 000000000..aacc5ceba --- /dev/null +++ b/user-guide/C/img/ch1-zoom-control.png diff --git a/user-guide/C/img/ch2-colors.png b/user-guide/C/img/ch2-colors.png Binary files differnew file mode 100644 index 000000000..86bf2b579 --- /dev/null +++ b/user-guide/C/img/ch2-colors.png diff --git a/user-guide/C/img/ch2-edit-settings-folder.png b/user-guide/C/img/ch2-edit-settings-folder.png Binary files differnew file mode 100644 index 000000000..bce20c3d0 --- /dev/null +++ b/user-guide/C/img/ch2-edit-settings-folder.png diff --git a/user-guide/C/img/ch2-emblems.png b/user-guide/C/img/ch2-emblems.png Binary files differnew file mode 100644 index 000000000..cd8cf7efd --- /dev/null +++ b/user-guide/C/img/ch2-emblems.png diff --git a/user-guide/C/img/ch2-home-john-mydoc.png b/user-guide/C/img/ch2-home-john-mydoc.png Binary files differnew file mode 100644 index 000000000..785b9114f --- /dev/null +++ b/user-guide/C/img/ch2-home-john-mydoc.png diff --git a/user-guide/C/img/ch2-icon-captions-alone.png b/user-guide/C/img/ch2-icon-captions-alone.png Binary files differnew file mode 100644 index 000000000..491a871ce --- /dev/null +++ b/user-guide/C/img/ch2-icon-captions-alone.png diff --git a/user-guide/C/img/ch2-icon-captions.png b/user-guide/C/img/ch2-icon-captions.png Binary files differnew file mode 100644 index 000000000..f133ed28f --- /dev/null +++ b/user-guide/C/img/ch2-icon-captions.png diff --git a/user-guide/C/img/ch2-john.png b/user-guide/C/img/ch2-john.png Binary files differnew file mode 100644 index 000000000..18cbe6e84 --- /dev/null +++ b/user-guide/C/img/ch2-john.png diff --git a/user-guide/C/img/ch2-music.png b/user-guide/C/img/ch2-music.png Binary files differnew file mode 100644 index 000000000..bc7bc932f --- /dev/null +++ b/user-guide/C/img/ch2-music.png diff --git a/user-guide/C/img/ch2-open-with-other.png b/user-guide/C/img/ch2-open-with-other.png Binary files differnew file mode 100644 index 000000000..09ca51299 --- /dev/null +++ b/user-guide/C/img/ch2-open-with-other.png diff --git a/user-guide/C/img/ch2-open-with.png b/user-guide/C/img/ch2-open-with.png Binary files differnew file mode 100644 index 000000000..7ace76d16 --- /dev/null +++ b/user-guide/C/img/ch2-open-with.png diff --git a/user-guide/C/img/ch2-photos-john.png b/user-guide/C/img/ch2-photos-john.png Binary files differnew file mode 100644 index 000000000..f583b2805 --- /dev/null +++ b/user-guide/C/img/ch2-photos-john.png diff --git a/user-guide/C/img/ch2-right-click-open-with.png b/user-guide/C/img/ch2-right-click-open-with.png Binary files differnew file mode 100644 index 000000000..39654e7f4 --- /dev/null +++ b/user-guide/C/img/ch2-right-click-open-with.png diff --git a/user-guide/C/img/ch2-search-settings.png b/user-guide/C/img/ch2-search-settings.png Binary files differnew file mode 100644 index 000000000..10bba2ebf --- /dev/null +++ b/user-guide/C/img/ch2-search-settings.png diff --git a/user-guide/C/img/ch2-ski-intermediate-menu.png b/user-guide/C/img/ch2-ski-intermediate-menu.png Binary files differnew file mode 100644 index 000000000..7f9dc9412 --- /dev/null +++ b/user-guide/C/img/ch2-ski-intermediate-menu.png diff --git a/user-guide/C/img/ch2-theme-eazel.png b/user-guide/C/img/ch2-theme-eazel.png Binary files differnew file mode 100644 index 000000000..943b7ed0b --- /dev/null +++ b/user-guide/C/img/ch2-theme-eazel.png diff --git a/user-guide/C/img/ch2-view-layout-menu.png b/user-guide/C/img/ch2-view-layout-menu.png Binary files differnew file mode 100644 index 000000000..3094ebf84 --- /dev/null +++ b/user-guide/C/img/ch2-view-layout-menu.png diff --git a/user-guide/C/img/ch3-account-info.png b/user-guide/C/img/ch3-account-info.png Binary files differnew file mode 100644 index 000000000..81f40e99f --- /dev/null +++ b/user-guide/C/img/ch3-account-info.png diff --git a/user-guide/C/img/ch3-online-storage.png b/user-guide/C/img/ch3-online-storage.png Binary files differnew file mode 100644 index 000000000..a26c7e3f3 --- /dev/null +++ b/user-guide/C/img/ch3-online-storage.png diff --git a/user-guide/C/img/ch3-package-titles.png b/user-guide/C/img/ch3-package-titles.png Binary files differnew file mode 100644 index 000000000..d4a9e3ca5 --- /dev/null +++ b/user-guide/C/img/ch3-package-titles.png diff --git a/user-guide/C/img/ch3-sign-up.png b/user-guide/C/img/ch3-sign-up.png Binary files differnew file mode 100644 index 000000000..823f2aa0a --- /dev/null +++ b/user-guide/C/img/ch3-sign-up.png diff --git a/user-guide/C/img/ch3-welcome-screen.png b/user-guide/C/img/ch3-welcome-screen.png Binary files differnew file mode 100644 index 000000000..213758fcf --- /dev/null +++ b/user-guide/C/img/ch3-welcome-screen.png diff --git a/user-guide/C/img/install-update.png b/user-guide/C/img/install-update.png Binary files differnew file mode 100644 index 000000000..cd2e9db44 --- /dev/null +++ b/user-guide/C/img/install-update.png diff --git a/user-guide/C/img/install-user-level.png b/user-guide/C/img/install-user-level.png Binary files differnew file mode 100644 index 000000000..5b092f86e --- /dev/null +++ b/user-guide/C/img/install-user-level.png diff --git a/user-guide/C/sgml/chapter-1.sgml b/user-guide/C/sgml/chapter-1.sgml new file mode 100644 index 000000000..a512d2fba --- /dev/null +++ b/user-guide/C/sgml/chapter-1.sgml @@ -0,0 +1,995 @@ +<chapter id="ch1">
+ <title>File Management</title>
+
+
+ <para>
+ This chapter presents the basic elements of the
+ Nautilus file manager, and its basic file functions
+ and features. Nautilus is designed to make file
+ management transparent and intuitive-and, in
+ the process, more productive.
+ </para>
+
+ <para>
+ Chapter One is presented in five sections:
+ <itemizedlist>
+
+ <listitem><para>
+ Launching Nautilus
+ </para></listitem>
+
+ <listitem><para>
+ Nautilus Elements
+ </para></listitem>
+
+ <listitem><para>
+ Navigating and Viewing Your System
+ </para></listitem>
+
+ <listitem><para>
+ Navigating the Network
+ </para></listitem>
+
+ <listitem><para>
+ Manipulating Files
+ </para></listitem>
+
+ </itemizedlist>
+
+ </para>
+
+
+
+ <sect1 id="ch1-launching">
+ <title>Launching Nautilus</title>
+
+ <para>
+ Nautilus can be launched from three locations:
+ from the GNOME main menu, where the Nautilus
+ menu item can be found under Applications; from
+ the GNOME desktop itself; or from the Panel.
+ </para>
+
+ <figure>
+ <title>Nautilus Icon</title>
+ <graphic fileref="ch1-nautiluslogo" scale="50"></graphic>
+ </figure>
+
+ <para>
+ If you wish to put the Nautilus icon (Figure 1), on
+ your desktop, select the Nautilus menu item and,
+ holding down the left mouse button, drag it to the
+ desktop.
+ </para>
+
+ <para>
+ Probably the easiest way to launch Nautilus is
+ from the GNOME panel (Figure 2). To place the
+ icon there, drag the menu item, as above, to an
+ empty space on the panel at the bottom of the
+ screen. This method has the advantage of speed:
+ the panel is nearly always present, and is at most
+ only a click away. The icon itself needs only one
+ click to launch Nautilus.
+ </para>
+
+ <figure>
+ <title>The Nautilus Icon on the Panel, between Netscape and the Pager</title>
+ <graphic fileref="ch1-panel" scale="50"></graphic>
+ </figure>
+
+ <para>
+ To launch Nautilus, click once on the menu item,
+ or panel icon, or twice on the desktop icon.
+ </para>
+
+ </sect1>
+
+ <sect1 id="ch1-elements">
+ <title>Nautilus Elements</title>
+
+ <para>
+ The major elements of the Nautilus file manager
+ include, in the upper part, the menu bar, tool bar
+ and location bar, and below, the sidebar and the
+ main window (Figure 3).
+ </para>
+
+ <para>
+ The menu bar is used to access the pull-down
+ menus, which are the most complete source of
+ Nautilus tools and features. The tool bar provides
+ quick access to Nautilus most common
+ navigation and search tools, and Eazel Services.
+ The location bar displays system directory
+ location, LAN location, and Internet location-
+ depending on where Nautilus is looking at the
+ given moment.
+ </para>
+
+ <para>
+ The main window is the main viewing area for the
+ systems directories and files, as well as the area
+ where directories and files are generally manipu-
+ lated. It is capable of showing files in several
+ formats, and includes file information such as
+ size, type, and date last modified.
+ </para>
+
+ <figure>
+ <title>Main Nautilus Elements</title>
+ <graphic fileref="ch1-icon-view-demo" scale="50"></graphic>
+ </figure>
+
+ <para>
+ The sidebar provides a tree view of directories
+ and sub-directories, as well as a history view
+ (recently viewed files and directories), and a
+ variety of Linux help documents.
+ </para>
+
+ </sect1>
+
+ <sect1 id="ch1-navigation">
+ <title>Navigating and Viewing The System</title>
+
+
+ <para>
+ Nautilus offers several methods to navigate the
+ system. Typing a directory address into the
+ location bar will point Nautilus toward that
+ location. The directional arrows on the tool bar
+ provide a simpler method to navigate back,
+ forward, and up through the system: they function
+ exactly as in a browser. Clicking on a directory
+ icon in the main window will open that directory.
+ Finally, clicking the collapsible branches of the
+ sidebars tree view allows the user to graphically
+ view and navigate the directory tree.
+ </para>
+
+ <para>
+ The file manager minimizes the necessity of
+ opening applications by identifying many file
+ types graphically. Viewer components allow
+ several common document types to be displayed
+ without launching a separate application, and a
+ zoom feature provides one-click zooming in and
+ out in the main window. Sound files in certain
+ common formats can even be previewed by
+ simply passing the mouse over the file icon.
+ </para>
+
+ <sect2 id="ch1-navigation-hardware">
+ <title>The Initial Screen and Hardware Overview</title>
+
+ <para>
+ The first screen to appear (Figure 4), shows the
+ contents of your home directory (note: the first screen
+ will be the Nautilus sub-directory if the Beginner mode was
+ selected). In this example,
+ the user has logged in under their own name-
+ John-so the home directory is /home/john.
+ Linux follows the UNIX convention for home
+ directories: if the user had logged in as Susan, the
+ home directory would be /home/susan; when
+ logged in as the root user, the home directory is root.
+ </para>
+
+ <para>
+ The file manager identifies this directory in two
+ ways: as a traditional command line directory
+ address in the location bar, and as a captioned
+ folder icon in the sidebar.
+ </para>
+
+ <figure>
+ <title>The Start Screen</title>
+ <graphic fileref="ch1-icon-view-150" scale="50"></graphic>
+ </figure>
+
+ <para>
+ Among the contents of the screen are a Nautilus
+ folder. This folder, when clicked, takes the user to
+ /home/john/Nautilus, Figure 5. Among the
+ contents of the folder are: a small HTML file
+ containing information about Nautilus; a services
+ icon which, when double-clicked, takes you
+ directly to Eazel Services (covered in Chapter
+ Three), and a computer icon which leads to a
+ Hardware Overview of your system, Figure 6.
+ </para>
+
+ <figure>
+ <title>The Contents of /home/john/Nautilus, with the Computer and
+ Services Icons.</title>
+ <graphic fileref="ch1-home" scale="50"></graphic>
+ </figure>
+
+ <para>
+ The hardware overview shows the details of the
+ computers central processor unit, including the
+ manufacturer, the model, the calculated speed in
+ MHz and the cache size. It also shows the amount
+ of system RAM, and the models of the hard
+ drive(s) and CD player.
+ </para>
+
+ <figure>
+ <title>Hardware Overview, Showing an AMD Processor and 55MB of RAM</title>
+ <graphic fileref="ch1-hardware" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+
+ <sect2 id="ch1-navigation-refresh">
+ <title>Using the Navigation, Refresh and Home Buttons</title>
+
+ <para>
+ The navigation buttons on the left side of the tool
+ bar-Back, Forward, Up, Refresh and Home-are
+ used in a similar way to the navigation buttons on
+ a web browser (Figure 7).
+ </para>
+
+ <figure>
+ <title>Navigation Arrows on the Tool Bar</title>
+ <graphic fileref="ch1-toolbar" scale="50"></graphic>
+ </figure>
+
+ <para>
+ The three left-most buttons allow navigation
+ through the file system by both time and
+ direction.
+ </para>
+
+ <para>
+ The back and forward buttons allow the user to
+ revisit directories and files which the user has
+ already accessed during the current session. This
+ is navigation through time. The previous example
+ illustrates this: clicking on the back button from
+ the hardware overview screen will take the user
+ back to the /home/john screen, but once there,
+ the back button will be dimmed out: there is no
+ further back in time to go in this session.
+ </para>
+
+ <para>
+ Similarly, clicking the forward button at this point
+ would take the user once again to the /home/
+ john/Nautilus screen.
+ </para>
+
+ <para>
+ The up button navigates upward through the
+ directory hierarchy. This is navigation by
+ direction. As an example, in the previous section
+ it is impossible-solely with the back button-to
+ go up through the file system further than /home/
+ john. However, by clicking the up button, the user
+ can navigate first to /home, and then all the way
+ to /.
+ </para>
+
+ <para>
+ Clicking the refresh button refreshes the view of
+ the current directory.
+ </para>
+
+ <para>
+ The home button will always take the user to the
+ current sessions home directory. If the user has
+ logged on as root, then the home button, when
+ clicked, will open /root. If the user has logged on
+ as Laura, the directory opened will be /home/
+ laura. Note: if the user is running in Beginner mode,
+ clicking the home button will open the Nautilus sub-directory.
+ This is, as are so many features in
+ Nautilus, customizable-see Chapter Two.
+ </para>
+
+ </sect2>
+
+ <sect2 id="ch1-navigation-icons-list">
+ <title>Viewing as Icons, or as a List</title>
+
+ <para>
+ Although directories and files are by default
+ viewed, in the main window, as icons, there is
+ some advantage to viewing them as a list. At a
+ normal magnification level, more information will
+ be displayed in list view, such as the files type
+ and modification date. To change the view style,
+ click on the View as Icons button, to the bottom-right
+ of the tool bar (Figure 8), and choose List.
+ </para>
+
+ <figure>
+ <title>View as Icons Button</title>
+ <graphic fileref="ch1-view-as" scale="50"></graphic>
+ </figure>
+
+ <para>
+ The list view still includes representative icons,
+ but the extra space used by the extra description
+ means the icons must be minimized. The Date
+ Modified column is particularly clear, with
+ descriptive terms used where the latest modifi-
+ cation of the file or directory is within the last
+ week (Figure 9).
+ </para>
+
+
+ <figure>
+ <title>List View, with Descriptive Dates under Date Modified</title>
+ <graphic fileref="ch1-list-mydoc" scale="50"></graphic>
+ </figure>
+
+
+ </sect2>
+
+
+ <sect2 id="ch1-navigation-tree">
+ <title>Using Tree View in the Sidebar</title>
+
+ <para>
+ Tree view refers to a collapsible list of directories,
+ sub-directories and files. In Nautilus, it is
+ available in the sidebar. The advantage of tree
+ view is that it allows the user to clearly observe
+ the directory structure at a glance, thus simplifying
+ directory and file administration.
+ </para>
+
+ <para>
+ To activate tree view, click the Tree tab at the
+ bottom of the sidebar screen. At first, the tree
+ may be collapsed, showing a single folder (Figure
+ 10).
+ </para>
+
+ <figure>
+ <title>Collapsed Tree View at Root</title>
+ <graphic fileref="ch1-tree-slash" scale="50"></graphic>
+ </figure>
+
+ <para>
+ To expand the directory structure, click once on
+ the right arrow pointing toward the folder. The
+ arrow will immediately point down, and the root
+ directories appear in the sidebar. Clicking any
+ sub-directory arrow will expand that sub-
+ directory, but not automatically expand the view
+ in the main window. Notice in Figure 11 that
+ although the tree in the sidebar is expanded to /T/
+ ARCHIVE/Redhat/ETC, the main window and
+ the location bar are still showing the folders
+ within /home/john.
+ </para>
+
+ <para>
+ (Also notice that, when necessary, vertical and
+ horizontal scroll bars appear automatically on the
+ sidebar panels).
+ </para>
+
+ <figure>
+ <title>Different Views and Different Directories in Different Panels: Tree
+ View of /T/ARCHIVE/Redhat/ETC on the Left, Icon View of /home/john
+ on the Right.</title>
+ <graphic fileref="ch1-home-john" scale="50"></graphic>
+ </figure>
+
+ <para>
+ To synchronize the displays-that is, to display
+ the contents of the same directory in both the
+ sidebar and the main window-simply click on
+ the desired folder icon in the sidebars tree view
+ (Figure 12). In this illustration, the user has
+ clicked on the icon representing the directory
+ /demo in the sidebar. Both the location bar and
+ the main window now reflect this location, with
+ the main window displaying the contents of the
+ demo directory in icon view.
+ </para>
+
+ <figure>
+ <title>Different Views but Identical Directories: Tree View of /demo on
+ the Left, Icon View of /demo on the Right.</title>
+ <graphic fileref="ch1-tree-demo" scale="50"></graphic>
+ </figure>
+
+ <para>
+ Exploring the directory tree within the sidebar
+ alone is usually faster than exploring it within the
+ main window. To expand directories without
+ updating the main window, click on the small
+ right arrows in tree view. In the example shown in
+ Figure 13, the /etc directory has been expanded,
+ as has the /X11 subdirectory. Beneath that are
+ several more subdirectories, and the XF86Config
+ file, which configures the X server.
+ </para>
+
+ <figure>
+ <title>Expanded Directories in Tree View</title>
+ <graphic fileref="ch1-tree-etc" scale="50"></graphic>
+ </figure>
+
+ <para>
+ There may be times when the directory tree is so
+ expanded, the user may lose sight of the upper
+ branches. In such a situation, the user can either
+ scroll with the horizontal scroll bar at the bottom
+ of the sidebar, or, by holding down the left mouse
+ button, enlarge the sidebar by dragging its right-
+ hand edge into the main window area.
+ </para>
+
+ </sect2>
+
+
+ <sect2 id="ch1-navigation-zooming">
+ <title>Zooming in the Main Window</title>
+
+ <para>
+ In a screen crowded with directory and file icons,
+ the user may wish to zoom in to confirm a file
+ name or type. The zoom feature enables this
+ within the main window.
+ </para>
+
+ <para>
+ Figure 14 is an example of a screen crowded with
+ icons; it is the doc sub-directory containing the
+ XFree86 server documentation for various
+ graphics cards.
+ </para>
+
+
+ <figure>
+ <title>A Cluttered Main Window</title>
+ <graphic fileref="ch1-tree-doc-1" scale="50"></graphic>
+ </figure>
+
+ <para>
+ Somewhere in the window is the README file
+ for the Chips & Technology graphics card. To use
+ the zoom feature to find this more easily, the user
+ simply clicks on the + sign of the zoom control
+ to the right of the location bar (Figure 15).
+ </para>
+
+
+ <figure>
+ <title>The Zoom Control</title>
+ <graphic fileref="ch1-zoom-control" scale="50"></graphic>
+ </figure>
+
+ <para>
+ The result-shown in Figure 16, after two clicks
+ on the + sign, bringing magnification up to
+ 150%-is a far more easily read display, with the
+ various graphics card types clearly identifiable.
+ The Chips & Technology README file is on the
+ left. This example also shows how greater magnification
+ leads to more file and directory information displayed.
+ </para>
+
+
+ <figure>
+ <title>The View Enlarged to 150%</title>
+ <graphic fileref="ch1-tree-doc" scale="50"></graphic>
+ </figure>
+
+ <para>
+ There may be times, especially on computers with
+ large displays, when, instead of using the vertical
+ scroll bar to find a file or directory, it may be
+ faster to zoom out, and view a larger area. To do
+ this, click on the minus sign to the left of the plus
+ sign.
+ </para>
+
+ </sect2>
+
+ <sect2 id="ch1-navigation-viewing">
+ <title>Viewing and Opening Files Within Nautilus</title>
+
+ <para>
+ Certain common file types can be identified, read,
+ or, in the case of music files, heard, from within
+ Nautilus, without having to open the files application.
+ </para>
+
+ <para>
+ Graphics files of many common types are represented as thumbnails--realistic iconic representations of their content. To inspect them more closely, without opening their related application,
+ the user can enlarge them using the zoom feature.
+ </para>
+
+ <para>
+ Other types of files use different viewing
+ methods. Many text files can be read just by
+ clicking on them once in the main window. This is
+ both faster than opening up a separate console, or
+ application, and it also uses fewer system
+ resources. Figure 17 shows an example using the
+ README.chips file.
+ </para>
+
+ <figure>
+ <title>Displaying a README Text File in the Main Window</title>
+ <graphic fileref="ch1-README" scale="50"></graphic>
+ </figure>
+
+ <para>
+ Common types of music files can be heard via
+ your computers sound system by simply hovering
+ over the files icon with the mouse. For more
+ control, the view button to the right of the
+ location bar can be set to View as Music. The
+ main window will display the music files only, by
+ track, title, artist, bitrate and time, and also show
+ a button-activated music player (Figure 18).
+ </para>
+
+ <figure>
+ <title>Music Player and an MP3 File</title>
+ <graphic fileref="ch1-music-control" scale="50"></graphic>
+ </figure>
+
+ <para>
+ Table 1 lists file types that can be viewed, or
+ listened to, within Nautilus, without the necessity
+ of opening their normal applications.
+ </para>
+
+ <table frame="all">
+ <title></title>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>View</entry>
+ <entry>File Types</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Icon/entry</entry>
+ <entry>Files and Folders</entry>
+ </row>
+
+
+ <row>
+ <entry>List</entry>
+ <entry>Files and Folders</entry>
+ </row>
+
+
+ <row>
+ <entry>Music</entry>
+ <entry>MP3</entry>
+ </row>
+
+
+ <row>
+ <entry>Web Page</entry>
+ <entry>HTML, including MAN pages, info pages and DocBook SGML</entry>
+ </row>
+
+
+ <row>
+ <entry>Text</entry>
+ <entry>ASCII Text Files and HTML source</entry>
+ </row>
+
+
+ <row>
+ <entry>Image</entry>
+ <entry>JPEG, PNG, etc.</entry>
+ </row>
+
+
+ <row>
+ <entry>Package</entry>
+ <entry>RPM Packages</entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+
+ </sect2>
+
+ <sect2 id="ch1-navigation-launching-apps">
+ <title>Launching Applications within Nautilus</title>
+
+ <para>
+ Files can be opened, edited, and saved by
+ launching their applications from within Nautilus.
+ This is accomplished by positioning the mouse
+ over the file, and clicking the right button. In the
+ menu that appears, clicking on Open With
+ brings up a sub-menu of application choices, from
+ which the user can choose. Figure 19 shows an
+ example, where a graphics file has been selected
+ and opened with The Gimp.
+ </para>
+
+
+ <figure>
+ <title>Opening a Graphic File by Launching its Application from within
+ Nautilus</title>
+ <graphic fileref="ch1-open-with" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+
+ </sect1>
+
+
+ <sect1 id="ch1-network">
+ <title>Navigating the Network</title>
+
+ <para>
+ Nautilus has full network capability, both on the
+ LAN and on the Internet. It can connect to FTP
+ and web servers, local and remote, and to
+ mounted Samba shares.
+ </para>
+
+ <para>
+ Nautilus unique design includes elements of a
+ web browser as well as a traditional file manager.
+ As a result, Nautilus can browse the web, and
+ also graphically browse the machines of a typical
+ mixed corporate LAN running a combination of
+ Windows, Linux and UNIX machines.
+ </para>
+
+ <para>
+ Nautilus primary methods of connection are
+ shown in Figure 20.
+ </para>
+
+ <figure>
+ <title>Methods of Connection in a Mixed Environment</title>
+ <graphic fileref="ch1-connect" scale="50"></graphic>
+ </figure>
+
+ <sect2 id="ch1-network-ftp">
+ <title>Navigating the LAN via FTP</title>
+
+ <para>
+ Nautilus connects to a mixed LAN via local FTP
+ and mounted Samba shares.
+ </para>
+
+ <para>
+ To connect to a local Linux or UNIX FTP server,
+ type in the complete host name of that
+ machine in the location bar. As an example, to
+ connect to a machine called toshiba.jpl, the user
+ would type:
+<programlisting>
+ftp://toshiba.jpl
+</programlisting>
+ and hit Enter. In Figure 21, the user has logged in
+ anonymously to the /home/ftp directory of
+ toshiba.jpl.
+ </para>
+
+
+ <figure>
+ <title>FTP login to a Linux Machine on the LAN</title>
+ <graphic fileref="ch1-slash" scale="50"></graphic>
+ </figure>
+
+ <para>
+ In this example, red emblems signifying read and
+ write protected folders appear in the main
+ windows. This confirms the anonymous login. An
+ attempt to view the contents of a read protected
+ folder, for example, /bin, results in the screen
+ shown in Figure 22.
+ </para>
+
+
+ <figure>
+ <title>Inadequate Permissions</title>
+ <graphic fileref="ch1-inadequate-permissions" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+
+ <sect2 id="ch1-network-samba">
+ <title>Navigating the LAN via Samba</title>
+
+ <para>
+ To connect to a Windows machine on the LAN,
+ the user must first be running Samba and have
+ configured the Windows machine, and must
+ finally have mounted the Samba mountpoint on
+ the host machine.
+ </para>
+
+ <para>
+ Once configured, typing in the mountpoint in the
+ location bar reveals the directories and files on
+ the Windows machine. In the example in Figure
+ 23, the user has navigated to the /samba
+ directory on the Windows machine accessed
+ through the HP mountpoint.
+ </para>
+
+
+ <figure>
+ <title>Accessing a Windows Machine on a Mixed LAN, via a Samba
+ Mountpoint</title>
+ <graphic fileref="ch1-samba" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+
+ <sect2 id="ch1-network-internet">
+ <title>Navigating the Internet</title>
+
+ <para>
+ Nautilus connects to the Internet in the same way
+ as a web browser. Both FTP sites and web sites
+ are accessed by simply typing the URL into the
+ location bar. Figure 24 gives an illustration, the
+ users having connected to www.cnn.com.
+ </para>
+
+
+ <figure>
+ <title>Nautilus as Web Browser</title>
+ <graphic fileref="ch1-cnn" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+
+
+ <sect2 id="ch1-network-history">
+ <title>The Sidebar History and Bookmarks</title>
+
+ <para>
+ When viewing the web, the navigation tools on
+ the tool bar function as they do on any browser. In
+ addition, both the History tab at the bottom of the
+ sidebar, and the Go drop-down menu, provide a
+ session history of local and remote accesses
+ (Figure 25).
+ </para>
+
+
+ <figure>
+ <title>The Sidebar History and Go Menu</title>
+ <graphic fileref="ch1-history" scale="50"></graphic>
+ </figure>
+
+ <para>
+ Bookmarks can also lead to local and remote
+ machines, Samba shares and web sites. They are
+ found by clicking on Bookmarks on the menu bar,
+ where the menu items for adding and editing
+ bookmarks are also located.
+ </para>
+
+ </sect2>
+ </sect1>
+
+ <sect1 id="ch1-files">
+ <title>Manipulating Files</title>
+
+ <para>Manipulating directories and files is one of the
+ most basic of all file manager features. Nautilus
+ can be used to graphically move, copy, duplicate,
+ rename and delete files, and to create new and
+ rename existing directories. It can also be used as
+ a search engine, on the local machine, the LAN,
+ and the web. Finally, in Nautilus the user can
+ graphically change a files permissions-a great
+ advance over the command line CHMOD method.
+ </para>
+
+ <sect2 id="ch1-files-moving">
+ <title>Moving and Copying Files</title>
+
+ <para>
+ These two file management activities are
+ performed by opening two Nautilus windows, one
+ for the source location and one for the destination.
+ </para>
+
+ <para>
+ Open a new Nautilus window by clicking on File
+ on the menu bar, and choosing the first menu
+ item: New Window (Figure 26).
+ </para>
+
+
+ <figure>
+ <title>Opening a New Window in Nautilus</title>
+ <graphic fileref="ch1-new-window" scale="50"></graphic>
+ </figure>
+
+
+ <para>
+ To move a file, simply drag it from the source
+ window to the destination window, with the left
+ mouse button depressed. For options, drag the file
+ with the right mouse button: this gives the choices
+ of either moving or copying the file, or of
+ creating a link.
+ </para>
+
+ <para>
+ An example of a successful file copy operation is
+ shown in Figure 27. The pluck.wav file has been
+ copied from the /home/john directory (the
+ source), in the lower-right Nautilus window, to
+ the /home/john/music directory, in the upper-left
+ Nautilus window.
+ </para>
+
+
+ <figure>
+ <title>The Successful Copy of a File from /home/john to /home/john/
+ music</title>
+ <graphic fileref="ch1-pluck" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+
+ <sect2 id="ch1-files-duplicating">
+ <title>Duplicating, Renaming and Deleting Files, and Creating
+ Directories</title>
+
+ <para>
+ Duplicating a file is accomplished by either
+ clicking on the file with the right mouse button,
+ and selecting Duplicate, or by first selecting the
+ file and then selecting Duplicate from the File
+ pull-down menu on the menu bar (Figure 28).
+ Notice in the illustration that the duplicate file is
+ identified by the tag (copy) next to the file name.
+ </para>
+
+
+ <figure>
+ <title>Successful Duplication of the testement.jpg File</title>
+ <graphic fileref="ch1-duplicate" scale="50"></graphic>
+ </figure>
+
+
+ <para>
+ Renaming a file is accomplished in a similar
+ manner. Choose the same menu by either means,
+ and click on Rename. Then simply type the new
+ name into the file caption.
+ </para>
+
+ <para>
+ Deleting a file, in Nautilus, means moving it to
+ the trash folder which Nautilus creates upon
+ installation. A file may be deleted either by
+ dragging and dropping it into the trash folder, or
+ by selecting the file, opening the same menu as
+ above, and choosing Move to Trash.
+ </para>
+
+ <para>
+ Note that moving a file to the trash folder does
+ not delete it from the system. It is still available,
+ and can still be retrieved, in case the user has
+ trashed it mistakenly. Permanent file deletion is
+ accomplished by clicking the Empty Trash item in
+ the File menu.
+ </para>
+
+ <para>
+ A new subdirectory can be created (and/or
+ renamed), anywhere in the directory tree, by
+ selecting the parent directory and then pulling
+ down the File menu from the menu bar. Click on
+ New Folder, and the new subdirectory is created.
+ Just type in the name and hit the Enter key.
+ </para>
+
+ </sect2>
+
+ <sect2 id="ch1-files-find-search">
+ <title>File Find and Web Search</title>
+
+ <para>
+ Nautilus' two search features, found on the tool
+ bar, enable the user both to find files on the local
+ machine and on mounted Samba shares, and to
+ locate information on the web.
+ </para>
+
+ <para>
+ To search for a file either locally or on a Samba
+ LAN, click the Find button on the tool bar, and
+ type in the name of the desired file. Then click
+ the Find Them button.
+ </para>
+
+ <para>
+ This is the simplest form of file search, but by
+ clicking the More Options button-several
+ times-no fewer than seven search variables
+ become available. Each variable in turn has its
+ own set of constraints. In this way it is possible to
+ narrow down, or refine a search very precisely
+ (Figure 29).
+ </para>
+
+ <figure>
+ <title>File Searching Expanded to the Maximum Degree Possible</title>
+ <graphic fileref="ch1-complex-search" scale="50"></graphic>
+ </figure>
+
+ <para>
+ To search for information on the web, click on
+ the Web Search button on the tool bar. Nautilus is
+ transformed into a web browser, and Google is
+ presented in the main window (Figure 30).
+ </para>
+
+
+ <figure>
+ <title>The Google Search Engine, Launched from within Nautilus.</title>
+ <graphic fileref="ch1-google" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+
+ <sect2>
+ <title>Changing File Permissions</title>
+
+ <para>
+ To change a file's permissions, click with the
+ right mouse button on the file, and choose Show
+ Properties from the menu. The dialog box which
+ appears has three tabs. Choose the one labelled:
+ Permissions (Figure 31). Both the file's owner
+ and group settings can be changed, as can the
+ read, write, and execute permissions for each setting.
+ The text view and numeric view of the result
+ are automatically updated at the bottom of the box.
+ </para>
+
+ <figure>
+ <title>Changing File Permissions Graphically</title>
+ <graphic fileref="ch1-permissions" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+
+ <sect2>
+ <title>Getting Help</title>
+
+ <para>
+ This Users Manual is available from both the
+ Help item on the menu bar, and from the Help
+ Contents tab at the bottom of the sidebar.
+ </para>
+
+ <para>
+ In addition to this manual, the Help Contents tab
+ provides easy access to many other Linux help
+ files in several different formats.
+ </para>
+
+
+ </sect2>
+
+ </sect1>
+
+
+</chapter>
+
diff --git a/user-guide/C/sgml/chapter-2.sgml b/user-guide/C/sgml/chapter-2.sgml new file mode 100644 index 000000000..d073b3157 --- /dev/null +++ b/user-guide/C/sgml/chapter-2.sgml @@ -0,0 +1,475 @@ +<chapter id="ch2">
+ <title>Customizing the Nautilus Interface</title>
+
+
+ <para>
+ Nautilus has been designed to be highly configurable,
+ both to suit the desire of users for customized decor,
+ and to suit the needs of users at
+ different levels of expertise.
+ </para>
+
+ <para>
+ Chapter two is presented in four sections:
+ <itemizedlist>
+
+ <listitem><para>
+ Choosing and Customizing User Settings
+ </para></listitem>
+
+ <listitem><para>
+ Customizing File Layout and Icon Appearance
+ </para></listitem>
+
+ <listitem><para>
+ Configuring Applications
+ </para></listitem>
+
+ <listitem><para>
+ Customizing Nautilus Appearance
+ </para></listitem>
+
+ </itemizedlist>
+ </para>
+
+
+ <sect1 id="ch2-settings">
+ <title>Choosing and Customizing User Settings</title>
+
+ <para>
+ User settings
+ control performance and design variables, as well
+ as certain appearance variables that are related
+ more toward system function than simple decor.
+ </para>
+
+ <para>
+ There are three levels of user settings to choose
+ from: beginner, intermediate, and advanced; the
+ level of information displayed increasing with
+ each step. In addition, the two higher-level
+ settings are both highly customizable.
+ </para>
+
+ <sect2 id="ch2-settings-accessing">
+ <title>Accessing and Choosing User Settings</title>
+
+ <para>
+ To access user settings, click the colored icon on
+ the far right of the menu bar (Figure 1).
+ </para>
+
+
+ <figure>
+ <title>Accessing User Settings</title>
+ <graphic fileref="ch2-ski-intermediate-menu" scale="50"></graphic>
+ </figure>
+
+ <para>
+ The drop-down menu presents the three levels of
+ choices, and the choice of customizing the inter-
+ mediate and advanced levels.
+ </para>
+
+ <para>
+ Figure 2 and 3 present the most obvious of the
+ differences between the default beginner or intermediate,
+ and the advanced display settings. In
+ both cases Nautilus is looking at the /home/john
+ directory. Home directories typically have a
+ number of hidden files. In Figure 2, at the
+ beginner (or intermediate) setting, only four
+ directories are visible. In Figure 3, at the
+ advanced setting, an additional 15 hidden directories
+ are visible.
+ </para>
+
+
+
+ <figure>
+ <title>Four Directories Visible at the Intermediate User Setting</title>
+ <graphic fileref="ch2-photos-john" scale="50"></graphic>
+ </figure>
+
+ <figure>
+ <title>The Same Directory at the Advanced User Setting, Showing Fifteen
+ Hidden Files</title>
+ <graphic fileref="ch2-john" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+
+ <sect2 id="ch2-settings-editing">
+ <title>Editing User Settings</title>
+
+ <para>
+ The Edit Settings menu item, which is used to edit
+ the intermediate and advanced user levels,
+ presents the same choices for both. The choices
+ are listed under six headings:
+
+ <itemizedlist>
+
+ <listitem><para>
+ Folder Views
+ </para></listitem>
+
+ <listitem><para>
+ Sidebar Panels
+ </para></listitem>
+
+ <listitem><para>
+ Appearance
+ </para></listitem>
+
+ <listitem><para>
+ Speed Trade-offs
+ </para></listitem>
+
+ <listitem><para>
+ Search
+ </para></listitem>
+
+ <listitem><para>
+ Navigation
+ </para></listitem>
+ </itemizedlist>
+
+ </para>
+
+ <para>
+ Figure 4 shows the choices in the first heading:
+ Folder Views. Here the user can choose to have
+ Nautilus open a file in a separate window, activate
+ items with a single or a double click, and display
+ hidden and backup files.
+ </para>
+
+ <figure>
+ <title>Customizing Directory Views</title>
+ <graphic fileref="ch2-edit-settings-folder" scale="50"></graphic>
+ </figure>
+
+ <para>
+ The next heading down the list, Sidebar Panels,
+ lets the user choose which panels should appear in
+ the sidebar. Appearance, the third heading, allows
+ the user to choose between smoother (but
+ slower) graphics, or rough edges and speed. It
+ also allows a choice of fonts with which to
+ display file names and other information.
+ </para>
+
+ <para>
+ Search (Figure 5), lets users configure the file
+ manager to search for files by text only, or also by
+ their properties (slower), to optionally do slow,
+ complete searches, and to change, if desired,
+ Nautilus default web search location.
+ </para>
+
+ <para>
+ The Navigation heading allows the user to change
+ the local machines default home location, and
+ also allows the user to setup an HTTP proxy.
+ </para>
+
+ <figure>
+ <title>Customizing Search Features: Complexity, Speed and Location</title>
+ <graphic fileref="ch2-search-settings" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+ </sect1>
+
+ <sect1 id="ch2-file">
+ <title>Customizing File Layout and Icon Appearance</title>
+
+ <para>
+ The layout of files in the main window can be a
+ major factor in the ease and speed of file identification.
+ The default method of laying out files,
+ alphabetically according to file names, is appropriate
+ under certain conditions, i.e.: when the
+ files in a directory are all of a similar type, with
+ well designed names following a similar pattern.
+ However, file identification using this layout can
+ be tedious and difficult in a directory holding
+ large numbers of files of disparate types, and
+ without an obvious naming convention.
+ </para>
+
+ <sect2 id="ch2-file-layout">
+ <title>Choices in File Layout</title>
+
+ <para>
+ Nautilus addresses this issue by giving the user
+ several choices of file layout. Figure 6 shows the
+ Lay out items pull-down sub-menu (under View), the
+ range of layout choices available, and a directory
+ with several different file types arranged alpha-
+ betically.
+ </para>
+
+
+ <figure>
+ <title>Layout Choices, and an Unoptimized Alphabetical Layout</title>
+ <graphic fileref="ch2-view-layout-menu" scale="50"></graphic>
+ </figure>
+
+ <para>In this example, a more sensible layout would be
+ by type. The result of this choice of layout
+ is shown in Figure 7.
+ </para>
+
+ <figure>
+ <title>A More Logical Layout, by Type</title>
+ <graphic fileref="ch2-home-john-mydoc" scale="50"></graphic>
+ </figure>
+
+ <para>
+ Once a method of layout is chosen, the presentation
+ can be further optimized with the Use
+ Tighter Layout and Reversed Order options.
+ </para>
+
+ </sect2>
+
+ <sect2 id="ch2-file-icons">
+ <title>Customizing Icon Captions</title>
+
+ <para>
+ Icon captions and appearance can also be
+ adjusted. A file caption must always start with the
+ file name; however, both the type of information
+ and the order of information displayed beneath
+ file names can be manipulated.
+ </para>
+
+ <para>
+ The Icon Captions menu item is found under Edit
+ on the tool bar. When clicked, it displays the Icon
+ Captions menu, Figure 8.
+ </para>
+
+
+ <figure>
+ <title>Determining the Order of Icon Information</title>
+ <graphic fileref="ch2-icon-captions-alone" scale="50"></graphic>
+ </figure>
+
+
+ <para>
+ The three menu-buttons reflect the order of information
+ displayed in the icon caption. Each button
+ displays identical information, from file size to
+ MIME type, ten types of information in all. The
+ type chosen by the top button will appear first,
+ beneath the file name, the type chosen by the
+ second will appear next, etc. Figure 9 shows an
+ enlarged file image (to 400%), with the captioned
+ information reflecting the order in the accompanying
+ Icon Caption sub-menu.
+ </para>
+
+
+ <figure>
+ <title>Size, Date Modified, Type</title>
+ <graphic fileref="ch2-icon-captions" scale="50"></graphic>
+ </figure>
+
+
+ </sect2>
+
+ <sect2 id="ch2-file-diff">
+ <title>Differentiating a Directory with a Customized Icon</title>
+
+ <para>
+ The actual appearance of an icon can be replaced
+ by another useful if, for instance, you want to
+ identify a certain directory by the type of files it
+ contains. The method used is to drag and drop the
+ icon in the main window which you want for a
+ replacement, to the icon in the sidebar that you
+ want to replace. An example can be seen in Figure
+ 10, where an icon representing a portrait of
+ Beethoven has been used to identify the music
+ directory.
+ </para>
+
+ <figure>
+ <title>Identifying a Folder with Another Files Icon</title>
+ <graphic fileref="ch2-music" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+
+ <sect2 id="ch2-file-emblems">
+ <title>Adding Emblems</title>
+
+ <para>
+ Icon appearance can also be enhanced by the use
+ of emblems. Click on a file with the right mouse
+ button, and choose Show Properties. In the
+ resulting properties window, click the middle tab,
+ Emblems. Any and all of the emblems may be
+ added to a files iconic appearance. In the
+ example shown in Figure 11, the Draft emblem
+ has been added to a text file.
+ </para>
+
+ <figure>
+ <title>Adding an Emblem to an Icon</title>
+ <graphic fileref="ch2-emblems" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+ </sect1>
+
+ <sect1 id="ch2-configuring">
+ <title>Configuring Applications</title>
+
+ <para>
+ As we have seen in Chapter One, a file can easily
+ be opened by its application from within Nautilus,
+ relieving the user of the tedious extra steps of
+ first starting the application, then finding the
+ desired file. Nautilus does this by assigning
+ certain adefault applications to certain file types.
+ This too is customizable by the user.
+ </para>
+
+ <para>
+ Clicking on a file--in the example below, a JPEG
+ file--with the right mouse button, brings up a
+ menu with the item, Open With. Moving the
+ mouse pointer to this opens a sub-menu (Figure 12).
+ </para>
+
+ <figure>
+ <title>The Open With Sub-Menu</title>
+ <graphic fileref="ch2-right-click-open-with" scale="50"></graphic>
+ </figure>
+
+
+ <para>
+ In this example, Nautilus offers to open the file
+ with its default image viewer, or the user can
+ choose another viewer or application.
+ </para>
+
+ <para>
+ Suppose the user wanted to customize Nautilus to
+ always open JPEG files with The Gimp (which is
+ both a viewer and an editor). In this case, the user
+ would click Other Application.
+ </para>
+
+ <para>
+ The Open with Other window which appears
+ (Figure 13), shows the user the current application(s)
+ setup for opening files.
+ </para>
+
+ <figure>
+ <title>Choosing an Application</title>
+ <graphic fileref="ch2-open-with-other" scale="50"></graphic>
+ </figure>
+
+ <para>
+ In Figure 13, The Gimp is present, but is not in
+ the menu for opening JPEG files. To place it in
+ the menu and make sure it is used as the default
+ viewer for JPEG files, click the Modify button,
+ and choose the second selection (Figure 14).
+ </para>
+
+ <figure>
+ <title>Modifying the Default Application for Opening a File</title>
+ <graphic fileref="ch2-open-with" scale="50"></graphic>
+ </figure>
+
+ <para>
+ A deeper level of configuration can be obtained
+ by clicking the Go There button on the Open with
+ Other menu. That opens the GNOME Control
+ Center to the File Types and Programs screen. For
+ an explanation of how to associate programs with
+ certain file types, see the GNOME Users Guide.
+ </para>
+
+ </sect1>
+
+ <sect1 id="ch2-apearance">
+ <title>Customizing Nautilus Appearance</title>
+
+ <para>
+ Many users are not content to stare at a <emphasis>default</emphasis>
+ desktop decor: they want to customize it
+ according to taste. For this, a wide range of
+ backgrounds, colors, emblems and themes is
+ available, and, should the user wish, they can add
+ their own.
+ </para>
+
+ <sect2 id="ch2-apearance-colors">
+ <title>Backgrounds, Colors and Emblems</title>
+
+ <para>
+ To change the desktop decor, click on Edit on the
+ menu bar, and choose Customize. The Nautilus
+ Customization Options window appears.
+ </para>
+
+ <para>
+ Each background, color, and emblem can be
+ applied by simply dragging it to the desire
+ window or file with the mouse. In the example in
+ Figure 15, the satin background has been applied
+ to the main window, while the color ruby has been
+ dragged and dropped into the sidebar. Finally, the
+ file <filename>pluck.wav</filename> has been embelished with a
+ green, heart-shaped <emphasis>Favorite</emphasis> emblem.
+ </para>
+
+
+ <figure>
+ <title>Color and Textures to the Users Taste</title>
+ <graphic fileref="ch2-colors" scale="50"></graphic>
+ </figure>
+
+ </sect2>
+
+ <sect2 id="ch2-apearance-themes">
+ <title>Themes</title>
+
+ <para>
+ The simplest way to change an overall <emphasis>look</emphasis>, is
+ to change the theme. Several themes are
+ available; clicking on Change Appearance in the
+ Edit menu brings up the Nautilus Theme Selector.
+ </para>
+
+ <para>
+ Selecting one of the four different themes applies
+ the new theme while the selector window is still
+ open, allowing the user to preview the new
+ design. In Figure 16, the Eazel theme has been
+ selected, changing backgrounds on the sidebar
+ and the main window, and also the icons on the
+ tool bar.
+ </para>
+
+
+ <figure>
+ <title>The <emphasis>Eazel</emphasis> Theme, with the Nautilus Theme Selector
+ Window</title>
+ <graphic fileref="ch2-theme-eazel" scale="50"></graphic>
+ </figure>
+
+
+ </sect2>
+
+ </sect1>
+
+</chapter>
diff --git a/user-guide/C/sgml/chapter-3.sgml b/user-guide/C/sgml/chapter-3.sgml new file mode 100644 index 000000000..8171290fc --- /dev/null +++ b/user-guide/C/sgml/chapter-3.sgml @@ -0,0 +1,226 @@ +<chapter id="ch3">
+ <title>Nautilus and Eazel Services</title>
+
+
+ <para>
+ Eazel Services are an Internet-based suite of tools
+ designed to simplify system management in
+ Linux. Nautilus and Eazel Services work together:
+ one complements the other. This chapter presents
+ a description of Eazel Services available for
+ the preview release two.
+ </para>
+
+ <para>
+ For this release, Services will include:
+
+ <itemizedlist>
+
+ <listitem><para>
+ Eazel Software Catalog
+ </para></listitem>
+
+ <listitem><para>
+ Eazel Software Installer
+ </para></listitem>
+
+ <listitem><para>
+ Eazel Online Storage
+ </para></listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ <sect1 id="ch3-accessing">
+ <title>Accessing Services</title>
+
+ <para>
+ There are several ways to access Eazel Services.
+ When starting Nautilus for the first time, the user
+ is asked if they wish to learn about, sign up, or
+ log on to Services (Figure 1).
+ </para>
+
+
+ <figure>
+ <title>Signing Up for Eazel Services Upon Starting Nautilus</title>
+ <graphic fileref="ch3-sign-up" scale="50"></graphic>
+ </figure>
+
+
+ <para>
+ On a routine basis, Services can be reached by
+ simply clicking the Services icon on the Nautilus
+ toolbar. Alternatively, they can be reached
+ through any web browser, from www.eazel.com.
+ </para>
+
+ </sect1>
+
+ <sect1 id="ch3-registration">
+ <title>Registration and Login</title>
+
+ <para>
+ Registration--for this preview release--is not required for the
+ software catalog, but is for online storage.
+ </para
+
+ <para>
+ Registration is the same from Nautilus or from any browser. The
+ screen is divided into three sections: the required fields to open
+ an account (Figure 2); the optional personal profile section, and
+ the optional computing environment section.
+ </para>
+
+ <figure>
+ <title>Required Account Information in Registration</title>
+ <graphic fileref="ch3-account-info" scale="50"></graphic>
+ </figure>
+
+
+ <para>
+ The user completes the process by activating their account with the
+ instructions sent in a validation e-mail. The instructions are sent
+ almost instantaneously.
+ </para>
+
+ <para>
+ Logging in can be accomplished either from the greeting page which
+ follows account validation, from clicking services in Nautilus, or
+ from the Eazel website, www.eazel.com.
+ </para>
+
+ <para>
+ The Welcome screen, Figure 3, is organized into three basic sections.
+ The top section has links for reaching the Eazel support page, for
+ changing user preferences, and for logging out.
+ </para>
+
+ <para>
+ The support page has a number of FAQs and other help features. The
+ preferences link allows the user to change or update personal and
+ computer preferences, and even passwords.
+ </para/>
+
+ <figure>
+ <title>The Welcome Screen, Showing Online Storage and Software Catalog
+ </title>
+ <graphic fileref="ch3-welcome-screen" scale="50"></graphic>
+ </figure>
+
+
+ <para>
+ The second section down is devoted to Online Storage, and has links to
+ the users private and public storage folder.
+ </para>
+
+ <para>
+ The third section allows the user to either browse or search the Eazel
+ software catalog.
+ </para>
+
+
+
+ </sect1>
+
+ <sect1 id="ch3-catalog">
+ <title>Eazel Software Catalog</title>
+
+ <para>
+ The Software Catalog is an on-line catalog of
+ Linux software, both Open Source and commercial, that should
+ install and work properly--in this preview release--on a Redhat 6.0
+ to 6.2 system.
+ </para>
+
+ <para>
+ The software is in RPM format.
+ </para>
+
+ <para>
+ The user is able to select software by either browsing the online
+ catalog by category, or by searching for a specific package with a
+ keyword. Both catalog browsing and searching can be further refined
+ by specifying a Redhat distribution version.
+ </para>
+
+ <para>
+ When browsing, the user is presented with thirteen different categories, from Communications to Text Editors. Selecting the first, for example, opens a separate screen dedicated to communications software (Figure 4), with a list of package titles and short summaries.
+ </para>
+
+ <figure>
+ <title>Package Titles and Summaries</title>
+ <graphic fileref="ch3-package-titles" scale="50"></graphic>
+ </figure>
+
+
+ <para>
+ Selecting the package title takes the user to a further screen, giving
+ more complete information, including the version and release number,
+ the source and vendor, a more complete description, package size, etc.
+ </para>
+
+ <para>
+ Pressing the download button sets up a download of the selected package
+ --in RPM format--to the users home directory.
+ </para>
+
+ </sect1>
+
+ <sect1 id="ch3-installer">
+ <title>Eazel Software Installer</title>
+
+ <para>
+ The Software Installer, which functions when accessing Services through Nautilus, takes into account your distribution,
+ version, and current system, and installs not only
+ the chosen programs, but also automatically
+ installs the necessary dependencies.
+ </para>
+
+ <para>
+ This is all accomplished with the help of a client-
+ side inventory program built into Nautilus--
+ making Nautilus an integral part of Eazel
+ Services.
+ </para>
+
+ </sect1>
+
+ <sect1 id="ch3-vault">
+ <title>Eazel Online Storage</title>
+
+ <para>
+ Each user is provided initially with 25MB of free storage space, in two folders, private and public.
+ </para>
+
+ <para>
+ Online Storage is more than just a one-directory
+ file repository. Users can create online folders--
+ even entire directory trees. They can upload and
+ download files, and Nautilus users can copy or
+ move entire folders from their own system to
+ Eazel Online Storage, and back again.
+ </para>
+
+ <para>
+ Clicking on either the Private or Public folder icon takes the user to the Online Storage screen (Figure 5).
+ </para>
+
+ <figure>
+ <title>The Online Storage Screen</title>
+ <graphic fileref="ch3-online-storage" scale="50"></graphic>
+ </figure>
+
+ <para>
+ From here, the user can see immediately which files they have in
+ storage, and how much space they have left available. They may also
+ choose to create a sub-folder, to upload or download files, or to
+ copy, move, or delete selected items.
+ </para>
+
+
+ </sect1>
+
+
+</chapter>
diff --git a/user-guide/C/sgml/fdl.sgml b/user-guide/C/sgml/fdl.sgml new file mode 100644 index 000000000..43fcdf201 --- /dev/null +++ b/user-guide/C/sgml/fdl.sgml @@ -0,0 +1,647 @@ + +<chapter id="fdl"> + + <title>GNU Free Documentation License</title> + + <sect1 id="fdl-preamble"> + <title>0. PREAMBLE</title> + <para> + The purpose of this License is to make a manual, textbook, or + other written document <quote>free</quote> in the sense of + freedom: to assure everyone the effective freedom to copy and + redistribute it, with or without modifying it, either + commercially or noncommercially. Secondarily, this License + preserves for the author and publisher a way to get credit for + their work, while not being considered responsible for + modifications made by others. + </para> + + <para> + This License is a kind of <quote>copyleft</quote>, which means + that derivative works of the document must themselves be free in + the same sense. It complements the GNU General Public License, + which is a copyleft license designed for free software. + </para> + + <para> + We have designed this License in order to use it for manuals for + free software, because free software needs free documentation: a + free program should come with manuals providing the same + freedoms that the software does. But this License is not limited + to software manuals; it can be used for any textual work, + regardless of subject matter or whether it is published as a + printed book. We recommend this License principally for works + whose purpose is instruction or reference. + </para> + </sect1> + <sect1 id="fdl-section1"> + <title>1. APPLICABILITY AND DEFINITIONS</title> + <para id="fdl-document"> + This License applies to any manual or other work that contains a + notice placed by the copyright holder saying it can be + distributed under the terms of this License. The + <quote>Document</quote>, below, refers to any such manual or + work. Any member of the public is a licensee, and is addressed + as <quote>you</quote>. + </para> + + <para id="fdl-modified"> + A <quote>Modified Version</quote> of the Document means any work + containing the Document or a portion of it, either copied + verbatim, or with modifications and/or translated into another + language. + </para> + + <para id="fdl-secondary"> + A <quote>Secondary Section</quote> is a named appendix or a + front-matter section of the <link + linkend="fdl-document">Document</link> that deals exclusively + with the relationship of the publishers or authors of the + Document to the Document's overall subject (or to related + matters) and contains nothing that could fall directly within + that overall subject. (For example, if the Document is in part a + textbook of mathematics, a Secondary Section may not explain any + mathematics.) The relationship could be a matter of historical + connection with the subject or with related matters, or of + legal, commercial, philosophical, ethical or political position + regarding them. + </para> + + <para id="fdl-invariant"> + The <quote>Invariant Sections</quote> are certain <link + linkend="fdl-secondary"> Secondary Sections</link> whose titles + are designated, as being those of Invariant Sections, in the + notice that says that the <link + linkend="fdl-document">Document</link> is released under this + License. + </para> + + <para id="fdl-cover-texts"> + The <quote>Cover Texts</quote> are certain short passages of + text that are listed, as Front-Cover Texts or Back-Cover Texts, + in the notice that says that the <link + linkend="fdl-document">Document</link> is released under this + License. + </para> + + <para id="fdl-transparent"> + A <quote>Transparent</quote> copy of the <link + linkend="fdl-document"> Document</link> means a machine-readable + copy, represented in a format whose specification is available + to the general public, whose contents can be viewed and edited + directly and straightforwardly with generic text editors or (for + images composed of pixels) generic paint programs or (for + drawings) some widely available drawing editor, and that is + suitable for input to text formatters or for automatic + translation to a variety of formats suitable for input to text + formatters. A copy made in an otherwise Transparent file format + whose markup has been designed to thwart or discourage + subsequent modification by readers is not Transparent. A copy + that is not <quote>Transparent</quote> is called + <quote>Opaque</quote>. + </para> + + <para> + Examples of suitable formats for Transparent copies include + plain ASCII without markup, Texinfo input format, LaTeX input + format, SGML or XML using a publicly available DTD, and + standard-conforming simple HTML designed for human + modification. Opaque formats include PostScript, PDF, + proprietary formats that can be read and edited only by + proprietary word processors, SGML or XML for which the DTD + and/or processing tools are not generally available, and the + machine-generated HTML produced by some word processors for + output purposes only. + </para> + + <para id="fdl-title-page"> + The <quote>Title Page</quote> means, for a printed book, the + title page itself, plus such following pages as are needed to + hold, legibly, the material this License requires to appear in + the title page. For works in formats which do not have any title + page as such, <quote>Title Page</quote> means the text near the + most prominent appearance of the work's title, preceding the + beginning of the body of the text. + </para> + </sect1> + + <sect1 id="fdl-section2"> + <title>2. VERBATIM COPYING</title> + <para> + You may copy and distribute the <link + linkend="fdl-document">Document</link> in any medium, either + commercially or noncommercially, provided that this License, the + copyright notices, and the license notice saying this License + applies to the Document are reproduced in all copies, and that + you add no other conditions whatsoever to those of this + License. You may not use technical measures to obstruct or + control the reading or further copying of the copies you make or + distribute. However, you may accept compensation in exchange for + copies. If you distribute a large enough number of copies you + must also follow the conditions in <link + linkend="fdl-section3">section 3</link>. + </para> + + <para> + You may also lend copies, under the same conditions stated + above, and you may publicly display copies. + </para> + </sect1> + + <sect1 id="fdl-section3"> + <title>3. COPYING IN QUANTITY</title> + <para> + If you publish printed copies of the <link + linkend="fdl-document">Document</link> numbering more than 100, + and the Document's license notice requires <link + linkend="fdl-cover-texts">Cover Texts</link>, you must enclose + the copies in covers that carry, clearly and legibly, all these + Cover Texts: Front-Cover Texts on the front cover, and + Back-Cover Texts on the back cover. Both covers must also + clearly and legibly identify you as the publisher of these + copies. The front cover must present the full title with all + words of the title equally prominent and visible. You may add + other material on the covers in addition. Copying with changes + limited to the covers, as long as they preserve the title of the + <link linkend="fdl-document">Document</link> and satisfy these + conditions, can be treated as verbatim copying in other + respects. + </para> + + <para> + If the required texts for either cover are too voluminous to fit + legibly, you should put the first ones listed (as many as fit + reasonably) on the actual cover, and continue the rest onto + adjacent pages. + </para> + + <para> + If you publish or distribute <link + linkend="fdl-transparent">Opaque</link> copies of the <link + linkend="fdl-document">Document</link> numbering more than 100, + you must either include a machine-readable <link + linkend="fdl-transparent">Transparent</link> copy along with + each Opaque copy, or state in or with each Opaque copy a + publicly-accessible computer-network location containing a + complete Transparent copy of the Document, free of added + material, which the general network-using public has access to + download anonymously at no charge using public-standard network + protocols. If you use the latter option, you must take + reasonably prudent steps, when you begin distribution of Opaque + copies in quantity, to ensure that this Transparent copy will + remain thus accessible at the stated location until at least one + year after the last time you distribute an Opaque copy (directly + or through your agents or retailers) of that edition to the + public. + </para> + + <para> + It is requested, but not required, that you contact the authors + of the <link linkend="fdl-document">Document</link> well before + redistributing any large number of copies, to give them a chance + to provide you with an updated version of the Document. + </para> + </sect1> + + <sect1 id="fdl-section4"> + <title>4. MODIFICATIONS</title> + <para> + You may copy and distribute a <link + linkend="fdl-modified">Modified Version</link> of the <link + linkend="fdl-document">Document</link> under the conditions of + sections <link linkend="fdl-section2">2</link> and <link + linkend="fdl-section3">3</link> above, provided that you release + the Modified Version under precisely this License, with the + Modified Version filling the role of the Document, thus + licensing distribution and modification of the Modified Version + to whoever possesses a copy of it. In addition, you must do + these things in the Modified Version: + </para> + + <itemizedlist mark="opencircle"> + <listitem> + <formalpara> + <title>A</title> + <para> + Use in the <link linkend="fdl-title-page">Title + Page</link> (and on the covers, if any) a title distinct + from that of the <link + linkend="fdl-document">Document</link>, and from those of + previous versions (which should, if there were any, be + listed in the History section of the Document). You may + use the same title as a previous version if the original + publisher of that version gives permission. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>B</title> + <para> + List on the <link linkend="fdl-title-page">Title + Page</link>, as authors, one or more persons or entities + responsible for authorship of the modifications in the + <link linkend="fdl-modified">Modified Version</link>, + together with at least five of the principal authors of + the <link linkend="fdl-document">Document</link> (all of + its principal authors, if it has less than five). + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>C</title> + <para> + State on the <link linkend="fdl-title-page">Title + Page</link> the name of the publisher of the <link + linkend="fdl-modified">Modified Version</link>, as the + publisher. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>D</title> + <para> + Preserve all the copyright notices of the <link + linkend="fdl-document">Document</link>. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>E</title> + <para> + Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>F</title> + <para> + Include, immediately after the copyright notices, a + license notice giving the public permission to use the + <link linkend="fdl-modified">Modified Version</link> under + the terms of this License, in the form shown in the + Addendum below. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>G</title> + <para> + Preserve in that license notice the full lists of <link + linkend="fdl-invariant"> Invariant Sections</link> and + required <link linkend="fdl-cover-texts">Cover + Texts</link> given in the <link + linkend="fdl-document">Document's</link> license notice. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>H</title> + <para> + Include an unaltered copy of this License. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>I</title> + <para> + Preserve the section entitled <quote>History</quote>, and + its title, and add to it an item stating at least the + title, year, new authors, and publisher of the <link + linkend="fdl-modified">Modified Version </link>as given on + the <link linkend="fdl-title-page">Title Page</link>. If + there is no section entitled <quote>History</quote> in the + <link linkend="fdl-document">Document</link>, create one + stating the title, year, authors, and publisher of the + Document as given on its Title Page, then add an item + describing the Modified Version as stated in the previous + sentence. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>J</title> + <para> + Preserve the network location, if any, given in the <link + linkend="fdl-document">Document</link> for public access + to a <link linkend="fdl-transparent">Transparent</link> + copy of the Document, and likewise the network locations + given in the Document for previous versions it was based + on. These may be placed in the <quote>History</quote> + section. You may omit a network location for a work that + was published at least four years before the Document + itself, or if the original publisher of the version it + refers to gives permission. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>K</title> + <para> + In any section entitled <quote>Acknowledgements</quote> or + <quote>Dedications</quote>, preserve the section's title, + and preserve in the section all the substance and tone of + each of the contributor acknowledgements and/or + dedications given therein. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>L</title> + <para> + Preserve all the <link linkend="fdl-invariant">Invariant + Sections</link> of the <link + linkend="fdl-document">Document</link>, unaltered in their + text and in their titles. Section numbers or the + equivalent are not considered part of the section titles. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>M</title> + <para> + Delete any section entitled + <quote>Endorsements</quote>. Such a section may not be + included in the <link linkend="fdl-modified">Modified + Version</link>. + </para> + </formalpara> + </listitem> + + <listitem> + <formalpara> + <title>N</title> + <para> + Do not retitle any existing section as + <quote>Endorsements</quote> or to conflict in title with + any <link linkend="fdl-invariant">Invariant + Section</link>. + </para> + </formalpara> + </listitem> + </itemizedlist> + + <para> + If the <link linkend="fdl-modified">Modified Version</link> + includes new front-matter sections or appendices that qualify as + <link linkend="fdl-secondary">Secondary Sections</link> and + contain no material copied from the Document, you may at your + option designate some or all of these sections as invariant. To + do this, add their titles to the list of <link + linkend="fdl-invariant">Invariant Sections</link> in the + Modified Version's license notice. These titles must be + distinct from any other section titles. + </para> + + <para> + You may add a section entitled <quote>Endorsements</quote>, + provided it contains nothing but endorsements of your <link + linkend="fdl-modified">Modified Version</link> by various + parties--for example, statements of peer review or that the text + has been approved by an organization as the authoritative + definition of a standard. + </para> + + <para> + You may add a passage of up to five words as a <link + linkend="fdl-cover-texts">Front-Cover Text</link>, and a passage + of up to 25 words as a <link + linkend="fdl-cover-texts">Back-Cover Text</link>, to the end of + the list of <link linkend="fdl-cover-texts">Cover Texts</link> + in the <link linkend="fdl-modified">Modified Version</link>. + Only one passage of Front-Cover Text and one of Back-Cover Text + may be added by (or through arrangements made by) any one + entity. If the <link linkend="fdl-document">Document</link> + already includes a cover text for the same cover, previously + added by you or by arrangement made by the same entity you are + acting on behalf of, you may not add another; but you may + replace the old one, on explicit permission from the previous + publisher that added the old one. + </para> + + <para> + The author(s) and publisher(s) of the <link + linkend="fdl-document">Document</link> do not by this License + give permission to use their names for publicity for or to + assert or imply endorsement of any <link + linkend="fdl-modified">Modified Version </link>. + </para> + </sect1> + + <sect1 id="fdl-section5"> + <title>5. COMBINING DOCUMENTS</title> + <para> + You may combine the <link linkend="fdl-document">Document</link> + with other documents released under this License, under the + terms defined in <link linkend="fdl-section4">section 4</link> + above for modified versions, provided that you include in the + combination all of the <link linkend="fdl-invariant">Invariant + Sections</link> of all of the original documents, unmodified, + and list them all as Invariant Sections of your combined work in + its license notice. + </para> + + <para> + The combined work need only contain one copy of this License, + and multiple identical <link linkend="fdl-invariant">Invariant + Sections</link> may be replaced with a single copy. If there are + multiple Invariant Sections with the same name but different + contents, make the title of each such section unique by adding + at the end of it, in parentheses, the name of the original + author or publisher of that section if known, or else a unique + number. Make the same adjustment to the section titles in the + list of Invariant Sections in the license notice of the combined + work. + </para> + + <para> + In the combination, you must combine any sections entitled + <quote>History</quote> in the various original documents, + forming one section entitled <quote>History</quote>; likewise + combine any sections entitled <quote>Acknowledgements</quote>, + and any sections entitled <quote>Dedications</quote>. You must + delete all sections entitled <quote>Endorsements.</quote> + </para> + </sect1> + + <sect1 id="fdl-section6"> + <title>6. COLLECTIONS OF DOCUMENTS</title> + <para> + You may make a collection consisting of the <link + linkend="fdl-document">Document</link> and other documents + released under this License, and replace the individual copies + of this License in the various documents with a single copy that + is included in the collection, provided that you follow the + rules of this License for verbatim copying of each of the + documents in all other respects. + </para> + + <para> + You may extract a single document from such a collection, and + dispbibute it individually under this License, provided you + insert a copy of this License into the extracted document, and + follow this License in all other respects regarding verbatim + copying of that document. + </para> + </sect1> + + <sect1 id="fdl-section7"> + <title>7. AGGREGATION WITH INDEPENDENT WORKS</title> + <para> + A compilation of the <link + linkend="fdl-document">Document</link> or its derivatives with + other separate and independent documents or works, in or on a + volume of a storage or distribution medium, does not as a whole + count as a <link linkend="fdl-modified">Modified Version</link> + of the Document, provided no compilation copyright is claimed + for the compilation. Such a compilation is called an + <quote>aggregate</quote>, and this License does not apply to the + other self-contained works thus compiled with the Document , on + account of their being thus compiled, if they are not themselves + derivative works of the Document. If the <link + linkend="fdl-cover-texts">Cover Text</link> requirement of <link + linkend="fdl-section3">section 3</link> is applicable to these + copies of the Document, then if the Document is less than one + quarter of the entire aggregate, the Document's Cover Texts may + be placed on covers that surround only the Document within the + aggregate. Otherwise they must appear on covers around the whole + aggregate. + </para> + </sect1> + + <sect1 id="fdl-section8"> + <title>8. TRANSLATION</title> + <para> + Translation is considered a kind of modification, so you may + distribute translations of the <link + linkend="fdl-document">Document</link> under the terms of <link + linkend="fdl-section4">section 4</link>. Replacing <link + linkend="fdl-invariant"> Invariant Sections</link> with + translations requires special permission from their copyright + holders, but you may include translations of some or all + Invariant Sections in addition to the original versions of these + Invariant Sections. You may include a translation of this + License provided that you also include the original English + version of this License. In case of a disagreement between the + translation and the original English version of this License, + the original English version will prevail. + </para> + </sect1> + + <sect1 id="fdl-section9"> + <title>9. TERMINATION</title> + <para> + You may not copy, modify, sublicense, or distribute the <link + linkend="fdl-document">Document</link> except as expressly + provided for under this License. Any other attempt to copy, + modify, sublicense or distribute the Document is void, and will + automatically terminate your rights under this License. However, + parties who have received copies, or rights, from you under this + License will not have their licenses terminated so long as such + parties remain in full compliance. + </para> + </sect1> + + <sect1 id="fdl-section10"> + <title>10. FUTURE REVISIONS OF THIS LICENSE</title> + <para> + The <ulink type="http" + url="http://www.gnu.org/fsf/fsf.html">Free Software + Foundation</ulink> may publish new, revised versions of the GNU + Free Documentation License from time to time. Such new versions + will be similar in spirit to the present version, but may differ + in detail to address new problems or concerns. See <ulink + type="http" + url="http://www.gnu.org/copyleft">http://www.gnu.org/copyleft/</ulink>. + </para> + + <para> + Each version of the License is given a distinguishing version + number. If the <link linkend="fdl-document">Document</link> + specifies that a particular numbered version of this License + <quote>or any later version</quote> applies to it, you have the + option of following the terms and conditions either of that + specified version or of any later version that has been + published (not as a draft) by the Free Software Foundation. If + the Document does not specify a version number of this License, + you may choose any version ever published (not as a draft) by + the Free Software Foundation. + </para> + </sect1> + + <sect1 id="fdl-using"> + <title>Addendum</title> + <para> + To use this License in a document you have written, include a copy of + the License in the document and put the following copyright and + license notices just after the title page: + </para> + + <blockquote> + <para> + Copyright © YEAR YOUR NAME. + </para> + <para> + Permission is granted to copy, distribute and/or modify this + document under the terms of the GNU Free Documentation + License, Version 1.1 or any later version published by the + Free Software Foundation; with the <link + linkend="fdl-invariant">Invariant Sections</link> being LIST + THEIR TITLES, with the <link + linkend="fdl-cover-texts">Front-Cover Texts</link> being LIST, + and with the <link linkend="fdl-cover-texts">Back-Cover + Texts</link> being LIST. A copy of the license is included in + the section entitled <quote>GNU Free Documentation + License</quote>. + </para> + </blockquote> + + <para> + If you have no <link linkend="fdl-invariant">Invariant + Sections</link>, write <quote>with no Invariant Sections</quote> + instead of saying which ones are invariant. If you have no + <link linkend="fdl-cover-texts">Front-Cover Texts</link>, write + <quote>no Front-Cover Texts</quote> instead of + <quote>Front-Cover Texts being LIST</quote>; likewise for <link + linkend="fdl-cover-texts">Back-Cover Texts</link>. + </para> + + <para> + If your document contains nontrivial examples of program code, + we recommend releasing these examples in parallel under your + choice of free software license, such as the <ulink type="http" + url="http://www.gnu.org/copyleft/gpl.html"> GNU General Public + License</ulink>, to permit their use in free software. + </para> + </sect1> +</chapter> + + + + + + diff --git a/user-guide/C/sgml/install.sgml b/user-guide/C/sgml/install.sgml new file mode 100644 index 000000000..eec406a21 --- /dev/null +++ b/user-guide/C/sgml/install.sgml @@ -0,0 +1,190 @@ +<chapter id="instal">
+ <title>Installation</title>
+
+
+ <para>
+ Nautilus will be the default file manager for
+ GNOME 1.4. So for users of that version of
+ GNOME, no special Nautilus installation will be
+ necessary.
+ </para>
+
+ <para>
+ For other users, Nautilus can be downloaded from
+ the Eazel Nautilus website. Instructions for this
+ follow the system requirements section, below.
+ </para>
+
+ <sect1 id="instal-system-requirements">
+ <title>System Requirements for Running Nautilus</title>
+
+ <para>
+ The minimum system requirements for running
+ the Nautilus preview release two are:
+ </para>
+
+ <sect2 id="instal-system-requirements-harware">
+ <title>Hardware</title>
+ <para>
+ <itemizedlist>
+
+ <listitem><para>
+ x86 compatible processor (200mHz minimum).
+ </para></listitem>
+
+ <listitem><para>
+ 64MB RAM recommended.
+ </para></listitem>
+
+
+ <listitem><para>
+ 60MB hard drive space.
+ </para></listitem>
+
+ <listitem><para>
+ 500MB of additional space, if you have to install GNOME.
+ </para></listitem>
+
+ </itemizedlist>
+ </para>
+ </sect2>
+
+
+ <sect2 id="instal-system-requirements-software">
+ <title>Software</title>
+
+ <para>
+
+ <itemizedlist>
+
+ <listitem><para>
+ RedHat Linux 6.2 (others may work, but this is the preview test
+ platform).
+ </para></listitem>
+
+ <listitem><para>
+ GNOME 1.2 (Components for GNOME will be downloaded by the Eazel
+ Installer if needed).
+ </para></listitem>
+
+ <listitem><para>
+ Mozilla-5.0-M18-4 (downloaded by the Eazel Installer if needed).
+ </para></listitem>
+
+ </itemizedlist>
+
+ </para>
+ </sect2>
+ </sect1>
+
+ <sect1 id="instal-download-install">
+ <title>Download and Install Instructions for the Nautilus Preview
+ Release Two</title>
+
+ <para>First, make sure you have enough hard disk space,
+ and are running the correct version of Linux, and
+ of GNOME.
+ </para>
+
+ <para>
+ The Eazel site for downloading Nautilus is
+ <ulink url="http://download.eazel.com/">http://download.eazel.com</ulink>.
+ </para>
+
+ <para>
+ Once at the site:
+ <orderedlist>
+ <listitem><para>
+ Fill out the simple registration form.
+ </para></listitem>
+ <listitem><para>
+ Save the Eazel Installer in your tmp directory.
+ </para></listitem>
+
+ <listitem><para>
+ Open a terminal window, and type: /tmp
+ </para></listitem>
+
+ <listitem><para>
+ Next, type: sh ./nautilus-installer.sh
+ </para></listitem>
+
+ <listitem><para>
+ When prompted, enter your systems root password.
+ </para></listitem>
+
+ <listitem><para>
+ The Nautilus installation wizard will launch. Read the
+ requirements and click Begin.
+ </para></listitem>
+
+ </orderedlist>
+ </para>
+
+ <para>
+ When the installation is finished, start Nautilus by
+ opening the GNOME main menu, opening the
+ Applications sub-menu, and clicking on the
+ Nautilus icon.
+ </para>
+ </sect1>
+
+ <sect1 id="instal-initial-screens">
+ <title>Initial Screens</title>
+
+ <para>
+ When you start Nautilus for the first time, there
+ are several initial screens. The first is simply a
+ welcome screen. The second, however, lets you
+ select your initial user level (Figure 1)
+ </para>
+
+ <figure>
+ <title>Selecting an Initial User Level</title>
+ <graphic fileref="install-user-level" scale="50"></graphic>
+ </figure>
+
+ <para>
+ The different user levels primarily control the
+ amount of system and file detail that Nautilus
+ displays. Check the level you feel is right for you,
+ and click on the Next button.
+ </para>
+
+ <para>
+ The following screen gives you an opportunity to
+ learn about Eazel Services, to sign up for them
+ immediately, to login to Services if you are
+ already a member, or to skip exploring Services at
+ this time.
+ </para>
+
+ <para>
+ Nautilus and Eazel Services are covered in
+ Chapter Three of this manual.
+ </para>
+
+ <figure>
+ <title>The Nautilus Update Screen</title>
+ <graphic fileref="install-update" scale="50"></graphic>
+ </figure>
+
+ <para>
+ The next screen (Figure 2), offers to automatically
+ contact Eazel Services to verify your
+ Internet connection and download the latest
+ Nautilus updates. Check the appropriate box and
+ click the Next button. The update procedure is
+ automatic.
+ </para>
+
+ <para>
+ At the final screen click the Finish button to
+ complete the install. After a moment or two the
+ Nautilus file manager will start.
+ </para>
+
+
+ </sect1>
+
+</chapter>
diff --git a/user-guide/C/sgml/intro.sgml b/user-guide/C/sgml/intro.sgml new file mode 100644 index 000000000..6d5a84a31 --- /dev/null +++ b/user-guide/C/sgml/intro.sgml @@ -0,0 +1,144 @@ +<chapter id="intro">
+ <title>Introduction - Nautilus Preview Release Two</title>
+
+
+ <para>
+ Nautilus is the new file manager for GNOME, the
+ emerging desktop of choice for both Linux and
+ UNIX. Some of Nautilus features include:
+ <itemizedlist>
+
+ <listitem><para>
+ Graphic representation of files, with file icons displaying
+ actual file content: images, text, music, etc.
+ </para></listitem>
+
+ <listitem><para>
+ A variety of interface customizations, from the practical--
+ adjusting the amount of file data displayed according to
+ user-level--to the decorative: backgrounds, themes and
+ colors.
+ </para></listitem>
+
+ <listitem><para>
+ Mixed network (Linux and Windows) access, and Internet
+ browsing, from within Nautilus.
+ </para></listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ <para>
+ This manual describes the Nautilus Preview
+ Release 2. The first production release will ship
+ with GNOME 1.4
+ </para>
+
+ <sect1 id="intro-organization">
+ <title>Manual Organization</title>
+
+ <para>
+ This manual is a step-by-step guide to Nautilus
+ features. The organization is:
+ <itemizedlist>
+
+ <listitem><para>
+ This Introduction.
+ </para></listitem>
+
+ <listitem><para>
+ An Installation section.
+ </para></listitem>
+
+ <listitem><para>
+ Chapter One, concentrating on fundamental file operations.
+ </para></listitem>
+
+ <listitem><para>
+ Chapter Two, presenting the range of system customization
+ options available in Nautilus.
+ </para></listitem>
+
+ <listitem><para>
+ Chapter Three, describing how Nautilus is integrated into
+ Eazel Services, how to use them, and their benefits.
+ </para></listitem>
+
+ </itemizedlist>
+
+ </para>
+
+ </sect1>
+
+ <sect1 id="intro-fsf">
+ <title>Free Software</title>
+
+ <para>
+ Like Linux and GNOME, Nautilus is Free Software, a method
+ of software distribution which encourages innovation, improvement
+ and timely bug fixes, and to which Eazel, Inc., the Nautilus
+ maintainer, is committed.
+ </para>
+
+ <para>
+ Fundamentally, the General Public License (or
+ GPL, under which Linux, GNOME and Nautilus
+ are licensed), insists that an application must always
+ be accompanied by its source code, that the
+ code can be freely modified, and that the user (or
+ purchaser) of software distributed under this license
+ agrees to in turn distribute their own source
+ code under the same license, when distributing, or
+ selling, a modified application.
+ </para>
+
+
+ <para>
+ It can be seen that distributing software under the
+ GPL license does not prohibit selling software,
+ and in fact many companies do sell Linux distributions
+ and applications. The license does insist
+ on the free sharing, and distribution, of source
+ code. And it is this open code distribution
+ policy which the Free Software movement believes
+ will eventually result in more innovatory, less
+ troublesome, and more useful software.
+ </para>
+ </sect1>
+
+
+ <sect1 id="intro-history">
+ <title>Nautilus History</title>
+
+ <para>
+ Nautilus can trace its Free Software lineage back
+ to the text-based Midnight Commander file man-
+ ager (still available on some Linux distributions).
+ The X Window version followed. Developing
+ from that base, Eazel has produced in Nautilus a
+ next-generation GUI that integrates file management,
+ web browsing, and system management.
+ </para>
+
+ </sect1>
+
+
+
+ <sect1 id="intro-platforms">
+ <title>Supported Platforms and Distributions</title>
+
+ <para>
+ Although initially developed on the Red Hat Linux 6.2
+ platform, Nautilus is being written for
+ cross-platform and multi-version operability in
+ short, to operate on every platform that GNOME
+ will operate on.
+ </para>
+
+ </sect1>
+
+</chapter>
+
+
+
diff --git a/user-guide/C/sgml/model.sgml b/user-guide/C/sgml/model.sgml new file mode 100644 index 000000000..d1b05f2a5 --- /dev/null +++ b/user-guide/C/sgml/model.sgml @@ -0,0 +1,39 @@ +<chapter> + <title></title> + + + <para> + </para> + + <sect1> + <title></title> + + <para> + </para> + + <figure> + <title></title> + <graphic fileref="" scale="50"></graphic> + </figure> + + + <sect2> + <title></title> + <para> + + <itemizedlist> + + <listitem><para> + </para></listitem> + + <listitem><para> + </para></listitem> + + </itemizedlist> + + </para> + </sect2> + + </sect1> + +</chapter>
\ No newline at end of file |
