oh-interfaces-ipc-to-service

Original：🇨🇳 Chinese

Translated

Add a transparent transmission channel in the graphic_2d repository of the OpenHarmony project. This capability is invoked when users want to add an RSInterface interface in the graphic_2d repository and specify that the interface is ToService.

2installs

Sourceopenharmonyinsight/openharmony-skills

Added on2026-02-25

NPX Install

npx skill4agent add openharmonyinsight/openharmony-skills oh-interfaces-ipc-to-service

SKILL.md Content (Chinese)

View Translation Comparison →

You are a senior graphics development engineer. Now you need to add a transparent transmission interface in the rs_interfaces.cpp/.h files of the OpenHarmony graphic_2d repository. Considering that some of these requirements depend on underlying hardware implementation while others do not, we can uniformly establish the transparent transmission channel at the rs_screen.cpp/.h layer, and leave appropriate blank spaces in the new interface implementation in rs_screen.cpp for users to implement the underlying calling logic. This task usually includes the following steps:

Ask for the interface declaration: The user provides the expected new interface declaration. Note that if the provided interface declaration does not comply with C++ syntax, you need to inform the user and ask for the correct one.
Ask for more interface information: Ask the user whether the interface requires @System authentication or @Foundation authentication, as these two pieces of information will be used in subsequent code generation.
Clarify reference interfaces: Focus on referring to the call chains of the SetDualScreenState() and GetPanelPowerStatus() interfaces in rs_interfaces.cpp/.h.
Add transparent transmission channel: Client side: Since the interface channel of the graphic_2d repository adopts a C/S architecture, on the Client side, you usually need to add interfaces in rs_interfaces.cpp/.h and rs_render_service_client.cpp/.h.
Add transparent transmission channel: Service side: On the Service side, you usually need to add interfaces in rs_client_to_service_connection.cpp/.h, rs_screen_manager.cpp/.h, and rs_screen.cpp/.h.
Add transparent transmission channel: IPC: In the graphic_2d repository, communication between the Client side and Service side is implemented via IPC. You need to add the declaration of the new interface in the rs_iclient_to_service_connection.h abstract class. In rs_client_to_service_connection_proxy.cpp/.h, call the capabilities of MessageParcel and SendRequest according to the parameter list and return value of the interface. In the OnRemoteRequest() function of rs_client_to_service_connection_stub.cpp, add a case to respond to the proxy's request, including reading the MessageParcel, calling the new interface in rs_client_to_service_connection.cpp, and writing the call result back to the Client side via MessageParcel. Additionally, there is one note:

The case has a dedicated enumeration value stored in rs_iclient_to_service_connection_ipc_interface_code.h. When adding a new interface, you need to synchronously add a new enumeration in this file.

Add transparent transmission channel: Authentication-related matters: The new enumeration value added in rs_iclient_to_service_connection_ipc_interface_code.h will also be used in two places:

In the descriptorCheckList of rs_client_to_service_connection_stub.cpp, you need to add this enumeration value;
In the IsExclusiveVerification function of rs_irender_service_connection_ipc_interface_code_access_verifier.cpp, you need to add a case, and call IsSystemCalling or IsFoundationCalling for authentication according to the user's expected authentication method.

Check the code: Finally, you need to check whether the code modifications strictly comply with C++ 17 syntax, and whether they are highly consistent with the existing code style (such as camelCase for function names and lower camelCase for variable names).

oh-interfaces-ipc-to-service

NPX Install

Tags

SKILL.md Content (Chinese)