A method of running a page function, a running system, and a storage medium

Abstract

The embodiment of the application discloses a page function running method, a running system and a device thereof, and is used in the technical field of page function. The embodiment of the application comprises the following steps: obtaining a target page function event meeting a preset running time length condition from at least one page function event stored in an event queue, wherein the target page function event corresponds to a post-extension event; running the target page function event in an asynchronous mode in the background and displaying a running progress of the target page function event; executing the post-extension event corresponding to the target page function event when the running progress meets a running end condition, so as to complete a page function corresponding to the target page function event. By running the target page function event meeting the preset running time length condition in the asynchronous mode in the background and displaying the running progress of the target page function event, it can be determined by a user whether a page function with a long time consumption is completed.

Description

Technical Field

[0001] This application relates to the field of page function technology, and in particular to a method, system and apparatus for operating page functions. Background Technology

[0002] The Web (World Wide Web), also known as the World Wide Web, is a global, dynamic, interactive, cross-platform distributed graphical information system based on hypertext and HTTP. It is a network service built on the Internet, providing users with a graphical, easily accessible, and intuitive interface for searching and browsing information. Its documents and hyperlinks organize information nodes on the Internet into an interconnected network structure.

[0003] However, when users execute page functions by clicking on web pages, if the execution of page functions takes a long time, such as time-consuming request functions (e.g., exporting multiple data to Excel), users may find it difficult to determine whether the time-consuming request function has been completed, which may lead to users clicking repeatedly and executing the time-consuming request function repeatedly. Summary of the Invention

[0004] This application provides a method, system, and apparatus for running page functions, enabling users to intuitively determine whether time-consuming page functions have been completed.

[0005] The first aspect of this application provides a method for operating page functions, including:

[0006] From at least one page function event stored in the event queue, obtain a target page function event that meets a preset runtime condition, wherein the target page function event corresponds to a subsequent extension event;

[0007] Run the target page function events asynchronously in the background and display the running progress of the target page function events;

[0008] When the running progress meets the running end condition, the post-extended event corresponding to the target page function event is executed to complete the page function corresponding to the target page function event.

[0009] Optionally, obtaining the target page function event that meets the preset runtime condition includes:

[0010] The runtime of each page function event in the event queue is determined according to the preset timing rules.

[0011] Obtain the target page function event when the runtime reaches the preset runtime.

[0012] Optionally, after obtaining the target page function event that meets the preset runtime condition, the method further includes:

[0013] Configure a time consumption flag for the target page function event so that the target page function event can be run asynchronously in the background according to the time consumption flag.

[0014] Optionally, the event of running the target page function asynchronously in the background includes:

[0015] Determine the preceding extended event corresponding to the target page function event in the event queue;

[0016] After the preceding extension event has finished running, the target page function event will run asynchronously in the background.

[0017] Optionally, displaying the running progress of the target page function events includes:

[0018] When the target page function event starts running, a floating progress control is created;

[0019] The floating progress control displays the running progress of the target page's functional events.

[0020] Optionally, displaying the running progress of the target page function event through the floating progress control includes:

[0021] When the target page function event is completed, control the floating progress control to display a prompt that the target page function event has been completed;

[0022] When the target page function event stops running, the floating progress control is used to clear the running progress of the target page function event to zero.

[0023] Optionally, the step of executing the follow-up extended event corresponding to the target page function event when the running progress meets the running end condition includes:

[0024] The running progress is used to callback the running result to the insertion point of the target page function event in the event queue;

[0025] If the execution result is successful, the post-expansion event corresponding to the insertion point is executed.

[0026] The method described in the first aspect of this application may be implemented using the content described in the second aspect of this application.

[0027] A second aspect of this application provides a system for operating page functions, including:

[0028] The acquisition unit is used to acquire a target page function event that meets a preset runtime condition from at least one page function event stored in the event queue, wherein the target page function event corresponds to a subsequent extension event.

[0029] The execution unit is used to run the target page function events asynchronously in the background;

[0030] The display unit is used to display the running progress of the target page function events;

[0031] An execution unit is used to execute the post-extended event corresponding to the target page function event when the running progress meets the running end condition, so as to complete the page function corresponding to the target page function event.

[0032] A third aspect of this application provides an electronic device, including:

[0033] Central processing unit, memory, and input / output interfaces;

[0034] The memory is either a short-term storage memory or a persistent storage memory;

[0035] The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method described in the first aspect of the embodiments of this application or any specific implementation thereof.

[0036] A fourth aspect of this application provides a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the method described in the first aspect of this application or any specific implementation thereof.

[0037] The fifth aspect of this application provides a computer program product comprising instructions or a computer program, which, when run on a computer, causes the computer to perform the method described in the first aspect of this application or any specific implementation thereof.

[0038] As can be seen from the above technical solutions, the embodiments of this application have the following advantages:

[0039] The method in this application includes: obtaining a target page function event that meets a preset runtime condition from at least one page function event stored in an event queue, wherein the target page function event corresponds to a subsequent extension event; running the target page function event asynchronously in the background and displaying the running progress of the target page function event; and executing the subsequent extension event corresponding to the target page function event when the running progress meets the running end condition to complete the page function corresponding to the target page function event. By running the target page function event that meets the preset runtime condition asynchronously in the background and displaying the running progress of the target page function event, users can intuitively determine whether a page function that takes a long time to complete has finished. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0041] Figure 1 This is a schematic diagram of an application scenario disclosed in an embodiment of this application;

[0042] Figure 2 This is a schematic diagram illustrating the operation flow of a page function disclosed in an embodiment of this application;

[0043] Figure 3 This is a schematic diagram illustrating the operation flow of another page function disclosed in an embodiment of this application;

[0044] Figure 4 This is a schematic diagram of the operating system of a page function disclosed in an embodiment of this application;

[0045] Figure 5 This is a schematic diagram of the structure of an electronic device disclosed in an embodiment of this application. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0047] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0048] In the following description, expressions such as "one specific implementation" or "one specific example" are used, which describe a subset of all possible embodiments. However, it is understood that "one specific implementation" or "one specific example" can be the same subset or a different subset of all possible embodiments, and can be combined with each other without conflict. In the following description, the term "plural" means at least two. The statement that a certain value reaches a threshold (if it exists) as used in this application may, in some specific examples, include cases where the former is greater than the latter.

[0049] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0050] To facilitate understanding and explanation, the application scenarios of this application will be briefly described before further detailed description of the embodiments. For example... Figure 1As shown, users can trigger page functions that require front-end execution through the page operating system in the page display device 101. The page display device 101 can communicate with the data execution device 102 to trigger the function execution system in the data execution device 102 to run the page function. The data execution device 102 then feeds back the execution result to the page display device 101. The page display device 101 can be a computer or mobile phone, etc., without specific limitations here. The data execution device 102 can be a backend server or a running host, without specific limitations here. It is understood that the page display device 101 can communicate and connect with one or more data execution devices 102, without specific limitations here. The page display device 101 can run and display a web page. Users can execute page functions by clicking on the web page. However, if the execution of a page function takes a long time, such as exporting multiple data points to an Excel spreadsheet file based on a request, the user may find it difficult to determine whether the time-consuming request function has been completed, easily leading to repeated clicks and repeated execution of the time-consuming request function.

[0051] To at least partially solve the above technical problems, this application provides a method for running page functions, which will be further described in detail below.

[0052] Please see Figure 2 This application provides a specific embodiment of a method for operating page functions, which includes steps 201-204.

[0053] 201. Retrieve target page function events that meet the preset runtime conditions from the event queue.

[0054] In this embodiment, a target page function event that meets a preset runtime condition can be obtained from an event queue. Specifically, a target page function event that meets the preset runtime condition is obtained from at least one page function event stored in the event queue, wherein the target page function event corresponds to a subsequent extended event. It is understood that the page function events in the event queue are arranged in chronological order; generally, the page function event at the head of the queue will be executed first, and the later the page function event, the later it will be executed. The target page function event that meets the preset runtime condition refers to a target page function event whose runtime reaches a preset runtime, such as 2 seconds or 3 seconds, which is not specifically limited here. In running a page function, the feedback of the page function's execution result is generally fast (milliseconds), meaning that the target page function event that meets the preset runtime condition is a long-running page function event.

[0055] 202. Run the target page's function events asynchronously in the background.

[0056] Specifically, after identifying a target page function event that meets the preset runtime condition, when the events in the event queue reach that target page function event in chronological order, the target page function event can be extracted and run asynchronously in the background. That is, the time-consuming page function event is extracted, its operation is changed from synchronous to asynchronous, and the corresponding follow-up events are temporarily suspended. The next page function event in the event queue that corresponds to the time-consuming page function event continues to execute.

[0057] 203. Display the running progress of the target page's function events.

[0058] Specifically, during the asynchronous execution of a target page function event in the background, the progress of that event can be obtained and displayed in real time. This progress can be displayed on the page operating system through various methods, such as a progress window or progress control. Progress controls include, but are not limited to, floating progress controls, and can also be embedded in the page, etc. The specific implementation method is not limited here. Users can intuitively obtain the progress of the target page function event from the page operating system, that is, intuitively obtain the progress of time-consuming page function events.

[0059] It is understandable that steps 202 and 203 above can be executed synchronously, that is, while the target page function event is running asynchronously in the background, the running progress of the target page function event is displayed.

[0060] 204. Execute the follow-up extended events corresponding to the target page function events according to the running progress.

[0061] In this embodiment, the subsequent extended events corresponding to the target page function event are executed according to the running progress to complete the page function corresponding to the target page function event. Specifically, the execution or non-execution of the subsequent extended events corresponding to the target page function event is determined according to the running progress. The running progress may include not started running, running, and running completed. The subsequent extended events corresponding to the target page function event are executed when the running progress meets the running end condition. Generally, the subsequent extended events corresponding to the target page function event are executed only when the running progress of the target page function event is running completed, thus completing the page function corresponding to the target page function event.

[0062] It's understandable that each page function event has a corresponding follow-up event. The page function is considered complete only when both the page function event and its corresponding follow-up event have completed. For example, if the page function is to export an Excel spreadsheet file, the page function event is to generate an Excel spreadsheet file from multiple data points, and the corresponding follow-up event is to display that Excel spreadsheet file.

[0063] In summary, this embodiment of the application obtains a target page function event that meets a preset runtime condition from at least one page function event stored in the event queue, wherein the target page function event corresponds to a subsequent extension event; the target page function event is run asynchronously in the background, and the running progress of the target page function event is displayed; the subsequent extension event corresponding to the target page function event is executed according to the running progress to complete the page function corresponding to the target page function event. By running the target page function event that meets the preset runtime condition asynchronously in the background and displaying the running progress of the target page function event, users can intuitively determine whether a page function with a long running time has been completed.

[0064] Please see Figure 3 Based on the examples above, some specific possible implementation examples will be provided below. In practical applications, the implementation content of these examples can be combined as needed according to the corresponding functional principles and application logic. Figure 3 The illustrated embodiment provides a page function method that specifically includes steps 301-304.

[0065] 301. Obtain target page function events that have reached the preset runtime in the event queue according to the preset timing rules.

[0066] In this embodiment, target page function events that have reached a preset runtime in the event queue can be obtained according to preset timing rules. Specifically, the runtime of each page function event in the event queue is determined according to the preset timing rules; and target page function events whose runtimes have reached the preset runtime are obtained. The determination of the runtime of each page function event in the event queue according to the preset timing rules can be achieved by obtaining the runtime of the page function event through a background database query operation or by manually configuring the runtime of the page function event; the specific method is not limited here.

[0067] 302. After the current extended event has finished running, the target page function event will run asynchronously in the background.

[0068] In this embodiment, after determining the target page function event, a time-consuming flag can be configured for the target page function event to run asynchronously in the background according to the time-consuming flag. The time-consuming flag can be an event name or a method name, and is not specifically limited here. The time-consuming flag can be manually configured at the framework level for the target page function event, or it can be enabled in the designer. It is understood that configuring the time-consuming flag for the target page function event allows it to be extracted separately from the event queue, and the synchronous operation of the subsequent extended event can be changed to an asynchronous operation, i.e., encapsulated into success and failure callback methods. Whether to run in the background and the corresponding callback methods can be configured separately for page-level functions. After the target page function event completes execution in the background, the corresponding subsequent extended event is completed through event triggering or method callback.

[0069] When a page function event is triggered in the event queue, the general execution order is as follows: execute the preceding extended events of the page function event, execute the page function event itself, and execute the following extended events of the page function event. The page function event is generally executed after the corresponding preceding extended events have finished; that is, the background asynchronous callback processing of the page function event usually occurs after the preceding extended events have completed. Specifically, the preceding extended events corresponding to the target page function event in the event queue can be determined; after the preceding extended events have finished running, the target page function event is run asynchronously in the background.

[0070] 303. Display the running progress of the target page's functional events using a floating progress control.

[0071] In this embodiment, a floating progress control can be used to display the running progress of a target page function event. The floating progress control is created when the target page function event begins running; this floating progress control can be a floating progress ball control or a floating progress bar control, and is not specifically limited here. The floating progress control can obtain and update the running progress of the target page function event in real time, and display the running progress of the target page function event through the floating progress control.

[0072] Understandably, during the process of the floating progress control displaying the running progress of the target page function event, when the target page function event is completed, the floating progress control displays a prompt indicating that the target page function event has been completed; when the target page function event stops running, the floating progress control clears the running progress of the target page function event to zero.

[0073] 304. Execute the follow-up extended events corresponding to the target page function events based on the running results corresponding to the running progress.

[0074] Based on the execution result corresponding to the execution progress, the subsequent extended events corresponding to the target page function event are executed. Specifically, the execution result can be callbacked to the insertion point of the target page function event in the event queue based on the execution progress; this insertion point is generally the position of the target page function event in the event queue in chronological order. If the execution result is successful, the subsequent extended event corresponding to the insertion point is executed; if the execution result is a failure, a failure message can be displayed on the floating progress control. That is, the initialization of the progress control and the callback of the progress acquisition method can be performed at the insertion point of the page function event. When the page function event is a time-consuming request function (target page function event), a floating progress control is created when the time-consuming request function starts. The floating progress control periodically acquires the corresponding progress and updates it in real time. When the request is completed, the subsequent corresponding operations (subsequent extended events) are triggered. When the request is aborted, the corresponding processing is triggered and the corresponding floating progress control is cleared.

[0075] As can be seen, in this embodiment, by combining the web event bus mechanism to uniformly process page functions in the background, it achieves asynchronous processing of time-consuming functions such as exporting Excel using a floating progress bar, displaying the progress asynchronously. When the request is completed, the corresponding subsequent methods are called back, improving the user's intuitive experience and avoiding repeated execution of page functions. Furthermore, existing technologies add progress details processing separately to time-consuming page function events, resulting in high code coupling. In contrast, this embodiment allows for background execution of specific time-consuming operations at the page level through page function configuration, optimizing the experience of time-consuming operations. Progress is uniformly processed and displayed through preset method callbacks. In addition, this embodiment allows for individual configuration of page-level functions, providing fine-grained control; optimizes the experience of time-consuming operations, allowing for intuitive viewing of processing progress; and reduces code coupling by uniformly processing and displaying progress through preset method callbacks.

[0076] Please see Figure 4 The second aspect of this application provides a specific example of a system for operating page functionality, the system comprising:

[0077] The acquisition unit 401 is used to acquire a target page function event that meets a preset runtime condition from at least one page function event stored in the event queue, wherein the target page function event corresponds to a subsequent extension event.

[0078] The execution unit 402 is used to run the target page function events asynchronously in the background;

[0079] Display unit 403 is used to display the running progress of the target page function events;

[0080] The execution unit 404 is used to execute the post-extended events corresponding to the target page function events according to the running progress, so as to complete the page functions corresponding to the target page function events.

[0081] Optionally, the acquisition unit 401 is specifically used to: determine the runtime of each page function event in the event queue according to a preset timing rule; and acquire the target page function event whose runtime has reached the preset runtime.

[0082] Optionally, after obtaining the target page function event that meets the preset runtime condition, the system further includes: a configuration unit, configured to configure a time consumption identifier for the target page function event, so as to run the target page function event asynchronously in the background according to the time consumption identifier.

[0083] Optionally, the running unit 402 is specifically used to determine the preceding extended event corresponding to the target page function event in the event queue; after the preceding extended event has finished running, the target page function event is run in the background in an asynchronous manner.

[0084] Optionally, the display unit 403 is used to create a floating progress control when the target page function event starts running; and to display the running progress of the target page function event through the floating progress control.

[0085] Optionally, the display unit 403 is specifically used to: when the target page function event is completed, control the floating progress control to display a prompt that the target page function event is completed; when the target page function event is stopped, control the floating progress control to clear the running progress of the target page function event to zero.

[0086] Optionally, the execution unit 404 is specifically used to call back the running result to the insertion point of the target page function event in the event queue according to the running progress; if the running result is successful, execute the post-extended event corresponding to the insertion point.

[0087] Please see Figure 5 The electronic device 500 of this application embodiment may include one or more central processing units (CPUs) 501 and a memory 505, wherein the memory 505 stores one or more applications or data.

[0088] The memory 505 can be volatile or persistent storage. The program stored in the memory 505 can include one or more modules, each module including a series of instruction operations on the electronic device. Furthermore, the central processing unit 501 can be configured to communicate with the memory 505 and execute the series of instruction operations stored in the memory 505 on the electronic device 500.

[0089] Electronic device 500 may also include one or more power supplies 502, one or more wired or wireless network interfaces 503, one or more input / output interfaces 504, and / or one or more operating systems, such as Windows Server™, MacOSX™, Unix™, Linux™, FreeBSD™, etc.

[0090] The central processing unit 501 can perform the operations performed by the first aspect or any specific method embodiment of the first aspect, which will not be described in detail here.

[0091] This application provides a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the method as described in the first aspect or any specific implementation thereof.

[0092] This application provides a computer program product containing instructions or computer programs, which, when run on a computer, causes the computer to perform the method described in the first aspect or any specific implementation thereof.

[0093] It is understood that, in the various embodiments of this application, the sequence number of each step does not imply the order of execution. The execution order of each step should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0094] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working process of the system and device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0095] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system or apparatus, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0096] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0097] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0098] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product (computer program product) is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a business server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A method for operating page functions, characterized in that, include: From at least one page function event stored in the event queue, obtain a target page function event that meets a preset runtime condition, wherein the target page function event is a time-consuming page function event whose runtime reaches the preset runtime condition, and the target page function event corresponds to a subsequent extension event. Run the target page function events asynchronously in the background and display the running progress of the target page function events; When the running progress meets the running end condition, the post-extension event corresponding to the target page function event is executed to complete the page function corresponding to the target page function event.

2. The operating method according to claim 1, characterized in that, The event for obtaining the target page function that meets the preset runtime conditions includes: The runtime of each page function event in the event queue is determined according to the preset timing rules. Obtain the target page function event when the runtime reaches the preset runtime.

3. The operating method according to claim 1, characterized in that, After obtaining the target page function event that meets the preset runtime condition, the method further includes: Configure a time consumption flag for the target page function event so that the target page function event can be run asynchronously in the background according to the time consumption flag.

4. The operating method according to claim 1, characterized in that, The event that runs the target page function asynchronously in the background includes: Determine the preceding extended event corresponding to the target page function event in the event queue; After the preceding extension event has finished running, the target page function event will run asynchronously in the background.

5. The operating method according to claim 1, characterized in that, The progress of the event displaying the target page function includes: When the target page function event starts running, a floating progress control is created; The floating progress control displays the running progress of the target page's functional events.

6. The operating method according to claim 5, characterized in that, The process of displaying the running progress of the target page function event through the floating progress control includes: When the target page function event is completed, control the floating progress control to display a prompt that the target page function event has been completed; When the target page function event stops running, the floating progress control is used to clear the running progress of the target page function event to zero.

7. The operating method according to claim 1, characterized in that, The subsequent extended events corresponding to the event of executing the target page function when the running progress meets the running end condition include: The running progress is used to callback the running result to the insertion point of the target page function event in the event queue; If the execution result is successful, the post-extension event corresponding to the insertion point is executed.

8. A system for operating page functions, characterized in that, include: The acquisition unit is used to acquire a target page function event that meets a preset runtime condition from at least one page function event stored in the event queue, wherein the target page function event is a time-consuming page function event whose runtime reaches the preset runtime condition, and the target page function event corresponds to a subsequent extension event. The execution unit is used to run the target page function events asynchronously in the background; The display unit is used to display the running progress of the target page function events; An execution unit is used to execute the post-extension event corresponding to the target page function event when the running progress meets the running end condition, so as to complete the page function corresponding to the target page function event.

9. An electronic device, characterized in that, include: Central processing unit, memory, and input / output interfaces; The memory is either a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 7.

11. A computer program product having a computer program stored thereon, characterized in that, When the computer program is executed by a computer device, it is used to perform the method according to any one of claims 1 to 7.

Images