Graphic subsystem provides graphical interface capabilities.
Its main structure is shown in the following figure:
The layered description of the OpenHarmony graphics stack is as follows:
• Interface layer: Provides native API capabilities for graphics, including: WebGL, Native Drawing drawing capabilities, OpenGL instruction-level drawing capabilities support, etc.
• Framework layer: divided into five modules: Render Service, Drawing, Animation, Effect, Display and Memory Management.
|Render Servicel||Provides the rendering capabilities of the UI framework. Its core responsibility is to convert ArkUI's control description into drawing tree information, and perform optimal path rendering according to the corresponding rendering strategy. At the same time, it is responsible for the core underlying mechanism of UI sharing in multi-window smoothness and spatial state.|
|Drawing||Provides a standardized interface within the graphics subsystem, and mainly completes basic functions such as 2D rendering, 3D rendering and rendering engine management.|
|Animation||Provides related capabilities of the animation engine.|
|Effect||Mainly completes the ability to process image effects, rendering effects and other effects, including: multi-effect series and parallel processing, adding rendering effects, control interaction effects and other related capabilities during layout.|
|Display and Memory Management||This module is the main module for the decoupling of the graphics stack and hardware. It mainly defines the display and memory management capabilities of OpenHarmony. The defined southbound HDI interface requires different OEMs to complete the adaptation of the OpenHarmony graphics stack. match.|
• Engine layer: includes two modules, 2D graphics library and 3D graphics engine. The 2D graphics library provides the underlying API for 2D graphics rendering, and supports the underlying capabilities of graphics rendering and text rendering. 3D graphics engine capabilities are still under construction.
foundataion/graphic/graphic_2d ├── figures # Markdown referenced image catalog ├── frameworks # framework code directory │ ├── animation_server # animationServer code │ ├── bootanimation # Boot animation directory │ ├── fence # fence code │ ├── vsync # Vsync code ├── rosen # framework code directory │ ├── build # build instructions │ ├── doc # doc │ ├── include # external header file code │ ├── lib # lib │ ├── modules # graphic Each module code of the subsystem │ ├── samples # sample code │ ├── test # develop test code │ ├── tools # tool code ├── interfaces # graphical interface storage directory │ ├── innerkits # internal native interface storage directory │ └── kits # js/napi external interface storage directory └── utils # widget storage directory
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。
：Code submit frequency
：React/respond to issue & PR etc.
：Well-balanced team members and collaboration
：Recent popularity of project
：Star counts, download counts etc.