One little correction: the window manager is not much responsible for the "look'n'feel" of the GUI - rather it only attaches the "window decorations" (those borders around windows, with close buttons, titles etc.) and manages their positions on the screen, allowing the user to move them around, minimize/maximize, close etc. The "look'n'feel" of the GUI is the job of a different component of the system, the one you didn't mention: the "widget library", sometimes called the "toolkit". Some well-known examples of widget libraries are GTK+ and Qt, but there are a couple of others (usually older and crude looking :q ), like AWT, Tk etc.
The de is a bunch of programs built around the wm. The compositor and tge window manager take care of stuff like transparency while a tool like nitrogen will draw the wallpaper. A de is basically a bunch of these programs together. Its possible and pretty easy to build your own de.
@@devikakrishna4464 Yeah, writing one is relatively easy. Having people using it to build their software upon it is much, much harder :q It helps when the toolkit has a nice clean API, but still I don't think many people would be willing to rewrite their existing software for a new toolkit unless the old one is getting obsoleted and they don't have much choice :q
This was an excellent and concise introduction to the X11 system. It would be nice to see another one about display managers and getting to the next level. Why did you stop making these?
Sounds easy, until you try to run an x server inside an android app. It then becomes hell due to opengl es lol. Btw the x server is also responsible for half of your OpenGL acceleration. If your x server doesnt support this, then you will not be able to run any opengl until you disable "DRI" (Direct Rendenring Interface) so your system doesnt try to use it for such a thing. But doing so will force you to use software graphics.
