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
/foundation/arkui/ui_lite
├── 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
│ ├── 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 # External 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/window/window_manager_lite/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
Platform Constraints
# Generate the libui.so file in the out directory of the product folder through GN compilation.
hb build -T //foundation/arkui/ui_lite:ui_lite -f #build libui.so
hb build -T //foundation/indow/window_manager_lite/test:sample_ui -f # build UI demo
hb build -T //foundation/arkui/ui_lite/test/unittest:arkui_ui_lite_test -f # build TDD testcases
# To compile the Qt library, see the Qt simulator project at arkui/ui_lite/tools/qt/simulator/simulator.pro.
Components are classified into basic components and container components.
Figure 2 Graphics subsystem components
For details about how to use components and APIs of graphics, see the examples provided in foundation/arkui/ui_lite/test/uitest.
The Qt project can be debugged in the Windows environment. User Guide
Project file path:
arkui/ui_lite/tools/qt/simulator/simulator.pro
For other debugging environments, you can run foundation/window/window_manager_lite/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.
graphic_ui
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。
Activity
Community
Health
Trend
Influence
:Code submit frequency
:React/respond to issue & PR etc.
:Well-balanced team members and collaboration
:Recent popularity of project
:Star counts, download counts etc.