Methods, apparatus, and devices for processing composite components

Abstract

Embodiments of this disclosure provide methods, apparatus, and devices for processing composite components and for determining the composite components to be produced. [Solution] The composite component to be generated includes target child components, and a composite component creation function is associated with the composite component to be generated. In response to attribute addition operations on the target child components of the composite component to be generated, each attribute of the target child component is added to the input parameters of the composite component creation function. Furthermore, the target composite component is generated based on the composite component creation function and its input parameters. In this way, attribute addition operations expose all attributes of the target child components contained within the target composite component at once. When using the target composite component, personalized adjustments can be made to each attribute of the target child components within the target composite component, meeting the adjustment needs for each attribute of the target child components within the target composite component in specific business scenarios.

Description

Technical Field

[0006] , , , , , ,

[0005]

[0001] Embodiments of the present disclosure relate to a method, apparatus, and device for processing composite components.

[0002] This application claims priority to Chinese Patent Application No. 202310906341.4, filed on July 21, 2023, and the entire content disclosed in the above Chinese patent application is incorporated herein by reference.

Background Art

[0003] When developing an application, the application includes multiple pages that can jump to and reference each other, and the pages are often composed of multiple components. An atomic component is a base component that is single and cannot be decomposed. On the other hand, a composite component is a component formed by combining and encapsulating multiple atomic components, and the composite component can be quickly reused on different pages.

[0004] When developing a composite component, it is necessary to set the exposure attributes of the composite component, and only the exposure attributes of the composite component are editable when using the composite component. Currently, in the process of developing a composite component, the generated composite component cannot meet the personalized needs of some business scenarios in the method of setting exposure attributes.

Summary of the Invention

Means for Solving the Problems

[0005] In view of the above circumstances, the present disclosure provides a method, apparatus, and device for processing composite components that enable the generated composite components to meet the personalized needs of specific business scenarios.

[0006] To solve the above problem, the proposed technology related to this disclosure is as follows:

[0007] In the first aspect, the present disclosure describes the method as follows: The step of determining the composite component to be generated, wherein the composite component to be generated includes a target child component, and a composite component creation function is associated with the composite component to be generated. The steps include adding each attribute of the target child component to the input parameters of the composite component creation function in response to an attribute addition operation of the target child component within the composite component to be generated, The present invention provides a method for processing a composite component, which includes the step of generating a target composite component based on the composite component creation function and the input parameters, wherein each attribute of the target child components included in the target composite component is editable.

[0008] In the second aspect, this disclosure is: A decision unit configured to determine which composite component to be generated, wherein the composite component to be generated includes a target child component, and a composite component creation function is associated with the composite component to be generated. A first addition unit is configured to add each attribute of the target child component to the input parameters of the composite component creation function in response to an attribute addition operation of the target child component within the composite component to be generated, The present invention provides a composite component processing device, which includes a first generation unit configured to generate a target composite component based on the composite component creation function and the input parameters, wherein each attribute of the target child component included in the target composite component is editable.

[0009] In a third aspect, this disclosure is: One or more processors, A storage device in which one or more programs are stored, The present invention provides an electronic device that, when one or more of the aforementioned programs are executed by one or more of the aforementioned processors, causes one or more of the aforementioned processors to perform the processing method of the composite component described in any one of the aforementioned items.

[0010] In a fourth aspect, the disclosure provides a computer-readable storage medium in which a computer program is stored, wherein when the computer program is executed by a processor, the computer causes the computer to perform the processing method of the composite component described in any one of the paragraphs. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a schematic diagram of the framework of an exemplary application scene according to an embodiment of the present disclosure. [Figure 2] Figure 2 is a flowchart of the processing method for a composite component according to an embodiment of the present disclosure. [Figure 3a] Figure 3a is a schematic diagram of the development of a composite component according to an embodiment of the present disclosure. [Figure 3b] Figure 3b is a schematic diagram of the development of another composite component according to an embodiment of the present disclosure. [Figure 4a] Figure 4a is a schematic diagram illustrating the use of a composite component according to an embodiment of the present disclosure. [Figure 4b] Figure 4b is a schematic diagram illustrating the use of another composite component according to an embodiment of the present disclosure. [Figure 4c] Figure 4c is a schematic diagram illustrating the use of another composite component according to an embodiment of the present disclosure. [Figure 5a] Figure 5a is a schematic diagram of the unbinding of a composite component according to an embodiment of the present disclosure. [Figure 5b]FIG. 5b is a schematic diagram of an unbinding pop-up window according to an embodiment of the present disclosure. [Figure 5c] FIG. 5c is a schematic diagram of the unbinding of another composite component according to an embodiment of the present disclosure. [Figure 5d] FIG. 5d is a schematic diagram of the composite component after unbinding according to an embodiment of the present disclosure. [Figure 6a] FIG. 6a is a schematic configuration diagram of a composite component E according to an embodiment of the present disclosure. [Figure 6b] FIG. 6b is a schematic diagram of a page according to an embodiment of the present disclosure. [Figure 6c] FIG. 6c is a schematic diagram of another page according to an embodiment of the present disclosure. [Figure 6d] FIG. 6d is a schematic diagram of another page according to an embodiment of the present disclosure. [Figure 7] FIG. 7 is a schematic configuration diagram of a processing device for a composite component according to an embodiment of the present disclosure. [Figure 8] FIG. 8 is a schematic diagram of the basic structure of an electronic device according to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE INVENTION

[0012] In order to make the above objects, features, and advantages of the present disclosure clearer and more understandable, the embodiments of the present disclosure will be described in more detail below with reference to the drawings and specific embodiments.

[0013] In order to facilitate the understanding and interpretation of the technical solutions according to the embodiments of the present disclosure, the background technology of the present disclosure will be described first below.

[0014] Before using the technical solutions of the embodiments of the present disclosure, it can be understood that it is necessary to inform the user of the type, scope of use, usage scenario, etc. of such personal information in an appropriate manner and obtain the user's permission.

[0015] For example, in response to receiving an active request from the user, prompt information is sent to the user to clearly prompt the user that the operation requested to be performed requires the acquisition and use of the user's personal information. This allows the user to choose whether or not to provide personal information to software or hardware such as electronic devices, application programs, servers, or storage media that perform the operation of the proposed technical method of this disclosure, depending on the prompt information.

[0016] As one selectable rather than limited embodiment, the method for sending prompt information to the user in response to receiving an active request from the user may be, for example, a pop-up window, which may display the prompt information in text format. The pop-up window may also include a selection control for the user to choose whether to "agree" or "disagree" to providing personal information to the electronic device.

[0017] The above notice and user permission process are illustrative and not limiting to the embodiments of this disclosure. It should be understood that other methods of complying with applicable laws and regulations may also be applicable to the embodiments of this disclosure.

[0018] Currently, applications can be built and developed based on the application building platform service aPaaS. This application building platform service allows users to quickly build applications that meet business needs with little to no development required, thereby improving application development efficiency.

[0019] An application consists of multiple application pages (abbreviated as pages) that can be jumped to or referenced from one another. A page often consists of multiple components, such as a table component for displaying multi-row breakdown data, or a line graph component for displaying data trends. Components within a page are the building blocks of the page. Inside a component, a set of UI code is encapsulated, and different components perform different functions through different UI code. Components can be dragged (referenced) to different pages, supporting reuse across different pages.

[0020] A component may include atomic components and composite components. An atomic component is a base component, also called a fundamental component; it is a single, indestructible component and the smallest unit for building an application page. A composite component is a component that combines and encapsulates multiple atomic components, allowing for rapid reuse on different pages, significantly improving application development efficiency and reducing service maintenance costs. For example, atomic components may include search components, screening components, sorting components, and empty tables. Combining and encapsulating these atomic components yields a composite component. The resulting composite component is an advanced table with table functionality, search functionality, screening functionality, and sorting functionality. Furthermore, users can drag and reuse this advanced table on different pages. It is understood that composite components and atomic components can be combined to build even more complex composite components.

[0021] Components are upgradeable, supporting component developers in adding / updating functionality to components and pushing it to users who use them. Furthermore, for composite components, if multiple pages all use a composite component, or if the same page uses the same composite component multiple times, changing one of those composite components will cause other composite components dragged onto the page to change accordingly, thereby giving components a centralized maintenance characteristic.

[0022] Each component has associated attributes, and the publicly displayed attributes of a component are custom attributes. In other words, custom attributes are a set of input parameters / configuration items that users set for a component, used to control the component's functionality and performance, and to meet the needs of various personalized scenarios. For example, in the case of a button group component, copy, icon, color, size, etc., can all be presented as custom attributes of the button group component. Different configurations of custom attributes for a component result in different functionality and performance, thus meeting the needs of various personalized scenarios.

[0023] When developing composite components, it is necessary to set the exposure attributes (i.e., publicly available attributes) of the composite component, and only the exposure attributes of the composite component can be edited when using the composite component. The creation of composite components is primarily to solve problems such as reuse and efficiency. Developing a composite component at once allows for multiple reuses, contributing to improved application development efficiency. However, the higher the degree of encapsulation and reuse of a composite component, the more difficult it becomes to meet the personalization needs of some business / application scenarios, making it difficult to achieve both reuse and personalization. In the development process of composite components, the current method of setting the exposure attributes of composite components does not allow the generated composite components to meet the personalization needs of some business scenarios.

[0024] Based on this, embodiments of the present disclosure provide a method, apparatus, and device for processing composite components and for determining a composite component to be generated. The composite component to be generated already includes a target child component, and a composite component creation function is associated with the composite component to be generated. The user can perform an attribute addition operation on the target child component of the composite component to be generated, and in response to the attribute addition operation, each attribute of the target child component is added to the input parameters of the composite component creation function corresponding to the composite component to be generated. Furthermore, a target composite component is generated based on the composite component creation function and the input parameters of the composite component creation function. Based on this, each attribute of the target child component contained in the target composite component is exposed, and each attribute of the target child component inside is editable when the target composite component is used. In this way, the present disclosure uses each attribute of the target child component as an input parameter through the attribute addition operation, exposes each attribute of the entire target child component as a unit, and performs a batch adjustment of each attribute of the target child component within the composite component to be generated. When using target composite components, personalized adjustments can be made to each attribute of the target child components within the target composite component, thus meeting the editing needs of each attribute of the target child components within the target composite component in specific business scenarios.

[0025] It is understandable that any defects in the relevant means described in the embodiments of this disclosure are the result of the discloser's practice and careful research. Therefore, both the process of discovering the relevant problems and the solutions proposed by the embodiments of this disclosure should be considered contributions made by the discloser in the disclosure process.

[0026] To make the processing method for composite components according to the embodiments of this disclosure easier to understand, the following explanation will refer to an example scene shown in Figure 1. As shown in Figure 1, the figure is a schematic diagram of the framework of an exemplary application scene according to the embodiments of this disclosure. The processing method for composite components according to the embodiments of this disclosure can be applied to any terminal device or server, and is not limited thereto.

[0027] In actual applications, composite components can be developed in the component editor, and the page presented when the component editor develops a composite component may also be called the composite component development page. For example, the first page in the embodiment of this disclosure is one such example. In the process of developing / constructing a composite component, the component editor first determines the child components that make up the composite component, places the child components in container components, combines them, and encapsulates them to construct the composite component. Container components are components that can store other components inside, such as table container components.

[0028] The composite component to be generated in the embodiments of this disclosure is a composite component under development / construction. Inside the composite component to be generated, at least one child component has already been constructed, and at least one child component contains the target child component. For example, at least one child component is child component 1 and child component 2, and the target child component is child component 1. In this case, inside the composite component to be generated in the embodiments of this disclosure, child component 1 may already be constructed, and child component 2 may or may not be constructed. It should be understood that when setting the attributes that need to be exposed for the composite component to be generated, this can be done after placing each child component in a container component, or after placing all child components in a container component.

[0029] The components shown in Figure 1 can be understood as child components that construct a composite component. A composite component creation function is associated with the composite component to be generated, and this function has corresponding input parameters (which may be abbreviated as input parameters), which can be understood as attributes that need to be exposed in the composite component being constructed. Typically, the backend renders the composite component on a page (e.g., the first page) based on the composite component creation function and its input parameters to obtain it.

[0030] In related technologies, users can set input parameters for a composite component to be generated by interacting with a component editor on the frontend. In response, the backend determines the corresponding data type based on the set result and sets the input parameters (i.e., exposed attributes) within the composite component creation function according to the data type. The data type is the type of the input parameter. For example, on the first page of the frontend, the user selects a button group component (one child component) within the composite component to be generated and sets one of the exposed attributes of the composite component to be generated as the button's text. In response to this operation, the data type of this input parameter is determined to be text, and thus, a text-type input parameter is associated with and set in the composite component creation function. On the first page of the frontend, the user sets another exposed attribute of the composite component to be generated as the width of the button group component (width is a numeric type). In this case, a numeric-type input parameter is associated with and set in the composite component creation function.

[0031] In embodiments of this disclosure, a data type-based input parameter setting method is provided, and further, a child component-based input parameter setting method is provided. Specifically, on the first page of the frontend, the user can perform an attribute addition operation on a target child component within the composite component to be generated, and in response to this operation, the backend directly adds each attribute of the target child component to the input parameters of the composite component creation function. That is, all attributes of the entire target child component are added to the input parameters of the composite component creation function all at once. In embodiments of this disclosure, this input parameter setting method may be called child component-based input parameter setting.

[0032] As is clear, based on the composite component to be generated, the child component-based input parameter setting method is one method for setting the input parameters of a composite component. In this case, once all input parameters have been set, the backend renders the target composite component based on the composite component creation function and input parameters to obtain the target composite component. In this way, each attribute of the target child components contained in the target composite component is editable. In cases where it is necessary to be able to edit each attribute of the entire target child component to satisfy personalization needs in a particular application scene, the child component-based input parameter setting method in the embodiment of this disclosure (i.e., using each attribute of the target child component as input parameters of a function collectively) can satisfy the personalization needs of that particular application scene.

[0033] Once a target composite component is generated, it can be used to build a page. For example, by dragging a target composite component onto a page, it can be made into one of the page's components.

[0034] Furthermore, as shown in Figure 1, the output of a target composite component can be understood as the presentation state of the target composite component on the page. For example, if a target composite component includes a button group component, whether the button group component is currently clicked, whether it is currently displayed, or whether it is currently hidden are all presentation states of the button group component, and are not limited to these.

[0035] As those skilled in the art will understand, the schematic diagram of the framework shown in Figure 1 is merely one example of how embodiments of the present disclosure can be implemented. The scope of application of embodiments of the present disclosure is not limited by any aspect of the framework.

[0036] To facilitate understanding of this disclosure, the processing method for composite components according to embodiments of this disclosure will be described below with reference to the drawings.

[0037] As shown in Figure 2, the figure is a flowchart of a method for processing a composite component according to an embodiment of the present disclosure, and the method can be carried out by a terminal device or a server. As shown in Figure 2, the method may include steps S201 to S203, which are applied to the development process of the composite component, and specifically include the following:

[0038] S201: Determine the composite component to be created. The composite component to be created will include a target child component, and a composite component creation function will be associated with the composite component to be created.

[0039] A component is a component in which a code segment is encapsulated, and this encapsulated code segment performs a specific function or renders a particular presentation effect. Atomic components are the most basic building blocks of a page, possess indivisible properties, and serve as the foundation for other components. To meet the reuse needs of business / application scenarios, a series of atomic components can be combined and encapsulated to form a composite component. Typically, a composite component may contain multiple child components, and these child components may be nested within different container components. For example, a composite component may contain child component 1 and child component 2, and child component 2 may be another composite component containing child component 3 and child component 4.

[0040] The composite component to be generated in the embodiments of this disclosure is a component under development / construction, which already contains at least one child component, the at least one child component containing a target child component. Based on the above description, the child component in the composite component to be generated may be an atomic component or another composite component that has been generated.

[0041] It is understandable that the exposed attributes of each composite component are all relevant to the business scenario, and that these exposed attributes determine the capabilities that the composite component provides. When building application pages, users can further edit the exposed attributes of composite components within the application pages, enabling further customization of the composite components. This allows the attributes of composite components to be edited not only during development but also during use, making them applicable to a wider range of business scenarios. For example, if the exposed attribute of a composite component is the title bar name, users can edit the title bar name when using the composite component.

[0042] In practical applications, composite components are obtained by rendering them using a composite component creation function and its input parameters. The composite component creation function can be understood as the code for rendering the composite component, and the input parameters are input parameters, which are configuration items that control the functional performance of the component instance on the page, such as the "color" of a button group component. Input parameters are the exposed attributes of the component and may also be called custom attributes.

[0043] In the process of developing a composite component, a composite component creation function is associated with the composite component to be generated. The attributes that need to be exposed for the composite component to be generated can be set on the frontend (for example, the first page of the frontend), and the backend adds the exposed attributes as input parameters to the composite component creation function corresponding to the composite component to be generated.

[0044] S202: In response to an attribute addition operation of a target child component within the composite component to be generated, add each attribute of the target child component to the input parameters of the composite component creation function.

[0045] Embodiments of this disclosure provide a child component-based input parameter setting method. Specifically, a user can perform an attribute addition operation on a target child component included in a composite component to be generated, and in response to this attribute addition operation, each attribute of the target child component is added collectively to the input parameters of the composite component creation function. In this way, child component-based input parameter setting can be performed, exposing the entire target child component, that is, each attribute of the target child component.

[0046] One possible example is when each attribute of a target child component is relatively complex and cannot be described with a single data type. In this case, in response to an attribute addition operation, the backend can describe each attribute of the target child component based on a struct method. A struct is a complex data type that can describe multiple attributes of a target child component. For example, a struct can simultaneously describe each attribute of a target child component, such as width, color, and name.

[0047] For example, on the first page, a user can perform an attribute addition operation on a target child component. As referenced in Figure 3a, Figure 3a is a schematic diagram of the development of a composite component according to an embodiment of the present disclosure. Figure 3a presents a component editor, the page presented in the component editor is the first page 110. The component editor is used by component developers and can be used to develop composite components.

[0048] In Figure 3a, the custom component is a composite component, and the composite component to be generated shown in Figure 3a is an advanced table component. As shown in Figure 3a, the first page 110 includes a component panel 111, a composite component development area 112, and a composite component attribute configuration area 113. The component panel 111 presents various components, including atomic components, container components, and custom components. Atomic components include, for example, text components, title bar components, screening components, picture components, button group components, and dropdown selection components. Container components include, for example, block components and column separator components. Custom components include, for example, advanced tables, headers, and footers. The composite component development area 112 presents the composite component under construction (i.e., the composite component to be generated). The development area 112 shown in Figure 3a presents the configuration of the child components inside the advanced table 1121, which is the composite component to be generated. As is clear, its interior includes a button group component 1121-1, a search component 1121-2, a screening component 1121-3, a sort component 1121-4, and a table container below (where content such as item name, item type, item status, target, and operation is displayed). The attribute configuration area 113 of the composite component is used to configure the attributes, styles, and events of the composite component. During the attribute configuration process, the attributes (including exposed attributes) of the table container, button group component, search component, screening component, sort component, etc. within the composite component can be configured in the configuration area 113. For example, if the composite component is an advanced table, the target child component may be a button group component, search component, screening component, sort component, etc., within the advanced table.

[0049] As one possible option, a component attribute citation control is associated with the composite component to be generated. Exemplarily, as shown in Figure 3a, the attribute configuration area 113 of the composite component on page 1 presents an "Add Attribute" control 113-1. The "Add Attribute" control is used to add attributes to the composite component, and this control allows you to set the exposed attributes of the composite component to be generated. The user can trigger the "Add Attribute" control, and in response to this trigger operation, page 113-2 is presented. Page 113-2 presents a "Custom Attribute Addition" control and a "Component Attribute Citation" control.

[0050] The "Add Custom Attribute" control is used to implement a data type-based input parameter setting method, which is relatively simple. The backend sets input parameters (i.e., custom attributes) based on the definition of the data type, for example, setting text type input parameters and numeric type input parameters (these input parameters may be attributes of a child component). Only one custom attribute can be set at a time. The "Quote Component Attribute" control is used to implement a child component-based input parameter setting method. As is clear, if the composite component to be generated is the advanced table 1121 shown in Figure 3a, the "Quote Component Attribute" control can be understood as a component attribute quote control corresponding to the advanced table, and its function is specifically to expose the child components of the advanced table as input parameters.

[0051] Based on this, in one possible embodiment, an embodiment of the present disclosure provides a specific embodiment that adds each attribute of a target child component to the input parameters of a composite component creation function in response to an attribute addition operation of a target child component in a composite component to be generated in S202, and includes steps A1-A2.

[0052] A1: In response to a trigger operation of the component attribute citation control corresponding to the composite component to be generated, the component attribute citation page corresponding to the composite component to be generated is presented.

[0053] The user can trigger a component attribute citation control corresponding to the composite component to be generated, and in response to this trigger operation, the component attribute citation page corresponding to the composite component to be generated will be presented. The trigger operation may be, but is not limited to, a click operation, a hover operation, or an air gesture operation.

[0054] A2: In response to selecting a tag for a target child component on the component attribute citation page, add each attribute of the target child component to the input parameters of the composite component creation function.

[0055] The component attribute citation page presents the tags for each child component within the composite component to be generated, including the tag for the target child component. As one possible example, the tag for the target child component may be the name or identification number of the target child component, and is not limited to that; it just needs to uniquely identify the target child component.

[0056] The user can select the tags of the target child component on the component attribute citation page, and in response to this selection, the backend adds each attribute of the target child component as an input parameter to the composite component creation function.

[0057] As is evident from the content of A1-A2, the embodiments of this disclosure provide specific embodiments of an attribute addition operation, namely, an attribute addition operation may be a combination of a trigger operation of a component attribute citation control corresponding to the composite component to be generated and an operation of selecting the tag of the target child component within the component attribute citation page.

[0058] As referenced in Figure 3b, Figure 3b is a schematic diagram of the development of another composite component according to an embodiment of the present disclosure. Figure 3b shows the component attribute citation page 210 corresponding to the composite component to be generated, which is presented after the "Component Attribute Citation" control is triggered. As shown in Figure 3b, the component attribute citation page presents the operable item "Category". Under the operable item "Category", you can select "Attribute" and "Component". If you select "Component", the component attribute citation page further presents operable items such as "Component Selection" and "Presentation Name". Under the operable item "Component Selection", there is a corresponding dropdown menu. As one selectable example, the tags (not shown) of each child component inside the composite component to be generated are presented in the dropdown menu of the operable item "Component Selection". In this way, you can select the tags of the target child component in the dropdown menu. After selecting the tags of the target child component, you can also edit the presentation name using the operable item "Presentation Name".

[0059] Based on the above content, in the first page shown in Figures 3a and 3b, the operation path for setting child component-based input parameters triggers the "Add Custom Attribute" control, then the "Quote Component Attribute" control, and finally, in the dropdown menu under the operable item "Select Component" on the Quote Component Attribute page, the tag of the target child component is selected. In this way, the entire target child component can be exposed as input, that is, each attribute of the target child component can be used as an input parameter for the composite component creation function.

[0060] Furthermore, the component attribute citation page includes the prompt: "Note: If you input a component, you can fully customize the associated configuration of this component on the page." In other words, when building a page, if you use a generated non-composite component, each attribute of the target child component contained within that composite component is editable.

[0061] When the target child component of the composite component to be generated is another already generated composite component, it can be understood that each attribute of the target child component is the same as the attributes of each atomic component that makes up that composite component.

[0062] S203: Based on the composite component creation function and input parameters, a target composite component is generated, and the attributes of each target child component contained within the target composite component are editable.

[0063] After the input parameters for the composite component creation function have been set, the backend can generate the target composite component based on the composite component creation function and input parameters. Specifically, it generates and renders a composite component based on the composite component creation function and input parameters to obtain the target composite component. It is understood that each attribute of the target child components contained within the generated target composite component is editable. That is, each attribute of the target child components contained within the target composite component is an exposed attribute.

[0064] After generating the target composite component, it is automatically added to the composite component area of ​​the component panel, such as the "Custom Components" area in Figures 3a and 3b. This allows subsequent users to quickly drag the target composite component from the composite component area to the application page, enabling them to build the application page and reuse the target composite component on the application page. The process of using a component on the application page may also be called the component consumption process.

[0065] As is evident from the above content, embodiments of this disclosure provide a child component-based input parameter setting method, enabling the entire set of child components within a composite component to be used as input parameters, thereby significantly improving the component's ability to meet the needs of personalized scenes without disrupting the component's advanced encapsulation and reusability characteristics. In this way, when a user consumes a target composite component, they can select target child components within the composite component to perform personalized adjustments, i.e., edit each attribute of the target child component.

[0066] As is evident from the related content in S201-S203 above, embodiments of this disclosure provide a method for processing composite components and determine which composite component to be generated. The composite component to be generated already contains target child components, and a composite component creation function is associated with the composite component to be generated. The user can perform an attribute addition operation on the target child components of the composite component to be generated, and in response to this attribute addition operation, each attribute of the target child component is added to the input parameters of the composite component creation function corresponding to the composite component to be generated. Furthermore, a target composite component is generated based on the composite component creation function and the input parameters of the composite component creation function. Based on this, each attribute of the target child components contained in the target composite component is exposed, and when the target composite component is used, each attribute of the target child components within it is editable. In this way, the disclosure uses each attribute of the target child component as input parameters through the attribute addition operation, exposes each attribute of the entire target child component as a unit, and performs a batch adjustment of each attribute of the target child components within the composite component to be generated. When using target composite components, personalized adjustments can be made to each attribute of the target child components within the target composite component, thus meeting the editing needs of each attribute of the target child components within the target composite component in specific business scenarios.

[0067] It is understandable that the number of attributes of child components within a composite component to be generated may be large. For example, the attributes of a text component include text font, text font size, text color, text font color, and text border. Depending on the needs of the business scenario, it may be necessary to expose only some of these attributes; for example, only the text font may need to be exposed. Based on this, in addition to the "add custom attribute" shown in Figure 3a, the embodiments of this disclosure further provide the following alternative methods to accomplish the objective of adjusting some of the attributes of a child component to custom attributes.

[0068] As one possible example, each attribute of a target child component includes a target attribute. The target attribute may be one or more attributes, but is not limited herein. For example, the target child component is a text component, and the target attribute is the text font attribute of the text component. Based on this, embodiments of the present disclosure further provide the following steps for carrying out the exposure of the target attribute, specifically including steps B1 to B3.

[0069] B1: In response to a trigger operation of the component attribute citation control corresponding to the composite component to be generated, the component attribute citation page corresponding to the composite component to be generated is presented.

[0070] Step B1 is the same as Step A1 above, and its technical implementation can be found by referring to Step A1; therefore, a redundant explanation is omitted here.

[0071] B2: In response to selecting a tag for a target child component within the component attribute citation page, and selecting a target attribute within the component attribute citation page, the target attribute of the target child component is added as an input parameter to the composite component creation function.

[0072] As in step A2, the user can select the tag of the target child component on the component attribute citation page, and in response to this selection, the child component to be operated on can be determined as the target child component. Furthermore, after determining the child component to be operated on as the target child component, the user can further select the target attribute of the target child component on the component attribute citation page, and in response to this selection, the user can decide to add the target attribute of the target child component as an input parameter to the composite component creation function.

[0073] As shown in Figure 3b, after selecting "Components" under the operable item "Category," the user can select the tag of the target child component under the operable item "Component Selection." In this way, the child component to be manipulated later is determined as the target child component. Furthermore, the user can select "Attributes" under the operable item "Category," thus presenting the operable item "Attribute Selection" (not shown) on the component attribute citation page. As one example of a selectable item, the operable item "Attribute Selection" has a corresponding dropdown menu, which presents each attribute of the target child component. Based on this, the user can further select a target attribute in the dropdown menu of the operable item "Attribute Selection." In response to this selection operation, it is decided to add the target attribute of the target child component to the input parameters of the composite component creation function.

[0074] B3: Based on the composite component creation function and input parameters, a target composite component is generated, and the target attributes of the target child components contained within the target composite component are editable.

[0075] After executing B1-B2, once the input parameters for the composite component creation function corresponding to the composite component to be generated are set, the target composite component can be generated based on the composite component creation function and input parameters. It is important to understand that the target attributes of the target child components included in the generated target composite component are editable. That is, the target attributes of the target child components are exposed attributes. In this way, based on B1-B3, component developers are given the ability to freely expose or restrict the attributes of the target child components, thereby improving the stability and availability of the entire composite component.

[0076] After creating the target composite component, the development process for the target composite component is completed. This allows the application pages to be built using the target composite component when developing application pages. Based on this, in one possible embodiment, the embodiments of this disclosure further include steps C1 to C3.

[0077] C1: In response to an operation to add a target composite component, present the target composite component.

[0078] For example, the target composite component is presented on the second page, which is a page within the page editor, and the page editor is used to develop application pages. On the second page, the user can add the target composite component, making it a component of the application page. It should be understood that the first page (the composite component development page) and the second page may be the same page or different pages, and this is not limited to that.

[0079] One possible example of an add operation for a target composite component is a drag operation. The user can drag the target composite component directly to the second page, and in response to this drag operation, the target composite component is added and presented on the second page. It is understandable that the presentation position of the target composite component on the second page will be determined according to the page development needs.

[0080] C2: In response to a trigger operation of a target child component contained within a target composite component, an attribute editing area corresponding to the target child component is presented, and each editable attribute of the target child component is displayed in the attribute editing area corresponding to the target child component.

[0081] After the entire target child component is exposed, the user can edit the attributes of each target child component contained within the target composite component. Specifically, when a page consumes the target composite component, it supports directly selecting target child components within the target composite component, and after selecting the target child component, it allows for personalized adjustments to each attribute of the target child component.

[0082] For example, when the mouse slides over a target child component or floats over a target child component, the bounding box of the target child component is displayed, and the bounding box may be displayed in a specific color, such as blue, which indicates that the target child component has been selected, and each attribute of the target child component can be personalized and edited.

[0083] Furthermore, the user can trigger target child components within the presented target composite component. In response to this trigger operation, an attribute editing area corresponding to the target child component is presented. The trigger operation may be, but is not limited to, a click operation, a hover operation, or an air gesture operation. The attribute editing area corresponding to the target child component presents each editable attribute of the target child component, and the attribute editing area is used to perform editing operations on each attribute of the target child component.

[0084] For example, on the second page, an attribute editing area corresponding to the target child component is presented. As shown in Figure 4a, Figure 4a is a schematic diagram of the use of a composite component according to an embodiment of the present disclosure. As shown in Figure 4a, when developing an application page, the page editor presents the second page 310. The second page presents the application page 311 under development, which is, exemplary, an item management development page. In Figure 4a, the target composite component presented on the second page 310 is an advanced table 312, and the target child component is a button group component (the "Create New" component 3121 in Figure 4a). In addition, the application page 311 also contains various content built according to the business scenario of item management, such as "Horizontal Specialty Items," "Co-creation Items," and "Experience Optimization Items."

[0085] For example, when the mouse slides over the "New" button group component 3121, its bounding box 3121-1 is presented. The user can trigger the "New" button group component 3121, and an attribute editing area corresponding to the "New" button group component 3121 is presented on the right side of the page editor 310. As shown in Figure 3a, the button type, icon and name, button width, etc., are all exposed attributes of the "New" button group component 3121 and can be custom edited by the user.

[0086] Furthermore, embodiments of this disclosure provide duplication, copy creation, and deletion functions for target child components. As shown in Figure 4a, when the bounding box 3121-1 of the "New" button group component 3121 is presented, operable controls 3121-2 corresponding to the "New" button group component 3121, such as a "Duplicate" control, a "Copy Creation" control, and a "Delete" control, are also presented. The "Duplicate" control is used to duplicate the "New" button group component 3121 (if a copy of the "New" button group component 3121 needs to be created, a paste operation must also be performed), the "Copy Creation" control is used to directly create a copy of the "New" button group component 3121, and the "Delete" control is used to delete the "New" button group component 3121. In this way, editing of target child components becomes more flexible and further satisfies the user's personalized editing needs for target child components.

[0087] As referenced in Figure 4b, Figure 4b is a schematic diagram of the use of another composite component according to an embodiment of the present disclosure. In Figure 4b, the target composite component is an advanced table, and the target child component is a search component (e.g., the "Search" component 3122 in Figure 4b). Exemplaryly, when the mouse slides over the "Search" component 3122, its bounding box 3122-1 is presented. The user can trigger the "Search" component 3122, which presents an attribute editing area corresponding to the "Search" component 3122 on the right side of the page editor 310. As shown in Figure 3b, placeholders, IDs, etc., are all attributes of the "Search" component 3122, and these are all exposed attributes that can be custom edited by the user. Similarly, the "Search" component 3122 also has a corresponding operable control 3122-2, the function it performs is the same as the function of the operable control 3121-2 corresponding to the "New" button group component 3121 described in the above embodiment, and a redundant explanation is omitted here.

[0088] Figures 4a and 4b are provided for illustrative purposes only and should not be considered limitations.

[0089] C3: In response to an editing operation on the attributes of the target child component in the attribute editing area corresponding to the target child component, the edited target child component is re-presented.

[0090] The attributes of the target child component within the attribute editing area are custom attributes and are all editable. Editing operations can be determined according to the specific attribute. After editing the attributes of the target child component, the edited target child component is presented, which is equivalent to re-rendering and presenting the edited target composite component. For example, if the target child component is the button group component 3122 shown in Figure 4a, its button width can be edited. As a result, the "Create New" button group component 3121 will be re-rendered on the page according to the edited button width.

[0091] As is evident from the content of C1-C3, when consuming a target composite component, the user can only perceive the inputs of the target composite component (i.e., the input parameters of the composite component creation function corresponding to the target composite component). Therefore, after exposing the entire target child component of the target composite component as input, when consuming the target composite component, it is possible to select the target child component and support the implementation of the atomization configuration of the target child component.

[0092] As one possible example, the target child component included in the composite component to be generated may be a slot component. A slot component is a type of container component that can be populated with other components. In this case, the slot component is selected and exposed as an input parameter before generating the composite component to be generated. For example, on component attribute citation page 210 shown in Figure 3b, the tag for the slot component is selected. The slot component is actually a placeholder (e.g., a slot placeholder) to which other components can be added. In practical applications, in response to the selection operation of the slot component tag, the backend adds the placeholder to the input parameters, thereby achieving the purpose of using the slot component as an input parameter.

[0093] One point to understand is that when developing a composite component to be generated, if you expose the slot components inside the composite component as input, after the target composite component is generated, the added target composite component will be presented with slot areas corresponding to the slot components, allowing the user to freely add other components in those slot areas.

[0094] Based on this, in one possible embodiment, the method for processing a composite component according to an embodiment of the present disclosure may further include the step of adding a component to a slot area in response to an operation to add a component to a slot area.

[0095] As referenced in Figure 4c, Figure 4c is a schematic diagram of the use of another composite component according to an embodiment of the present disclosure. As shown in Figure 4c, the slot area 3123 is typically indicated by a bounding box that other components can be dragged into it. In Figure 4c, the slot area 3123 already presents one internal component, a "New" button group component 3121. As is clear, the slot area 3123 still has empty space to which other components can be added. Therefore, other components can be added to the slot area, and components can be added to the slot area in response to add operations. In this way, when different pages consume the target composite component, components that meet the needs of page development can be added to the slot area, thereby making the development of different pages more flexible and meeting the personalization needs of different pages.

[0096] It can be understood that each attribute of a component added to the slot area is editable.

[0097] As is evident from the above content, embodiments of this disclosure provide a child component-based input parameter setting method that meets the user's editing needs for the entire child component. Therefore, if the exposed child component still cannot meet the needs of the business scene, embodiments of this disclosure further provide the methods described in D1-D3 below. D1-D3 are methods for consuming composite components and specifically include steps D1-D3.

[0098] D1: In response to an unbinding operation on an added target composite component, the child components after the target composite component has been unbound are presented, and each attribute of the child components after the target composite component has been unbound is editable.

[0099] The user can perform an unbinding operation on an added target composite component, which is an operation that divides the target composite component into the finest granular atomic components. In response to the unbinding operation, the unbound child components of the target composite component are presented, and these unbound child components are atomic components.

[0100] The composite component creation function corresponding to the target composite component describes the internal structure and encapsulation of the target composite component. In practical applications, in response to an unbinding operation, the backend breaks the description of the internal structure and encapsulation of the target composite component in the composite component creation function and further renders the atomic components inside the target composite component directly.

[0101] Even if the target composite component on which the unbinding operation is performed contains another composite component, it is understandable that the unbinding operation will restore the finest granular atomic components. For example, if target composite component E contains composite component F, atomic component A, and atomic component B, and composite component F contains atomic component C and atomic component D, then when the unbinding operation is performed on target composite component E, it will be split into atomic component A, atomic component B, atomic component C, and atomic component D, with each atomic component being independent of the others and not combined or encapsulated. Based on this, the child components of the unbound target composite component are atomic components, and each attribute of an atomic component is editable.

[0102] As one possible example, an unbinding control is associated with the target composite component. Based on this, embodiments of the present disclosure provide specific embodiments that present the unbound child components of the target composite component in response to an unbinding operation of the target composite component added in D1.

[0103] The process includes the step of presenting each child component of the target composite component after it has been unbound, in response to a trigger operation of the unbinding control corresponding to the target composite component.

[0104] As referenced in Figure 5a, Figure 5a is a schematic diagram of the unbinding of a composite component according to an embodiment of the present disclosure. Figure 5a presents the second page of one application scene. As shown in Figure 5a, the target composite component 410 is a custom table, which consists of an advanced table and each indicator card component (e.g., indicator card 1 "Unresolved Issue", indicator card 2 "Issues in Progress", indicator card 3 "Resolved Issues", indicator card 4 "Timed-Out Unresolved Issues"). When the user slides the target composite component 410 or the mouse hovers over the target composite component 410, the target composite component 410 is displayed in a selected state, and at this time, the corresponding operable controls are presented above the target composite component 410, and the operable controls include an "Unbinding" control 410-1. By triggering the "Unbinding" control 410-1, each child component of the target composite component after unbinding can be presented.

[0105] When a target composite component is unbound, it is updated, its internal atomic components are revealed, and its original internal structure is destroyed. If another identical target composite component still exists on the same page, unbinding one component does not synchronously unbind the other identical target composite component on the same page. In other words, the unbound target composite component is equivalent to creating a new copy of the original target composite component. However, the atomic components within the copy are not encapsulated, and changes to the copy do not affect other identical target composite components on the same page, nor do changes to the other identical target composite components on the same page affect the copy.

[0106] Based on this, the user is prompted to decide whether or not to unbind before the unbinding is performed. As shown in Figure 5b, Figure 5b is a schematic diagram of an unbinding popup window according to an embodiment of the present disclosure. As shown in Figure 5b, the popup window presents prompt information stating that "After unbinding, changes to the component will not be synchronized within the current component, configured content will not be affected, all atomic components will be exposed and will support individual configuration," prompting the user to decide whether or not to unbind the composite component. "Current component" refers to the target composite component itself.

[0107] As shown in Figure 5c, Figure 5c is a schematic diagram of the unbinding of another composite component according to an embodiment of the present disclosure. Figure 5c shows the second page before unbinding, and as shown in Figure 5c, before unbinding the target composite component 410, its component outline tree contains only the component node of the target composite component "Custom Table", and does not contain the component nodes of the internal child components of the target composite component 410. As shown in Figure 5d, Figure 5d is a schematic diagram of the composite component after unbinding according to an embodiment of the present disclosure. Figure 5d shows the second page after unbinding, and as shown in Figure 5d, after unbinding the target composite component 410, its component outline tree presents the component nodes of each child component of the target composite component 410. When developing the target composite component 410, it can be understood that atomic components such as the title bar component, button group component, search component, and sort component are all placed in a table container, and the table container and atomic components such as indicator card 1, indicator card 2, indicator card 3, and indicator card 4 are all placed in block components. Block components are container components that can contain other components. After unbinding the target composite component 410, the component outline tree presents each atomic component, each atomic component containing indicator card 1, indicator card 2, indicator card 3, indicator card 4, title bar component, button group component, search component, and sort component. The title bar component, button group component, search component, and sort component are still located in a table component, and each atomic component is still located in a block component, but is not encapsulated.As a result, each attribute of each atomic component is editable.

[0108] Furthermore, as shown in Figure 5d, the root node is presented by default in the component outline tree after unbinding and in the component attribute editing area on the right side of the page. Since the block component's position in the component outline tree is the root / outermost layer of the entire target composite component, the component node of the block component is presented by default.

[0109] As is clear from the above content, after unbinding a target composite component, all of its internal child components are exposed. Specifically, the child components after unbinding the target composite component can be individually selected and configured, and the component outline tree presented on the page displays the component nodes of the child components after unbinding the target composite component.

[0110] D2: In response to a trigger operation on a child component after the target composite component has been unbound, an attribute editing area corresponding to the child component is presented, and each editable attribute of the child component is displayed in the attribute editing area corresponding to the child component.

[0111] After unbinding a target composite component, its child components can be individually selected and configured by the user. Therefore, the user can trigger any child component after unbinding the target composite component, and in response to this trigger operation, an attribute editing area corresponding to the triggered child component is presented. As shown in Figure 5d, the attribute editing area on the right side of the page is specifically the attribute editing area corresponding to the triggered child component, and is used to present each editable attribute of the child component and to implement each attribute of the triggered child component.

[0112] For example, if the triggered child component is a "Create New" button group component, the attribute editing area corresponding to the button group component will be displayed on the right (see Figure 4a).

[0113] D3: In response to an editing operation on the attributes of a child component in the attribute editing area corresponding to the child component, the edited child component is re-presented.

[0114] The editing operations for the attributes of a child component are determined by the child component and are not limited to those operations. For example, if the triggered child component is a "New" button group component, and the attributes of the child component are button type, icon and name, button width, etc., then the editing operations could be editing the button type, editing the icon and name, or editing the button width.

[0115] In response to an editing operation on the attributes of a child component in the attribute editing area corresponding to the child component, the page re-presents the edited child component. For example, if the triggered child component is a "New" button group component and the editing operation is re-editing the button width, the backend re-renders and presents the "New" button group component, and the width of the re-presented "New" button group component is the edited button width.

[0116] As is evident from D1-D3, this disclosure supports flexible unbinding of target composite components on a page, and each attribute of each child component after unbinding is editable. In this way, it can be applied to business scenarios with a high need for personalization and improves the flexibility of component editing without disrupting its functional performance.

[0117] Again, as referenced in Figure 5a, the corresponding operable controls presented above the target composite component 410 on page 2 further include a "Configuration" control 410-2. The user can trigger the "Configuration" control 410-2, and in response to this trigger operation, the target composite component 410 and the configuration area corresponding to the target composite component 410 (the configuration area can refer to the configuration area 113 shown in Figure 3a) are presented on page 1. Furthermore, the user can re-edit the attributes of the target composite component in the configuration area corresponding to the target composite component 410. For example, a specific child component inside the target composite component can be re-exposed as an input parameter. In this way, when the user consumes the target composite component, if they find that the created target composite component does not meet the needs of the scene, the "Configuration" control 410-2 on page 2 can also be used to jump to page 1 of the component editor and perform secondary development on the target composite component to meet the needs of the new scene.

[0118] The method for unbinding a target composite component according to an embodiment of this disclosure will be further described below in the form of a simple block diagram shown in Figures 6a to 6c.

[0119] As shown in Figure 6a, Figure 6a is a schematic diagram of the configuration of a composite component E according to an embodiment of the present disclosure. The target composite component E is constructed from components A, B, C, and D. As shown in the internal structure of E in Figure 6a, component C includes component D, and component A, component B, and component C including component D jointly constitute the target composite component E.

[0120] As shown in Figure 6b, which is a schematic diagram of a page according to an embodiment of the present disclosure, when developing an application page, two target composite components E are dragged onto the page to become components of the page. As is clear, the two target composite components E correspond to the same composite component creation function, i.e., the composite component creation function created when the target composite components E were developed. Since the target composite components E are newly created components, if the internal structure of one target composite component E on the page changes, it calls the same composite component creation function, and the other target composite component E on the page also references the same composite component creation function, so the internal structure of the other target composite component E also changes accordingly. For example, if the positions of components A and B in one target composite component E on the page are adjusted, the positions of components A and B in the other target composite component E on the page also change accordingly. Before unbinding the target composite components E, the user can only select the target composite component E and edit the exposed attributes of the target composite component E.

[0121] As referenced in Figure 6c, Figure 6c is a schematic diagram of another page relating to an embodiment of the present disclosure. As shown in Figure 6C, when a target composite component E is unbound, the internal structure of the target composite component E is laid out on the page, and the user can further select components A, B, C, and D and directly edit the attributes of the internal components A, B, C, and D. It is understood that even if the positions of components A and B within the target composite component E on the page are adjusted after unbinding the target composite component E, the positions of components A and B within the other target composite component E on the page do not change accordingly.

[0122] As one possible example, the child components of the target composite component may be reassembled after unbinding. Based on this, in one possible embodiment, the method for processing a composite component according to an embodiment of the present disclosure may further include the following steps E1 to E2.

[0123] E1: In response to a combination operation of at least two child components after the unbinding of the target composite component, obtain a composite component consisting of at least two child components.

[0124] After unbinding a target composite component, it's also possible to recombine its child components. In practical applications, depending on the business scenario, you might determine at least two child components that need to be recombined, and this is not limited to those cases.

[0125] The user performs a combination operation on at least two child components within a target composite component, and in response to that operation, the system creates a composite component combining those at least two child components and renders it on the page. In a specific implementation, in response to the combination operation, the backend creates a corresponding composite component creation function and renders the composite component consisting of at least two child components on the page based on the composite component creation function and its input parameters. The input parameters of the composite component creation function corresponding to a composite component consisting of at least two child components may be default parameters.

[0126] It is understood that after retrieving the composite component (i.e., a composite component consisting of at least two child components), the re-retrieved composite component can be selected and edited by the user, but its internal child components cannot be selected or edited. Furthermore, the component outline tree is updated again after retrieving the composite component.

[0127] As one selectable example, an embodiment of the present disclosure provides a specific embodiment in E1 that obtains a composite component consisting of at least two child components in response to a combination operation of at least two child components after the unbinding of a target composite component, and includes the step of obtaining a composite component consisting of at least two child components in response to a selection operation of at least two child components after the unbinding of a target composite component and a trigger operation of a combination control corresponding to at least two child components in the target composite component.

[0128] The user can simultaneously select at least two child components within a target composite component and trigger corresponding combination controls, thereby obtaining a composite component consisting of at least two child components in response to these operations. That is, the combination operation of at least two child components within a target composite component includes the selection operation of at least two child components within the target composite component and the trigger operation of the combination controls corresponding to at least two child components within the target composite component.

[0129] It is understood that the embodiments of this disclosure do not limit the presentation method and location of combination controls within a page. For example, as shown in Figures 4a and 4b, after selecting at least two child components, the corresponding operable controls may be presented on a second page, and these operable controls may include combination controls.

[0130] As referenced in Figure 6d, which is a schematic diagram of another page relating to an embodiment of the present disclosure, when the target composite component is unbound, components A, B, C, and D are obtained. Components A and B are determined to be recombined, and on the page, components A and B are selected, the corresponding combination control is triggered, and thus the recombined composite component F is obtained. The internal implementation / internal structure of composite component F is components A and B.

[0131] E2: A composite component consisting of at least two child components is automatically added to the composite component list, and the generated composite component is presented in the composite component list.

[0132] After obtaining a composite component consisting of at least two child components, the composite component can be automatically added to the composite component list. The "Custom Components" area in Figures 3a and 3b presents the composite component list, which contains various generated composite components.

[0133] As one selectable example, an embodiment of the present disclosure provides a specific embodiment that obtains a composite component consisting of at least two child components in response to a combination operation of at least two child components after the unbinding of a target composite component in E1, and includes steps E11 to E13.

[0134] E11: In response to a combination operation of at least two child components after the unbinding of the target composite component, the composite component to be configured, consisting of at least two child components, is obtained and a configuration control is associated with the composite component to be configured.

[0135] In this example, it can be understood that the "combination operation of at least two child components within the target composite component" may also be the "selection operation of at least two child components within the target composite component and the trigger operation of the combination control corresponding to at least two child components within the target composite component" as described in the above embodiment.

[0136] In response to the combination operation of at least two child components after the unbinding of the target composite component, it is first necessary to obtain the composite component to be composed, which consists of at least two child components, and then to configure the composite component to be composed.

[0137] As one possible option, a configuration control is associated with the composite component to be configured. After obtaining the composite component to be configured and selecting it, an operable control corresponding to the composite component to be configured is presented, and the operable control presents the configuration control corresponding to the composite component to be configured (see the "Configure" control 410-2 in Figure 5a).

[0138] E12: In response to a trigger operation of the configuration control corresponding to the composite component to be configured, the composite component to be configured and the configuration area corresponding to the composite component to be configured are presented.

[0139] The user can trigger a configuration control corresponding to the composite component to be configured, and in response to this trigger operation, the composite component to be configured and the configuration area corresponding to the composite component to be configured are presented. For example, the composite component to be configured and the configuration area corresponding to the composite component to be configured (the configuration area can refer to configuration area 113 shown in Figure 3a) are presented on the first page. Furthermore, the user can configure the composite component to be configured within the configuration area corresponding to the composite component to be configured. For example, the user can configure the attributes of the composite component to be configured.

[0140] E13: In response to a configuration operation of the composite component to be configured in the configuration area corresponding to the composite component to be configured, obtain the composite component consisting of at least two child components.

[0141] After the configuration of the composite component to be configured in the configuration area corresponding to the composite component to be configured is complete, the composite component consisting of at least two child components is obtained.

[0142] As is evident from E1-E2 and E11-E13, the embodiments of this disclosure provide a method for generating composite components, which allows some of the child components obtained after unbinding the original target composite component to be reassembled, thereby making the operability of the components more flexible and better meeting the needs of business scenarios.

[0143] As those skilled in the art will understand, in the above-described method of a specific embodiment, the order in which each step is created does not mean a strict order of execution and does not constitute any limitation on the process, but rather the specific order of execution of each step should be determined by its function and possible internal logic.

[0144] This disclosure can also provide more embodiments by combining the embodiments described above.

[0145] Based on the method for processing composite components according to the above-described embodiment of the method, the embodiments of this disclosure further provide a processing apparatus for composite components, which will be described below with reference to the drawings. Since the principle by which the apparatus in the embodiments of this disclosure solves the problem is the same as that of the method for processing composite components according to the embodiments of this disclosure, the implementation of the apparatus can be seen by referring to the implementation of the method, and redundant explanations will be omitted.

[0146] As shown in Figure 7, the figure is a schematic diagram of the configuration of a processing apparatus for a composite component according to an embodiment of the present disclosure. As shown in Figure 7, the processing apparatus for the composite component is A decision unit 701 used to determine which composite component to be generated, wherein the composite component to be generated includes a target child component, and a composite component creation function is associated with the composite component to be generated, A first addition unit 702 is used to add each attribute of the target child component to the input parameters of the composite component creation function in response to an attribute addition operation of the target child component within the composite component to be generated, A first generation unit 703 is used to generate a target composite component based on the composite component creation function and the input parameters, and each attribute of the target child component included in the target composite component is editable, and the first generation unit 703 is used to generate a target composite component.

[0147] In one possible embodiment, a component attribute reference control is associated with the composite component to be generated, and the first additional unit 702 is A presentation subunit used to present a component attribute citation page corresponding to the composite component to be generated in response to a trigger operation of a component attribute citation control corresponding to the composite component to be generated, Includes an additional subunit used to add each attribute of the target child component to the input parameters of the composite component creation function in response to a selection operation of the tag of the target child component within the component attribute citation page.

[0148] In one possible embodiment, the composite component to be generated is associated with a component attribute reference control, and each attribute of the target child component includes a target attribute, and the device, A first presentation unit is used to present a component attribute citation page corresponding to the composite component to be generated in response to a trigger operation of a component attribute citation control corresponding to the composite component to be generated, A second additional unit is used to add the target attribute of the target child component to the input parameters of the composite component creation function in response to the selection operation of the tag of the target child component within the component attribute citation page and the selection operation of the target attribute within the component attribute citation page. The second generation unit is used to generate a target composite component based on the composite component creation function and the input parameters, and further includes a second generation unit in which the target attributes of the target child components included in the target composite component are editable.

[0149] In one possible embodiment, the apparatus is A second presentation unit is used to present the target composite component in response to an additional operation of the target composite component, A third presentation unit used to present an attribute editing area corresponding to a target child component in response to a trigger operation of the target child component included in the target composite component, wherein the attribute editing area corresponding to the target child component presents each editable attribute of the target child component. The system further includes a fourth presentation unit used to re-present the edited target child component in response to an editing operation of the attributes of the target child component in the attribute editing area corresponding to the target child component.

[0150] In one possible embodiment, the target child component is a slot component, and the target composite component presents a slot region corresponding to the slot component, and the device is The system further includes a third addition unit used to add a component to the slot area in response to an operation to add a component to the slot area.

[0151] In one possible embodiment, the apparatus is An unbinding unit used to present the unbound child components of the target composite component in response to an unbinding operation of the added target composite component, wherein each attribute of the unbound child components of the target composite component is editable. A fifth presentation unit used to present an attribute editing area corresponding to a child component in response to a trigger operation of the child component after the target composite component has been unbound, wherein the attribute editing area corresponding to the child component is used to present each editable attribute of the child component, The present invention further includes a sixth presentation unit used to re-present the edited child component in response to an editing operation of the attributes of the child component in the attribute editing area corresponding to the child component.

[0152] In one possible embodiment, the target composite component is associated with an unbinding control, and the unbinding unit specifically comprises: This is used to present each child component of the target composite component after it has been unbound, in response to a trigger operation of the unbinding control corresponding to the target composite component.

[0153] In one possible embodiment, the apparatus is A combination unit used to obtain a composite component consisting of at least two child components in response to a combination operation of at least two child components after the unbinding of the target composite component, A fourth append unit used to automatically add a composite component consisting of at least two child components to a composite component list, the composite component list further includes a fourth append unit which presents the generated composite component.

[0154] In one possible embodiment, the combination unit is specifically: It is used to obtain a composite component consisting of at least two child components in response to the selection operation of at least two child components after the unbinding of the target composite component and the trigger operation of the combination control corresponding to at least two child components within the target composite component.

[0155] In one possible embodiment, the combination unit is A combination subunit used to obtain a composite component to be configured, consisting of at least two child components, in response to a combination operation of at least two child components after the unbinding of the target composite component, wherein a configuration control is associated with the combination subunit, A trigger subunit used to present the composite component to be configured and the configuration area corresponding to the composite component to be configured in response to a trigger operation of a configuration control corresponding to the composite component to be configured, The system includes a configuration subunit used to obtain a composite component consisting of at least two child components in response to a configuration operation of the composite component to be configured in a configuration area corresponding to the composite component to be configured.

[0156] For specific implementations of each unit in this embodiment, please refer to the relevant descriptions of the above-mentioned method embodiments. In the embodiments of this disclosure, the division of units is illustrative and merely represents a division of logical functions; in actual implementations, other division methods may be used. Each functional unit in the embodiments of this disclosure may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit. For example, in the above embodiments, the processing unit and the transmission unit may be the same unit or different units. The integrated unit may be implemented in hardware form or in the form of a software functional unit.

[0157] Based on the composite component processing method according to the above embodiment of the method, the present disclosure further provides an electronic device comprising one or more processors and a memory device storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are made to perform the composite component processing method described in any one of the above embodiments.

[0158] The following diagrams show schematic configurations of electronic devices 800 applicable to implementing embodiments of the present disclosure, as referenced in Figure 8. Terminal devices in embodiments of the present disclosure may include, but are not limited to, mobile devices such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (portable Android devices, tablet computers), PMPs (Portable Media Players), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs (televisions) and desktop computers. The electronic devices shown in Figure 8 are merely examples and do not impose any limitations on the functions and scope of use of embodiments of the present disclosure.

[0159] As shown in Figure 8, the electronic device 800 may include a processing unit (e.g., a central processing unit, graphics processor, etc.) 801 capable of performing various appropriate operations and processes depending on the program stored in the read-only memory (ROM) 802 or the program loaded from the storage device 808 into the random access memory (RAM) 803. The RAM 803 further stores various programs and data necessary for the operation of the electronic device 800. The processing unit 801, ROM 802, and RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0160] Typically, devices that can be connected to the I / O interface 805 include, for example, input devices 806 such as touch panels, touchpads, keyboards, mice, cameras, microphones, accelerometers, and gyroscopes; output devices 807 such as liquid crystal displays (LCDs), speakers, and vibrators; storage devices 808 such as tapes and hard disks; and communication devices 809. The communication device 809 enables the electronic device 800 to communicate wirelessly or via wired connection with other devices to exchange data. Figure 8 shows the electronic device 800 with various devices, but it should be understood that it is not necessary to implement or include all of the devices shown. Instead, more or fewer devices may be implemented or included.

[0161] In particular, according to embodiments of the present disclosure, the process described with reference to the flowchart above may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product which includes a computer program contained on a non-temporary computer-readable medium, the computer program which includes program code for performing the method shown in the flowchart. In such embodiments, the computer program may be downloaded and installed from a network via a communication device 809, installed from a storage device 808, or installed from a ROM 802. When the computer program is executed by the processing unit 801, the above-described functions, limited to the methods of embodiments of the present disclosure, are performed.

[0162] The electronic device according to the embodiment of this disclosure belongs to the same inventive concept as the processing method for composite components according to the above embodiment, and for technical details not described in detail in this embodiment, refer to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0163] Based on the composite component processing method according to the above embodiment, the embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the composite component processing method described in any one of the above embodiments is performed.

[0164] The computer-readable medium in this disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. The computer-readable storage medium may be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage mediums may include, but are not limited to, electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium containing or storing a program, the program may be used by or in combination with an instruction execution system, apparatus, or device. In this disclosure, the computer-readable signal medium may include data signals propagated in the baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, and such computer-readable signal medium can transmit, propagate, or transmit programs for use by or in combination with instruction execution systems, apparatus, or devices. Program code contained in the computer-readable medium can be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), or any suitable combination thereof.

[0165] In some embodiments, the client and server may communicate by any currently known or future-developed network protocol, such as HTTP (Hypertext Transfer Protocol), and may interconnect with digital data communications (e.g., communication networks) in any form or medium. Examples of communication networks include local area networks ("LANs"), wide area networks ("WANs"), internetworks (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), and any currently known or future-developed networks.

[0166] The computer-readable medium described above may be included in the electronic device described above, or it may exist independently without being assembled into the electronic device.

[0167] The computer-readable medium contains one or more programs, and when these one or more programs are executed by the electronic device, the electronic device is instructed to perform the processing method of the composite component.

[0168] Computer program code for performing the operations disclosed herein can be programmed in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java®, Smalltalk, and C++, and further including conventional procedural programming languages ​​such as C and similar programming languages. The program code may run entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. Where a remote computer is involved, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it may be connected to an external computer (for example, connected via the Internet using an Internet service provider).

[0169] The flowcharts and block diagrams in the drawings illustrate the architectures, functions, and operations that can be implemented by the systems, methods, and computer program products of various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or part of code containing one or more executable instructions for performing a given logical function. In some alternative implementations, the functions shown in the blocks may be performed in an order different from the order shown in the drawings. For example, two consecutively shown blocks may actually be executed almost in parallel, or in some cases, in reverse order depending on the related functions. Each block in a block diagram and / or flowchart, and combinations of blocks in a block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs a given function or operation, or by a combination of dedicated hardware and computer instructions.

[0170] The units relating to the embodiments of this disclosure may be implemented in software form or in hardware form. In some cases, the name of the unit / module is not limiting to the unit itself; for example, an audio data acquisition module may be described as a "data acquisition module."

[0171] The functions described herein may be performed, at least partially, by one or more hardware logic components. For example, non-limiting exemplary types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standards (ASSPs), systems-on-a-chip (SOCs), and complex-programmable logic devices (CPLDs).

[0172] In the context of this disclosure, a machine-readable medium may be a tangible medium containing or storing a program that can be used by, or in combination with, an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More specific examples of machine-readable storage media may include one or more wire-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0173] Each example in this specification is described progressively, with each example focusing on its differences from other examples, and identical and similar parts between examples should be referenced to one another. The systems or apparatus disclosed in the examples correspond to the methods disclosed in the examples, and therefore their explanation is relatively simple; for relevant parts, refer to the description in the method section.

[0174] It should be understood that in this disclosure, “at least one” means one or more, and “more than one” means two or more. “And / or” is used to describe the relationship between related objects and indicates that there may be three types of relationships. For example, “A and / or B” indicates three situations: A alone exists, B alone exists, or A and B exist simultaneously, and A and B may be singular or plural. The symbol “ / ” generally indicates that the preceding and following related objects have an “or” relationship. “At least one of the following” or similar expressions means any combination of these terms, including any combination of one or more terms. For example, at least one of a, b, or c could mean a, b, c, “a and b,” “a and c,” “b and c,” or “a, b and c,” and a, b, and c may be one or more.

[0175] Furthermore, in this specification, relational terms such as "first" and "second" are used solely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is an actual relationship or order between these entities or operations. The terms "include," "incorporate," or any other variation thereof are intended to cover non-exclusive inclusion, thereby meaning that a process, method, article, or apparatus containing a set of elements includes not only those elements but also other elements not expressly enumerated, or elements specific to that process, method, article, or apparatus. Where there is no further restriction, an element limited by the phrase "includes one..." does not preclude the presence of another identical element in a process, method, article, or apparatus containing the said element.

[0176] Steps of methods or algorithms described in conjunction with the embodiments disclosed herein may be carried out directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may be located in random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art.

[0177] The above description of the disclosed embodiments will enable those skilled in the art to implement or use the disclosure. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the disclosure. Accordingly, the disclosure is not limited to these embodiments shown herein, but will adhere to the broadest scope consistent with the principles and novelty features disclosed herein.

Claims

1. A method for processing composite components, A step of determining a composite component to be generated, wherein the composite component to be generated includes a target child component, and a composite component creation function is associated with the composite component to be generated. The steps include adding each attribute of the target child component to the input parameters of the composite component creation function in response to an attribute addition operation of the target child component within the composite component to be generated, A method for processing a composite component, comprising the steps of generating a target composite component based on the composite component creation function and the input parameters, wherein each attribute of the target child component included in the target composite component is editable.

2. The composite component to be generated is associated with a component attribute citation control. The step of adding each attribute of the target child component to the input parameters of the composite component creation function in response to an attribute addition operation of the target child component in the composite component to be generated is: The steps include: presenting a component attribute citation page corresponding to the composite component to be generated in response to a trigger operation of a component attribute citation control corresponding to the composite component to be generated; The method according to claim 1, further comprising the step of adding each attribute of the target child component to the input parameters of the composite component creation function in response to a selection operation of the tag of the target child component in the component attribute citation page.

3. The composite component to be generated is associated with a component attribute citation control, and each attribute of the target child component includes the target attribute. The aforementioned method, The steps include: presenting a component attribute citation page corresponding to the composite component to be generated in response to a trigger operation of a component attribute citation control corresponding to the composite component to be generated; The steps include adding the target attribute of the target child component to the input parameters of the composite component creation function in response to the selection operation of the tag of the target child component within the component attribute citation page and the selection operation of the target attribute within the component attribute citation page, The method according to claim 1, further comprising the step of generating a target composite component based on the composite component creation function and the input parameters, wherein the target attributes of the target child components included in the target composite component are editable.

4. The steps include presenting the target composite component in response to an operation to add the target composite component, A step of presenting an attribute editing area corresponding to a target child component in response to a trigger operation of a target child component included in the target composite component, wherein the attribute editing area corresponding to the target child component presents each editable attribute of the target child component. The method according to claim 1 or 2, further comprising the step of re-presenting the edited target child component in response to an editing operation of the attributes of the target child component in the attribute editing area corresponding to the target child component.

5. The aforementioned target child component is a slot component, and the aforementioned target composite component is provided with a slot region corresponding to the aforementioned slot component. The aforementioned method, The method according to claim 4, further comprising the step of adding a component to the slot area in response to an operation to add a component to the slot area.

6. In response to an unbinding operation of the added target composite component, the steps include presenting the unbound child components of the target composite component, wherein each attribute of the unbound child components of the target composite component is editable. A step in which, in response to a trigger operation of a child component after the target composite component has been unbound, an attribute editing area corresponding to the child component is presented, wherein each editable attribute of the child component is presented in the attribute editing area corresponding to the child component. The method according to claim 4, further comprising the step of re-presenting the edited child component in response to an editing operation of the attributes of the child component in the attribute editing area corresponding to the child component.

7. An unbinding control is associated with the aforementioned composite component. The step of presenting the unbound child components of the target composite component in response to an unbinding operation of the added target composite component is: The method according to claim 6, further comprising the step of presenting each child component of the target composite component after unbinding in response to a trigger operation of an unbinding control corresponding to the target composite component.

8. The steps include obtaining a composite component consisting of at least two child components in response to a combination operation of at least two child components after the unbinding of the target composite component, The method according to claim 6, further comprising the steps of automatically adding a composite component consisting of at least two child components to a composite component list, wherein the composite component list presents the generated composite component.

9. The step of obtaining a composite component consisting of at least two child components in response to a combination operation of at least two child components after the unbinding of the target composite component is: The method according to claim 8, further comprising the steps of obtaining a composite component consisting of the at least two child components in response to an operation to select at least two child components after unbinding the target composite component and an operation to trigger a combination control corresponding to at least two child components within the target composite component.

10. The step of obtaining a composite component consisting of at least two child components in response to a combination operation of at least two child components after the unbinding of the target composite component is: A step of obtaining a composite component to be configured, consisting of at least two child components, in response to a combination operation of at least two child components after the unbinding of the target composite component, wherein a configuration control is associated with the composite component to be configured. The steps include: presenting the composite component to be configured and the configuration area corresponding to the composite component to be configured in response to a trigger operation of the configuration control corresponding to the composite component to be configured; The method according to claim 8 or 9, further comprising the step of obtaining a composite component consisting of at least two child components in response to a configuration operation of the composite component to be configured in a configuration region corresponding to the composite component to be configured.

11. A processing unit for a composite component, A decision unit configured to determine which composite component to be generated, wherein the composite component to be generated includes a target child component, and a composite component creation function is associated with the composite component to be generated. A first addition unit is configured to add each attribute of the target child component to the input parameters of the composite component creation function in response to an attribute addition operation of the target child component within the composite component to be generated, A processing unit for a composite component, comprising: a first generation unit configured to generate a target composite component based on the composite component creation function and the input parameters, wherein each attribute of the target child components included in the target composite component is editable; and a processing unit for a composite component.

12. It is an electronic device, One or more processors, A storage device in which one or more programs are stored, An electronic device that enables the processing method of a composite component according to any one of claims 1 to 10 to be implemented by the one or more processors when the one or more programs described above are executed by the one or more processors.

13. A computer-readable storage medium that stores a computer program, and when the computer program is executed by a processor, realizes the processing method for a composite component according to any one of claims 1 to 10.

Images