{"id":35315,"date":"2024-11-11T13:21:23","date_gmt":"2024-11-11T05:21:23","guid":{"rendered":"https:\/\/www.deepin.org\/?p=35315"},"modified":"2024-12-17T10:21:08","modified_gmt":"2024-12-17T02:21:08","slug":"dde-treeland","status":"publish","type":"post","link":"https:\/\/www.deepin.org.cn\/en\/dde-treeland\/","title":{"rendered":"Unveiling the Treeland Technology Behind DDE(deepin Desktop Environment)"},"content":{"rendered":"\"\"<\/p>\n

Recently, the deepin\u00a0 community made an appearance at COSCon'24, the 9th China Open Source Conference, where senior desktop R&D engineer Zhang Dingyuan presented a technical sharing session titled \"Treeland: The Stepping Stone of DDE's Progress.\"<\/p>\n

Taking this opportunity, let's discuss how to pursue gorgeous animations and smooth experiences while maintaining a lightweight and efficient system. It's like playing a balancing game, with designers and architects standing at opposite ends of a scale, one side being a visual feast and the other a performance beast. Striking the balance between these two requires our R&D team to cleverly \"sacrifice\" some hair (brainpower) to achieve.<\/p>\n

\"\"<\/p>\n

deepin in\u00a0 COSCon'24<\/p>\n

 <\/p>\n

Historical Background<\/strong><\/h1>\n

During the deepin 15 era, the development team utilized Mutter to provide smooth graphics effects for high-performance devices and Metacity to ensure system fluidity on low-specification devices. However, in the deepin 20 era, the team decided to adopt KWin as the new window manager due to its robust features and the ability to disable compositing, making it adaptable to various hardware configurations. As a result, the combination of Mutter and Metacity was abandoned to ensure a smooth and secure graphical interface experience across different devices. Nevertheless, the continuous advancement of technology has once again prompted us to face technological innovation.<\/p>\n

 <\/p>\n

Technical Choices: X11 and Wayland<\/strong><\/h1>\n

Currently, under Linux, there are two technology stacks: the long-standing X11 and the relatively newer Wayland. Let's compare these two technologies together.<\/p>\n

\n\n\n\n\n\n\n\n\n\n
<\/td>\nX11<\/td>\nWayland<\/td>\n<\/tr>\n
Architecture<\/td>\nThe traditional client-server model, supporting network transmission and remote display.<\/td>\nSimplified design, removing the complexity of the \u00d7 server, improving efficiency and response speed, focusing on local display.<\/td>\n<\/tr>\n
Performance<\/td>\nDue to its outdated design, performance is suboptimal in modern scenarios, relying on extensions and patches to achieve modern graphical effects.<\/td>\nModernized design, simplified rendering process, with significant performance improvements, especially in animation and window operations.<\/td>\n<\/tr>\n
Security<\/td>\nSignificant security issues, applications can access each other's window information and are susceptible to interference from malicious programs.<\/td>\nStrong application isolation, unable to access the graphics or input\/output of other programs, ensuring high security.<\/td>\n<\/tr>\n
Scalability and Compatibility<\/td>\nX11 has very extensive application support and compatibility, with many old applications and desktop environments still relying on the X11 protocol.<\/td>\nGradually supported by mainstream desktop environments, but the ecosystem is not as widespread as X11, requiring compatibility layers to run X11 applications.<\/td>\n<\/tr>\n
Input Device Support<\/td>\nMature support for traditional input devices, but not flexible enough in multi-touch and gesture support.<\/td>\nOptimized support for modern hardware, especially in multi-touch and gesture recognition.<\/td>\n<\/tr>\n
Remote Desktop and Network Transparency<\/td>\nSupports the remote transmission of display content over the network, suitable for professional use.<\/td>\nLacks X11's network transparency, with limited remote desktop functionality, often requiring third-party tools.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
<\/section>\n

In summary, X11, as a veteran display server, boasts extensive compatibility and a mature ecosystem. However, its architecture has certain limitations in terms of security, performance, and ease of use. In contrast, Wayland, as an emerging display server, simplifies the communication process between clients and servers, reducing potential security vulnerabilities and thus enhancing overall security.<\/p>\n

Furthermore, Wayland has significant advantages in performance, being better equipped to support modern display technologies, such as high-resolution and high-frame-rate display tasks. Lastly, Wayland's architectural design makes its configuration and management relatively straightforward, resulting in a more user-friendly experience, which helps attract more novice users.<\/p>\n

 <\/p>\n

Architectural Design and the New Window Manager Treeland<\/strong><\/h1>\n

From a technical perspective, we believe it is time to update our technical solution. The former model of X11 + window manager + compositor was flexible but did not meet the demands. Wayland offers an updated mechanism that avoids screen tearing by integrating the window manager, compositor, and display system at the foundation level.<\/p>\n

Therefore, DDE decided to develop a new window manager\u2014Treeland\u2014in conjunction with Wayland. It uses wlroots as the underlying Wayland base library, without modifying the wlroots code, allowing for synchronization with upstream progress at any time to obtain new features and fixes. The upper layer uses Qt, making the technology stack more unified. It is designed specifically to meet the needs of DDE, avoiding common issues such as destructive adjustments, synchronization problems, and maintenance costs associated with using third-party window managers.<\/p>\n

\"\"<\/p>\n

The diagram above illustrates which projects or interfaces Treeland will use overall to complete its functions.<\/p>\n

\"\"<\/p>\n

Treeland Structure Diagram<\/p>\n

 <\/p>\n

Treeland's Technical Structure and Features
\n<\/strong><\/h1>\n
\n
\n
\n
\n
\n
<\/section>\n<\/section>\n<\/section>\n<\/section>\n<\/section>\n<\/section>\n
\n

1\u3001Important Project Introduction<\/strong><\/h2>\n<\/section>\n
<\/section>\n
\n
\n