Data processing method and device, program product, computer equipment and medium

Abstract

The invention discloses a data processing method and device, a program product, computer equipment and a medium, and the method comprises the steps: when a target application page of a target application program needs to be displayed, obtaining a first component compiling file of an instant display component depending on the target application page, and obtaining a second component compiling file of a placeholder component; the placeholder component is used for carrying out placeholder on the time-of-use display component depending on the target application page; rendering and displaying the target application page based on the first component compiling file and the second component compiling file; the rendered and displayed target application page comprises an instant display component and a placeholder component; and asynchronously acquiring a third component compiling file of the time-used display component, and replacing the occupied component in the rendered and displayed target application page with the time-used display component according to the third component compiling file. By adopting the application, the speed of starting the target application page can be improved.

Description

[0001] This application is a divisional application of Chinese patent application filed with the State Intellectual Property Office on March 1, 2022, application number 2022101965069, entitled "Data Processing Method, Apparatus, Program Product, Computer Equipment and Media", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of computer technology, and in particular to a data processing method, apparatus, program product, computer equipment, and medium. Background Technology

[0003] With the continuous development of computer networks, various applications have emerged. These applications can run on terminal devices, and in the process of running these applications, the relevant application pages will be displayed.

[0004] An application page is often composed of several page components. In existing applications, when application page Y needs to be displayed, the compiled files of all page components that depend on application page Y can be obtained simultaneously, and then the display of application page Y can be achieved through the compiled files of all page components. Using this approach, when the network speed is slow, or when the amount of data in the compiled files of all page components that depend on application page Y is large, it can lead to a long startup time for application page Y, resulting in page lag. Summary of the Invention

[0005] This application provides a data processing method, apparatus, program product, computer equipment, and medium that can reduce the startup time of a target application page, improve the display speed of the target application page, and enhance the smoothness of the target application page display.

[0006] This application provides a data processing method, which includes: When the target application page of the target application needs to be displayed, the first component compilation file of the on-demand display component that depends on the target application page is obtained, and the second component compilation file of the placeholder component is obtained; the placeholder component is used to place the on-demand display component that depends on the target application page. The target application page is rendered and displayed based on the first component compilation file and the second component compilation file; the rendered target application page includes an instant display component and a placeholder component; Asynchronously retrieve the third-party component compilation file of the time-based display component, and replace the placeholder component in the target application page to the time-based display component based on the third-party component compilation file.

[0007] This application provides a data processing apparatus, which includes: The file acquisition module is used to acquire the first component compilation file of the on-demand display component that depends on the target application page when the target application page of the target application needs to be displayed, and to acquire the second component compilation file of the placeholder component; the placeholder component is used to place the on-demand display component that depends on the target application page. The display module is used to render and display the target application page based on the first component compilation file and the second component compilation file; the rendered and displayed target application page includes an instant display component and a placeholder component; The replacement module is used to asynchronously obtain the third-party component compilation file of the component to be displayed when the time comes, and replace the placeholder component in the target application page to be displayed when the time comes based on the third-party component compilation file.

[0008] Optionally, when it is necessary to display the target application page of the target application, the file acquisition module may acquire the first component compilation file of the on-demand display component that depends on the target application page, and the second component compilation file of the placeholder component, in the following ways: When the target application page needs to be displayed, obtain the first component identifier of the component to be displayed immediately, and obtain the second component identifier of the component to be displayed at a later time; The first component compilation file of the instant display component is obtained based on the first component identifier, and the second component compilation file of the placeholder component is obtained based on the second component identifier.

[0009] Optionally, when the target application page needs to be displayed, the file acquisition module obtains the first component identifier of the component to be displayed immediately and the second component identifier of the component to be displayed in a timely manner, including: When it is necessary to display the target application page, retrieve the page configuration file of the target application page; The page configuration file is parsed to obtain a list of full component identifiers consisting of component identifiers of all components that depend on the target application page, and a list of time-based component identifiers consisting of component identifiers of time-based display components that depend on the target application page. The first component identifier is determined based on the full list of component identifiers and the list of time-used component identifiers, and the second component identifier is extracted from the list of time-used component identifiers.

[0010] Optionally, the file acquisition module determines the first component identifier based on the full list of component identifiers and the list of component identifiers used in the specified time, including: Remove the second component identifier contained in the time-used component identifier list from the full component identifier list to obtain the retained component identifier list; The component identifier in the list of retained component identifiers is determined as the second component identifier.

[0011] Optionally, the target application is a subroutine, and the subroutine has a host program; The file acquisition module acquires the first component compilation file of the real-time display components that depend on the target application page in the following ways: The first file fetch request is generated in the subroutine; the first file fetch request carries the first component identifier of the component to be displayed immediately; The host program is invoked to retrieve the first component compilation file associated with the first component identifier from the host program's background device based on the first file retrieval request.

[0012] Optionally, the target application is a subroutine; The file retrieval module retrieves the second component's compiled file from the placeholder component in the following ways: If the placeholder component is a built-in component of the subroutine, then the second component compilation file of the placeholder component is obtained within the subroutine.

[0013] Optionally, the target application is a subroutine; the subroutine has a host program. The file retrieval module retrieves the second component's compiled file from the placeholder component in the following ways: If the placeholder component is a custom component, a second file fetch request is generated in the subroutine; the second file fetch request carries the identifier of the second component to be displayed. The host program is invoked to retrieve the second component compilation file of the placeholder component indicated by the second component identifier from the host program's background device according to the second file retrieval request.

[0014] Optionally, the target application is a subroutine; the subroutine has a host program. Replace the way the module asynchronously retrieves the third-party component compilation file used by the component to display the component, including: Generate a third file fetch request in the subroutine; the third file fetch request carries the identifier of the second component used for display; The host program is invoked to retrieve the compiled file of the third component associated with the second component identifier from the host program's background device based on the third file retrieval request.

[0015] Optionally, the target application is a subroutine, the subroutine has a host program, the subroutine contains multiple application pages, the multiple application pages contain the target application page, the multiple application pages have a component set, the component set contains various components that depend on the multiple application pages, and the background device of the host program compiles the component compilation files corresponding to each component in the component set according to the component unit.

[0016] Optionally, a real-time display component refers to a component that needs to be displayed in real time when the target application page is rendered and displayed, while a time-display component refers to a component that is displayed in the target application page based on the trigger operation on the page control.

[0017] This application provides a computer device, including a memory and a processor. The memory stores a computer program, and when the computer program is executed by the processor, the processor performs the method of this application.

[0018] This application provides a computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed by a processor, cause the processor to perform the method described above.

[0019] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various alternative embodiments described above.

[0020] When this application needs to display the target application page of the target application, it can obtain the first component compilation file of the on-demand display component that depends on the target application page, and obtain the second component compilation file of the placeholder component. The placeholder component is used to place the on-demand display component that depends on the target application page. The target application page is rendered and displayed based on the first and second component compilation files. The rendered and displayed target application page includes the on-demand display component and the placeholder component. The third component compilation file of the on-demand display component is obtained asynchronously, and the placeholder component in the rendered and displayed target application page is replaced with the on-demand display component according to the third component compilation file. Therefore, the method proposed in this application can render and display the on-demand display component and the placeholder component of the on-demand display component of the target application page first when the target application page is rendered and displayed for the first time. After the rendering is completed, the on-demand display component can be rendered and displayed asynchronously in the target application page that was rendered and displayed for the first time, so as to reduce the startup time of the target application page and improve the startup speed of the target application page. Attached Figure Description

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

[0022] Figure 1 This is a schematic diagram of a network architecture provided in this application; Figure 2 This is a schematic diagram of a page display scenario provided in this application; Figure 3 This is a flowchart illustrating a data processing method provided in this application; Figure 4 This is a schematic diagram illustrating a scenario for obtaining a component identifier, as provided in this application. Figures 5-7 This is a page illustration of a target application page provided in this application; Figures 8-9 This is a schematic diagram of a component debugging page provided in this application; Figure 10 This is a schematic diagram of the structure of a data processing device provided in this application; Figure 11 This is a schematic diagram of the structure of a computer device provided in this application. Detailed Implementation

[0023] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0024] This application relates to cloud technology. Cloud technology refers to a managed technology that unifies a series of resources such as hardware, software, and networks within a wide area network or local area network to achieve data computing, storage, processing, and sharing.

[0025] Cloud technology is a collective term for network technology, information technology, integration technology, management platform technology, and application technology applied to the cloud computing business model. It can form resource pools, providing flexible and convenient on-demand access. Cloud computing technology will become a crucial support. Backend services of technical network systems require substantial computing and storage resources, such as video websites, image websites, and many portal websites. With the rapid development and application of the internet industry, every item may have its own identification mark in the future, requiring transmission to backend systems for logical processing. Data at different levels will be processed separately, and various industry data will all require robust system support, which can only be achieved through cloud computing.

[0026] The cloud technology involved in this application can refer to the interaction between the front-end and the back-end through the "cloud" so that the front-end can display the relevant application pages of the application by fetching relevant data from the back-end. The cloud technology involved in this application can also refer to the storage of the relevant compiled files (i.e. component compiled files) of the page components of the application's application pages through the "cloud".

[0027] First, it should be noted that this application may display a prompt interface or pop-up window before and during the collection of relevant data (such as request data for displaying application pages or trigger data for page controls). This prompt interface or pop-up window is used to inform the user that their relevant data is being collected. This application will only begin executing the relevant data collection steps after receiving confirmation from the user regarding the prompt interface or pop-up window; otherwise (i.e., without receiving confirmation from the user), the relevant data collection steps will end, meaning no user data will be collected. In other words, all user-related data collected in this application is collected with the user's consent and authorization, and the collection, use, and processing of relevant user data must comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0028] First, the relevant concepts in this application will be explained: Mini Programs: Applications that can be used without downloading or installing. To provide users with more diverse business services, developers can create corresponding mini programs for terminal applications (such as instant messaging applications, shopping applications, email applications, etc.). These mini programs can be embedded as sub-applications into the terminal applications, and by running the sub-applications (i.e., the corresponding mini programs) within the application, they can provide users with the corresponding business services.

[0029] Pages and Components: A mini-program consists of one or more pages, and each page consists of one or more components. Each page and component has corresponding files such as wxml (a tag language designed by the program framework, which, combined with basic components and the event system, can construct the structure of the mini-program page), wxss (a style language designed by the program framework, which can set component styles and describe how each component on the page is rendered), json (a lightweight data exchange format), and js (a programming language). A page is a special type of component.

[0030] Mini Program compilation: refers to the compilation process that occurs in the background when the mini program code is uploaded. Editing the mini program code at the component level will generate component-level files (such as component compilation files).

[0031] On-demand injection: refers to injecting only the content of the current page when redirecting to another page, including the page content and dependent components or JS files.

[0032] On-demand injection refers to injecting only the components needed for the first page rendering, while other components are replaced by placeholder components. After rendering is complete, the placeholder components are asynchronously loaded and injected to replace them.

[0033] Please see Figure 1 , Figure 1This is a schematic diagram of a network architecture provided in an embodiment of this application. Figure 1 As shown, the network architecture may include server 200 and a cluster of terminal devices. The cluster of terminal devices may include one or more terminal devices; the number of terminal devices is not limited here. Figure 1 As shown, the multiple terminal devices may specifically include terminal device 100a, terminal device 101a, terminal device 102a, ..., terminal device 103a; as Figure 1 As shown, terminal devices 100a, 101a, 102a, ..., 103a can all connect to server 200 via the network, so that each terminal device can interact with server 200 via the network.

[0034] like Figure 1 The server 200 shown can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal device can be a smartphone, tablet, laptop, desktop computer, smart TV, or other smart terminal. The following description uses the communication between terminal device 100a and server 200 as an example to illustrate the specific implementation of this application.

[0035] Please see also Figure 2 , Figure 2 This is a schematic diagram of a page display scenario provided in this application. For example... Figure 2 As shown, the target application can be any application that needs to display a page. The target application can be an application in the aforementioned terminal device 100a, and it can be a subroutine of an app (software). This subroutine can be a mini-program, and the mini-program can have a host program. The aforementioned server 200 can be a background device for the mini-program's host program. The target application can contain several application pages that can be displayed, and these several application pages can include application page 1 to application page n.

[0036] Here, it is assumed that the application page to be displayed is the target application page of the target application, which can be any one of application pages from application page 1 to application page n. This target application page can contain several page components, which can include page component 1 to page component m. Page components 1 to page component m can be divided into two categories: components that are displayed immediately and components that are displayed when needed. For example, some page components among page components 1 to page component m can be components that are displayed immediately, while others can be components that are displayed when needed.

[0037] Among them, the instant display component refers to the page component that needs to be displayed immediately on the target application page when rendering and displaying the target application page, while the time-display component refers to the page component that is displayed based on the trigger operation of the page control in the target application page.

[0038] Therefore, in this application, the target application in terminal device 100a can first render and display the real-time display component in the target application page in real-time according to the component compilation files of each page component of the target application page in server 200, and then asynchronously render and display the display time component in the displayed target application page, thereby reducing the startup time of the target application page and improving the display speed of the target application page. This specific process can also be found in the following... Figure 3 The relevant descriptions in the corresponding embodiments.

[0039] Please see Figure 3 , Figure 3 This is a flowchart illustrating a data processing method provided in this application. The executing entity in the embodiments of this application can be a single computer device or a cluster of computer devices. The computer device can be a server or a terminal device. Therefore, the executing entity in the embodiments of this application can be a server, a terminal device, or a combination of both. Here, we will use a terminal device as the executing entity in this application as an example for explanation. Figure 3 As shown, the method may include: Step S101: When it is necessary to display the target application page of the target application, obtain the first component compilation file of the on-time display component that depends on the target application page, and obtain the second component compilation file of the placeholder component; the placeholder component is used to place the on-time display component that depends on the target application page.

[0040] Optionally, the terminal device may contain a target application. This target application can be any application that needs to display an application page. It can be an app (software) application, a sub-program within an app (such as a mini-program), or a web-based application. When the target application is a sub-program, it can be a mini-program with a host application, which is the app containing the mini-program.

[0041] The target application contains several application pages that can be displayed on a terminal interface. The target application can run on a terminal device, and during the operation of the target application, it can request the display of any application page of the target application. In this application, since the principle of displaying each application page of the target application is the same, the process of displaying the target application page is used as an example for specific explanation. The target application page can be any application page of the target application.

[0042] When a request to display or redirect to display a target application page is triggered within the running target application, it indicates that the target application page needs to be displayed. For example, another application page within the target application besides the target application page may contain a control 'a'. This control 'a' can be a control used to request the display of the target application page. When the user clicks (or performs other actions such as long-pressing, swiping, or voice control) on control 'a', it indicates that a request to display or redirect to display the target application page has been triggered.

[0043] It should be noted that, in the following description, any operation performed by the terminal device can be performed by calling the target application or the host program to which the target application belongs (when the target application is an applet), and conversely, the operation performed by the target application or the host program to which the target application belongs can also be performed by the terminal device.

[0044] Furthermore, the target application page can contain several page components. Each page component contained in the target application page has a dependency relationship with the target application page, and the page components that have a dependency relationship with the target application page depend on the target application page. Here, all the page components contained in the target application page can be divided into two types: one is the component that is displayed immediately (there can be multiple, and the specific number is determined according to the actual application scenario), and the other is the component that is displayed when used (there can be multiple, and the specific number is determined according to the actual application scenario).

[0045] Among them, the instant display component refers to the component that needs to be displayed immediately when the target application page is rendered and displayed, while the time-based display component refers to the component that does not need to be displayed immediately when the target application page is rendered and displayed. Specifically, the time-based display component can refer to the component that is displayed based on the trigger operation (such as click operation, long press operation, etc.) of the page control in the displayed target application page. The page control can be any control in the target application page that can be triggered to display the time-based display component.

[0046] Therefore, in this application, when it is necessary to display the target application page of the target application, the terminal device can first obtain the component compilation files of the on-demand display page that depends on the target application page, and can also obtain the component compilation files of the placeholder components. Here, the component compilation files can be simply referred to as compilation files, and can be obtained by compiling the source code of the page components. The component compilation file of the on-demand display component can be referred to as the first component compilation file, and the component compilation file of the placeholder component can be referred to as the second component compilation file.

[0047] Placeholder components are components used to reserve space for time-based display components that depend on the target application page. For example, when the compiled file of the time-based display component is not yet available, a placeholder component can be displayed in the display position of the time-based display component on the target application page using the obtained compiled file of the placeholder component. The compiled file of this placeholder component can have less data and be simpler to compile than the compiled file of the time-based display component. For example, the placeholder component can be a component in the form of a rotating buffer.

[0048] Optionally, when it is necessary to display the target application page of the target application, the mini-program can obtain the component identifier of the instantly displayed component and the component identifier of the time-used component. The component identifier of the instantly displayed component can be referred to as the first component identifier, and the component identifier of the time-used component can be referred to as the second component identifier. Furthermore, the mini-program can use the first component identifier to retrieve the first component compilation file of the instantly displayed component, and can use the second component identifier to retrieve the component compilation files of the time-used component and / or the placeholder component of the time-used component. This process is described in the following section.

[0049] The process by which the target application obtains the first component identifier and the second component identifier can be as follows: When the target application page needs to be displayed, the target application can obtain the page configuration file of the target application page, which is a pre-configured file associated with the display of the target application page. Optionally, when the target application is a mini-program, the mini-program can retrieve the page configuration file of the target application page from the background device of the host program through the host program.

[0050] After obtaining the page configuration file of the target application page, the target application can parse the configuration file to obtain a list of component identifiers consisting of the component identifiers of all components that depend on the target application page. This list can be called the full component identifier list; in other words, the full component identifier list can contain the component identifiers of all components that depend on the target application page, with one component corresponding to one component identifier. Furthermore, after parsing the page configuration file, the target application can also obtain a list of component identifiers pre-configured for the target application page, consisting of the component identifiers of time-based display components that depend on the target application page. This list can be called the time-based component identifier list.

[0051] Therefore, the mini-program can extract the second component identifier of the time-display component from the parsed list of time-display components. The mini-program can also remove component identifiers included in the time-display component identifier list from the parsed list of all component identifiers to obtain a retained component identifier list. This retained component identifier list is the list obtained after removing the second component identifier from the list of all component identifiers. Therefore, the mini-program can use all component identifiers in the retained component identifier list as the second component identifier.

[0052] Please see Figure 4 , Figure 4 This is a schematic diagram illustrating a scenario for obtaining a component identifier, as provided in this application. For example... Figure 4 As shown, the target application can parse the page configuration file of the target application page to obtain the full list of component identifiers and the list of time-based component identifiers of the target application page. Here, the full list of component identifiers can include the component identifiers of each page component that depends on the target application page (specifically including component identifier 1 to component identifier 6), and the list of time-based component identifiers can include the component identifiers of each time-based display component that depends on the target application page (specifically including component identifier 2 to component identifier 4). Therefore, the target application can directly extract the second component identifier of the time-based display component from the list of time-based component identifiers. There are three second component identifiers: component identifier 2, component identifier 3, and component identifier 4.

[0053] Furthermore, the target application can remove component identifiers from the full component identifier list and the time-based component identifier list to obtain a retained component identifier list. This retained component identifier list can contain component identifier 1, component identifier 5, and component identifier 6. Therefore, the target application can use component identifier 1, component identifier 5, and component identifier 6 from the retained component identifier list as the first component identifier for the component to be displayed instantly.

[0054] The component identifiers included in the above full component identifier list can be understood as the identifiers of the on-demand injected components of the target application page, and the component identifiers included in the above time-based component identifier list can be understood as the identifiers of the time-based injected components of the target application page.

[0055] If the target application is a mini-program, the process of the mini-program obtaining the first component compilation file of the instant display component can be as follows: The mini-program can generate a first file pull request. The first file pull request can refer to a request used to pull the component compilation file of the instant display component. The first file pull request can carry the component identifier of the instant display component (which can be called the first component identifier). Therefore, the terminal device can call the mini-program's host program to pull the first component compilation file associated with the first component identifier from the host program's background device according to the first file pull request. The instant display component is associated with its own first component identifier.

[0056] Optionally, you can configure on-demand component injection by adding the configuration statement "lazyCodeLoading":"requiredComponents" to app.json (the target application's JSON file). This allows the backend to pre-compile the target application's source code at the component level (e.g., compiling the component's compiled files before applying the target application) and load components at the page level (e.g., loading the full list of component identifiers for the target application page). Furthermore, you can configure which injections should be asynchronous (i.e., displaying component configurations only when needed) and the corresponding placeholder components in the JSON file corresponding to the target application page.

[0057] Furthermore, placeholder components can be pre-configured for the time-display component, and one time-display component can correspond to one placeholder component. The placeholder component configured for the time-display component can be a built-in component of the target application (i.e., several pre-configured selectable components within the mini-program), or it can be a custom component.

[0058] Therefore, if the target application is a subroutine, specifically a mini-program, and the placeholder component is a built-in component within that mini-program, then the second component compilation file of the placeholder component resides within the subroutine (i.e., the mini-program), not on the background device. Thus, the terminal device can obtain the second component compilation file of the placeholder component within the mini-program (front end). If the target application is a mini-program, and the placeholder component is a custom component, then the mini-program can retrieve the second component compilation file of the placeholder component from the background device of its host application. This process can involve the terminal device generating a second file retrieval request within the mini-program. This request is for retrieving the component compilation file of the placeholder component for the time-display component. This second file retrieval request can carry the component identifier of the time-display component (which can be called the second component identifier). Therefore, the terminal device can invoke the host application to retrieve the second component compilation file of the placeholder component indicated (or associated with) the second component identifier from the host application's background device based on this second file retrieval request. Furthermore, when configuring a placeholder component for the time-display component, an association can be established between the placeholder component and the second component identifier of the time-display component.

[0059] In one possible implementation, the target application can be a mini-program, which may have a host program. The mini-program may contain multiple application pages (the specific number of application pages can be determined according to the actual application scenario and is not limited thereto). These multiple application pages may contain the target application page, and these multiple application pages may have a component set. The component set may contain all components (all page components) that depend on these multiple application pages. The backend device of the host program (which may be a server or a server cluster) can compile the component compilation files corresponding to each component in the component set on a component-by-component basis, with one component corresponding to one component compilation file. In other words, the backend device of the host program can pre-compile the component compilation files corresponding to all page components of each application page that depend on the target application page on a component-by-component basis, instead of compiling on a data packet basis (a data packet may contain the source code of each page component that depends on several application pages). This allows the frontend (such as a terminal device) to only obtain the compilation files of the page components related to the application page that needs to be displayed, without having to obtain the compilation files of other page components related to application pages that do not currently need to be displayed, reducing the amount of data obtained and thus reducing the page startup (display) time.

[0060] Step S102: Render and display the target application page based on the first component compilation file and the second component compilation file; the rendered and displayed target application page includes an instant display component and a placeholder component.

[0061] Optionally, the target application in the terminal device can render and display the target application page based on the first compilation file and the second compilation file. The first compilation file compiles (or indicates) the way to render and display the real-time display component on the target application page, and the second compilation file compiles the way to render and display the placeholder component on the target application page. Therefore, the rendered and displayed target application page can contain the rendered real-time display component and the placeholder component of the real-time display component.

[0062] That is, the target application in the terminal device can display the rendered target application page, which includes real-time display components and placeholder components, on the terminal interface.

[0063] Step S103: Asynchronously obtain the third component compilation file of the time-display component, and replace the placeholder component in the target application page to be rendered and displayed with the time-display component according to the third component compilation file.

[0064] Optionally, after rendering and displaying the target application page, the mini-program on the terminal device can then asynchronously obtain the component compilation file of the on-time display component. This component compilation file can be referred to as the third component compilation file. The mini-program can use this third component compilation file to replace the placeholder component in the rendered target application page with the on-time display component. After the replacement, the final target application page is displayed, which includes both the rendered on-time display component and the on-time display component.

[0065] Optionally, if the target application is a mini-program, the process for the mini-program to obtain the third-component compiled file of the time-display component can be as follows: The mini-program can generate a third-file pull request. This third-file pull request can refer to a request for pulling the component compiled file of the time-display component. The third-file pull request can carry the component identifier (i.e., the second-component identifier) ​​of the time-display component. Therefore, the terminal device can call the mini-program's host program to pull the third-component compiled file associated with the second-component identifier from the host program's background device according to the third-file pull request. The time-display component is associated with its own second-component identifier.

[0066] Please see Figures 5-7 , Figures 5-7 This is a schematic diagram of a target application page provided in this application. Figure 5 The target application page is rendered based on the component compilation file of the real-time display component. The target application page contains the real-time display component, which may specifically include page component 100b, page component 101b (page component 101b is actually a kind of page control), page component 102b and page component 103b.

[0067] More importantly, when a target is detected... Figure 5 The triggering operation of page control 101b in the target application page can display Figure 6 The target application page shown includes a placeholder component 104b for a timing display component, which is displayed on the target application page before the third component compilation file is obtained. Then, once the target application obtains the third component compilation file for the timing display component, it can use this third component compilation file to... Figure 5 or Figure 6 The placeholder component shown is replaced with a time-display component, at which point the target application page can be displayed as follows: Figure 7 As shown, Figure 7 The image shows a time display component 105b after the placeholder component has been replaced. The placeholder component of the time display component 105b is the aforementioned placeholder component 104b. The time display component can also contain three controls, which can include a like control, a comment control, and a share control.

[0068] Using the method provided in this application, page components in the application page are divided into two types: instant display components and time-based display components. Therefore, when rendering the application page, placeholder components for both instant and time-based display components can be rendered and displayed first. This allows for rapid presentation and display of the target application page on the terminal interface, reducing startup time. This target application page includes placeholder components for both instant and time-based display components. Next, the compiled file for the time-based display component can be asynchronously retrieved, and the target application page can be rendered a second time, replacing the placeholder components from the first rendering with the time-based display components. Since the compiled file for the time-based display component is significantly larger than that of its placeholder components, and the parsing difficulty of the compiled file for the time-based display component (rendering the corresponding component by parsing the compiled file) is also significantly greater than that of its placeholder components, this application, by first displaying the placeholder components of the time-based display component and then asynchronously displaying the time-based display component, can improve the display speed of the target application page, reduce page lag, and enhance the user experience.

[0069] Optionally, the above process can be part of the target application's application process. Furthermore, the developer tools also provide a placeholder component debugging switch (which can exist in the placeholder component's debugging controls or debugging tools). During the development and debugging process of the target application (the implementation of which is actually the same as the target application's application process described above), if this placeholder component debugging switch is enabled, after the application page is first rendered and displayed, if the compiled file of the time-injected component (i.e., the time-display component) is obtained, and a request is made to inject the time-injected component into the application page (e.g., replacing the placeholder component with the time-injected component), the process will stop (i.e., pause the injection, which can be understood as blocking the interface for injecting the time-display component). This facilitates developers in debugging custom placeholder components of the time-injected component. It is understandable that when the placeholder component debugging switch is disabled, the target application can normally replace the placeholder component in the first rendered application page with the corresponding time-display component.

[0070] Please see Figures 8-9 , Figures 8-9 This is a schematic diagram of a component debugging page provided in this application. For example... Figure 8 As shown, Figure 8 The page shown (which may be a page in the developer tools) refers to the state when the placeholder component debugging switch in the placeholder component debugging tool is off. At this time, the process of injecting the time-injected component into the target application page is normal and will not be blocked. Figure 9 The page shown refers to the state when the placeholder component debugging switch in the placeholder component debugging tool is turned on. In this state, the placeholder component remains in the target application page during the initial rendering and is not replaced by the corresponding time-injected component (i.e., the time-displayed component). Figure 9 The visual containers, basic content, and form components on the page shown can be used to debug the currently displayed placeholder components. The specific content to be debugged can be determined according to the actual application scenario.

[0071] Optionally, the target application mentioned above can be a subroutine, which can be a mini-program. A mini-program can have two sides: a webview side (which can be called the interface side) and an appservice side (which can be called the service side). That is, the mini-program is divided into two threads: webview and appservice. The webview is mainly used to display and render the interface (i.e., the page), while the appservice is used to handle business logic, data, and API calls. Communication is achieved through a system-level JSBridge to realize UI (interface) rendering and event handling.

[0072] In this application, the source code of the target application is compiled at the component level (before the target application is applied). This can generate common files and files corresponding to each component / page. The directory structure of the compiled files can generally include: app-config.json (global configuration), common.app.js (common code on both sides, which may be empty), appservice.app.js (common code on the appservice side), webview.app.js (common code on the webview side), path / to / a / component.common.js (specific component code shared on both sides), path / to / a / component.appservice.js (specific component code on the appservice side), path / to / a / component.webview.js (specific component code on the webview side), and path / to / a / page.html (page identifier file representing custom components as application pages (empty file)).

[0073] Based on the aforementioned target application (if it is a mini-program), the process of this application is explained as follows: When a user launches a mini-program and navigates to a certain page within the mini-program, the client of the target application (the front-end client in the application process of the target application) / the developer tools (the program tools on the developer's device in the development process of the target application, which can be understood as the target application in the development process) receives routing information (used to indicate which application page needs to be displayed) from the base library (the program running framework of the mini-program, possessing framework capabilities and mechanical capabilities). Based on this routing information, the page configuration information of the application page to be displayed is obtained. Through this page configuration information, common files such as common.js (common files on both sides) and webview.js (specific files on the webview side) are injected into the webview side (compiled files), and common files such as common.js (common files on both sides) and appservice.js (specific files on the appservice side) can also be injected into the appservice side.

[0074] Furthermore, the base library can analyze the dependencies between pages and components using the page configuration information obtained above. Through the analyzed dependencies, it can obtain a list of time-injected components (such as the time-injected component identifier list above) and a list of on-demand injected components (such as the full component identifier list above), and obtain the placeholder components for the pre-configured time-injected display components.

[0075] Next, the base library can call the `loadJsFiles / loadComponents` methods (methods for dynamically loading resources) provided by the client / developer tools on the webview and appservice sides to inject the on-demand injection lists required for rendering the application page to be displayed on both sides. This initial rendering of the application page includes placeholder components for both live and on-demand injected components. After the page has finished loading and rendering, the base library can again call the `loadJsFiles / loadComponents` methods provided by the target application's client / developer tools on both the webview and appservice sides to inject the on-demand injected component lists. After injection, the base library retrieves the on-demand injected components (e.g., the compiled files of the on-demand injected components) and replaces the corresponding placeholder components in the rendered application page.

[0076] When this application needs to display the target application page of the target application, it can obtain the first component compilation file of the on-demand display component that depends on the target application page, and obtain the second component compilation file of the placeholder component. The placeholder component is used to place the on-demand display component that depends on the target application page. The target application page is rendered and displayed based on the first and second component compilation files. The rendered and displayed target application page includes the on-demand display component and the placeholder component. The third component compilation file of the on-demand display component is obtained asynchronously, and the placeholder component in the rendered and displayed target application page is replaced with the on-demand display component according to the third component compilation file. Therefore, the method proposed in this application can render and display the on-demand display component and the placeholder component of the on-demand display component of the target application page first when the target application page is rendered and displayed for the first time. After the rendering is completed, the on-demand display component can be rendered and displayed asynchronously in the target application page that was rendered and displayed for the first time, so as to reduce the startup time of the target application page and improve the startup speed of the target application page.

[0077] Please see Figure 10 , Figure 10 This is a schematic diagram of a data processing apparatus provided in this application. The data processing apparatus can be a computer program (including program code) running on a computer device; for example, the data processing apparatus is application software. This data processing apparatus can be used to execute corresponding steps in the methods provided in the embodiments of this application. Figure 10 As shown, the data processing device 1 may include: The file acquisition module 11 is used to acquire the first component compilation file of the on-demand display component that depends on the target application page when the target application page of the target application needs to be displayed, and to acquire the second component compilation file of the placeholder component; the placeholder component is used to place the on-demand display component that depends on the target application page. Display module 12 is used to render and display a target application page based on the first component compilation file and the second component compilation file; the rendered and displayed target application page includes an instant display component and a placeholder component; Replacement module 13 is used to asynchronously obtain the third component compilation file of the time-display component, and replace the placeholder component in the target application page to be rendered and displayed with the time-display component according to the third component compilation file.

[0078] Optionally, when it is necessary to display the target application page of the target application, the file acquisition module 11 acquires the first component compilation file of the on-demand display component that depends on the target application page, and acquires the second component compilation file of the placeholder component in the following ways: When the target application page needs to be displayed, obtain the first component identifier of the component to be displayed immediately, and obtain the second component identifier of the component to be displayed at a later time; The first component compilation file of the instant display component is obtained based on the first component identifier, and the second component compilation file of the placeholder component is obtained based on the second component identifier.

[0079] Optionally, when the target application page needs to be displayed, the file acquisition module 11 acquires the first component identifier of the component to be displayed immediately, and acquires the second component identifier of the component to be displayed immediately, in the following ways: When it is necessary to display the target application page, retrieve the page configuration file of the target application page; The page configuration file is parsed to obtain a list of full component identifiers consisting of component identifiers of all components that depend on the target application page, and a list of time-based component identifiers consisting of component identifiers of time-based display components that depend on the target application page. The first component identifier is determined based on the full list of component identifiers and the list of time-used component identifiers, and the second component identifier is extracted from the list of time-used component identifiers.

[0080] Optionally, the file acquisition module 11 determines the first component identifier based on the full list of component identifiers and the list of time-used component identifiers in the following ways: Remove the second component identifier contained in the time-used component identifier list from the full component identifier list to obtain the retained component identifier list; The component identifier in the list of retained component identifiers is determined as the second component identifier.

[0081] Optionally, the target application is a subroutine, and the subroutine has a host program; The file acquisition module 11 acquires the first component compilation file of the real-time display component that depends on the target application page in the following ways: The first file fetch request is generated in the subroutine; the first file fetch request carries the first component identifier of the component to be displayed immediately; The host program is invoked to retrieve the first component compilation file associated with the first component identifier from the host program's background device based on the first file retrieval request.

[0082] Optionally, the target application is a subroutine; The file acquisition module 11 acquires the second component compilation file of the placeholder component in the following ways: If the placeholder component is a built-in component of the subroutine, then the second component compilation file of the placeholder component is obtained within the subroutine.

[0083] Optionally, the target application is a subroutine; the subroutine has a host program. The file acquisition module 11 acquires the second component compilation file of the placeholder component in the following ways: If the placeholder component is a custom component, a second file fetch request is generated in the subroutine; the second file fetch request carries the identifier of the second component to be displayed. The host program is invoked to retrieve the second component compilation file of the placeholder component indicated by the second component identifier from the host program's background device according to the second file retrieval request.

[0084] Optionally, the target application is a subroutine; the subroutine has a host program. Replace module 13 with a method for asynchronously obtaining the third-party component compilation file used by the component to display the data, including: Generate a third file fetch request in the subroutine; the third file fetch request carries the identifier of the second component used for display; The host program is invoked to retrieve the compiled file of the third component associated with the second component identifier from the host program's background device based on the third file retrieval request.

[0085] Optionally, the target application is a subroutine, the subroutine has a host program, the subroutine contains multiple application pages, the multiple application pages contain the target application page, the multiple application pages have a component set, the component set contains various components that depend on the multiple application pages, and the background device of the host program compiles the component compilation files corresponding to each component in the component set according to the component unit.

[0086] Optionally, a real-time display component refers to a component that needs to be displayed in real time when the target application page is rendered and displayed, while a time-display component refers to a component that is displayed in the target application page based on the trigger operation on the page control.

[0087] According to one embodiment of this application, Figure 3 The steps involved in the data processing method shown can be derived from... Figure 10 The data processing apparatus 1 shown is executed by each module. For example, Figure 3 Step S101 shown can be performed by Figure 10 The file acquisition module 11 in the middle is used to execute, Figure 3 Step S102 shown can be performed by Figure 10 The display module 12 in the middle is used to execute; Figure 3 Step S103 shown can be performed by Figure 10 The replacement module 13 in the middle is used to execute.

[0088] When this application needs to display the target application page of the target application, it can obtain the first component compilation file of the on-demand display component that depends on the target application page, and obtain the second component compilation file of the placeholder component. The placeholder component is used to place the on-demand display component that depends on the target application page. The target application page is rendered and displayed based on the first and second component compilation files. The rendered and displayed target application page includes the on-demand display component and the placeholder component. The third component compilation file of the on-demand display component is obtained asynchronously, and the placeholder component in the rendered and displayed target application page is replaced with the on-demand display component according to the third component compilation file. Therefore, the method proposed in this application can render and display the on-demand display component and the placeholder component of the on-demand display component of the target application page first when the target application page is rendered and displayed for the first time. After the rendering is completed, the on-demand display component can be rendered and displayed asynchronously in the target application page that was rendered and displayed for the first time, so as to reduce the startup time of the target application page and improve the startup speed of the target application page.

[0089] According to one embodiment of this application, Figure 10 The modules in the data processing device 1 shown can be individually or entirely combined into one or more units, or one or more of these units can be further divided into multiple functionally smaller sub-units to achieve the same operation without affecting the technical effects of the embodiments of this application. The above modules are based on logical functional division. In practical applications, the function of one module can be implemented by multiple units, or the function of multiple modules can be implemented by one unit. In other embodiments of this application, the data processing device 1 may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0090] According to one embodiment of this application, a general-purpose computer device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM), can perform operations such as... Figure 3 The computer program (including program code) involved in each step of the corresponding method shown, to construct such... Figure 10 The data processing apparatus 1 shown herein, and the data processing method for implementing the embodiments of this application, are described. The computer program described above may be recorded on, for example, a computer-readable recording medium, loaded onto the aforementioned computing device via the computer-readable recording medium, and run therein.

[0091] Please see Figure 11 , Figure 11 This is a schematic diagram of the structure of a computer device provided in this application. For example... Figure 11 As shown, computer device 1000 may include: a processor 1001, a network interface 1004, and a memory 1005. Furthermore, computer device 1000 may also include: a user interface 1003, and at least one communication bus 1002. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen and a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as at least one disk storage device. Optionally, the memory 1005 may also be at least one storage device located remotely from the aforementioned processor 1001. Figure 11 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a device control application program.

[0092] exist Figure 11 In the computer device 1000 shown, the network interface 1004 provides network communication functionality; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to achieve: When the target application page of the target application needs to be displayed, the first component compilation file of the on-demand display component that depends on the target application page is obtained, and the second component compilation file of the placeholder component is obtained; the placeholder component is used to place the on-demand display component that depends on the target application page. The target application page is rendered and displayed based on the first component compilation file and the second component compilation file; the rendered target application page includes an instant display component and a placeholder component; Asynchronously retrieve the third-party component compilation file of the time-based display component, and replace the placeholder component in the target application page to the time-based display component based on the third-party component compilation file.

[0093] In one possible implementation, the processor 1001 can also be used to invoke a device control application stored in the memory 1005 to achieve: When the target application page needs to be displayed, obtain the first component identifier of the component to be displayed immediately, and obtain the second component identifier of the component to be displayed at a later time; The first component compilation file of the instant display component is obtained based on the first component identifier, and the second component compilation file of the placeholder component is obtained based on the second component identifier.

[0094] In one possible implementation, the processor 1001 can also be used to invoke a device control application stored in the memory 1005 to achieve: When it is necessary to display the target application page, retrieve the page configuration file of the target application page; The page configuration file is parsed to obtain a list of full component identifiers consisting of component identifiers of all components that depend on the target application page, and a list of time-based component identifiers consisting of component identifiers of time-based display components that depend on the target application page. The first component identifier is determined based on the full list of component identifiers and the list of time-used component identifiers, and the second component identifier is extracted from the list of time-used component identifiers.

[0095] In one possible implementation, the processor 1001 can also be used to invoke a device control application stored in the memory 1005 to achieve: Remove the second component identifier contained in the time-used component identifier list from the full component identifier list to obtain the retained component identifier list; The component identifier in the list of retained component identifiers is determined as the second component identifier.

[0096] Optionally, the target application is a subroutine, and the subroutine has a host program; In one possible implementation, the processor 1001 can also be used to invoke a device control application stored in the memory 1005 to achieve: The first file fetch request is generated in the subroutine; the first file fetch request carries the first component identifier of the component to be displayed immediately; The host program is invoked to retrieve the first component compilation file associated with the first component identifier from the host program's background device based on the first file retrieval request.

[0097] Optionally, the target application is a subroutine; In one possible implementation, the processor 1001 can also be used to invoke a device control application stored in the memory 1005 to achieve: If the placeholder component is a built-in component of the subroutine, then the second component compilation file of the placeholder component is obtained within the subroutine.

[0098] Optionally, the target application is a subroutine; the subroutine has a host program. In one possible implementation, the processor 1001 can also be used to invoke a device control application stored in the memory 1005 to achieve: If the placeholder component is a custom component, a second file fetch request is generated in the subroutine; the second file fetch request carries the identifier of the second component to be displayed. The host program is invoked to retrieve the second component compilation file of the placeholder component indicated by the second component identifier from the host program's background device according to the second file retrieval request.

[0099] Optionally, the target application is a subroutine; the subroutine has a host program. In one possible implementation, the processor 1001 can also be used to invoke a device control application stored in the memory 1005 to achieve: Generate a third file fetch request in the subroutine; the third file fetch request carries the identifier of the second component used for display; The host program is invoked to retrieve the compiled file of the third component associated with the second component identifier from the host program's background device based on the third file retrieval request.

[0100] In one possible implementation, the target application is a subroutine, the subroutine has a host program, the subroutine contains multiple application pages, the multiple application pages contain the target application page, the multiple application pages have a component set, the component set contains various components that depend on the multiple application pages, and the background device of the host program compiles component compilation files corresponding to each component in the component set according to the component unit.

[0101] In one possible implementation, an instant-display component refers to a component that needs to be displayed in real time when rendering and displaying the target application page, while a time-display component refers to a component that is displayed in the target application page based on the trigger operation on the page control.

[0102] It should be understood that the computer device 1000 described in the embodiments of this application can execute the foregoing text. Figure 3 The data processing method described in the corresponding embodiments can also be executed as described above. Figure 10 The description of the data processing apparatus 1 in the corresponding embodiments will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated.

[0103] Furthermore, it should be noted that this application also provides a computer-readable storage medium storing a computer program executed by the aforementioned data processing apparatus 1. The computer program includes program instructions, which, when executed by a processor, enable the execution of the aforementioned... Figure 3 The description of the data processing method in the corresponding embodiments is already provided and will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the embodiments of the computer storage medium involved in this application, please refer to the description of the method embodiments of this application.

[0104] As an example, the above program instructions can be deployed and executed on a single computer device, or deployed and executed on multiple computer devices located in one location, or executed on multiple computer devices distributed across multiple locations and interconnected via a communication network. Multiple computer devices distributed across multiple locations and interconnected via a communication network can form a blockchain network.

[0105] The aforementioned computer-readable storage medium can be an internal storage unit of the data processing apparatus or computer device provided in any of the foregoing embodiments, such as a hard disk or memory of the computer device. The computer-readable storage medium can also be an external storage device of the computer device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., provided on the computer device. Furthermore, the computer-readable storage medium can include both internal storage units and external storage devices of the computer device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0106] This application provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned... Figure 3 The data processing method described in the corresponding embodiments will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the computer-readable storage medium embodiments related to this application, please refer to the description of the method embodiments of this application.

[0107] The terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the term "comprising," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or device that includes a series of steps or units is not limited to the listed steps or modules, but may optionally include steps or modules not listed, or may optionally include other step units inherent to these processes, methods, apparatuses, products, or devices.

[0108] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0109] The methods and related apparatus provided in this application are described with reference to the method flowcharts and / or structural diagrams provided in this application. Specifically, each block of the method flowchart and / or structural diagram, as well as combinations of blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to create a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, generate instructions for implementing the process. Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1 The computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1 The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 A process or multiple processes and / or structures illustrate the steps of the functions specified in one or more boxes.

[0110] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. A data processing method, characterized in that, The method includes: When it is necessary to display the target application page of the target application, obtain the page configuration file that depends on the target application page; The page configuration file is parsed to obtain a first component identifier of the real-time display component that depends on the target application page, and a second component identifier of the time-based display component that depends on the target application page; The first component compilation file of the real-time display component is obtained according to the first component identifier, and the second component compilation file of the placeholder component is obtained according to the second component identifier; the placeholder component is used to place a space for the time-based display component. The target application page is rendered and displayed based on the first component compilation file and the second component compilation file; the rendered and displayed target application page includes the instant display component and the placeholder component.

2. The method according to claim 1, characterized in that, After rendering and displaying the target application page based on the first component compilation file and the second component compilation file, the method further includes: When a trigger operation is detected targeting a page control in the target application page, the third component compilation file of the time-display component is asynchronously obtained; The placeholder component in the target application page is replaced with the time display component according to the third component compilation file; wherein, after a trigger operation on the page control is detected and before the third component compilation file is obtained, the placeholder component of the time display component associated with the page control is rendered and displayed in the target application page.

3. The method according to claim 2, characterized in that, The step of parsing the page configuration file to obtain a first component identifier for an instant display component dependent on the target application page and a second component identifier for a timed display component dependent on the target application page includes: The page configuration file is parsed to obtain a list of full component identifiers consisting of component identifiers of all components that depend on the target application page, and a list of time component identifiers consisting of component identifiers of the time display component that depends on the target application page. The first component identifier is determined based on the full list of component identifiers and the list of time-consuming component identifiers, and the second component identifier is extracted from the list of time-consuming component identifiers.

4. The method according to claim 3, characterized in that, Determining the first component identifier based on the full list of component identifiers and the list of time-consuming component identifiers includes: Remove the second component identifier contained in the time-consuming component identifier list from the full component identifier list to obtain the retained component identifier list; The component identifier in the reserved component identifier list is determined as the first component identifier.

5. The method according to claim 1, characterized in that, The target application is a subroutine, and the subroutine has a host program; The step of obtaining the first component compilation file of the instant display component based on the first component identifier includes: The subroutine generates a first file fetch request; the first file fetch request carries a first component identifier of the instant display component; The host program is invoked to retrieve the compiled file of the first component associated with the first component identifier from the background device of the host program according to the first file retrieval request.

6. The method according to claim 1, characterized in that, The target application is a subroutine; the subroutine has a host program. The step of obtaining the second component compilation file of the placeholder component based on the second component identifier includes: If the placeholder component is a custom component, a second file fetch request is generated in the subroutine; the second file fetch request carries the second component identifier of the time-display component; The host program is invoked to retrieve the compiled file of the second component of the placeholder component indicated by the second component identifier from the background device of the host program according to the second file retrieval request.

7. The method according to claim 2, characterized in that, The target application is a subroutine; the subroutine has a host program. The asynchronous acquisition of the third component compilation file of the time-display component includes: A third file fetch request is generated in the subroutine; the third file fetch request carries the second component identifier of the timing display component; The host program is invoked to retrieve the compiled file of the third component associated with the second component identifier from the background device of the host program according to the third file retrieval request.

8. The method according to claim 1, characterized in that, The target application is a subroutine, which has a host program. The subroutine contains multiple application pages, which include the target application page. The multiple application pages have a component set, which contains various components that depend on the multiple application pages. The background device of the host program compiles component compilation files corresponding to each component in the component set according to the component unit.

9. The method according to claim 1, characterized in that, The instant display component refers to the component that needs to be displayed instantly when rendering and displaying the target application page, while the time-based display component refers to the component that is displayed on the target application page according to the trigger operation on the page control.

10. A data processing apparatus, characterized in that, The device includes: The file acquisition module is used to acquire the page configuration file that depends on the target application page when it is necessary to display the target application page of the target application. The file acquisition module is also used to parse the page configuration file to obtain a first component identifier of the instant display component that depends on the target application page and a second component identifier of the time display component that depends on the target application page. The file acquisition module is further configured to acquire the first component compilation file of the real-time display component according to the first component identifier, and acquire the second component compilation file of the placeholder component according to the second component identifier; the placeholder component is used to place a space for the time-based display component; The display module is used to render and display the target application page based on the first component compilation file and the second component compilation file; the rendered and displayed target application page includes the instant display component and the placeholder component.

11. The apparatus according to claim 10, characterized in that, The instant display component refers to the component that needs to be displayed instantly when rendering and displaying the target application page, while the time-based display component refers to the component that is displayed on the target application page according to the trigger operation on the page control.

12. A computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1-9.

13. A computer device, characterized in that, It includes a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1-9.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted to be loaded by a processor and executed as described in any one of claims 1-9.

Images