Language Selection

English French German Italian Portuguese Spanish

X Factor - understanding the X window system

Filed under

X was originally created in the mid-80s by a research group from MIT. Its goal was to create a windowing system quite unlike any that had been conceived before. Thus X's design differs greatly from that of other windowing systems, having designed-in support for many elements which are unique ­ features which in fact are nowadays often being hacked into other windowing systems.

More often than not, such attempts are kludgy and don't work well, because they lack the ground-up desig X offers.

X went through a number of iterations because the original releases were not under a copyleft license. Every Unix developer created his own version, usually only modifying small parts, resulting in divergence into many incompatible versions, most of which fell under proprietary licences.

As a result, a standards body was eventually created to oversee the development of X. This body, known as the X Consortium, includes amongt its members IBM, Hewlett Packard and even Microsoft.

The X server has two important functions. Firstly, it speaks to the hardware; this means the X server needs to contain the driver for your graphics card, mouse, keyboard etc. Secondly, it speaks to X clients (every X program, from xterm to is an X client). Thus no X client ever talks directly to the hardware.

The most common channel is Unix Domain Sockets (UDS, a very fast mechanism for interprocess communication on Unix) which provides the highest speeds for local usage (for example where the X server and X clients are on the same machine). However it can also run over several network protocols, such as TCP/IP, allowing you to use your local X server to run a program on a distant machine over the Internet.

Luckily, working directly with the X protocol is seldom needed because X also provides xlib. Xlib is essentially a library of standard X tasks, such as basic drawing primitives and event handling. Xlib is written in C (with wrappers to many languages) and it in turn speaks to the X protocol for you. Xlib takes care of the low-level detail part of using the X protocol, such as establishing a connection over the appropriate channel and talking to the server.

Today the two most important widget sets in the Linux world are GTK and QT respectively. Their importance is greatly enhanced by the fact that these are the two toolkits on which the Gnome and KDE desktops are respectively built. Many other widget sets exist, and although none are as feature-rich as GTK or QT, they are still often used.

The two most important desktop environments today are of course KDE and Gnome, as most new Linux applications are built for one or the other. Currently KDE and Gnome basically match each other for features and which one a user prefers tend to be a matter of taste rather than a technical decision. Almost all Linux users use one of these two. Old-time Unix users and programmers often shun them however, preferring minimalist desktops.

Full Article.

More in Tux Machines

IBM Promises Apache Spark for Linux on Z Systems

Expanding the z Systems ecosystem means data scientists can use Apache Spark’s common programming framework and get the full use of the mainframe’s advanced analytics capabilities - without having to get sidelined by any specific format for data. Read more

Red Hat augments presence in Malaysia

Senior director and general manager, ASEAN, Damien Wong Yok Weng said Malaysia was an important market for the company and it had much potential for the adoption of open source technology across industries. Speaking to reporters at the official announcement of the subsidiary here, Wong said in terms of expansion strategy, Red Hat had looked at all the surrounding factors in the information technology (IT) industry. Read more

An Everyday Linux User Review Of Android x86 - Release 4.4 r3

This review might not be very long but I have spent a long time playing and experimenting with Android x86 and if you stick with it and are willing to play with settings then you may get something close to desirable. Those who will get the most out of Android x86 will be using a computer with a touchscreen. Read more

Will an upgrade to Windows 10 on a dual-boot system mess GRUB up?

If the setup is on a computer with UEFI firmware, with the boot files of all systems on the EFI Boot Partition, then I don’t see anything that will mess GRUB up during or after upgrading to Windows 10. That’s because the EFI Boot Partition is like a public park, where the space occupied by each operating system’s boot files is respected. So the Windows 10 upgrade script will only update the files and directory that pertains to the Windows boot manager. That this is true has been verified by none other than a Microsoft employee in this blog post. The same goes with the upgrade script of the installed Linux distribution(s), but you knew that already. Read more