Go to file
h00574155 c31e3c0b02 Decoupling lidrm fence
Signed-off-by: h00574155 <hujunjian1@huawei.com>
Change-Id: Iddeefafd76ee95ee8d881705e4fa0c4c60f40d37
2022-08-10 07:34:03 +00:00
figures update graphic architecture in README_zh.md 2022-02-28 14:30:36 +08:00
frameworks Decoupling lidrm fence 2022-08-10 07:34:03 +00:00
interfaces Decoupling lidrm fence 2022-08-10 07:34:03 +00:00
rosen Decoupling lidrm fence 2022-08-10 07:34:03 +00:00
utils Decoupling lidrm fence 2022-08-10 07:34:03 +00:00
.clang-format add .clang-format config, for auto code format 2022-03-31 10:28:00 +08:00
.gitattributes update OpenHarmony 2.0 Canary 2021-06-02 02:21:18 +08:00
BUILD.gn Decoupling lidrm fence 2022-08-10 07:34:03 +00:00
bundle.json Decoupling lidrm fence 2022-08-10 07:34:03 +00: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 add surface image ndk 2022-08-04 22:01:52 +08:00
graphic.cfg DFX: reboot the system when rs crash 2022-07-28 09:01:21 +08:00
graphic.rc Decoupling lidrm fence 2022-08-10 07:34:03 +00:00
hisysevent.yaml add event manager 2022-07-14 09:26:19 +08:00
LICENSE update OpenHarmony 2.0 Canary 2021-06-02 02:21:18 +08:00
OAT.xml update OAT.xml. 2022-05-05 12:08:27 +00:00
README_zh.md change media_standard to player_framework 2022-07-12 19:46:45 +08:00
README.md change media_standard to player_framework 2022-07-12 19:46:45 +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
│   ├── dumper                   # graphic dumper code
│   ├── 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