WMS

• Introduction

• Directory Structure

• Compilation and Building

• Description

  • Usage

• Repositories Involved

Introduction

The graphics service uses the client/server (C/S) architecture and is divided into two sub-services: Window Manager Service (WMS) and Input Manager Service (IMS). The application calls the APIs provided by the client to obtain the window status and process events. The server interacts with the hardware to implement display and input event distribution.

• WMS: Manages and combines windows of different applications in a unified manner. Each window is bound to a RootView object.
• IMS: Connects to the underlying input event driver framework to monitor and distribute input events.

Figure 1

Directory Structure

/foundation/window/window_manager_lite
├── frameworks      # Client
│   ├── ims         # Input event management service client
│   └── wms         # Window management service client
├── interfaces      # APIs
│   ├── innerkits   # APIs between modules
├── services        # Server
│   ├── ims         # Input event management service
│   └── wms         # Window management service
└── test            # Test code

Compilation and Building

# Generate the wms_server and libwms_client.so files in the out directory of the product folder through GN compilation.
hb build window_manager_lite

Description

Usage

• WMS provides methods to display various UI components, send event notifications, and process various events. For details, see the related source code.
• test/sample_window provides the unit testing for each WMS API. Refer to it for the usage of WMS.

Repositories Involved

Graphic subsystem

window_manager_lite

graphic_surface_lite

arkui_ui_lite

graphic_graphic_utils_lite