Several basic concepts about xwin

What are the differences (if any) between the terms GUI, window manager, desktop, and interface, and what is their relationship with Xwindow?
In the world of X, things are divided into many components, unlike other operating systems where everything is a part of the OS. Here are some definitions:

Interface is a general term that refers to a connection, a bridge, between two independent components of a computer system. It is usually used to refer to the "user interface" which is the connection between the user and the computer system.

GUI is another common term. Represents graphical user interface, graphical user interface. It's just as pretty as it sounds; it's a user interface that's mostly graphics. Both Mac OS and Windows are GUI-based, and in fact, quite a few of them are now used on desktop computers.

In Mac OS and Windows, the functions of building graphical interfaces are built into the operating system, and you can only use those. This method is simple, but not flexible. Unix and Unix-like operating systems do not have this functionality built-in, and to use the GUI you have to use a "windowing system". X is one of them - and now it seems the only one.

The function provided by Close them,

b) Standard controls like button menus

c) Standards for designing user interfaces, programming, or interaction between programs (such as drag and drop or standard help systems?

Window manager is a program that allows you to move windows and change their size. It also usually supports shrinking a window into an icon or task bar. There is usually some kind of program execution mechanism that the user can use. Do what you want - any X application should be able to work on any window manager, but you can run one in succession. This means that you can switch to any number of window managers, but you can run them at the same time. A. All programs on the screen can be managed by the running window manager. The widget set is a general tool library used by programmers to construct standard controls such as buttons and menus (X Programmer Call them widgets. The set of widgets used by an application is chosen by the programmer, not the user. Many people install multiple widget sets so that they can run programs written by multiple programmers at the same time. 🎜>
Finally, explain the desktop environment. This is the latest and most ambiguous X term. It basically means that "Mac OS and Windows have graphical interfaces, but X does not have them but should have them." "Stuff". Typically a set of applications that share a common look and feel, libraries, and methods for creating new applications. For example, all KDE applications use the same set of widgets (Qt) and helpers , you can install multiple desktop environments at the same time, and you can run applications from a different desktop environment in one desktop environment without switching to the past (of course you have to install that Desktop only). That is, if you use GNOME, but you like KDE's word processor KLyX, then you can run KLyX without running any other KDE programs, but it will not interact with your GNOME programs. . You can even run GNOME and KDE core programs at the same time, which actually makes no sense, you will have two file managers, two panels, etc.

All window managers ( Like GNOME or KDE or FVWM95) all run on X windows?

Yes, although GNOME and KDE are not window managers (they are desktop environments) and a window manager called KWM. together. GNOME is not integrated with any window manager. You can use any window manager you want, although some are written specifically for GNOME (Enlightenment is one). But they all require X to run.

What does it mean to say that an application is based on GNOME or KDE? What if it isn't? Can you still run it?

This just means that it is written using GNOME or KDE libraries. Meaning: 1) the program may not be based on both GNOME and KDE, 2) you have to install GNOME libraries to run KDE-based software, 3) you can run GNOME applications and KDE applications side by side, 4) If you use either environment, you can always run applications that are not based on that environment.

What exactly is GTK (for GNOME) or Troll (for KDE)?

GTK and Qt (Qt is a product of Troll Tech used by KDE) are both widget sets. That is, they provide buttons, menus, scroll bars, and various other objects for program developers to use. Note that applications not based on GNOME or KDE can use GTK or Qt, but all GNOME applications use GTK, and all KDE applications use Qt.

How does the history of Linux (or UNIX) window managers compare with the desktop used by Windows98/95 users

Sample? In particular, how do you rate Microsoft for limiting users' choices by giving them only one desktop, which is believed to be designed for user convenience?

This is a very complicated question. Essentially, Windows provides a set of constructs consisting of a window system, a window manager, a widget set, and a desktop environment, so everyone can only use it. , rather than being able to choose what they like.

What about the Common Desktop Environment (CDE)? Is it because it consumes too much system resources or is not open source and is not widely adopted by Linux users?

Yes, it takes up too much memory. You can get it from RedHat.

--
Tim

-------------------------------- -------------------------------
Date: Wed, 2 Dec 1998 00:34:46 0100 (AMT)
From: Hans Nieuwenhuis, niha@ing.hj.se

Today I saw your email from Linux Gazette and I decided to try to answer your question.

is like this:

X-Windows is designed to be a client-server system. The advantage of this is that you can run the server on a different machine than the one where your monitor is located. You need a client. This may be a program or a window manager. The window manager communicates with the server by asking it to create windows. When the server receives a request, it gives a title bar and lets the application create its own interface. Basically, the window manager is between the server and the application, but it is not required. You can run an application directly on the server without a window manager, but the only things you can do are run the specified application, close it, and shut down the X server (i.e., you cannot move it, resize the window, etc.) .

GUI refers to the graphical user interface, which means that all information presented on the screen is represented by windows, menus, buttons, etc., just like Windows. Everything is interactive, and the interface is built on top of these windows and buttons. The main purpose of the GUI is to provide a unified system for displaying windows and collecting information. A good example is the Alt F4 shortcut key in MS Windows. With this key, you can close any window on the screen. A window manager may be part of this system. This is true in both KDE and CDE. Their common feature is that they have their own window managers, and you can get a unified form on the desktop. Basically, what you see on the desktop is a collection of applications that can run on a system. A unified graphical user interface can have features like drag&Drop and point&shoot and associate applications with certain file types. The question you asked about being based on GNOME or KDE is this: a program is designed to be in which environment it is, so that it can communicate with other applications in that environment. Drag and drop is an example. It's true that some programs won't run without a desktop environment designed for them, but some will. For example, I use KDE programs, but I don't like their window manager, so I use Window Maker, and Window Maker is not designed for the KDE environment, so I have to lose some functionality and cannot use it.

These two libraries: GTK and Qt (the Troll you mentioned) are tool kits. Their basic use is to draw windows, buttons and menus. These will help you structure your interface. If you want to run an application designed for a specific environment, say GNOME, you will at least need the GNOME libraries, like GTK and others.

As I mentioned earlier, the client-server design of the X-Windows system allows users to more flexibly choose their favorite window manager. But basically, they do the same thing as win95/98 systems. Win95/98 limits you to one style and the same look and feel (although you can change the background color, but that's still it), but it doesn't give users the freedom to try other styles and feel. Many popular window managers allow you to define other key combinations. If you don't like GNOME, you can use KDE and vice versa. (There are several others)

All I know about CDE is that it is based on the Motif toolkit (unlike GTK and Qt). This toolkit is not free like GTK (more appropriately Say it is not GPL). I think this may be the main reason why it is not used a lot on Linux. But I don't know if it consumes system resources. The reason I personally don't use it is because it looks silly :-)

That's it, I hope this stuff will be of some use to you. If you have questions, don’t hesitate…………

--
Hans Nieuwenhuis

-------------------------- ------------------------------------------
Date: Sat, 05 Dec 1998 00:29:34 -0500
From: sottek, sottek@quiknet.com

I thought I'd take a moment to answer the question you posted on Linux Gazette. From your question, I can tell you that although you are new to Linux, you see some basic differences in how the interface works. I am currently working at Inter, managing the Unix Cad tool. I have to explain these differences to the administrators every day. I think you will know more than them.

1. What are the differences between the terms GUI, window manager, desktop, and interface (if any

), and what is their relationship with X window?

X windows are a way to draw things on your screen. All X windows clients (the part that's drawn in front of you) know how to respond to certain commands, such as "draw a green box", "draw a dot" and allocate memory for the client image... It's not like you imagine Windows That way. All applications send these commands to your client. This is accomplished via TCP/IP, even if your application and client are on the same machine. This is very important. The primary design flaw in MS Windows is the lack of a network layer in the window system. Every X application (any window...xterm netscape xclock) views "DIS