CN115904763B - Event driving method and system applied to live broadcast system and live broadcast system - Google Patents
Event driving method and system applied to live broadcast system and live broadcast system Download PDFInfo
- Publication number
- CN115904763B CN115904763B CN202310046306.XA CN202310046306A CN115904763B CN 115904763 B CN115904763 B CN 115904763B CN 202310046306 A CN202310046306 A CN 202310046306A CN 115904763 B CN115904763 B CN 115904763B
- Authority
- CN
- China
- Prior art keywords
- event
- component
- task
- queue
- live broadcast
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Abstract
The application discloses an event driving method applied to a live broadcast system, a system thereof and a live broadcast system. The live broadcast system comprises a live broadcast end and at least two watching ends with different webpage types. The event driven method comprises the following steps: registering a task component of the live broadcast end in the event-driven system to obtain a unique registration number of the task component in the event-driven system; performing task component processing on the task component based on the unique registration number; forming an event queue according to the event of the processed task component; carrying out queue processing on the events in the event queue; and distributing the event execution event processed by the queue so as to execute event actions corresponding to the event on at least two viewing ends with different webpage types.
Description
Technical Field
The application relates to the technical field of live broadcasting, in particular to an event driving method applied to a live broadcasting system, a system thereof and a live broadcasting system.
Background
In web page application of a business system, a component is a basis for ensuring normal operation of a web page. Components are parts that make up the page content, while components are simple packages of data and methods, with the components possessing their own properties and methods.
The components can be driven by the event to drive the corresponding components to execute the corresponding method or action of the event. For example, the event may be some interactive instruction that a user has occurred in a web page, such as a click event of a certain element, a movement event of a mouse, or a closing event of a popup window, etc. Driven by these events, the component can complete corresponding actions on the display side of the web page.
Disclosure of Invention
According to one aspect of the present application, an event driven method for use in a live broadcast system is provided. The live broadcast system comprises a live broadcast end and at least two watching ends with different webpage types. The event driven method comprises the following steps: registering a task component of the live broadcast end in the event-driven system to obtain a unique registration number of the task component in the event-driven system; performing task component processing on the task component based on the unique registration number; forming an event queue according to the event of the processed task component; carrying out queue processing on the events in the event queue; and distributing the event execution event processed by the queue so as to execute event actions corresponding to the event on at least two viewing ends with different webpage types.
According to some embodiments of the present application, task component processing includes at least component service verification, component service setup, component service acquisition, and component service deletion.
According to some embodiments of the present application, the queue processing includes at least: event task registration, event task addition, event task transmission, event task initiation and event task execution.
According to some embodiments of the present application, performing event dispatch of a queued event includes: performing callback function configuration based on the unique registration number, wherein the callback function corresponds to the architecture of the task component of the viewing end; analyzing the event processed by the queue according to the callback function so as to distribute the method corresponding to the event to at least two viewing ends with different webpage types.
According to one aspect of the present application, an event driven system for use in a live broadcast system is provided. The event driven system comprises a component registration unit, a component management unit, an event queue management unit and an event dispatch management unit. The component registration unit registers the task component of the live broadcast end to obtain a unique registration number of the task component; the component management unit processes task components based on the unique registration number; the event queue management unit forms an event queue according to the event of the processed task component and performs queue processing on the event queue; the event dispatch management unit dispatches the event execution event processed by the queue to display event actions corresponding to the event on at least two viewing ends with different webpage types.
According to some embodiments of the present application, task component processing includes at least component service verification, component service setup, component service acquisition, and component service deletion.
According to some embodiments of the present application, the queue processing includes at least: event task registration, event task addition, event task transmission, event task initiation and event task execution.
According to some embodiments of the application, the event dispatch management unit performs callback function configuration based on the unique registration number, and the callback function corresponds to the architecture of the task component of the viewing end; and the event dispatch management unit analyzes the event processed by the queue according to the callback function so as to dispatch the method corresponding to the event to at least two viewing ends with different webpage types.
According to yet another aspect of the present application, the present application further provides a live broadcast system. The live system comprises an event driven system as described above.
According to yet another aspect of the present application, there is also provided a non-transitory computer readable storage medium. The storage medium has stored thereon a computer program which may implement the event driven method as described above.
According to yet another aspect of the present application, an electronic device is also provided. The electronic device comprises one or more processors and storage means for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the event driven method as described above.
The event-driven method provided by the application can flexibly organize and call the component interaction between the live broadcast end and the watching end in the live broadcast system. And in the component interaction, the task component can only pay attention to the API or the function provided by the task component and is not subjected to the interactive coupling of other components, so that the task component has expansibility, and the product interaction under the complex environment is solved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 illustrates a schematic diagram of a prior art component nesting relationship;
FIG. 2 shows a flow diagram of an event driven method of an example embodiment of the present application;
FIG. 3 shows a schematic diagram of different web page types according to an example embodiment of the present application;
FIG. 4 illustrates a task component schematic diagram of an example embodiment of the present application;
FIG. 5 illustrates a schematic diagram of a callback function of an example embodiment of the present application;
FIG. 6 shows a schematic diagram of an event driven system according to an example embodiment of the present application.
Reference numerals illustrate:
an event driven system 1; a component registration unit 10; a component management unit 20; an event queue management unit 30; the event dispatch management unit 40.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments can be embodied in many forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted.
The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the disclosed aspects may be practiced without one or more of the specific details, or with other methods, components, materials, apparatus, etc. In these instances, well-known structures, methods, devices, implementations, materials, or operations are not shown or described in detail.
Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.
The terms first, second and the like in the description and in the claims of the present application and in the above-described figures, are used for distinguishing between different objects and not for describing a particular sequential order.
The following description of the embodiments of the present application, taken in conjunction with the accompanying drawings, will clearly and fully describe the technical aspects of the present application, and it will be apparent that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
The web page interaction method of the current service system generally comprises component initiated event dispatch, component nesting, data information transmission, component event processing and component interaction completion. Each link in the system can influence the interaction effect of complex components, especially important links such as component nesting, data information transmission, event dispatch and the like.
The current component nesting relationship is mostly dependent on parent-child level calling relationship. FIG. 1 shows a schematic diagram of a prior art component nesting relationship, as shown in FIG. 1, between component A and component is a parent-child calling relationship. The component A at the upper parent level calls the upper parent level method to transmit data, and the component A performs corresponding logic processing according to the transmitted data; or the component A at the upper parent level calls the component B, and the component B performs corresponding interaction processing according to the transmission data.
However, the inventor of the application finds that such a component nesting relationship is too dependent on a parent-child level calling relationship, and is easily limited by inflexibility of application in some complex interaction scenes, so that the coupling of service systems is caused.
Taking a live broadcast system as an example, the live broadcast system comprises a live broadcast end and a viewing end, and the viewing end adopted by a spectator can be different types of service webpages according to the limitation of the actual use situation. For example, the viewing end of the first audience member may be a SAAS webpage, and the viewing end of the second audience member is a notification webpage.
Therefore, under the different page layout and structure frameworks of the SAAS webpage and the notification webpage, the same component at the live broadcast end is limited by different product structures of the SAAS webpage and the notification webpage in component interaction, so that the components have different interactions under different scenes, the interaction rule between the components is limited in a certain product structure, and the component nesting relationship depending on the parent-child calling relationship is not fully applicable under the scene.
Based on the above, an aspect of the present application provides an event-driven method applied to a live broadcast system, where the event-driven method can flexibly organize and invoke component interaction between a live broadcast end and a viewing end in the live broadcast system, so as to reduce the coupling of the component interaction, thereby solving product interaction in a complex environment.
The technical scheme of the application will be described in detail below with reference to the accompanying drawings.
Fig. 2 shows a flow diagram of an event driven method of an example embodiment of the present application. As shown in FIG. 2, the event driven method includes steps S100-S500. According to an example embodiment, the event driven method is performed by an event driven system.
According to an example embodiment, the event driven system may be a MiddleEventSdk, a front-end SDK for performing event control, management, and scheduling execution of events. The MiddleEventSdk is internally integrated with the service contents such as EventQueue, dispetcher, serverPool and the like.
According to an example embodiment, a live broadcast system in an example embodiment of the present application includes a live broadcast end and at least two viewing ends having different web page types. For example, a live end initiates a live broadcast and displays live content at least two viewing ends having different web page types.
FIG. 3 shows a schematic diagram of different web page types according to an example embodiment of the present application. As shown in fig. 3, at least two viewing ends with different web page types may be the SAAS web page and the guest web page, and the SAAS web page and the guest web page have different product layout and structure frameworks, such as the SAAS web page and the guest web page have different layout configurations, component arrangements (1, 2, 3, 4 as shown in fig. 3), and interaction arrangements. The first audience obtains live content from the SAAS web page and the second audience obtains live content from the guest web page, but the application is not limited thereto.
In step S100, the event-driven system registers the task component at the live end in the event-driven system to obtain a unique registration number of the task component in the event-driven system;
for example, after service initialization of a service system (such as a live broadcast system), all relevant service components (such as service components at the live broadcast end) are registered in the event-driven system, so that unique registration numbers of the service components can be obtained by marking.
FIG. 4 illustrates a task component schematic diagram of an example embodiment of the present application. As shown in fig. 4, the task components of a service system include a component a and a component B, where 4 method attributes are configured in the component a: amplifying F (1); shrinking F (2); suspending F (3); play F4), 4 method attributes are configured in component B: displaying F (1); hiding F (2); full screen F (3); f (4) is reduced.
And the component A and the component B register an API in the event driven system to obtain registration numbers of the component A and the component B. It is understood herein that the unique registration number may also be understood as the service resolution Key of the service component.
In step S200, the event driven system performs task component processing on the task component based on the unique registration number.
Optionally, the task component process includes at least component service verification, component service setup, component service acquisition, and component service deletion.
And processing the task components of the task group based on the registration number, so that the event-driven system can orderly and effectively manage the task components.
In step S300, the event driven system forms an event queue from the events of the processed task components.
According to an example embodiment, the task component forms event instructions from the live side into an event queue. For example, the event command may be a click event of a certain element, a movement event of a mouse, a closing event of a pop-up window, an enlargement/reduction/closing/displaying/hiding event of a document or page, etc., which is not limited in this application.
In step S400, the event-driven system performs queue processing on events in the event queue.
Optionally, the event-driven system performing queue processing on the events in the event queue at least includes: event task registration, event task addition, event task transmission, event task initiation and event task execution.
For example, the event driven system manages the event queue, thereby undertaking management of multiple tasks of the event queue in the component interaction, and enabling all events to interact with the component according to the first-in first-out execution strategy, so that events among the tasks in the process of the component interaction can be orderly invoked.
In step S500, the event-driven system performs event dispatch on the events processed by the queue, so as to display event actions corresponding to the events on at least two viewing ends with different web page types.
For example, when the event processed by the complete event queue is sequentially dispatched, the event-driven system executes the method corresponding to the component, and finally executes the event action corresponding to the event at least two viewing ends with different webpage types.
Optionally, the event-driven system performs event dispatch on the event processed by the queue, wherein the event-driven system performs callback function configuration based on the unique registration number, and the callback function corresponds to the architecture of the task component of the viewing end.
FIG. 5 illustrates a schematic diagram of a callback function of an example embodiment of the present application. As shown in fig. 5, a configuration callback function (or understood as an interactive orchestration configuration) corresponding to the registration number of a component.
According to an example embodiment, the event driven system parses the event processed through the queue according to a callback function to dispatch a method corresponding to the event to at least two viewing ends having different web page types.
Fig. 5 shows callback function configuration logic of the component a and the component B, where the event driven system performs message parsing processing through the callback function, performs a method corresponding to the parsed task (such as F (1) -F (4) of the component a or the component B shown in fig. 4), and drives a next event in the event queue after the completion of the execution, so as to ensure event ordered call between tasks in the process of component interaction.
According to the technical scheme, a task component of a live broadcast end is registered in an event driving system to obtain a unique registration number of the task component in the event driving system, task component processing is carried out on the task component based on the unique registration number, an event queue is formed according to the event of the processed task component, the event in the event queue is subjected to queue processing, and event execution events processed by the queue are distributed to execute event actions corresponding to the event at least two watching ends with different webpage types.
Through the above example embodiments, the event driven method provided by the present application may flexibly organize and invoke component interactions between a live side and a viewing side in a live system. And in the component interaction, the task component can only pay attention to the API or the function provided by the task component and is not subjected to the interactive coupling of other components, so that the task component has expansibility, and the product interaction under the complex environment is solved.
Another aspect of the present application provides an event driven system applied to a live broadcast system, where the event driven system can flexibly organize and invoke component interactions between a live broadcast end and a viewing end in the live broadcast system, and reduce the coupling of the component interactions, thereby solving product interactions in a complex environment.
FIG. 6 shows a schematic diagram of an event driven system according to an example embodiment of the present application. As shown in fig. 6, the event driven system 1 includes a component registration unit 10, a component management unit 20, an event queue management unit 30, and an event dispatch management unit 40.
For example, the event driven system may be a MiddleEventSdk, a front-end SDK for event control, management, and scheduling execution of events. The MiddleEventSdk is internally integrated with the service contents such as EventQueue, dispetcher, serverPool and the like.
According to an example embodiment, a live broadcast system in an example embodiment of the present application includes a live broadcast end and at least two viewing ends having different web page types.
For example, a live end initiates a live broadcast and displays live content at least two viewing ends having different web page types. The at least two viewing ends with different web page types may be SAAS web pages and guest web pages, and the SAAS web pages and the guest web pages have different product layouts and structure frameworks, such as SAAS web pages and guest web pages having different layout configurations, component arrangements, and interaction arrangements. The first audience obtains live content from the SAAS web page and the second audience obtains live content from the guest web page, but the application is not limited thereto.
According to an exemplary embodiment, the component registration unit 10 registers the task component of the live side to obtain a unique registration number of the task component.
After the service of the service system (such as a live broadcast system) is initialized, all relevant service components (such as service components at the live broadcast end) are registered in the event driven system 1, so that the unique registration numbers of the service components can be obtained by marking.
For example, the task components of a business system include component a and component B, where component a is configured with 4 method attributes: amplifying F (1); shrinking F (2); suspending F (3); play F4), 4 method attributes are configured in component B: displaying F (1); hiding F (2); full screen F (3); f (4) is reduced.
And the component A and the component B register an API in the event driven system to obtain registration numbers of the component A and the component B. It is understood herein that the unique registration number may also be understood as the service resolution Key of the service component.
According to an example embodiment, the component management unit 20 performs task component processing based on the unique registration number.
Optionally, the task component process includes at least component service verification, component service setup, component service acquisition, and component service deletion.
The task component processing is performed on the task group based on the registration number, so that the event driven system 1 can orderly complete effective management of task components.
According to an example embodiment, the event queue management unit 30 forms an event queue according to the event of the processed task component and performs queue processing on the event queue.
According to an example embodiment, the task component forms event instructions from the live side into an event queue. For example, the event command may be a click event of a certain element, a movement event of a mouse, a closing event of a pop-up window, an enlargement/reduction/closing/displaying/hiding event of a document or page, etc., which is not limited in this application.
Optionally, the event-driven system performing queue processing on the events in the event queue at least includes: event task registration, event task addition, event task transmission, event task initiation and event task execution.
For example, the event driven system manages the event queue, thereby undertaking management of multiple tasks of the event queue in the component interaction, and enabling all events to interact with the component according to the first-in first-out execution strategy, so that events among the tasks in the process of the component interaction can be orderly invoked.
According to an example embodiment, the event dispatch management unit 40 performs event dispatch of the event processed through the queue to display event actions corresponding to the event on at least two viewing ends having different web page types.
For example, when the event for which the event queue is completed is sequentially dispatched, the event dispatch management unit 40 executes the method corresponding to the component, and finally executes the event action corresponding to the event on at least two viewing ends with different web page types.
Optionally, the event dispatch management unit 40 dispatches the event execution event processed by the queue, including performing callback function configuration based on the unique registration number, where the callback function corresponds to the architecture of the task component of the viewing end.
The event dispatch management unit 40 parses the event processed through the queue according to the callback function to dispatch the method corresponding to the event to at least two viewing ends having different web page types.
The event dispatch management unit 40 performs message parsing processing through the callback function, executes the method corresponding to the parsed tasks (F (1) -F (4) of the component a or the component B as described above), and drives the next event in the event queue after the completion of the execution, thereby ensuring the orderly calling of the events between the tasks in the process of component interaction.
Through the above example embodiments, the event driven method provided by the present application may flexibly organize and invoke component interactions between a live side and a viewing side in a live system. And in the component interaction, the task component can only pay attention to the API or the function provided by the task component and is not subjected to the interactive coupling of other components, so that the task component has expansibility, and the product interaction under the complex environment is solved.
According to yet another aspect of the present application, the present application further provides a live broadcast system. The live system comprises an event driven system as described above.
According to yet another aspect of the present application, there is also provided a non-transitory computer readable storage medium. The storage medium has stored thereon a computer program which may implement the event driven method as described above.
According to yet another aspect of the present application, an electronic device is also provided. The electronic device comprises one or more processors and storage means for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the event driven method as described above.
Finally, it should be noted that the foregoing description is only a preferred embodiment of the present application, and is not intended to limit the present application, but the detailed description of the present application will be given with reference to the foregoing embodiment, and it is possible for those skilled in the art to make modifications to the technical solutions of the foregoing embodiments, or to make equivalent substitutions for some technical features thereof. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application.
Claims (9)
1. An event driven method applied to a live broadcast system, wherein the live broadcast system comprises a live broadcast end and at least two viewing ends with different webpage types, the event driven method comprising:
registering the task component of the live broadcast end in an event-driven system to obtain a unique registration number of the task component in the event-driven system;
performing task component processing on the task component based on the unique registration number;
forming an event queue according to the event of the processed task component;
performing queue processing on the events in the event queue;
distributing the event execution event processed by the queue so as to display event actions corresponding to the event on the at least two viewing ends with different webpage types;
the event execution event dispatch to be processed by the queue includes:
performing callback function configuration based on the unique registration number, wherein the callback function corresponds to the architecture of the task component of the viewing end;
and analyzing the event processed by the queue according to the callback function so as to dispatch the method corresponding to the event to the at least two viewing ends with different webpage types.
2. The event driven method of claim 1, wherein the task component processing comprises at least component service verification, component service setup, component service acquisition, and component service deletion.
3. The event driven method of claim 1, wherein the queue processing comprises at least: event task registration, event task addition, event task transmission, event task initiation and event task execution.
4. An event driven system for a live broadcast system, the live broadcast system including a live broadcast end and at least two viewing ends having different web page types, the event driven system comprising:
the component registration unit registers the task component of the live broadcast end to obtain a unique registration number of the task component;
the component management unit is used for processing task components based on the unique registration number;
an event queue management unit, which forms an event queue according to the event of the processed task component and processes the event queue;
the event dispatch management unit dispatches the event execution event processed by the queue so as to display event actions corresponding to the event on the at least two viewing ends with different webpage types;
the event dispatch management unit carries out callback function configuration based on the unique registration number, and the callback function corresponds to the architecture of the task component of the viewing end;
and the event dispatch management unit analyzes the event processed by the queue according to the callback function so as to dispatch the method corresponding to the event to the at least two viewing ends with different webpage types.
5. The event driven system of claim 4, wherein the task component process comprises at least component service verification, component service setup, component service acquisition, and component service deletion.
6. The event driven system of claim 4, wherein the queue processing comprises at least: event task registration, event task addition, event task transmission, event task initiation and event task execution.
7. A live broadcast system comprising an event driven system as claimed in any of claims 4-6.
8. A non-transitory computer readable storage medium having stored thereon a computer program, wherein the computer program implements the event driven method of any of claims 1-3.
9. An electronic device, comprising:
one or more processors;
a storage means for storing one or more programs;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the event driven method of any of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310046306.XA CN115904763B (en) | 2023-01-31 | 2023-01-31 | Event driving method and system applied to live broadcast system and live broadcast system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310046306.XA CN115904763B (en) | 2023-01-31 | 2023-01-31 | Event driving method and system applied to live broadcast system and live broadcast system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115904763A CN115904763A (en) | 2023-04-04 |
| CN115904763B true CN115904763B (en) | 2023-05-30 |
Family
ID=85735493
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310046306.XA Active CN115904763B (en) | 2023-01-31 | 2023-01-31 | Event driving method and system applied to live broadcast system and live broadcast system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115904763B (en) |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107015851A (en) * | 2016-01-28 | 2017-08-04 | 阿里巴巴集团控股有限公司 | A kind of serviced component management method and system |
| US20180260819A1 (en) * | 2017-03-09 | 2018-09-13 | Capital One Services, Llc | Systems and methods for real time message processing using an event driven framework |
| CN107632885A (en) * | 2017-09-26 | 2018-01-26 | 郑州云海信息技术有限公司 | The readjustment management method and device of inter-module |
| CN109976923B (en) * | 2019-03-12 | 2020-12-18 | 深圳点猫科技有限公司 | Component communication implementation method and device based on WeChat applet |
| CN111475140B (en) * | 2020-03-20 | 2023-09-22 | 湖南快乐阳光互动娱乐传媒有限公司 | App componentization method based on event-driven architecture and event-driven architecture |
| CN114675982A (en) * | 2020-12-25 | 2022-06-28 | 北京国双科技有限公司 | General method and system for acquiring data of service integration system |
-
2023
- 2023-01-31 CN CN202310046306.XA patent/CN115904763B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN115904763A (en) | 2023-04-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104246659B (en) | The gesture object that can be instantiated | |
| US7716278B2 (en) | Context and action-based application design | |
| CN101364236B (en) | Data processing apparatus and processing method of WEB page | |
| US9298429B2 (en) | System and method for extending legacy applications with undo/redo functionality | |
| US8132119B2 (en) | Priority controlled display | |
| CN110209967B (en) | Page loading method and device, terminal equipment and computer readable medium | |
| CN110634171B (en) | Device and method for drawing map | |
| CN108121738A (en) | media content display method and device | |
| EP3404509A1 (en) | Slider and history field for smart chat sessions | |
| CN102591657B (en) | Graphical user interface (GUI) system achieving method based on collaboration mechanism of central processing unit (CPU) and digital signal processor (DSP) | |
| CN101427216A (en) | Enhancing software application features and content objects | |
| JP5162459B2 (en) | Script markup | |
| CN106469073A (en) | The method and apparatus of display application program splashette image | |
| CN109766196A (en) | A kind of method for scheduling task, device and equipment | |
| CN106843794B (en) | Split screen display method and system based on android | |
| CN109885301B (en) | Method, device, storage medium and equipment for generating scalable vector graphics | |
| CN110020329A (en) | For generating the methods, devices and systems of webpage | |
| WO2023077951A1 (en) | Data rendering method and apparatus | |
| CN109144650B (en) | Display object management method and device, electronic equipment and computer storage medium | |
| CN111813308B (en) | Interface processing method and device, electronic equipment and storage medium | |
| CN111008047B (en) | Page element conflict processing method and device and electronic equipment | |
| CN115904763B (en) | Event driving method and system applied to live broadcast system and live broadcast system | |
| CN103049430A (en) | Page display method based on IDF (interactive document format) files | |
| CN117555534A (en) | Configuration method and device for linkage interaction of visual components and computer equipment | |
| CN115562777A (en) | Target activity display method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |