21 Star 108 Fork 122

OpenHarmony / graphic_ui

Create your Gitee Account
Explore and code with more than 6 million developers,Free private repositories !:)
Sign up
Clone or Download
Cancel
Notice: Creating folder will generate an empty file .keep, because not support in Git
Loading...
README.md

UI

Introduction

The graphics UI module implements a system-level graphics engine.

This module provides the UIKit APIs for application development. You can use the APIs to add animations, manage layouts, transform images, process events, and operates on rich UI components.

The graphics UI directly calls the HAL API or uses the client provided by the Window Manager Service (WMS) to interact with the hardware to complete operations such as event response and image drawing.

Figure 1 Graphics subsystem architecture

Directory Structure

/foundation/graphic/ui
├── frameworks                  # Framework code
│   ├── animator                # Animator module
│   ├── common                  # Common module
│   ├── components              # Components
│   ├── core                    # UI main processes (such as rendering and task management)
│   ├── default_resource
│   ├── dfx                     # Maintenance and test
│   ├── dock                    # Driver adaptation layer
│   │   └── ohos                # OHOS platform adaptation
│   ├── draw                    # Drawing logic
│   ├── engines                 # Drawing engines
│   │   ├── dfb
│   │   ├── general
│   │   ├── gpu_vglite
│   │   └── software_zlite
│   ├── events                  # Events
│   ├── font                    # Fonts
│   ├── imgdecode               # Image management
│   ├── layout                  # Page layout
│   ├── themes                  # Theme management
│   ├── window                  # Window management adaptation layer
│   └── window_manager
│       └── dfb
├── interfaces                  # APIs
│   ├── innerkits               # APIs between modules
│   │   └── xxx                 # Sub-module APIs
│   └── kits                    # Externel APIs
│   │   └── xxx                 # Sub-module APIs
├── test                        # Test code
│   ├── framework
│   │   ├── include             # Header files for the test framework
│   │   └── src                 # Source code for the test framework
│   ├── uitest                  # Display effect test (The executable program is in foundation/graphic/wms/test:sample_ui.)
│   │   └── test_xxx            # Specific UI effect test
│   └── unittest                # Unit testing
│       └── xxx                 # Unit testing for a specific UI component
└── tools                       # Test and simulation tools (simulator projects and resource files)
    └── qt                      # Qt project

Constraints

Platform Constraints

  • The Windows platform supports only Qt and OHOS IDE.
  • For the support of other platforms, see the graphic tag in vendor/hisilicon/[product_name]/config.json. If the graphic tag does not exist, it indicates that the product does not have the graphics subsystem.

Compilation and Building

# Generate the libui.so file in the out directory of the product folder through GN compilation.
hb build -T //foundation/graphic/ui:lite_ui -f  #build libui.so
hb build -T //foundation/graphic/wms/test:sample_ui -f # build UI demo
hb build -T //foundation/graphic/ui/test/unittest:lite_graphic_ui_test -f # build TDD testcases

# To compile the Qt library, see the Qt simulator project at graphic/ui/tools/qt/simulator/simulator.pro.

Description

Component Description

Components are classified into basic components and container components.

  • Basic components: Implement only a single function, such as Text, Button, Image, and List.
  • Container components: Hold and combine child components to implement complex functions.

Figure 2 Graphics subsystem components

Usage

For details about how to use components and APIs of graphics, see the examples provided in foundation/graphic/ui/test/uitest.

  • The Qt project can be debugged in the Windows environment. User Guide

    Project file path:

    graphic/ui/tools/qt/simulator/simulator.pro
  • For other debugging environments, you can run foundation/graphic/wms/test:sample_ui.

    After the building is successful, the executable program out/[product_name]/dev_tools/bin/sample_ui is obtained. You can run the program in an environment to view the display effect of a specific component.

Repositories Involved

Graphic subsystem

graphic_wms

graphic_surface

graphic_ui

graphic_utils

Repository Comments ( 0 )

Sign in to post a comment

About

Graphic ui components | 图形UI组件 expand collapse
C++ and 3 more languages
Apache-2.0
Cancel

Releases

No release

OpenHarmony

Contributors

All

Activities

Load More
can not load any more
1
https://git.oschina.net/openharmony/graphic_ui.git
git@git.oschina.net:openharmony/graphic_ui.git
openharmony
graphic_ui
graphic_ui
master

Search

182229 41614e54 1850385 182230 7885ed45 1850385