CN114661287A

CN114661287A - Component linkage rendering method and device, electronic equipment, storage medium and product

Info

Publication number: CN114661287A
Application number: CN202210248452.6A
Authority: CN
Inventors: 律小娇
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2022-03-14
Filing date: 2022-03-14
Publication date: 2022-06-24

Abstract

The disclosure provides a component linkage rendering method, a component linkage rendering device, electronic equipment, a storage medium and a product, and relates to the technical field of computers, in particular to the fields of cloud computing and intelligent search. The specific implementation scheme is as follows: acquiring at least one component to be rendered; determining rendering events having incidence relations with the components, and obtaining rendering events respectively corresponding to at least one of the components; if the number of the assemblies is multiple, grouping the assemblies according to the rendering event to obtain at least one group of assemblies; acquiring event information of a rendering event of which at least one group of components have an incidence relation; generating a corresponding rendering event according to the event information of the rendering event, and executing at least one rendering event according to a preset rendering sequence; the event information comprises execution relation information of at least one component related to the same rendering event when the rendering action is executed. The technical scheme of the disclosure improves the rendering success rate.

Description

Component linkage rendering method and device, electronic equipment, storage medium and product

Technical Field

The present disclosure relates to the field of cloud computing and intelligent search in the field of computer technologies, and in particular, to a method and an apparatus for rendering component linkage, an electronic device, a storage medium, and a product.

Background

A Low-Code Development Platform (LCDP) is a Development Platform that can generate an application quickly without coding or with a small amount of coding. The low-code platform can provide external development services, and generally, the development services can provide visual component configuration through a renderer. In practical applications, multiple renderers may be used, for example, a form (form) renderer may provide form components such as a picture input box and a file input box, and a condition renderer may provide a condition expression component to dynamically display different contents according to data.

Generally, program development is finished, and a program page can be rendered and displayed, and the rendering of the page is completed by a rendering engine. However, in practical applications, in the engine rendering process, it may not be possible to accurately control the rendering actions of different components of different renderers, and rendering failures are likely to occur in the components, resulting in a high rendering failure rate.

Disclosure of Invention

The present disclosure provides a component linkage rendering method, apparatus, electronic device, storage medium and product for a low code platform.

According to a first aspect of the present disclosure, there is provided a component linkage rendering method, including:

acquiring at least one component to be rendered;

determining rendering events having incidence relations with the components, and obtaining rendering events respectively corresponding to at least one of the components;

if the number of the assemblies is multiple, grouping the assemblies according to the rendering event to obtain at least one group of assemblies;

acquiring event information of a rendering event of which at least one group of components have an incidence relation;

generating a corresponding rendering event according to the event information of the rendering event, and executing at least one rendering event according to a preset rendering sequence; the event information comprises execution relation information of at least one component related to the same rendering event when the rendering action is executed.

According to a second aspect of the present disclosure, there is provided a component linkage rendering apparatus including:

the device comprises a component acquisition unit, a rendering unit and a rendering unit, wherein the component acquisition unit is used for acquiring at least one component to be rendered;

the event determining unit is used for determining rendering events which have incidence relations with the components and obtaining rendering events corresponding to at least one component;

the component grouping unit is used for grouping the components according to the rendering events if the number of the components is multiple to obtain at least one group of components;

the event generating unit is used for acquiring event information of rendering events with at least one group of components having incidence relation;

the event execution unit is used for generating a corresponding rendering event according to the event information of the rendering event and executing at least one rendering event according to a preset rendering sequence; the event information comprises execution relation information of at least one component related to the same rendering event when the rendering action is executed.

According to a third aspect of the present disclosure, there is provided an electronic device comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of rendering in conjunction with components of the first aspect.

According to a fourth aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to execute the component linkage rendering method of the first aspect.

According to a fifth aspect of the present disclosure, there is provided a computer program product comprising: a computer program, stored in a readable storage medium, from which at least one processor of an electronic device can read the computer program, execution of the computer program by the at least one processor causing the electronic device to perform the method of the first aspect.

According to the technology disclosed by the invention, the problem that rendering failure easily occurs during multi-component multi-event linkage rendering is solved, and at least one component is obtained by adopting a rendering monitoring mode. By determining the rendering events having the association relation with the components, the rendering events respectively corresponding to at least one component can be obtained, and the grouping of the rendering events can be realized. After grouping, the corresponding rendering events can be generated by using the rendering information of the rendering events, and the rendering success rate can be ensured by generating and executing the rendering events in sequence. The rendering event is generated and executed by utilizing the event information of the assembly, the rendering event of the assembly can be accurately rendered, and the rendering success rate of the assembly is improved.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

FIG. 1 is a diagram of an application scenario in which a component rendering method provided by the present disclosure may be implemented;

FIG. 2 is a flow diagram of one embodiment of a component linkage rendering method provided by embodiments of the present disclosure;

FIG. 3 is a flowchart of yet another embodiment of a component linkage rendering method provided by embodiments of the present disclosure;

FIG. 4 is a flowchart of a further embodiment of a component linkage rendering method provided by an embodiment of the present disclosure;

FIG. 5 is a flowchart of yet another embodiment of a component linkage rendering method provided by embodiments of the present disclosure;

FIG. 6 is a schematic structural diagram of a component linkage rendering system according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram illustrating an embodiment of a component linkage rendering apparatus according to the present disclosure;

FIG. 8 is a block diagram of an electronic device for implementing a component linkage rendering method according to an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

The technical scheme of the disclosure can be applied to a use scene of a low-code platform, and the mapping relation between the components and the events can be stored by monitoring the events of at least one component, so that when a target component is triggered, a corresponding rendering event can be constructed and executed according to the event information of the component. The event can be accurately executed, and the storage efficiency of the event is improved.

Generally, a Low-Code Development Platform (LCDP) is a Development Platform that can generate an application program quickly without coding or with a small amount of coding. In practical applications, a low-code platform, which may be referred to as a low-code rendering engine or a low-code front-end framework, may generally provide a user with a renderer, which may include a plurality of components from which the user may select an appropriate component and set corresponding data for the component in a related attribute. And after the component selection and the attribute setting are finished, the page can be rendered. Rendering of pages is primarily accomplished by the low code rendering engine. The rendering engine may read the data of the component through the communication protocol to render the component event with the data of the component. The component event can be composed by information such as a component name, an event description, and the like. Rendering of the component may be accomplished using the component event. The rendering engine can render a plurality of components, but because the components in the program have more calling flows and processing modes, one component may have a plurality of events at the same time, and when the rendering engine renders, the rendering engine may accurately control the event actions respectively executed by different components of different renderers, so that rendering failure of the components is easy to occur, and rendering failure rate is high.

The present disclosure provides a component rendering method, apparatus, electronic device, storage medium, and product. The method can be applied to the fields of cloud computing and intelligent search in the field of computers, so as to achieve the aim of effectively improving the success rate of component rendering.

In order to solve the above technical problem, in this embodiment, a rendering listening mode is adopted to obtain at least one component. By determining the rendering events having the association relation with the components, the rendering events respectively corresponding to at least one component can be obtained, and the grouping of the rendering events can be realized. After grouping, the corresponding rendering events can be generated by using the rendering information of the rendering events, and the rendering success rate can be ensured by generating and executing the rendering events in sequence. The rendering event is generated and executed by utilizing the event information of the assembly, the rendering event of the assembly can be accurately rendered, and the rendering success rate of the assembly is improved.

Based on the inventive discovery, the technical scheme of the disclosure is provided. The component rendering method provided by the embodiments of the present disclosure is described in detail below.

Fig. 1 is a diagram of an application scenario in which a component rendering method provided by the present disclosure may be implemented. As shown in fig. 1, the system architecture corresponding to the component rendering method may include: a first electronic device 1 and a second electronic device 2. As shown in fig. 1, the first electronic device 1 may be a computer. The second electronic device may be a cloud server. Wherein, a low-code development platform, such as a low-code rendering engine or referred to as a low-code front-end framework, can be configured in the first electronic device 1, and one or more renderers can be provided for a user, and candidate components of the renderers are shown for the user. And detecting one or more rendering events created by the user based on the candidate components, and when the user initiates an information generation request, initiating the information generation request to the second electronic equipment based on the information generation request carrying the one or more rendering events. The rendering event may correspond to at least one component.

The second electronic device 2 may obtain event information of at least one rendering event based on an information generation request initiated by the first electronic device, so that the component linkage rendering method provided by the present disclosure is used to perform corresponding component grouping on rendering events that determine at least one component and obtain an association relationship between each component, and then sequentially generate and execute at least one rendering event.

As shown in fig. 2, a flowchart of an embodiment of a component linkage rendering method provided by the embodiment of the present disclosure may be configured as a component linkage rendering apparatus, which may be located in an electronic device. The method for rendering the components in a linkage manner can comprise the following steps:

201: at least one component to be rendered is obtained.

The component may refer to a specific object obtained by encapsulating data and a method, and may refer to a component corresponding to a control in a page. The technical scheme disclosed by the invention can be applied to cloud computing and intelligent search scenes in the computer technology, in particular to a low-code front-end framework. The low-code front-end framework is a page renderer, can be configured to render the set pages based on JSON (Java Object Notation, Chinese full name: Object Notation of a just-in-time compilation programming language) with a specific format, can be used for developing various management pages, and can also be called as a low-code rendering engine. The components are page objects which can be configured through the JSON format, and corresponding page control can be completed through JSON.

202: and determining rendering events having incidence relation with the components, and obtaining rendering events respectively corresponding to at least one component.

Alternatively, a rendering event may refer to a specific interaction moment occurring in a document or a browser window, and the browser needs to perform a corresponding page rendering operation according to the document. At least one rendering event may be fired simultaneously. Rendering events may be obtained by listening. The rendering event may perform a corresponding rendering of the at least one component. A component may be rendered by multiple events.

In this embodiment, rendering the event may include: event name, event description, and context of the event. The event name may be a string or symbol that serves an identifying meaning to the component. The event description may be information that records the content of the event specific execution. The sequence of at least one execution action in the event and the execution content can be recorded through the event description. The execution content may be the specific execution content of the component. Taking a text box as an example, the execution content may input text information, such as an account number or a password of the user. An event context may refer to an executed rendering event that is located before and after the rendering event.

203: and if the number of the components is multiple, grouping the multiple components according to the rendering event to obtain at least one group of components.

The components may be distinguished using component names. When one component is used, the rendering event can be directly utilized to render the component, and the rendering efficiency of the component is improved.

In this embodiment, when there are multiple components, the components may be grouped according to event names corresponding to the components. When a component is bound to an event, it may be referred to as a component event, which may include an event name and an event name. A component may be in multiple events. The plurality of events may be multi-level events, and the multi-level events may refer to rendering events that are executed in a hierarchical order.

204: event information of rendering events of which at least one group of components has an association relation is acquired.

The event information of the rendering event may include an event name and an event description of the rendering event.

Any group of components is composed of at least one component with the same rendering event, and the rendering event with the association relationship of at least one group of components can refer to the rendering event corresponding to at least one component of each group of components.

205: and generating a corresponding rendering event according to the event information of the rendering event. And executing at least one rendering event in a pre-configured rendering order. The event information comprises execution relation information of at least one component related to the same rendering event when the rendering action is executed.

After the components are obtained, rendering events corresponding to the components can be generated, and the rendering events corresponding to the components can be started. Execution may begin upon generation of a rendering event.

In the embodiment of the present disclosure, at least one component to be rendered is acquired, and rendering control may be performed on the at least one component. And determining the rendering events having the association relation with the components, obtaining the rendering events respectively corresponding to at least one component, and realizing the correspondence of the rendering events of each component. And if the number of the components is determined to be multiple, grouping the multiple components according to the rendering event to obtain at least one group of components. At least one group of components can correspond to corresponding rendering events respectively, and management of the components and the events is achieved. The event information of the rendering events of which at least one group of components have the incidence relation is obtained, the corresponding rendering events can be generated according to the event information of the rendering events, and the real-time triggering generation of the events is realized. The method and the device have the advantages that at least one rendering event is executed according to the preset rendering sequence, sequential execution of each rendering event can be realized, conflicts generated in the execution processes of different components of different rendering events are avoided, and accurate execution of the events can be realized.

In one possible design, as shown in fig. 3, a flowchart of an embodiment of a component linkage rendering method provided by the embodiment of the present disclosure may be configured as a component linkage rendering apparatus, which may be located in an electronic device. The difference between the component linkage rendering method and the component linkage rendering method shown in fig. 2 is that, step 201: obtaining at least one component to be rendered may comprise the steps of:

step 2011: at least one broadcast event information is listened to. The broadcast event information may include event information associated with at least one component of the same rendering event and the rendering event.

Step 2012: and respectively reading at least one component from at least one piece of broadcast event information to obtain at least one component to be rendered.

The broadcast event information may include an event name, an event description, and an event context of the rendering event. The broadcast event information may be obtained by a format definition conversion of the broadcast event according to the rendering event. The event name and the event context can be automatically provided by the low-code front-end framework, and the user can set the event name and the event context through the visual configuration of the low-code front-end framework.

When monitoring an event, the event name of the monitoring event and the action set of the event can be set. The set of actions may include at least one rendering action of the event. The rendering action may include an action name, an action description. In use, one component may configure multiple actions. The action set can agree on information such as execution order of a plurality of actions, execution dependency condition of the actions, action intervention, and the like. Wherein the execution order may be obtained by the user arranging the actions.

In this example, the broadcast event information may be authenticated by a listener, such as a didMount component.

In the embodiment of the present disclosure, one or more pieces of broadcast event information may be acquired by monitoring the broadcast event information. And the event information associated with at least one component of the same rendering event and the rendering event may be included in the broadcast event information. The at least one component to be rendered may be obtained by reading the at least one component from the at least one broadcast information, respectively. Through the monitoring mode, the accurate acquisition of the components to be rendered can be realized, the omission of the components to be rendered is avoided, and the rendering comprehensiveness is ensured.

In certain embodiments, after listening to the at least one event broadcast information in step 2011, the method may further comprise:

and establishing an association relation between the rendering event in the event broadcast information and at least one component belonging to the rendering event.

Optionally, an event binding module may be adopted to establish an association relationship between a rendering event in the event broadcast information and at least one component belonging to the rendering event. Through the association relationship, the corresponding relationship between at least one component and the corresponding rendering event can be realized, and bidirectional query can be realized.

In the embodiment of the present disclosure, after monitoring at least one event broadcast message, a corresponding association relationship may be established by using a rendering event and at least one component in each event broadcast message. The association may be used to determine a component corresponding to the rendering event upon execution of a subsequent rendering event. By establishing the association relationship between the rendering event and the at least one component, the corresponding relationship between the rendering event and the at least one component can be more definite, and the accuracy of event execution can be ensured.

In some embodiments, prior to listening for at least one event broadcast message, the method may further comprise:

and detecting an information generation request triggered by a user, and obtaining at least one rendering event in the information generation request.

And converting the original event information corresponding to the rendering event into event broadcast information corresponding to the rendering event according to a broadcast event format.

The broadcast of the event broadcast information may be generated by a user trigger. And converting original event information corresponding to the rendering event, namely information such as event name and event description of the rendering event into corresponding event broadcast information according to a broadcast event format.

The information generation request may be initiated after a user completes the orchestration of components and the setting of component properties using a renderer in the low code front end framework. Initiation of the information generation request may cause the electronic device to enter an event rendering operation. Events can be broadcast through the event broadcast information so that the listener can listen to the corresponding rendering event.

In the embodiment of the present disclosure, the generation of the event broadcast information may be an information generation request based on a user trigger. And obtaining at least one rendering event in the information generation request by detecting the information generation request triggered by the user. The processing object of the information generation request can be accurately determined by acquiring the rendering event. After the rendering event is obtained, the original event information corresponding to the rendering event may be converted into event broadcast information corresponding to the rendering event according to a broadcast event format. The accurate generation of the rendering event can be ensured by converting the format of the broadcast event, so that the rendering event can be accurately executed.

For more accurate management of rendering events, after performing at least one rendering event in a preconfigured rendering order, the method may further comprise:

and if the rendering event execution is determined to be finished, canceling the association relation between the rendering event and at least one component belonging to the rendering event.

Optionally, a logout component, such as a willUnmount component, may be used to logout the association between the rendering event and at least one component belonging to the rendering event, which may ensure accurate logout of the rendering event. The logout machine may be a preset device for logging out the association relationship.

In the embodiment of the present disclosure, when it is determined that the execution of the rendering event is finished, the association relationship between the rendering event and the at least one component belonging to the rendering event may be cancelled. By canceling the association relation corresponding to the rendering event, the rendering event can be accurately and effectively managed, repeated rendering of the rendering event or rendering conflict with other rendering events due to the existence of the association relation is avoided, and the processing efficiency and accuracy of the rendering event are improved.

In order to perform accurate execution on the rendering events, as shown in fig. 4, in the embodiment shown in fig. 2, the step 205 of executing at least one rendering event according to the preconfigured rendering order may include the following steps:

step 2051: and according to the configured rendering sequence, determining a target rendering event to be rendered currently from at least one rendering event.

Step 2052: and executing the target rendering events, and when the rendering of the target rendering events is finished, returning to the step 2051 to continuously execute the step of determining the target rendering event to be rendered currently from at least one rendering event according to the configured rendering sequence until the execution of the last rendering event is finished.

The rendering order may be determined when the user terminal sets the rendering events. The rendering sequence can be specified by a user, and can also be accurately generated by the jump relation between more than two rendering events, so that accurate rendering is realized.

The rendering events may be sequentially generated based on a rendering order. Each time a rendering event is generated according to the rendering order, that is, the rendering event can be determined as a target rendering event, and the target rendering event is executed.

In one possible design, if it is determined that any target rendering event fails to render, a prompt message indicating that the target rendering event fails to render is output. If it is determined that the rendering of the target rendering event is finished, the rendering result of each rendering event may be fed back to the user, for example, the rendering result is sent to the user equipment, and the user equipment displays the corresponding rendering result. If all rendering events are rendered and rendering failure does not occur, prompt information of rendering success of all rendering events can be output. Specifically, the rendering success prompt information may be sent to the user equipment, and the user equipment displays the rendering success prompt information.

In the embodiment of the disclosure, according to the configured rendering sequence, the target rendering event to be rendered currently can be determined from the at least one rendering event, so that the at least one rendering event is sequentially acquired, execution omission of the rendering event is avoided, each rendering event is ensured to be executed, and execution efficiency and accuracy of the rendering event are improved.

As an embodiment, in step 2052, executing the target rendering event may specifically include the following steps:

and acquiring an execution action tree corresponding to at least one rendering action of the target rendering event. The execution action tree includes at least one execution node. The execution node corresponds to the corresponding rendering action.

And determining a node execution sequence corresponding to at least one execution node according to the corresponding execution relation information of the rendering action of the rendering event. The execution relation information of the rendering actions comprises the execution sequence and the action nesting relation among the rendering actions of the rendering events.

And according to the execution sequence of the nodes, sequentially controlling and executing one execution node to respectively execute corresponding rendering actions so as to finish the target rendering event.

Alternatively, the execution action tree may be generated based on action execution relationship information between at least one rendering action set for the target rendering event when the target rendering event is generated. The action execution relation information may render at least one of execution logic, jump logic, etc. information of the action. Jump logic, information transmission mode and the like between two adjacent rendering actions can be determined by executing the relationship information.

The action execution tree may be generated according to a jump logic between actions. For example, when the execution of the a rendering action is finished, the node jumps to the B rendering action, and the a rendering action is the parent execution node of the B rendering action.

The execution nodes in the action execution tree can be generated according to the rendering action, and the node categories of the execution nodes correspond to the rendering content of the rendering action. For example, when a rendering action is a logical action, the execution node corresponding to the rendering action may be, for example, a Break node, a Continue node (ending this loop and continuing to a next loop), and the like. Further, based on the lack of use of rendering actions, the execution phase may further include: concurrent nodes, exclusive nodes, cyclic nodes, custom action nodes, component generic action nodes, component specific action nodes, and/or broadcast nodes.

In the disclosed embodiments, a rendering event may include at least one rendering action. When a target rendering event is executed, a corresponding execution action tree may be obtained. The execution action tree may include at least one execution node. The execution action tree can accurately position the context association between at least one rendering action of the rendering events, and the execution relation information of the rendering events can determine the node execution sequence corresponding to at least one execution node, so that the rendering actions corresponding to at least one execution node in the execution action tree are executed according to the node execution sequence. The accurate execution of the at least one rendering action of the rendering event is realized, and the rendering efficiency and the accuracy of the at least one rendering action of the rendering event are improved.

In one possible design, an action execution tree corresponding to at least one rendering action of the target rendering event may be generated at the time of generation of the rendering event. After determining the target rendering event, obtaining an execution action tree corresponding to at least one rendering action of the target rendering event may include:

and acquiring global event information corresponding to the target rendering event. The global event information may include positioning information generated when the target rendering event is generated as a global event.

Based on the global event information corresponding to the rendering event, an execution action tree corresponding to at least one rendering action of the target rendering event can be located.

The rendering event may be a global event, and the global event information may be generated when a corresponding target rendering event is generated by using the event information, and may include a location of the target rendering event in the memory.

In the embodiment of the disclosure, global event information corresponding to a target rendering event is acquired, so as to accurately position an execution action tree for at least one rendering action of the target rendering event based on the global event corresponding to the rendering event by using positioning information generated when the target rendering event is generated by using the global event information. By acquiring the global event information, the execution action tree of the target rendering event can be accurately positioned, the execution action tree of the target rendering event can be quickly and accurately acquired, and the rendering efficiency is improved.

Wherein, in order to realize the accurate execution of the rendering action. The step of executing the rendering action corresponding to the execution node may specifically include the following steps:

determining at least one target component corresponding to the rendering action of the execution node in at least one component of the target rendering event;

and executing corresponding rendering contents on the at least one target component respectively based on the rendering contents corresponding to the rendering actions on the at least one target component respectively.

The action object corresponding to at least one target component may be determined for the rendering action of the execution node, and then respective rendering contents may be executed for at least one component.

In the embodiment of the present disclosure, when the rendering action is executed, at least one target component corresponding to the rendering action may be determined from the at least one component corresponding to the target rendering event, so as to obtain the at least one target component of the rendering action. And executing corresponding rendering contents on the at least one target component respectively based on the rendering contents respectively corresponding to the at least one target component by the rendering action. By determining at least one target component corresponding to the target rendering event, the at least one target component corresponding to the target rendering event can be accurately positioned, the rendering content corresponding to each target component is determined, the corresponding rendering content is executed respectively, the accurate execution of the rendering event is realized, the rendering failure caused by unclear association relationship of the components and unclear rendering content corresponding to the components is avoided, and the accurate rendering of the target rendering event is realized.

As shown in fig. 5, a flowchart of another embodiment of a component linkage rendering method provided by the embodiment of the present disclosure may be configured as a component linkage rendering apparatus, and the component linkage rendering apparatus may be located in an electronic device. The method for rendering the components in linkage with each other is different from the embodiment shown in fig. 1 in that before determining at least one component to be rendered, the method may further include the following steps:

501: detecting a renderer set by a user based on a page configuration platform, and obtaining at least one candidate component in the renderer.

502: at least one rendering event setting request initiated by a user based on at least one candidate component is detected.

The rendering event may be defined by a collection of event names, event actions. The set of event actions may include rendering actions respectively determined for at least one component of the rendering event. Wherein, the rendering action of any one component corresponding to the same rendering event may include one or more.

503: generating at least one rendering event according to the at least one rendering event setting request; at least one rendering event corresponds to a rendering order.

In the embodiment of the disclosure, before rendering, a renderer set by a user based on a page configuration platform can be detected to obtain at least one candidate component in the renderer. The at least one candidate component can be used for quickly generating the rendering event, and the generation efficiency of the rendering event is improved. By detecting a setting request of at least one rendering event initiated by a user based on at least one candidate component, the at least one rendering event can be generated according to the setting request of the at least one rendering event, so that the personalized setting of the at least one rendering event by the user is realized, and the matching degree of the at least one rendering event and the user requirement is improved. By setting the corresponding rendering sequence for the at least one rendering event, the accurate execution of the at least one rendering event can be ensured, and the execution success rate of the at least one rendering event is effectively guaranteed.

In one possible design, step 503 above: the method for generating at least one rendering event according to at least one rendering event setting request can comprise the following steps when the method is executed in detail:

a preconfigured candidate action is determined according to the at least one rendering event setting request.

At least one rendering action of the rendering event is determined from the candidate actions based on the rendering action execution relationship information of the rendering event.

The candidate actions may include one or more of broadcast actions, component generic actions, component specific actions, logical actions, and custom actions.

The actions may be component-specific actions, may also be referred to as component actions, and may include component-generic actions as well as component-specific actions. The component action may be constituted by the contents of an action name, an action description, an action context, an action execution condition, an action intervention, a sub-action of the action, and the like. A component may be defined multiple actions at the same time in one rendering event. The rendering action is a candidate action for the determined rendering content. The rendering content is the specific content corresponding to the action, that is, the definition or description of what operation is performed by the component under what condition.

The context of an action may refer to a previous and/or subsequent action to the current action, an adjacent action, and the like. An execution condition may refer to a condition under which an action is triggered to execute. Action intervention may include preventing performance of a subsequent action or preventing performance of a component subsequent component-specific action, etc. In real applications, action intervention may be configured in dependence on preventdefaults (preventing default events) and stopprogress (preventing bubbles). The preventDefault may inform the renderer not to perform the default action associated with the event. stopPropagation may stop the propagation of events, preventing events from being dispatched to other nodes.

If a component corresponds to one or more actions, the one or more actions may belong to different rendering events, that is, a component may correspond to at least one action corresponding to at least one rendering event respectively. In this embodiment, a rendering event is used as a rendering unit.

Wherein the broadcast action may refer to encapsulating the acquisition of the broadcast event. Component actions may refer to component specific actions and component generic actions defined for a component.

Component common actions may include pop-up, jump, drawer, etc.; component-specific actions may include component-specific actions, e.g., a Tabs (Tabs) switch component may switch to a certain tab page, and a tab switch component may include multiple tab pages.

The logical actions may include parallel, branch, loop, Continue (skipping a loop to Continue executing the next loop), Break (stopping a loop under certain conditions), etc. types of actions, and the logical action node may contain one or more sub-actions. The parallel actions do not interfere with each other, but any set sub-action of the interference configuration influences the execution result of the subsequent logic action. The Break action provides interrupt logic for the loop and the Continue action provides skip logic for the loop.

The custom action may refer to custom execution logic based on the JS implementation. Execution logic may refer to the specific content of the action execution.

In this embodiment, the preconfigured candidate action may be determined according to the at least one rendering event setting request, so as to accurately obtain the candidate action. At least one rendering action of the rendering event is determined from the candidate actions based on the rendering action execution relationship information of the rendering event. And through the acquisition of the at least one rendering action, selecting a component for the rendering action from the at least one candidate component, and generating a rendering event based on the at least one rendering action and the component corresponding to each rendering action to obtain at least one rendering event. And through action selection and the selection of the rendering action corresponding to the action, the rendering event can be quickly generated.

For easy understanding, as shown in fig. 6, a schematic structural diagram of a component linkage rendering system provided in the embodiment of the present disclosure may include a component manager 601, an event handler 602, and an event executor 603.

Component manager 601 can be used to retrieve at least one component to be rendered.

An event processor 602 may be used to determine rendering events that have an association with a component. And obtaining rendering events corresponding to at least one component respectively. And if the number of the components is multiple, grouping the multiple components according to the rendering event to obtain at least one group of components. Event information of rendering events of which at least one group of components has an association relation is acquired. And generating a corresponding rendering event according to the event information of the rendering event. And executing at least one rendering event in a pre-configured rendering order. The event information comprises execution relation information of at least one component related to the same rendering event when the rendering action is executed.

The event executor 603 may be used to execute specific rendering events.

In this embodiment, through the cooperation of the component manager, the event handler, and the event executor, the components can be accurately and cooperatively rendered, so that the cooperative sequential rendering of multiple events is realized, and the component rendering accuracy is improved.

In one possible design, in order to manage components more accurately and more precisely, referring to fig. 6, a component manager 601 may include a component obtaining unit 6011, a request detecting unit 6012, an association logout unit 6013, and an event triggering unit 6014.

The component obtaining unit 6011 may monitor at least one event broadcast message, and read at least one component from the at least one event broadcast message.

The request detecting unit 6012 may first detect an information generation request triggered by a user, and obtain at least one rendering event in the information generation request; the original event information corresponding to the rendering event is converted into event broadcast information corresponding to the rendering event according to a broadcast event format, and each event broadcast information is broadcasted to be monitored by the information monitoring module 6011, so as to obtain at least one component.

After the information monitoring module 6011 monitors the at least one event broadcast information, the at least one component may be read from the at least one event broadcast information, respectively, to obtain the at least one component to be rendered. Thereafter, a request for establishing an association relationship between at least one component and a corresponding rendering event may be initiated to the event processor 602, and the association establishing unit 6021 in the event processor 602 may establish an association relationship between the rendering event in the event broadcast information and at least one component belonging to the rendering event. And the association deregistration unit 6013 may deregister an association between a rendering event and at least one component belonging to the rendering event when it is determined that the execution of the rendering event is finished.

The event trigger unit 6014 may execute at least one rendering event based on a pre-configured rendering order, triggering execution of a corresponding target rendering event. The event execution unit 6022 in the event processor 602 may read at least one component corresponding to the event and the event information from the association relationship based on the trigger of the event trigger unit 6014, and generate a corresponding rendering event, so as to execute the at least one rendering event according to a pre-configured rendering order.

For specific steps performed by each component, reference may be made to the description of the foregoing embodiments, and details are not described here.

As shown in fig. 7, a schematic structural diagram of an embodiment of a component linkage rendering apparatus provided in an embodiment of the present disclosure, the component linkage rendering apparatus may be configured with the component linkage rendering method in the foregoing embodiment, the apparatus may be located in an electronic device, and the component linkage rendering apparatus 700 may include the following units:

the component acquisition unit 701: for obtaining at least one component to be rendered.

The event determination unit 702: the method is used for determining the rendering events which have the association relation with the components and obtaining the rendering events respectively corresponding to at least one component.

The component grouping unit 703: and if the number of the components is multiple, grouping the multiple components according to the rendering event to obtain at least one group of components.

The event generation unit 704: and the event information is used for acquiring the rendering events of which at least one group of components has the association relationship.

The event execution unit 705: the rendering system is used for generating a corresponding rendering event according to the event information of the rendering event and executing at least one rendering event according to a preset rendering sequence; the event information comprises execution relation information of at least one component related to the same rendering event when the rendering action is executed.

As one embodiment, a component acquiring unit includes:

the information monitoring module is used for monitoring at least one event broadcast message; the event broadcast information includes event information associated with at least one component of the same rendering event and the rendering event;

and the component reading module is used for respectively reading at least one component from at least one event broadcast message and obtaining at least one component to be rendered.

In certain embodiments, further comprising:

and the association establishing unit is used for establishing the association relationship between the rendering event in the event broadcast information and at least one component belonging to the rendering event.

In certain embodiments, further comprising:

the request detection unit is used for detecting an information generation request triggered by a user and acquiring at least one rendering event in the information generation request;

and the information conversion unit is used for converting the original event information corresponding to the rendering event into the event broadcast information corresponding to the rendering event according to the broadcast event format.

In one possible design, further comprising:

and the association logout unit is used for logging out the association relation between the rendering event and at least one component belonging to the rendering event if the rendering event is determined to be finished.

In one embodiment, the event execution unit includes:

the target determination module is used for determining a target rendering event to be rendered currently from at least one rendering event according to the configured rendering sequence;

and the event execution module is used for executing the target rendering events, returning to the step of determining the current target rendering event to be rendered from at least one rendering event according to the configured rendering sequence when the rendering of the target rendering events is finished, and executing the step until the execution of the last rendering event is finished.

In some embodiments, the event execution module comprises:

the action acquisition sub-module is used for acquiring an execution action tree corresponding to at least one rendering action of the target rendering event; the execution action tree comprises at least one execution node, and the execution node corresponds to a corresponding rendering action;

the node determining submodule is used for determining a node execution sequence corresponding to at least one execution node according to the execution relation information of the rendering action of the rendering event; the execution relation information of the rendering actions comprises the execution sequence and action nesting information among the rendering actions of the rendering events;

and the node execution submodule is used for sequentially controlling at least one execution node to respectively execute corresponding rendering actions according to the node execution sequence so as to finish the target rendering event.

As an optional implementation manner, the action obtaining sub-module is specifically configured to:

acquiring global event information corresponding to a target rendering event; the global event information comprises positioning information generated when the target rendering event is generated as a global event;

and positioning an execution action tree corresponding to at least one rendering action of the target rendering event based on the global event information corresponding to the rendering event.

As a possible implementation, the node execution submodule is specifically configured to:

determining at least one target component corresponding to a rendering action in at least one component of a target rendering event;

As still another embodiment, further comprising:

detecting a renderer set by a user based on a page configuration platform, and obtaining at least one candidate component in the renderer;

detecting at least one rendering event setting request initiated by a user based on at least one candidate component;

generating at least one rendering event according to the at least one rendering event setting request; at least one rendering event corresponds to a rendering order.

In some embodiments, generating at least one rendering event according to at least one rendering event setting request includes:

determining a pre-configured candidate action according to the at least one rendering event setting request;

determining at least one rendering action of the rendering event from the candidate actions based on the execution relation information of the rendering actions of the rendering event;

detecting a component selected by a user for a rendering action from at least one candidate component;

and generating a rendering event based on the at least one rendering action and the component corresponding to the rendering action to obtain at least one rendering event.

It should be noted that the head model in this embodiment is not a head model for a specific user, and cannot reflect personal information of a specific user. It should be noted that the two-dimensional face image in the present embodiment is from a public data set.

In the technical scheme of the disclosure, the processes of collecting, storing, using, processing, transmitting, providing, disclosing and the like of the personal information of the related user all accord with the regulations of related laws and regulations, and do not violate the common customs of public order.

The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.

According to an embodiment of the present disclosure, the present disclosure also provides a computer program product comprising: a computer program, stored in a readable storage medium, from which at least one processor of the electronic device can read the computer program, and the execution of the computer program by the at least one processor causes the electronic device to perform the solutions provided by any of the above embodiments.

FIG. 8 shows a schematic block diagram of an example electronic device 800 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 8, the apparatus 800 includes a computing unit 801 which can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)802 or a computer program loaded from a storage unit 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data necessary for the operation of the device 800 can also be stored. The calculation unit 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

A number of components in the device 800 are connected to the I/O interface 805, including: an input unit 806, such as a keyboard, a mouse, or the like; an output unit 807 such as various types of displays, speakers, and the like; a storage unit 808, such as a magnetic disk, optical disk, or the like; and a communication unit 809 such as a network card, modem, wireless communication transceiver, etc. The communication unit 809 allows the device 800 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

Computing unit 801 may be a variety of general and/or special purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and the like. The calculation unit 801 executes the respective methods and processes described above, such as the component linkage rendering method. For example, in some embodiments, the component linkage rendering method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of the computer program can be loaded and/or installed onto device 800 via ROM 802 and/or communications unit 809. When loaded into RAM 803 and executed by computing unit 801, the computer programs may perform one or more of the steps of the component linkage rendering method described above. Alternatively, in other embodiments, the computing unit 801 may be configured to perform the component-linkage rendering method by any other suitable means (e.g., by way of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The Server can be a cloud Server, also called a cloud computing Server or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service ("Virtual Private Server", or simply "VPS"). The server may also be a server of a distributed system, or a server incorporating a blockchain.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A method for rendering components in linkage comprises the following steps:

acquiring at least one component to be rendered;

2. The method of claim 1, wherein the obtaining at least one component to be rendered comprises:

monitoring at least one event broadcast message; the event broadcast information includes event information associated with at least one component of the same rendering event and the rendering event;

and respectively reading at least one component from at least one event broadcast message, and obtaining at least one component to be rendered.

3. The method of claim 2, wherein the listening for at least one event broadcast information further comprises:

4. The method of claim 2, wherein prior to listening for at least one event broadcast message, further comprising:

detecting an information generation request triggered by a user, and acquiring at least one rendering event in the information generation request;

5. The method of claim 3, wherein after said performing at least one of said rendering events in a preconfigured rendering order, further comprising:

and if the rendering event is determined to be finished, logging out the association relation between the rendering event and at least one component belonging to the rendering event.

6. The method of any of claims 1-5, wherein the performing at least one rendering event in a preconfigured rendering order comprises:

determining the current target rendering event to be rendered from at least one rendering event according to the configured rendering sequence;

and executing the target rendering events, and returning to the step of determining the current target rendering event to be rendered from at least one rendering event according to the configured rendering sequence when the rendering of the target rendering events is finished, and executing the step until the execution of the last rendering event is finished.

7. The method of claim 6, wherein the executing the target rendering event comprises:

acquiring an execution action tree corresponding to at least one rendering action of the target rendering event; the execution action tree comprises at least one execution node, and the execution node corresponds to a corresponding rendering action;

determining a node execution sequence corresponding to at least one execution node according to the execution relation information of the rendering action of the rendering event; the execution relation information of the rendering actions comprises the execution sequence and action nesting information among the rendering actions of the rendering events;

and sequentially controlling at least one execution node to respectively execute corresponding rendering actions according to the node execution sequence so as to finish the target rendering event.

8. The method of claim 7, wherein the obtaining of the execution action tree corresponding to the at least one rendering action of the target rendering event comprises:

acquiring global event information corresponding to the target rendering event; the global event information comprises positioning information generated when the target rendering event is generated as a global event;

9. The method according to claim 7 or 8, wherein the step of executing the rendering action corresponding to the execution node comprises:

determining at least one target component corresponding to the rendering action in at least one component of the target rendering event;

and executing corresponding rendering contents on at least one target component respectively based on the rendering contents corresponding to the rendering actions on at least one target component respectively.

10. The method according to any one of claims 1-9, further comprising:

detecting at least one rendering event setting request initiated by a user based on at least one of the candidate components;

generating at least one rendering event according to at least one rendering event setting request; at least one of the rendering events corresponds to a rendering order.

11. The method of claim 10, wherein the generating at least one rendering event according to at least one rendering event setup request comprises:

determining at least one rendering action of the rendering events from the candidate actions based on execution relation information of the rendering actions of the rendering events;

detecting a component selected by a user for the rendering action from at least one of the candidate components;

generating the rendering event based on at least one rendering action and a component corresponding to the rendering action to obtain at least one rendering event.

12. A component-linkage rendering device, comprising:

the component grouping unit is used for grouping the components according to the rendering event to obtain at least one group of components if the components are multiple;

13. The apparatus of claim 12, wherein the component acquisition unit comprises:

the information monitoring module is used for monitoring at least one event broadcast message; the event broadcast information includes at least one component associated with the same rendering event and event information for the rendering event;

and the component reading module is used for respectively reading at least one component from at least one piece of event broadcast information to obtain at least one component to be rendered.

14. The apparatus of claim 13, further comprising:

15. The apparatus of claim 13, further comprising:

and the information conversion unit is used for converting the original event information corresponding to the rendering event into the event broadcasting information corresponding to the rendering event according to a broadcasting event format.

16. The apparatus of claim 14, further comprising:

and the association logout unit is used for logging out the association relationship between the rendering event and at least one component belonging to the rendering event if the rendering event is determined to be finished.

17. The apparatus according to any one of claims 12-16, wherein the event execution unit comprises:

the target determination module is used for determining the current target rendering event to be rendered from at least one rendering event according to the configured rendering sequence;

and the event execution module is used for executing the target rendering events, returning to the step of determining the target rendering event to be rendered currently from at least one rendering event according to the configured rendering sequence when the rendering of the target rendering events is finished, and executing the step until the execution of the last rendering event is finished.

18. The apparatus of claim 17, wherein the event execution module comprises:

19. The apparatus of claim 18, wherein the action acquisition submodule is specifically configured to:

20. The apparatus according to claim 18 or 19, wherein the node executes a submodule, in particular for:

21. The apparatus of any of claims 12-20, further comprising:

22. The apparatus of claim 21, wherein the generating at least one rendering event according to at least one rendering event setting request comprises:

23. An electronic device, comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-11.

24. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-11.

25. A computer program product comprising a computer program which, when executed by a processor, carries out the steps of the method of any one of claims 1 to 11.