代码拉取完成，页面将自动刷新
The Graphics subsystem mainly consists of user interface (UI) components, layout, animator, font, input event, window management, and rendering and drawing modules. It is an application framework that can be built on the LiteOS to develop OpenHarmony applications for Internet of Things (IoT) devices with limited hardware resources or on the standard OS to develop OpenHarmony applications for standard- and large-system devices.
The Graphics subsystem mainly consists of UI components, layout, animator, font, input event, window management, and rendering and drawing modules. It is an application framework that can be built on the LiteOS to develop OpenHarmony applications for IoT devices with limited hardware resources.
Figure 1 Graphics subsystem architecture
The related modules are described as follows:
/foundation/arkui
├── ui_lite # UI module, including UI components, animations, and fonts
/foundation/graphic
├── surface_lite # Shared memory
├── graphic_utils_lite # Basic graphics library and hardware adaptation layer
/foundation/window
└── window_manager_lite # Window and input event management
For details, see the README and test directory of each repository.
Graphics subsystem
The Graphics subsystem provides graphics APIs.
The following figure shows the architecture of the Graphics subsystem.
The OpenHarmony graphics stack is divided into the following layers:
Interface layer: provides native APIs for the Graphics subsystem, including WebGL, native drawing, and OpenGL command-level drawing.
Framework layer: consists of the Render Service, Drawing, Animation, Effect, and Display and Memory Management modules.
| Module | Description |
|---|---|
| Render Service | Performs UI framework drawing. This module converts the ArkUI component description into drawing tree information and renders the optimal path based on the corresponding rendering policy. It also provides the core underlying mechanism for multi-window smoothness and spatial UI sharing. |
| Drawing | Provides standard internal interfaces in the Graphics subsystem to implement 2D rendering, 3D rendering, and rendering engine management. |
| Animation | Provides capabilities related to the animation engine. |
| Effect | Processes image effects and rendering effects, including cascading and parallel processing of multiple effects, and adding rendering effects and component interaction effects during layout. |
| Display and Memory Management | Decouples the graphics stack from hardware and provides OpenHarmony display and memory management. OEMs need to adapt the HDIs defined by this module. |
Engine layer: consists of the 2D graphics library and 3D graphics engine. The 2D graphics library provides bottom-layer APIs for 2D graphics drawing (including text drawing). The 3D graphics engine capability is being developed.
foundation/graphic/standard/
├── figures # Images referenced by Markdown
├── frameworks # Framework code
│ ├── animation_server # Animation server code
│ ├── bootanimation # Boot animation
│ ├── dumper # Graphic dumper code
│ ├── fence # Fence code
│ ├── surface # Surface code
│ ├── vsync # Vsync code
├── rosen # Framework code
│ ├── build # Build description
│ ├── doc # doc
│ ├── include # Code of external header files
│ ├── lib # lib
│ ├── modules # Graphic subsystem code, organized by module
│ ├── samples # Sample code
│ ├── test # Development and test code
│ ├── tools # Tool code
├── interfaces # Graphics APIs
│ ├── innerkits # Native APIs
│ └── kits # JS APIs and native APIs
└── utils # Utilities
Programming language version: C++ 11 or later
For details, see the README and test directory of each repository.
Graphics subsystem
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。