Source string Read only

(itstool) path: sect1/title
42/420
Context English State
X was designed from the beginning to be network-centric, and adopts a <quote>client-server</quote> model. In this model, the <quote>X server</quote> 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 <quote>X server</quote> to be the big powerful machine down the hall, and the <quote>X client</quote> to be the machine on their desk.
X client
Each X application, such as <application>XTerm</application> or <application>Firefox</application>, is a <quote>client</quote>. A client sends messages to the server such as <quote>Please draw a window at these coordinates</quote>, and the server sends back messages such as <quote>The user just clicked on the OK button</quote>.
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.
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 <link xlink:href="http://www.xwinman.org/">dozens of window managers</link> 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 <quote>Start</quote> button, and some are themeable, allowing a complete change of the desktop's look-and-feel. Window managers are available in the <filename>x11-wm</filename> 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.
desktop environment
<application>KDE</application> and <application>GNOME</application> 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 <quote>click-to-focus</quote>. In this model, a window becomes active upon receiving a mouse click. In the <quote>focus-follows-mouse</quote> 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 <quote>sloppy-focus</quote> 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 <quote>click-to-focus</quote> 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 <application>KDE</application>, and GTK+, used by <application>GNOME</application>. As a result, applications will have a different look and feel, depending upon which widget toolkit was used to create the application.
Installing <application>Xorg</application>
On FreeBSD, <application>Xorg</application> can be installed as a package or port.
The binary package can be installed quickly but with fewer options for customization:
<prompt>#</prompt> <userinput>pkg install xorg</userinput>
To build and install from the Ports Collection:
<prompt>#</prompt> <userinput>cd /usr/ports/x11/xorg</userinput>
<prompt>#</prompt> <userinput>make install clean</userinput>
Either of these installations results in the complete <application>Xorg</application> system being installed. Binary packages are the best option for most users.
A smaller version of the X system suitable for experienced users is available in <package>x11/xorg-minimal</package>. Most of the documents, libraries, and applications will not be installed. Some applications require these additional components to function.
<application>Xorg</application> Configuration
<personname> <firstname>Warren</firstname> <surname>Block</surname> </personname> <contrib>Originally contributed by </contrib>
<primary>Xorg</primary>
<primary><application>Xorg</application></primary>
Quick Start
<application>Xorg</application> supports most common video cards, keyboards, and pointing devices.
Video cards, monitors, and input devices are automatically detected and do not require any manual configuration. Do not create <filename>xorg.conf</filename> or run a <option>-configure</option> step unless automatic configuration fails.
If <application>Xorg</application> has been used on this computer before, move or remove any existing configuration files:

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect1/title
Flags
read-only
Source string location
book.translate.xml:11173
String age
a year ago
Source string age
a year ago
Translation file
books/handbook.pot, string 1863