From owner-svn-doc-all@FreeBSD.ORG Tue Oct 8 15:11:07 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6B80C64C; Tue, 8 Oct 2013 15:11:07 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4A5952961; Tue, 8 Oct 2013 15:11:07 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r98FB7qi080236; Tue, 8 Oct 2013 15:11:07 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r98FB7Z4080235; Tue, 8 Oct 2013 15:11:07 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201310081511.r98FB7Z4080235@svn.freebsd.org> From: Dru Lavigne Date: Tue, 8 Oct 2013 15:11:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r42895 - head/en_US.ISO8859-1/books/handbook/x11 X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:11:07 -0000 Author: dru Date: Tue Oct 8 15:11:06 2013 New Revision: 42895 URL: http://svnweb.freebsd.org/changeset/doc/42895 Log: White space fix only. Translators can ignore. Modified: head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/x11/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Tue Oct 8 14:56:51 2013 (r42894) +++ head/en_US.ISO8859-1/books/handbook/x11/chapter.xml Tue Oct 8 15:11:06 2013 (r42895) @@ -79,25 +79,28 @@ Terminology While it is not necessary to understand all of the details - of the various components in the X Window System and how they interact, some basic - knowledge of these components can be useful: + of the various components in the X Window System and how they + interact, some basic knowledge of these components can be + useful: X server - + - X was designed from the beginning to be network-centric, - and adopts a client-server model. In this model, the X server runs on the - computer that has the keyboard, monitor, and mouse attached. - The server's responsibility includes tasks such as managing - the display, handling input from the keyboard and mouse, and - handling input or output from other devices such as a tablet - or a video projector. This confuses some people, because the X terminology is - exactly backward to what they expect. They expect the - X server to be the big powerful machine down - the hall, and the X client to be the machine - on their desk. + X was designed from the beginning to be + network-centric, and adopts a client-server + model. In this model, the X server runs + on the computer that has the keyboard, monitor, and mouse + attached. The server's responsibility includes tasks + such as managing the display, handling input from the + keyboard and mouse, and handling input or output from + other devices such as a tablet or a video projector. + This confuses some people, because the X terminology is + exactly backward to what they expect. They expect the + X server to be the big powerful machine + down the hall, and the X client to be the + machine on their desk. @@ -105,22 +108,22 @@ X client - Each X application, such as - XTerm or - Firefox, is a - client. A client sends messages to the server - such as - Please draw a window at these coordinates, and - the server sends back messages such as - The user just clicked on the OK button. - - In a home or small office environment, the X server and - the X clients commonly run on the same computer. It - is also possible to run the X server on a less powerful - computer and to run the X applications on a more - powerful system. - In this scenario, the communication between the X - client and server takes place over the network. + Each X application, such as + XTerm or + Firefox, is a + client. A client sends messages to the + server such as Please draw a window at these + coordinates, and the server sends back messages + such as The user just clicked on the OK + button. + + In a home or small office environment, the X server + and the X clients commonly run on the same computer. It + is also possible to run the X server on a less powerful + computer and to run the X applications on a more + powerful system. In this scenario, the communication + between the X client and server takes place over the + network. @@ -128,27 +131,27 @@ window manager - X does not dictate what windows - should look like on screen, how to move them around with the - mouse, which keystrokes should be used to move between windows, what the - title bars on each window should look like, whether or not - they have close buttons on them, and so on. Instead, X delegates this responsibility to a - separate window manager application. There - are dozens of window managers - available. Each window manager provides a - different look and feel: some support - virtual desktops, some allow customized - keystrokes to manage the desktop, some have a - Start button, and some are - themeable, allowing a complete change of the desktop's - look-and-feel. Window managers are - available in the x11-wm category of the - Ports Collection. - - Each window manager uses a different configuration - mechanism. Some expect configuration file written by hand while - others provide graphical tools for most configuration tasks. + X does not dictate what windows should look like on + screen, how to move them around with the mouse, which + keystrokes should be used to move between windows, what + the title bars on each window should look like, whether + or not they have close buttons on them, and so on. + Instead, X delegates this responsibility to a separate + window manager application. There are dozens of window + managers available. Each window manager + provides a different look and feel: some support virtual + desktops, some allow customized keystrokes to manage the + desktop, some have a Start button, and + some are themeable, allowing a complete change of the + desktop's look-and-feel. Window managers are available + in the x11-wm category of the + Ports Collection. + + Each window manager uses a different configuration + mechanism. Some expect configuration file written by + hand while others provide graphical tools for most + configuration tasks. @@ -156,66 +159,68 @@ desktop environment - KDE and - GNOME are considered to be desktop environments - as they include an entire suite of applications for performing - common desktop tasks. These may include office suites, web - browsers, and games. + KDE and + GNOME are considered to be + desktop environments as they include an entire suite of + applications for performing common desktop tasks. These + may include office suites, web browsers, and games. focus policy - - The window manager is responsible for the - mouse focus policy. This policy provides - some means for choosing which window is actively - receiving keystrokes and it should also visibly indicate which - window is currently active. - - One focus policy is called - click-to-focus. In this model, a window becomes active - upon receiving a mouse click. In the - focus-follows-mouse policy, the window that is under the mouse pointer - has focus and the focus is changed by pointing at - another window. If the mouse is over the root window, then this - window is focused. In the sloppy-focus model, if - the mouse is moved over the root window, the most recently used window still - has the focus. With sloppy-focus, focus - is only changed when the cursor enters a new - window, and not when exiting the current - window. In the click-to-focus policy, the active window is selected by mouse click. - The window may then be raised and - appear in front of all other windows. All keystrokes - will now be directed to this window, even if the - cursor is moved to another window. - - Different window managers - support different focus models. All of them support - click-to-focus, and the majority of them also support other policies. - Consult the - documentation for the window manager to determine which - focus models are available. - - + + The window manager is responsible for the mouse focus + policy. This policy provides some means for choosing + which window is actively receiving keystrokes and it + should also visibly indicate which window is currently + active. + + One focus policy is called + click-to-focus. In this model, a window + becomes active upon receiving a mouse click. In the + focus-follows-mouse policy, the window + that is under the mouse pointer has focus and the focus + is changed by pointing at another window. If the mouse + is over the root window, then this window is focused. + In the sloppy-focus model, if the mouse + is moved over the root window, the most recently used + window still has the focus. With sloppy-focus, focus + is only changed when the cursor enters a new window, and + not when exiting the current window. In the + click-to-focus policy, the active window + is selected by mouse click. The window may then be + raised and appear in front of all other windows. All + keystrokes will now be directed to this window, even if + the cursor is moved to another window. + + Different window managers support different focus + models. All of them support click-to-focus, and the + majority of them also support other policies. Consult + the documentation for the window manager to determine + which focus models are available. + + widgets - Widget is a term for all of the items in - the user interface that can be clicked or manipulated in - some way. This includes buttons, check boxes, radio buttons, icons, and lists. - A widget toolkit is a set of widgets used to create - graphical applications. There are several popular widget toolkits, including Qt, used by - KDE, and GTK+, used by - GNOME. As a result, applications will have a - different look and feel, depending upon which widget toolkit - was used to create the application. + Widget is a term for all of the items in the user + interface that can be clicked or manipulated in some way. + This includes buttons, check boxes, radio buttons, icons, + and lists. A widget toolkit is a set of widgets used to + create graphical applications. There are several popular + widget toolkits, including Qt, used by + KDE, and GTK+, used by + GNOME. As a result, + applications will have a different look and feel, + depending upon which widget toolkit was used to create + the application. - - + +