Go to file
2024-04-11 17:06:01 +08:00
etc Merge branch 'master' of gitee.com:openharmony/graphic_graphic_2d into master 2023-10-08 01:20:35 +00:00
figures update graphic architecture in README_zh.md 2022-02-28 14:30:36 +08:00
frameworks !9863 enable blobcache 2024-04-10 11:46:23 +00:00
interfaces !9910 add paragraph_builder interface 2024-04-11 06:57:10 +00:00
rosen !9909 修复健康管理应用图标移动闪烁白线问题 2024-04-11 07:26:54 +00:00
utils GPU subhealth monitoring 2024-04-11 16:48:33 +08:00
.clang-format refactor transition animation with modifier, remove RSTransitionProperties 2022-09-06 11:31:26 +08:00
.gitattributes update OpenHarmony 2.0 Canary 2021-06-02 02:21:18 +08:00
BUILD.gn sync code Signed-off-by: s30029175 <shiqiwei4@huawei.com> 2024-04-09 02:46:57 +00:00
bundle.json !9673 解决产品重启问题 2024-04-09 10:08:28 +00:00
CODEOWNERS 渲染服务code码访问权限校验与管控(part11) 2023-08-30 16:46:20 +08:00
default.scss add window type 2021-12-21 21:12:04 +08:00
flutter.gni Description:change dir graphic/graphic to graphic/graphic_2d 2022-05-19 14:59:57 +08:00
graphic_config.gni merge conflict fix Signed-off-by: s30029175 <shiqiwei4@huawei.com> 2024-04-07 06:27:10 +00:00
graphic.cfg enable critical function 2024-03-25 16:19:26 +08:00
graphic.rc 回退 'Pull Request !3058 : del unused code' 2022-11-24 06:23:33 +00:00
hisysevent.yaml !9292 hgm新增帧率决策打点 2024-03-26 03:25:06 +00:00
LICENSE update OpenHarmony 2.0 Canary 2021-06-02 02:21:18 +08:00
OAT.xml fix bootanimation oat warnning 2024-03-06 16:28:31 +08:00
README_zh.md fix name 2023-07-11 21:55:33 +08:00
README.md quduoyu 2023-05-17 19:00:42 +08:00

graphic_graphic_2d

Introduction

Graphic subsystem provides graphical interface capabilities.

Its main structure is shown in the following figure:

Graphic subsystem architecture diagram

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.

Module Capability Description
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.

content

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

Repositories Involved