Interface configuration method and device, equipment and storage medium

Abstract

The embodiment of the invention discloses an interface configuration method and device, equipment and a storage medium. The method comprises the steps that a component configuration interface of target equipment is displayed; in response to a component selection operation for the component configuration interface, displaying a binding interface corresponding to the selected target component; in response to a function binding operation for the binding interface, binding the selected target function item with the target component; according to the target component and the binding information of the target component, an interface configuration file is generated, and the interface configuration file is used for generating an interface of the target device. According to the scheme, the problem of tedious interface configuration scheme flow in the prior art can be solved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to an interface configuration method, device, equipment and storage medium. Background Art

[0002] With the development of Internet technology, more and more smart devices support control through applications. For various operating platforms, the key to controlling smart devices through applications lies in interface display and interaction, both of which often require programmers to write corresponding codes based on the requirements described by product managers, and then go online after the interface passes the test and finally deliver it to users.

[0003] However, when new functions or controls need to be added to the interface, the programmer is required to rewrite the code and configure the interface based on the rewritten code. If the number of iterations and the content of the iterations of the interface are complex, the programmer is required to write a large amount of code, which affects the time of interface release. It can be seen that the current interface configuration solution process is cumbersome. Summary of the invention

[0004] In view of this, the present invention provides an interface configuration method, device, equipment and storage medium, which are used to solve the problem of cumbersome interface configuration process in the prior art. In order to achieve one or part or all of the above purposes or other purposes, the present invention proposes an interface configuration method, device, equipment, storage medium and interface configuration component.

[0005] In a first aspect, the present application provides an interface configuration method, comprising:

[0006] Display the component configuration interface of the target device;

[0007] In response to a component selection operation on the component configuration interface, displaying a binding interface corresponding to the selected target component;

[0008] In response to a function binding operation on the binding interface, binding the selected target function item with the target component;

[0009] An interface configuration file is generated according to the target component and the binding information of the target component, and the interface configuration file is used to generate an interface of the target device.

[0010] In a second aspect, the present application provides an interface configuration method, comprising:

[0011] In response to an interface request operation for a target device, obtaining an interface configuration file corresponding to the target device;

[0012] Parsing the interface configuration file to obtain a target component and binding information of the target component; the binding information carries a target function item bound to the target component;

[0013] An interface configuration is performed according to the target component and binding information of the target component to obtain an interface of the target device.

[0014] In a third aspect, the present application provides an interface configuration device, comprising:

[0015] A first display module, used to display the component configuration interface of the target device;

[0016] A second display module, configured to display a binding interface corresponding to a selected target component in response to a component selection operation on the component configuration interface;

[0017] A binding module, configured to bind the selected target function item to the target component in response to a function binding operation on the binding interface;

[0018] A generating module is used to generate an interface configuration file according to the target component and the binding information of the target component, wherein the interface configuration file is used to generate an interface of the target device.

[0019] In some embodiments of the present application, the binding module includes:

[0020] A first determining unit, configured to determine, in response to a function binding operation on the binding interface, a target function item corresponding to the function binding operation;

[0021] A second determining unit, configured to determine attribute information of the target component in response to an attribute editing operation on the target component;

[0022] A binding unit is used to bind the target function item, the target component and the attribute information of the target component.

[0023] In some embodiments of the present application, the first determining unit is specifically configured to:

[0024] In response to a function binding operation on the binding interface, displaying a plurality of function items corresponding to the target device;

[0025] In response to a selection operation on the function item, the function item corresponding to the selection operation is determined to be a target function item.

[0026] In some embodiments of the present application, the second determining unit is specifically configured to:

[0027] Displaying the information editing interface of the target function item;

[0028] In response to an editing operation on the information editing interface, editing information corresponding to the editing operation is determined, and the editing information is associated with the target function item.

[0029] In some embodiments of the present application, the interface configuration device further includes:

[0030] A display unit, used to display a function item definition interface of the target device;

[0031] The configuration unit is used to configure the function of the target device in response to the configuration operation on the function item definition interface to determine the function item corresponding to the target device.

[0032] In some embodiments of the present application, the function item definition interface includes a custom configuration entry and a standard function configuration entry, and the configuration unit is specifically used to:

[0033] In response to a trigger operation on the custom configuration entry, display a custom function configuration interface, generate a custom function item according to the configuration operation on the custom function configuration interface, and configure the custom function item as a function item of the target device; and / or,

[0034] In response to a trigger operation on the standard function configuration entry, a standard function list is displayed, and according to a selection operation on a standard function item in the standard function list, the standard function item corresponding to the selection operation is configured as a function item of the target device.

[0035] In some embodiments of the present application, the display unit is specifically used for:

[0036] A function list configured for the target device is displayed, wherein the function list includes the standard function items and / or the custom function items corresponding to the target device.

[0037] In some embodiments of the present application, the component configuration page includes a component type list, a first display area, and a second display area. The component type list includes multiple component types. The first display module is specifically used to:

[0038] In response to a first selection operation on a target component type in the component type list, displaying a component gallery corresponding to the target component type in the first display area, the component gallery including at least one preset component icon;

[0039] In response to a second selection operation on a target component icon in the first display area, adding the target component icon to the second display area, where the second display area is a component display page corresponding to the target device;

[0040] The second display module is specifically configured to display a binding interface corresponding to the target component icon in response to a component selection operation on the target component icon in the second display area.

[0041] In some embodiments of the present application, the generating module is specifically used for:

[0042] Generate a description file of the target component based on the target component and the binding information of the target component;

[0043] An interface configuration file is generated according to the preset compilation information of the target component and the description file.

[0044] In a fourth aspect, the present application further provides an interface configuration device, comprising:

[0045] An acquisition module, configured to acquire an interface configuration file corresponding to the target device in response to an interface request operation for the target device;

[0046] A parsing module, used to parse the interface configuration file to obtain a target component and binding information of the target component; the binding information carries a target function item bound to the target component;

[0047] A rendering module is used to configure the interface according to the target component and the binding information of the target component to obtain the interface of the target device.

[0048] Fifth aspect:

[0049] A computer program is stored thereon, and when the computer program is executed by the processor, the computer program in the interface configuration method of each embodiment of the present application is implemented.

[0050] Sixth aspect:

[0051] The present application provides a computer program product, including a computer program, which implements the steps of the interface configuration method in each embodiment of the present application when executed by a processor.

[0052] Implementing the embodiments of the present application will have the following beneficial effects:

[0053] After displaying the target device component configuration interface, in response to the component selection operation on the component configuration interface, the binding interface corresponding to the selected target component is displayed. Then, in response to the function binding operation on the binding interface, the selected target function item is bound to the target component. Finally, according to the target component and the binding information of the target component, an interface configuration file is generated. The interface configuration file is used to generate the interface of the target device. Therefore, when adding new functions or controls to the interface, the programmer does not need to rewrite the code. Thus, interface configuration events with many iterations and complex iteration contents can be met, that is, the time of interface configuration is reduced, thereby improving the efficiency of interface configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0055] in:

[0056] Figure 1 An application environment diagram of the interface configuration method provided in an embodiment of the present application;

[0057] Figure 2 A flowchart of the interface configuration method provided in the embodiment of the present application;

[0058] Figure 3 Another schematic diagram of the flow of the interface configuration method provided in the embodiment of the present application;

[0059] Figure 4 A schematic diagram of an interface configuration method provided in an embodiment of the present application;

[0060] Figure 5 A schematic diagram of a function definition interface of an interface configuration method provided in an embodiment of the present application;

[0061] Figure 6 A schematic diagram of an interface for configuring a large placeholder image in the interface configuration method provided in an embodiment of the present application;

[0062] Figure 7 This is a schematic diagram of an interface when configuring an account information component in the interface configuration method provided in an embodiment of the present application;

[0063] Figure 8 A schematic diagram of a configuration interface in the interface configuration method provided in an embodiment of the present application;

[0064] Fig. 9Another schematic diagram of configuring an interface in the interface configuration method provided in an embodiment of the present application;

[0065] Fig.10 A schematic diagram of the structure of the main modules of the framework provided in the embodiment of the present application;

[0066] Fig.11 A schematic diagram of a configuration file directory provided in an embodiment of the present application;

[0067] Fig.12 A schematic diagram of the structure of the interface configuration device provided in an embodiment of the present application;

[0068] Fig.13 Another structural schematic diagram of the interface configuration device provided in an embodiment of the present application;

[0069] Fig.14 An internal structure diagram of a computer device is provided for an embodiment of the present application. DETAILED DESCRIPTION

[0070] The interface configuration method provided in this application can be applied to Figure 1 In the application environment shown. Figure 1 An interface configuration system is provided, which includes a smart device 100, a gateway 200 communicatively connected to the smart device 100, a router 300, a server 400, and a terminal 500.

[0071] The smart device 100 accesses the gateway 200 in the interface configuration system, and communicates with the gateway 200 through its own configured communication module, and is then controlled by the gateway 200. In one embodiment, the smart device 100 accesses the gateway 200 through a local area network path or a wide area network path, and is deployed in the gateway 200. Among them, the local area network may include ZIGBEE or Bluetooth, and the wide area network may include 2G / 3G / 4G / 5G / WIFI, etc.

[0072] The gateway 200 establishes a network connection with the terminal 500 or the server 400 through the router 300. In one embodiment, the gateway 200 and the terminal 500 may establish a network connection through a local area network or a wide area network path. The network 200 is connected to interact with the terminal 500, so that the user can control the smart home device connected to the gateway to perform corresponding actions with the help of the terminal 500 or the smart device 100.

[0073] The terminal 500 may be a smart phone, a laptop, a personal computer, a tablet computer, a smart control panel or other smart devices that can be connected to a network, which is not limited here. The server may be implemented as an independent server or a server cluster composed of multiple servers.

[0074] The present application provides an interface configuration method, including: displaying a component configuration interface of a target device; in response to a component selection operation on the component configuration interface, displaying a binding interface corresponding to the selected target component; in response to a function binding operation on the binding interface, binding the selected target function item with the target component; generating an interface configuration file based on the target component and the binding information of the target component.

[0075] See also Figure 2 , provides an interface configuration method, which is described by taking the method applied to an electronic device as an example, and the electronic device may be Figure 1 The terminals, smart devices, gateways, servers, etc. in the system specifically include the following steps:

[0076] S101, displaying a component configuration interface of a target device.

[0077] The target device refers to the device that needs to be configured with the interface. The target device can be a smart home device, such as a smart light bulb, smart socket, smart thermostat, etc. The component configuration interface is a user interface that allows users to select, customize, and configure various components on the device. For example, a user can open a visual editing tool for interface rendering (such as an interface rendering application), and then display the component configuration interface in the visual editing tool. The component configuration interface can display different components, which refer to elements used to control or display the status of the device, such as the display component of a temperature and humidity sensor, the switch button of a light control, etc. Components may specifically include control components, information display components, and visual element components. Control components allow users to perform operations, such as switch buttons, sliders, selectors, etc., to control the functions of the device; information display components are used to display device status information or serve as an entry for users to further operate, such as displaying the device's online status, battery level, etc.; visual element components may specifically include header main visual components and placeholder large image components. The header main visual component is one of the most conspicuous parts of the user interface, usually located at the top or header area of ​​the screen. Its main purpose is to provide brand recognition, display the name, brand, etc. of the application or device, and help users immediately identify which product or service the interface belongs to. In addition, the header main visual component also includes other navigation elements, such as the main menu button, user account information, or search bar, so that users can quickly access other functions or information; placeholder large image components are used to display eye-catching images, which can be device icons, product pictures, or graphics related to application functions.

[0078] S102: In response to a component selection operation on a component configuration interface, display a binding interface corresponding to the selected target component.

[0079] The component selection operation refers to the operation of the user selecting a specific component in the component configuration interface, such as the click operation of clicking a component, the drag operation of dragging a component, or the long press operation of long pressing a component; the binding interface refers to an interface that is displayed after the user selects a component, and the binding interface allows the selected component to be associated with the device. In the binding interface, the binding interface related to the selected component will be displayed. It can be understood that due to the different functions and uses of different types of components, different types of components will correspond to different binding interfaces. For example, in the binding interface corresponding to the control component, the binding interface can display all available control functions, such as the switch status of the device; in the binding interface corresponding to the information display component, the binding interface can list all data types that can be displayed, such as temperature, humidity, power, etc.; in the binding interface corresponding to the main visual component of the head, the binding interface can display the brand, application name or other visual elements corresponding to the target device; in the binding interface corresponding to the placeholder large image component, the binding interface can display the selection of device icons, product pictures or promotional images. For example, the user can choose to bind the large image component to a specific image resource and set the image display method, such as static display or carousel.

[0080] It can be seen that through the component configuration interface, users can configure appropriate components for the interface of smart home devices, and associate the selected components with the device information through the binding interface to achieve personalized and functional interface design.

[0081] S103: In response to the function binding operation on the binding interface, the selected target function item is bound to the target component.

[0082] Binding refers to the process of connecting a component to the target functional item of the target device. Binding is a key step in personalizing and functionalizing the device interface, allowing users to define the behavior of the device interface through visual editing tools without writing code.

[0083] For example, after the user selects a target component in the component configuration interface of the visual editing tool, the terminal can display the binding interface corresponding to the target component. The binding interface displays the function items corresponding to the target device. These function items represent the actions that the target device can perform or the types of data displayed. The user can select a target function item that matches the selected component from the function item list for binding.

[0084] Specifically, the user selects a header main visual component and sets it to display the brand name and icon through the binding interface. For the placeholder large image component, the user selects an image representing the smart thermostat in the binding interface and sets it to static display or looping.

[0085] S104: Generate an interface configuration file according to the target component and the binding information of the target component.

[0086] Among them, the interface configuration file is used to generate the interface of the target device. The interface configuration file describes in detail the various components that make up the user interface, such as buttons, text labels, sliders, charts, etc., so that the device's user interface (UI) can be rendered and displayed according to the user's specific configuration. Binding information refers to the details of the association between the component and the function or data source of the device. For example, the terminal collects the binding information of all components, including the functional items, property settings, and trigger conditions to which they are bound. Then, an interface configuration file is generated based on the collected binding information. The interface configuration file is usually stored in JSON, XML or other formats, which contains all the data required to render the user interface.

[0087] In one embodiment, the terminal collects binding information of all components including component identification, bound function items, property settings, and trigger conditions. Then, the terminal generates an interface configuration file in JSON format according to the collected binding information.

[0088] In summary, after displaying the target device component configuration interface, the embodiment of the present application responds to the component selection operation on the component configuration interface and displays the binding interface corresponding to the selected target component. Then, in response to the function binding operation on the binding interface, the selected target function item is bound to the target component. Finally, according to the target component and the binding information of the target component, an interface configuration file is generated. The interface configuration file is used to generate the interface of the target device. Therefore, when adding new functions or controls to the interface, the programmer does not need to rewrite the code. Thus, interface configuration events with many iterations and complex iteration content can be met, that is, the time of interface configuration is reduced, thereby improving the efficiency of interface configuration.

[0089] In some embodiments of the present application, before the step of “displaying the component configuration interface of the target device”, the following steps may be specifically included:

[0090] Display the function item definition interface of the target device;

[0091] In response to the configuration operation on the function item definition interface, the function of the target device is configured to determine the function item corresponding to the target device.

[0092] It is understandable that the function items of the target device can be pre-set, and the user can select the function that he wants to use on the target device from the pre-defined function items according to his own needs and preferences. Configuration operation refers to the operation of setting and adjusting the function items of the device by the user. The user can configure all the function items supported by the target device on the function item definition interface. The user configures each function item of the target device according to the needs of the target device. For example, for the temperature sensor, which is a target device, it needs to display various functions such as device icon, temperature information, humidity information, battery information, etc., then on the function definition interface corresponding to the temperature sensor, the corresponding function items can be configured for each required function.

[0093] When configuring each function item, the user can also make detailed definitions for the corresponding function items, for example, enter necessary parameters in the function item definition interface, such as temperature alarm threshold, humidity automatic adjustment range, function type, value type, ID name, function description, etc., thereby completing the function configuration of the function items of the target device. By configuring the function items, it is ensured that the target device can operate according to the user's preferences and needs. After the configuration is completed, these function items are associated with the target device.

[0094] In some embodiments of the present application, the function item definition interface includes a custom configuration entry and a standard function configuration entry, and the step of "configuring the function of the target device in response to the configuration operation on the function item definition interface to determine the function item corresponding to the target device" includes at least one of the following:

[0095] In response to a trigger operation on a custom configuration entry, a custom function configuration interface is displayed, and a custom function item is generated according to a configuration operation on the custom function configuration interface, and the custom function item is configured as a function item of a target device;

[0096] In response to a trigger operation on a standard function configuration entry, a standard function list is displayed, and according to a selection operation on a standard function item in the standard function list, the standard function item corresponding to the selection operation is configured as a function item of the target device.

[0097] The configuration entry is a component or a function point in the function item definition interface. The configuration entry allows the user to enter specific settings. Therefore, it can be understood that the custom configuration entry and the standard function configuration entry are both configuration entries with specific functions in the function item definition interface. The custom configuration entry allows the user to create and configure unique functions according to the specific needs of the target device, while the standard function configuration entry allows the user to configure preset standard functions according to the needs of the target device.

[0098] Standard functions are pre-defined functions in visual editing tools that may be reused by multiple devices. For example, the function of displaying battery power is a function that different types of devices will use. In visual editing tools, this function can be pre-defined as a standard function and included in the standard function library of the visual editing tool. When configuring a specific device, the function in the standard function library can be directly added as a function item of the corresponding device without the need to define the function in detail. Standard function items usually reflect the main features and uses of the device, providing users with a ready-to-use experience.

[0099] Custom functions refer to unique functions created and configured by users based on the specific needs of specific devices. These functions may not be included in the standard function library of the visual editing tool, but can be implemented by users customizing new function items. For example, the user selects the "Custom Function" option through the function item definition interface of the target device, and then displays the custom function configuration interface. Then, the user creates a new function called "Night Mode" to automatically activate the security camera and adjust the light to the night light mode at night. After the user completes the configuration, the user names this custom function "Night Security Mode" and saves the configuration information. The configured custom function can be used as the function item of the target device. It is understandable that the configured custom function can also be set as a standard function. For example, after the configuration of the customized new function "Night Mode" is completed, if the user believes that the function is likely to be used on other devices, the custom function can be set as a standard function, so that the function enters the standard function library. When configuring other devices, if other devices also need to use this function, then the function can be directly selected in the standard function library for association.

[0100] For a certain target device, the required function items may all be in the standard function library of the visual editing tool. In this case, when configuring the target device, the required function items can be directly selected from the standard function list of the standard function library as the function items of the target device. For other target devices, all the required function items may need to be redefined. In this case, when configuring the target device, it is necessary to trigger the custom configuration entry to enter the custom function configuration interface to generate custom function items and configure the custom function items as the function items of the target device. For some other target devices, some of the required function items are in the standard function list of the standard function library, and some need to be customized. In this case, when configuring the target device, it is necessary to perform corresponding trigger operations on the custom configuration entry and the standard function configuration entry respectively to complete the function item configuration of the target device.

[0101] Therefore, the custom function items and standard function items of the function item definition interface are configured to meet the specific needs of different target devices, thereby improving the flexibility of interface configuration.

[0102] In some embodiments of the present application, after configuring the functions of the target device, the following steps may also be included:

[0103] Displays a list of features that have been configured on the target device.

[0104] The function list includes standard function items and / or custom function items corresponding to the target device. The user can learn the standard function items and custom function items corresponding to the target device through the configured function list. For example, the user can see the standard function items of device A, such as "automatic dimming", "temperature control", "security alarm", etc. The user can also see the custom function items of device A, such as "night mode" or "automatic door lock when leaving home". By displaying the configured function list of the target device, it is convenient for the user to check and check whether the function items of the target device are accurately and completely configured.

[0105] In some embodiments of the present application, the step of “binding the selected target function item with the target component in response to the function binding operation on the binding interface” may specifically include:

[0106] In response to a function binding operation on a binding interface, determining a target function item corresponding to the function binding operation;

[0107] In response to a property editing operation on a target component, determining property information of the target component;

[0108] Bind the target function item, target component and the attribute information of the target component.

[0109] Property editing operation refers to the operation in which the user edits the properties of the selected target component. The properties of the target component include appearance properties, layout properties, text properties, state properties or interaction properties, etc. Among them, appearance properties include color, font, size, border, shadow, transparency, etc.; layout properties include the position, width, height, margin, padding, and alignment of the component in the interface; text properties include text content, font size, font style, line spacing, and text color; state properties include the display method of the component in different states, such as disabled state, hover state, active state, etc.; interaction properties include the behavior when the user interacts with the component, such as the click effect of a button, the toggle state of a switch, and the drag feedback of a slider.

[0110] After binding the function item, the user can edit the properties of the target component, such as label, size, color, position, etc., to ensure that the performance of the target component on the interface meets the user's expectations. After the user completes the property editing, these property information are bound together with the target component and the target function item. For example, after the user selects the target component, the property editor displays all editable properties of the target component, such as color, size, font, text content, border style, etc. The user modifies the property value as required. For example, change the background color of the button or adjust the size of the slider, and then bind the target function item, the target component, and the property information of the target component.

[0111] Specifically, after the user selects a target component of the target device, the terminal displays a binding interface, which can display all available function items, such as "turn on the light", "turn off the light", etc. The user selects the "turn on the light" function item in the binding interface and binds it to the target component, so that the target component is configured as a light-on component, so that when the user clicks on the target component, the smart light bulb will turn on. Then, the user edits the properties of the target component and sets the property information of the target component to correspond to the function item "turn on the light", such as editing the main text content, sub-text content, specific description, component icon style, component interaction information and other property information of the target component, wherein the main text content, sub-text content, specific description, component icon style, etc. can be used to change the display form of the target component so that the target component is displayed in a display form corresponding to the target function item; the component interaction information can be used to determine the change adjustment of the target component in the interface. It can be understood that when the target component is bound to different target function items, the corresponding property information may be different.

[0112] After editing the property information of the target component, the target function item, the target component and all the property information of the target component can be bound. The user can specifically bind the "turn on light" function item, the target component and all the property information by clicking the "bind" or "apply" button in the interface.

[0113] In some embodiments of the present application, the step of “determining, in response to a function binding operation on a binding interface, a target function item corresponding to the function binding operation” may specifically include:

[0114] In response to a function binding operation on the binding interface, display multiple function items corresponding to the target device;

[0115] In response to a selection operation on a function item, the function item corresponding to the selection operation is determined to be a target function item.

[0116] The multiple function items corresponding to the target device refer to various operation and data display options associated with the specific device. These function items are predefined, such as the standard function items and / or custom function items defined in the function definition interface as mentioned above.

[0117] For example, after a user selects a target component in the component configuration interface, the binding interface corresponding to the target component is displayed. The binding interface can display multiple function items defined by the target device (such as smart light bulbs, smart sockets, etc.). The user selects a function item from multiple function items according to the requirements of the target component (i.e., triggers the selection operation), and the terminal responds to the user's selection operation and determines the selected function item as the target function item. For example, the user selects a text label component and intends to use it to display the temperature reading of the smart temperature sensor. After the text label component is selected, the terminal is triggered to display the binding interface. The user clicks the "Function Binding" button in the binding interface, and the terminal responds to the user's operation and displays multiple function items defined by the smart temperature and humidity sensor, such as "temperature display", "humidity display", "battery power", etc. After browsing these function items, the user can select the "temperature display" function item that he wants to bind as the function that he wants to bind to the text label component. The terminal responds to the user's selection operation and determines the "temperature display" function item as the target function item.

[0118] In some embodiments of the present application, the step of “determining the attribute information of the target component in response to the attribute editing operation on the target component” may specifically include:

[0119] Display the information editing interface of the target function item;

[0120] In response to an editing operation on the information editing interface, editing information corresponding to the editing operation is determined, and the editing information is associated with a target function item.

[0121] It should be noted that after the target component is associated with the function item, the target component also presents the information corresponding to the function item. In order to ensure that the user can understand the meaning of the information displayed on the interface when using it, after the binding is completed, the user needs to edit the text content of the information component to provide contextual information or explanation of the numerical value. For example, the user selects the text component as the target component in the component configuration interface and binds it to a function item of the temperature sensor, such as the temperature display function item. After the binding is completed, the user needs to edit the text content of the target component to provide relevant information or explanation of the target component. For example, the user clicks the edit option of the text component, and the terminal displays a text editing interface, which allows the user to enter or modify the text content. For example, the user enters a descriptive text in the text editing interface, such as indoor temperature: ℃, to indicate that the value displayed subsequently is the reading of the indoor temperature. The user can also set the style attributes of the text, such as font size, color, bold or italic, to improve readability or conform to the interface design. The user associates the input text with the text component to ensure that when the text component displays the numerical value, the descriptive text is also displayed.

[0122] As a result, the target component not only displays the numerical data of the device, but also provides necessary text descriptions, so that users can more easily understand the meaning of the data, thereby improving the user experience.

[0123] In some embodiments of the present application, the component configuration page specifically includes different display areas such as a component type list, a first display area, and a second display area. The display areas can be arranged side by side, in a stacked arrangement, or in any other manner.

[0124] The step of “displaying the component configuration interface of the target device” may specifically include:

[0125] In response to a first selection operation on a target component type in the component type list, displaying a component gallery corresponding to the target component type in a first display area, each type of component gallery including at least one preset component icon;

[0126] In response to a second selection operation on the target component icon in the first display area, the target component icon is added to a second display area, wherein the second display area is a component display page corresponding to the target device.

[0127] The component type list includes multiple component types to meet the different component display requirements of various target devices. Among them, multiple component types include control components, information / entry components, head main visual components, etc. Each component type corresponds to a component gallery. When the user selects a different component type, the component gallery corresponding to the corresponding component type will be displayed in the first display area. Each component gallery includes at least one preset component icon, and a preset component icon is used to represent or display a preset component.

[0128] When configuring a target device, the user can select the component type corresponding to each function item in the component type list according to the needs of the target device or the function items defined by the target device, and then select the component icon that he wants to use from at least one preset component icon in the first display area as the target component icon. The selected target component icon will be automatically added to the second display area to indicate that the target component icon has been added to the target device. The user can select the target component icon multiple times according to the number of function items required by the target device, and each selected target component icon will be displayed in the second display area to facilitate the user to understand all component icons that have been added to the target device.

[0129] It is understandable that the user can also perform operations such as deletion on each target component icon displayed in the second display area.

[0130] The step of “in response to the component selection operation on the component configuration interface, displaying the binding interface corresponding to the selected target component” may specifically include:

[0131] In response to a component selection operation on a target component icon in the second display area, a binding interface corresponding to the target component icon is displayed.

[0132] After the user adds the target component icon to the second display area, the user can perform steps such as function binding operations and property editing operations on the target component. Specifically, when the user selects a target component icon in the second display area, the interface will display the binding interface corresponding to the target component icon (that is, the binding of the target component expires), and the user can perform function binding operations and property editing operations in the binding interface.

[0133] It is understandable that the binding interface and the component configuration interface can be different interfaces or different areas within the same interface. In one embodiment, the binding interface and the component configuration interface are located in the same interface, and the component type list, the first display area, the second display area and the binding interface in the component configuration interface are arranged in sequence in the same interface.

[0134] In some embodiments of the present application, the step of “generating an interface configuration file according to the target component and the binding information of the target component” may specifically include:

[0135] Obtain the compilation information of the target component from the local computer; the compilation information includes driver files, static resource files, and data models;

[0136] Generate a description file of the target component based on the target component and the binding information of the target component;

[0137] Generate an interface configuration file based on the preset compilation information and description file.

[0138] The description file contains detailed information and configuration of the components corresponding to the device. The description file is used to instruct the client on how to render and interact with the user interface. It may include component identification (such as an identifier), the binding relationship between the component and the device function item, the layout parameters of the component in the interface, etc.; the compilation information is a set of instructions and parameters that guide how to convert source code or configuration files into executable programs, application interfaces or other final products. The compilation information is pre-set by the developer. The preset compilation information ensures that all developers and build environments use the same configuration to reduce problems caused by environmental differences.

[0139] For example, ensure that all preset compilation information is ready, including development environment settings, resource paths, style sheets, script references, data model definitions, layout engines, version control, dependency declarations, compilation instructions, and target platform information. Also, ensure that the description file of the target component has been generated and contains all necessary binding information, such as component identifiers, bound function items, property settings, trigger conditions, and action descriptions. At the beginning of the compilation process, the system reads the description file, extracts the configuration information of the component, and then uses the preset compilation information to process the data in the description file, for example, correctly linking resources such as images and fonts to the interface configuration according to the resource path. Then, according to the layout parameters in the description file and the rules of the layout engine, the layout structure of the interface is generated. Then, the style information in the description file is applied to the corresponding components, and the script reference is integrated into the interface configuration to ensure that user interaction and data updates can work properly. After the compilation process is completed, the final interface configuration file is generated, which contains files with all the necessary information of the interface, such as HTML, CSS, JavaScript files, etc.

[0140] Specifically, extract the configuration of the temperature and humidity display components, then apply the component style to the ReactNative style sheet, integrate the event processing logic into the JavaScript script, and then use the React Native compilation tool to convert the code into App files (i.e., interface configuration files) for iOS and Android platforms.

[0141] Through the above process, the user can obtain an interface of the device generated according to the customized configuration file, providing a personalized user experience.

[0142] In summary, after displaying the target device component configuration interface, the embodiment of the present application responds to the component selection operation on the component configuration interface and displays the binding interface corresponding to the selected target component. Then, in response to the function binding operation on the binding interface, the selected target function item is bound to the target component. Finally, according to the target component and the binding information of the target component, an interface configuration file is generated. The interface configuration file is used to generate the interface of the target device. Therefore, when adding new functions or controls to the interface, the programmer does not need to rewrite the code. Thus, interface configuration events with many iterations and complex iteration content can be met, that is, the time of interface configuration is reduced, thereby improving the efficiency of interface configuration.

[0143] See also Figure 3 , provides an interface configuration method, which is described by taking the method applied to an electronic device as an example, and the electronic device may be Figure 1 The terminal in the embodiment specifically includes the following steps:

[0144] S201. In response to an interface request operation for a target device, obtain an interface configuration file corresponding to the target device.

[0145] An interface request operation usually refers to an operation in which a user requests a terminal to display a user interface through a client software (such as a smartphone app, web interface, or smart control platform). The terminal responds to the interface request operation for the target device and obtains the interface configuration file corresponding to the target device from the cloud.

[0146] Specifically, the terminal responds to the interface request operation for the target device and obtains the corresponding interface configuration file from the cloud service, such as obtaining the corresponding interface configuration file from the cloud service through the Application Programming Interface (API). After receiving the request from the terminal, the cloud service verifies the requested authority and then retrieves the interface configuration file from the cloud database. Finally, the cloud service sends the interface configuration file corresponding to the interface request operation back to the terminal. This file contains all the information required for the user interface, such as component definition, layout, style, and bound data source.

[0147] S202: Parse the interface configuration file to obtain the target component and binding information of the target component.

[0148] The binding information carries the target function items and attribute information bound to the target component. After receiving the interface configuration file, the terminal reads the contents of the configuration file through the parser. The parser identifies all components defined in the configuration file. For each component, the parser extracts its attributes, including visual and layout attributes such as style, size, color, and font. At the same time, the parser obtains the binding information related to each component, such as the type of data displayed or the device function controlled.

[0149] S203: Perform interface configuration according to the target component and binding information of the target component to obtain an interface of the target device.

[0150] For example, based on the parsed component definitions, the client software creates an actual instance of each component. Apply the parsed attribute information to the corresponding component instance, such as setting the text of a button, the range of a slider, or the font size of a display label. For components that need to display device data, set the data source according to the binding information to ensure that the component can receive and display data from the device. For components that need to respond to user operations, such as button clicks or slider adjustments, configure event handlers according to the binding information. Set the interaction logic between components according to the interaction definition in the binding information, such as the device control action triggered by a button click. Calculate and set the position of the component on the interface based on the layout properties of the component and the layout rules of the interface. Load all resources required for the interface, such as images, icons, style sheets, etc. Assemble all components into a complete user interface according to the established layout and hierarchical relationship. Render the user interface in the client software so that it is displayed on the user's device.

[0151] In summary, the embodiment of the present application provides an interface configuration method, which responds to an interface request operation for a target device, obtains an interface configuration file corresponding to the target device, parses the interface configuration file, obtains the target component and the binding information of the target component, and then performs interface configuration according to the target component and the binding information of the target component to obtain the interface of the target device. Therefore, when performing interface configuration, a pre-generated interface configuration file can be obtained, thereby satisfying interface configuration events with a large number of iterations and complex iteration content, that is, reducing the time of interface configuration, thereby improving the efficiency of interface configuration.

[0152] In order to further understand the interface configuration method provided by the present application, the following is further explained with specific scenarios. When the user configures the interface, the standardized functions of the device (taking the temperature and humidity sensor T1 as an example) can be configured, or the customized functions of the device can be configured, such as Figure 4 As shown in the figure, the user can click the "Define Function" option to configure the function items of the device first. After the user clicks the "Define Function" option, the function definition interface can be displayed, such as Figure 5As shown, in the function definition interface, there are two configuration entries, namely, adding custom functions and adding standard functions. Users can configure the various function items of the temperature and humidity sensor T1 through these two configuration entries. The function definition interface can also display the list of configured functions of the temperature and humidity sensor T1. Each configured function includes the following information: serial number, resource name, resource ID, attr (attribute), state type, transmission type, numerical type, enumeration and operable content, and the operable content includes edit, copy and delete.

[0153] The user selects the "Custom Function" option through the function item definition interface, and then the custom function configuration interface is displayed. The custom function configuration interface contains the configuration information of the added custom function, including resource name, resource ID, attribute (attr), numeric type, actual report, function type, function type value, default value and function description. The function type value can include Boolean, enumeration, numeric and text types. Boolean, enumeration, numeric and text types are common data types. Boolean: Boolean data represents a logical true or false value, usually represented by true or false. It is often used for conditional judgment, such as loop control and branch logic. Enumeration: It is a special data type that consists of a set of predefined constant values, each value represents a label. Enumeration allows variables to be one of a set of named integer constants, which increases the readability of the code. Numeric: Numeric data is used to represent values. It can be an integer (such as int in C language or int in Python) or a floating point number (such as float or double in C language, float in Python). Numeric data types are used to perform mathematical operations and store numerical information. Text (Text / String): Text or string data is used to store text information, which is a sequence of characters. Strings can contain letters, numbers, symbols, and other Unicode characters and are used to store user input, messages, names, etc.

[0154] In the smart home scenario, Boolean type is used for switch buttons or toggle components to indicate the on or off state of a device. Enumeration type is used for drop-down menus or radio buttons to allow users to select from preset options. Numeric type is used to display numerical information of a device, such as temperature, humidity, power, etc., or used for input components to allow users to enter numerical values. Text type is used to display or edit text information, such as device name, status information, user notes, etc.

[0155] After editing, you can preview all defined function lists in the visualization tool. The function list includes information such as resource name, resource ID, function type, and function description. For example, the temperature sensor has configured functions including battery power display, so its corresponding resource name can be battery power, the resource ID is 8.0.2001, its corresponding function type is a numerical type, and the function description is battery power.

[0156] When actually configuring the temperature and humidity sensor T1, the temperature and humidity sensor needs to display functions such as device icons, temperature information, humidity information, and battery information. Therefore, you can select "Placeholder Large Image Component", "Information Component", "Information Component", and "Information Component" to display the relevant information of each function. Different types of function items can be selected from the control component, information entry component, and head main visual component.

[0157] When configuring the placeholder component, such as Figure 6 As shown in the figure, first select a "placeholder image component" to display the device icon of the temperature and humidity sensor. Set the properties of the placeholder image component, such as size, position, and source of the icon image. Finally, bind the placeholder image component to the device icon data source of the temperature and humidity sensor to ensure that the icon can be displayed correctly.

[0158] When configuring information / entry components, such as Figure 7 As shown, in the visual editing tool, select components suitable for displaying information, such as text labels, status indicators, etc. Then, the user selects a suitable component icon according to the type of information to be displayed (such as numerical type, text type, etc.). The various information components in the second display area are arranged from top to bottom in the order of the time they were added. Later, you can also adjust the order of the various information components by long pressing the components and dragging them.

[0159] Next, perform the functional binding of each information component, such as Figure 8 As shown in the figure, the selected information component is bound to the specific function of the device, for example, a certain information component is bound to the temperature information function of the temperature sensor. The initial binding only supports the display of numerical data, but does not include the specific meaning or context information of the numerical value. The user needs to set the meaning of the numerical value to ensure that the numerical value on the user interface is easy to understand. Fig. 9 As shown, for example, add attribute editing information such as 0°C, temperature, and icon to the information component corresponding to the temperature function. After editing the information component, save the configuration, and the corresponding information component in the second display area will also adaptively display the edited display format.

[0160] After completing the configuration of each information component, the configuration information will be used to generate an interface configuration file. The generated configuration file is uploaded to the cloud for the application (APP) to download and use.

[0161] When displaying the interface, the parser in the APP of this application reads the contents of the configuration file. The parser identifies all components defined in the configuration file. For each component, the parser extracts its properties, including visual and layout properties such as style, size, color, font, etc. At the same time, the parser obtains binding information related to each component, such as obtaining the type of data displayed or the function of the device controlled. The APP architecture of this application is as follows: Fig.10 As shown, the APP architecture includes a parser, a renderer, and a driver, among which the parser is mainly responsible for downloading, verifying, and loading configuration files. It is used to download configuration files from the cloud, verify whether the configuration files are complete and have not been tampered with, and decrypt and decompress the configuration files to the local directory in the mobile phone; the renderer is mainly responsible for parsing the "UI description file" in the configuration file, finding the corresponding UI components according to the file, and sorting the UI components according to the file; the driver is mainly responsible for running the "executable driver file", loading the data model, and providing the interaction logic and data processing of the corresponding functions. For example, if you click the switch-on, 1 is sent; if you click the switch-off, 0 is sent. The architecture of the configuration file is as follows Fig.11 As shown, the configuration file includes an executable driver file, a data model, a UI description file and a resource file. The executable driver file is mainly a JavaScript file, which is responsible for responding to the user's interactive behavior and processing its business logic, such as sending corresponding instructions after a user clicks an event; the data model is mainly responsible for processing data, such as requesting a cloud interface, processing the response data and translating it into the data format required by the UI component; the main data structure of the UI description file is composed of JSON, which mainly includes the arrangement order of UI components and the binding relationship between UI components and functions; the resource file mainly provides the image resources and multi-language copywriting (Chinese, English, Russian, etc.) required by the page.

[0162] See also Fig.12 , Fig.12 This is a schematic diagram of the structure of the first implementation of the interface configuration device provided in the embodiment of the present application. The interface configuration device includes a first display module 301, a second display module 302, a binding module 303 and a generation module 203. The specific implementation can be as follows:

[0163] The first display module 301 is used to display the component configuration interface of the target device;

[0164] A second display module 302 is used to display a binding interface corresponding to the selected target component in response to a component selection operation on the component configuration interface;

[0165] A binding module 303, configured to bind the selected target function item with the target component in response to a function binding operation on the binding interface;

[0166] The generating module 304 is used to generate an interface configuration file according to the target component and the binding information of the target component, wherein the interface configuration file is used to generate the interface of the target device.

[0167] In some embodiments of the present application, the binding module 303 includes:

[0168] A first determining unit, configured to determine, in response to a function binding operation on the binding interface, a target function item corresponding to the function binding operation;

[0169] A second determining unit, configured to determine attribute information of the target component in response to an attribute editing operation on the target component;

[0170] A binding unit is used to bind the target function item, the target component and the attribute information of the target component.

[0171] In some embodiments of the present application, the first determining unit is specifically configured to:

[0172] In response to a function binding operation on the binding interface, display multiple function items corresponding to the target device;

[0173] In response to a selection operation on a function item, the function item corresponding to the selection operation is determined to be a target function item.

[0174] In some embodiments of the present application, the second determining unit is further configured to:

[0175] Displaying the information editing interface of the target function item;

[0176] In response to an editing operation on the information editing interface, editing information corresponding to the editing operation is determined, and the editing information is associated with the target function item.

[0177] In some embodiments of the present application, the interface configuration device further includes:

[0178] A display unit, used to display a function item definition interface of the target device;

[0179] The configuration unit is used to configure the function of the target device in response to the configuration operation on the function item definition interface to determine the function item corresponding to the target device.

[0180] In some embodiments of the present application, the function item definition interface includes a custom configuration entry and a standard function configuration entry, and the configuration unit is specifically used to:

[0181] In response to a trigger operation on the custom configuration entry, displaying a custom function configuration interface, generating a custom function item according to a configuration operation on the custom function configuration interface, and configuring the custom function item as a preset function item of the target device; and / or,

[0182] In response to a trigger operation on the standard function configuration entry, a standard function list is displayed, and according to a selection operation on a standard function item in the standard function list, the standard function item corresponding to the selection operation is configured as a preset function item of the target device.

[0183] In some embodiments of the present application, the display unit is specifically used for:

[0184] A function list configured for the target device is displayed, wherein the function list includes the standard function items and / or the custom function items corresponding to the target device.

[0185] In some embodiments of the present application, the component configuration page includes a component type list, a first display area, and a second display area. The component type list includes multiple component types. The first display module 301 is specifically used to:

[0186] In response to a first selection operation on a target component type in the component type list, displaying a component gallery corresponding to the target component type in the first display area, the component gallery including at least one preset component icon;

[0187] In response to a second selection operation on a target component icon in the first display area, adding the target component icon to the second display area, where the second display area is a component display page corresponding to the target device;

[0188] The second display module 302 is specifically configured to display a binding interface corresponding to the target component icon in response to a component selection operation on the target component icon in the second display area.

[0189] In some embodiments of the present application, the generating module 304 is specifically used for:

[0190] Generate a description file of the target component based on the target component and the binding information of the target component;

[0191] Generate an interface configuration file based on the preset compilation information of the target component and the description file.

[0192] The embodiment of the present application provides an interface configuration method. After the first display module 301 displays the component configuration interface of the target device, the second display module 302 responds to the component selection operation on the component configuration interface and displays the binding interface corresponding to the selected target component. Then, the binding module 303 responds to the function binding operation on the binding interface and binds the selected target function item with the target component. Finally, the generation module 304 generates an interface configuration file based on the target component and the binding information of the target component. The interface configuration file is used to generate the interface of the target device. Therefore, when adding new functions or controls to the interface, the programmer does not need to rewrite the code. Therefore, interface configuration events with many iterations and complex iteration contents can be met, that is, the time of interface configuration is reduced, thereby improving the efficiency of interface configuration.

[0193] See also Fig.13 , Fig.13 This is a schematic diagram of the structure of a second implementation of the interface configuration device provided in the embodiment of the present application. The interface configuration device includes an acquisition module 401, a parsing module 402, and a rendering module 403. Specifically, it can be as follows:

[0194] An acquisition module 401 is used to acquire an interface configuration file corresponding to a target device in response to an interface request operation for the target device;

[0195] The parsing module 402 is used to parse the interface configuration file to obtain the target component and the binding information of the target component; the binding information carries the target function item bound to the target component;

[0196] The rendering module 403 is used to perform interface configuration according to the target component and the binding information of the target component to obtain the interface of the target device.

[0197] An embodiment of the present application provides an interface configuration device, in which an acquisition module 401 responds to an interface request operation for a target device, and after acquiring an interface configuration file corresponding to the target device, a parsing module 402 parses the interface configuration file to obtain a target component and binding information of the target component. Then, a rendering module 403 performs interface configuration according to the target component and the binding information of the target component to obtain the interface of the target device. Therefore, when performing interface configuration, a pre-generated interface configuration file can be obtained, thereby satisfying interface configuration events with a large number of iterations and complex iteration content, that is, reducing the time of interface configuration, thereby improving the efficiency of interface configuration.

[0198] In one embodiment, an electronic device is provided. The electronic device may be a smart device, a server, a terminal, etc., and its internal structure diagram may be as follows: Fig.14As shown. The computer device includes a processor, a memory, and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, an intention recognition method is implemented.

[0199] Those skilled in the art will understand that Fig.14 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0200] In one embodiment, an electronic device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0201] In one embodiment, a computer-readable storage medium is provided, storing a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0202] In one embodiment, a computer program product is provided, which is stored in a computer-readable storage medium and implements the steps in the above-mentioned method embodiments when the computer program product is executed by a processor.

[0203] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0204] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0205] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be construed as limiting the scope of the patent application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent application shall be subject to the attached claims.

Claims

1. An interface configuration method, characterized in that: include: Display the component configuration interface of the target device; In response to a component selection operation on the component configuration interface, displaying a binding interface corresponding to the selected target component; In response to a function binding operation on the binding interface, binding the selected target function item with the target component; An interface configuration file is generated according to the target component and the binding information of the target component, and the interface configuration file is used to generate an interface of the target device.

2. The interface configuration method according to claim 1, characterized in that: The step of binding the selected target function item with the target component in response to the function binding operation on the binding interface includes: In response to a function binding operation on the binding interface, determining a target function item corresponding to the function binding operation; In response to a property editing operation on the target component, determining property information of the target component; The target function item, the target component and the attribute information of the target component are bound.

3. The interface configuration method according to claim 2, characterized in that: The step of determining, in response to a function binding operation on the binding interface, a target function item corresponding to the function binding operation includes: In response to a function binding operation on the binding interface, displaying a plurality of function items corresponding to the target device; In response to a selection operation on the function item, the function item corresponding to the selection operation is determined to be a target function item.

4. The interface configuration method according to claim 2, characterized in that: The step of determining the attribute information of the target component in response to the attribute editing operation on the target component includes: Displaying the information editing interface of the target function item; In response to an editing operation on the information editing interface, editing information corresponding to the editing operation is determined, and attribute information of the target component is determined according to the editing information.

5. The interface configuration method according to any one of claims 1 to 4, characterized in that: Before displaying the component configuration interface of the target device, the method further includes: Displaying the function item definition interface of the target device; In response to a configuration operation on the function item definition interface, the function of the target device is configured to determine a function item corresponding to the target device.

6. The interface configuration method according to claim 5, characterized in that: The function item definition interface includes a custom configuration entry and a standard function configuration entry, and the configuration of the function of the target device in response to the configuration operation on the function item definition interface includes at least one of the following: In response to a trigger operation on the custom configuration entry, display a custom function configuration interface, generate a custom function item according to the configuration operation on the custom function configuration interface, and configure the custom function item as a function item of the target device; In response to a trigger operation on the standard function configuration entry, a standard function list is displayed, and according to a selection operation on a standard function item in the standard function list, the standard function item corresponding to the selection operation is configured as a function item of the target device.

7. The interface configuration method according to any one of claims 1 to 4, characterized in that: The component configuration page includes a component type list, a first display area, and a second display area. The component type list includes multiple component types. The component configuration interface of the display target device includes: In response to a first selection operation on a target component type in the component type list, displaying a component gallery corresponding to the target component type in the first display area, the component gallery including at least one preset component icon; In response to a second selection operation on a target component icon in the first display area, adding the target component icon to the second display area, where the second display area is a component display page corresponding to the target device; In response to the component selection operation on the component configuration interface, displaying a binding interface corresponding to the selected target component includes: In response to a component selection operation on the target component icon in the second display area, a binding interface corresponding to the target component icon is displayed.

8. The interface configuration method according to any one of claims 1 to 4, characterized in that: Generate an interface configuration file according to the target component and the binding information of the target component, including: Obtaining compilation information of the target component locally; the compilation information includes driver files, static resource files and data models; Generate a description file of the target component based on the target component and the binding information of the target component; An interface configuration file is generated according to the compilation information and the description file.

9. An interface configuration method, characterized in that: include: In response to an interface request operation for a target device, obtaining an interface configuration file corresponding to the target device; Parsing the interface configuration file to obtain the target component and binding information of the target component; The binding information carries the target function item bound to the target component; An interface configuration is performed according to the target component and binding information of the target component to obtain an interface of the target device.

10. An interface configuration device, characterized in that: include: A first display module, used to display the component configuration interface of the target device; A second display module, configured to display a binding interface corresponding to a selected target component in response to a component selection operation on the component configuration interface; A binding module, configured to bind the selected target function item to the target component in response to a function binding operation on the binding interface; A generating module is used to generate an interface configuration file according to the target component and the binding information of the target component, wherein the interface configuration file is used to generate an interface of the target device.

11. An interface configuration device, characterized in that: include: An acquisition module, configured to acquire an interface configuration file corresponding to the target device in response to an interface request operation for the target device; A parsing module, used to parse the interface configuration file to obtain the target component and binding information of the target component; The binding information carries the target function item bound to the target component; A rendering module is used to configure the interface according to the target component and the binding information of the target component to obtain the interface of the target device.

12. An electronic device, characterized in that: include: at least one processor and at least one memory, wherein: The memory stores program instructions or codes; The program instructions or codes are loaded and executed by the processor, so that the electronic device implements the interface configuration method as described in any one of claims 1-9.

13. A storage medium, characterized in that: A computer program is stored which can be loaded by a processor and execute the interface configuration method according to any one of claims 1 to 9.

14. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

Images