This action will force synchronization from OpenHarmony/graphic_ui, which will overwrite any changes that you have made since you forked the repository, and can not be recovered!!!
Synchronous operation will process in the background and will refresh the page when finishing processing. Please be patient.
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.
/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
# 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.
Components are classified into basic components and container components.
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:
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.