A page acquisition method, device, equipment, storage medium and product

Abstract

The application provides a page acquisition method, device, equipment, storage medium and product. The page acquisition method comprises the following steps: acquiring a to-be-compiled component generated by each component development framework; compiling the to-be-compiled component to obtain a page component; combining the page component corresponding to each component development framework in at least two component development frameworks to obtain a plurality of page components; and presenting the plurality of page components, and in response to a selection operation on the plurality of page components, aggregating the selected page components to obtain an application page, wherein the application page is a front-end page of a functional application. Through the application, the flexibility of page acquisition can be improved.

Description

Technical Field

[0001] This application relates to information processing technology in the field of computer applications, and more particularly to a page acquisition method, apparatus, device, storage medium, and product. Background Technology

[0002] Micro-frontend refers to breaking down a functional application into multiple sub-functional applications or components according to different dimensions, and loading these sub-functional applications or components through the main application to realize the corresponding functions of the functional application; that is, in micro-frontend, a functional application is composed of multiple sub-applications or components.

[0003] Generally, to implement micro-frontends, a front-end development framework is typically used to develop sub-applications or components, which are then aggregated into the front-end pages of the main application. However, in the process of implementing micro-frontends described above, the front-end pages are developed using a single front-end development framework, which imposes limitations. Consequently, the flexibility of page retrieval is relatively low during the implementation of micro-frontends. Summary of the Invention

[0004] This application provides a page acquisition method, apparatus, device, computer-readable storage medium, and computer program product, which can improve the flexibility of page acquisition during the implementation of micro-frontends.

[0005] The technical solution of this application embodiment is implemented as follows:

[0006] This application provides a page acquisition method, including:

[0007] Obtain the components to be compiled generated by each component development framework;

[0008] The component to be compiled is then compiled to obtain the page component;

[0009] In at least two of the component development frameworks, the page components corresponding to each of the component development frameworks are combined to obtain a plurality of page components;

[0010] Multiple page components are presented, and in response to a selection operation on the multiple page components, the selected page components are aggregated to obtain an application page, wherein the application page is the front-end page of the functional application.

[0011] This application provides a page acquisition device, including:

[0012] The component acquisition module is used to acquire the components to be compiled generated by each component development framework;

[0013] The component encoding module is used to compile the component to be compiled to obtain the page component;

[0014] A component combination module is used to combine the page components corresponding to each of the at least two component development frameworks to obtain multiple page components.

[0015] The component aggregation module is used to present multiple page components. In response to a selection operation on the multiple page components, the selected page components are aggregated to obtain an application page, wherein the application page is the front-end page of the functional application.

[0016] In this embodiment of the application, the page acquisition device further includes a page presentation module, configured to acquire the rendering logic corresponding to the selected page component in response to a rendering operation for the application page; during the execution of the rendering logic, for each of the selected page components, a corresponding framework runtime is loaded, wherein the framework runtime is the runtime of the component development framework; and the application page is presented based on the framework runtime corresponding to each loaded page component.

[0017] In this embodiment of the application, the page rendering module is further configured to, in response to the rendering operation for the application page, obtain the aggregation logic between each page component in the selected page component; based on the aggregation logic, obtain the implementation logic corresponding to each page component in the selected page component, and combine the obtained implementation logic corresponding to each page component into the rendering logic corresponding to the selected page component.

[0018] In this embodiment of the application, the page presentation module is further configured to: obtain data to be converted for each page component based on the framework runtime corresponding to each loaded page component; perform data conversion on the data to be converted based on the data format of the component development framework corresponding to the page component to obtain data to be displayed; and present the application page based on the data to be displayed.

[0019] In this embodiment of the application, the page acquisition device further includes a page interaction module, which is used to respond to a first application operation performed on the application page, instruct the triggered page component to send a first interaction instruction to the associated page component through a message center; instruct the associated page component to execute the first interaction instruction, and present interactive information corresponding to the associated page component based on the execution result of the first interaction instruction.

[0020] In this embodiment of the application, the page interaction module is further configured to respond to a second application operation performed on the application page by obtaining a second interaction instruction sent by the triggered page component through a message center; executing the second interaction instruction; and performing system interaction processing on the application page based on the execution result of the second interaction instruction.

[0021] In this embodiment, the selection operation includes a template component selection operation and a functional component selection operation. The selected page component includes a selected template component and a selected functional component. The component aggregation module is further configured to obtain the selected template component in response to the template component selection operation for multiple page components; and to aggregate the selected functional components based on the selected template component in response to the functional component selection operation for multiple page components to obtain the application page.

[0022] In this embodiment, the page acquisition device further includes a page management module, configured to acquire at least one application page corresponding to the functional application; present an application page list based on the at least one application page, wherein the presented application page list includes at least one application page and a page setting control corresponding to each application page, the page setting control including one or more of page information setting controls, component configuration controls, status setting controls, interface configuration controls, and preview controls; and, in response to a page setting operation performed on the page setting control, execute the page setting operation for the application page corresponding to the page setting control.

[0023] In this embodiment of the application, the page acquisition device further includes an application management module, configured to acquire at least one of the functional applications; present a list of functional applications based on the at least one functional application, wherein the presented list of functional applications includes at least one of the functional applications and an application settings control corresponding to each functional application; and, in response to an application settings operation performed on the application settings control, execute the application settings operation for the functional application corresponding to the application settings control.

[0024] This application provides a page acquisition device, including:

[0025] Memory, used to store executable instructions;

[0026] The processor, when executing executable instructions stored in the memory, implements the page acquisition method provided in the embodiments of this application.

[0027] This application provides a computer-readable storage medium storing executable instructions for inducing a processor to execute and implement the page acquisition method provided in this application.

[0028] This application provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement the page acquisition method provided in this application.

[0029] The embodiments of this application have at least the following beneficial effects: by compiling the components developed by each of the at least two component development frameworks, it is possible to simultaneously support multiple page components corresponding to the at least two component development frameworks; then, by visually aggregating the multiple page components, the front-end page of the functional application is obtained; that is, the application page is obtained by aggregating the page components developed by different component development frameworks, which is a cross-framework page acquisition method, thereby improving the flexibility of page acquisition in the micro-frontend implementation process. Attached Figure Description

[0030] Figure 1 This is an optional architecture diagram of the page acquisition system provided in the embodiments of this application;

[0031] Figure 2 This is one of the embodiments provided in this application. Figure 1 A schematic diagram of the terminal's composition structure;

[0032] Figure 3 This is an optional flowchart illustrating the page acquisition method provided in the embodiments of this application;

[0033] Figure 4 This is another optional flowchart illustrating the page acquisition method provided in the embodiments of this application;

[0034] Figure 5 This is another optional flowchart illustrating the page acquisition method provided in the embodiments of this application;

[0035] Figure 6 This is an architecture diagram of an exemplary page retrieval system provided in an embodiment of this application;

[0036] Figure 7 This is a schematic diagram illustrating an exemplary data conversion method provided in an embodiment of this application;

[0037] Figure 8 This is a schematic diagram illustrating another exemplary data conversion provided in an embodiment of this application;

[0038] Figure 9 This is a schematic diagram of an exemplary page template provided in an embodiment of this application;

[0039] Figure 10 This is a schematic diagram of an exemplary functional component provided in an embodiment of this application;

[0040] Figure 11 This is a schematic diagram of an exemplary configuration template / functional component provided in an embodiment of this application;

[0041] Figure 12 This is a schematic diagram of an exemplary application page management page provided in an embodiment of this application;

[0042] Figure 13 This is a schematic diagram of an exemplary rendered application page provided in an embodiment of this application;

[0043] Figure 14 This is a schematic diagram illustrating an exemplary loading framework runtime provided in an embodiment of this application;

[0044] Figure 15 This is an exemplary communication diagram provided in an embodiment of this application. Detailed Implementation

[0045] 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.

[0046] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0047] In the following description, the terms "first" and "second" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first" and "second" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

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

[0049] In the implementation of this application, the collection and processing of relevant data should strictly comply with the requirements of relevant laws and regulations, obtain the informed consent or separate consent of the personal information subject, and carry out subsequent data use and processing within the scope of laws and regulations and the authorization of the personal information subject.

[0050] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0051] 1) Microservices refer to a single functional application consisting of multiple loosely coupled and independently deployable sub-services; while micro-frontends are based on microservices and refer to the division of a functional application into multiple sub-functional applications or components according to different dimensions. These sub-functional applications or components are loaded by a main application (a sub-application) to realize the corresponding functions of the functional application; that is, in micro-frontends, a functional application is an aggregation of multiple sub-applications or components.

[0052] 2) Components are the basic elements that make up a page. For example, buttons, input boxes, and drop-down selection boxes are all components. Furthermore, combining components creates a more complex component. In a component system, independent and reusable components can be used to combine into an application, thus the application's page can be abstracted as a component tree. In the embodiments of this application, the components involved are page components (templates / functional components), and page components include not only the components that make up the page but also the templates used to aggregate components.

[0053] 3) A template is the result of fixing and standardizing the structural rules of a thing; in the embodiments of this application, a template refers to a fixed and standardized page presentation form, that is, the template component involved in the embodiments of this application.

[0054] 4) Base system, a system for carrying components developed by at least two component development frameworks; in the embodiments of this application, the page acquisition device is the base system, also known as the micro front-end base system.

[0055] 5) JavaScript Object Notation (JSON) is a lightweight data-interchange format that uses a text format completely independent of programming languages ​​to store and represent data. It is used to transmit data objects composed of attribute values ​​or sequential values. Its concise and clear hierarchical structure makes JSON an ideal data exchange language; it is easy to read and write, easy for machines to parse and generate, and can effectively improve network transmission efficiency. In this embodiment, page components can be implemented using JavaScript Object Notation, referred to as "JSON".

[0056] 6) Front-end development frameworks, used to generate front-end pages, such as "React", "Vue", "Angular", "QuicikUI", "Layui", "Avalon", "Dojo", "Ember", and "Aurelia". "React" is a JavaScript library for building components within an application's pages; "Angular" is a JavaScript framework based on "TypeScript"; and "Vue" is also a progressive JavaScript framework for building pages. Here, "front-end" refers to the webpages running on the user's terminal and displayed for browsing. In this embodiment, the front-end development framework is referred to as a component development framework.

[0057] Generally, to implement micro-frontends, a front-end development framework is typically used to develop sub-applications or components, which are then aggregated into the front-end pages of the main application. However, in the process of implementing micro-frontends described above, the front-end pages are developed using a single front-end development framework, which imposes limitations. Consequently, the flexibility of page retrieval is relatively low during the implementation of micro-frontends.

[0058] Additionally, to implement micro-frontends, one can import specified libraries into a single front-end development framework to develop sub-applications or components using two different frameworks, and then aggregate these sub-applications or components into the front-end pages of the main application. However, in the process of implementing micro-frontends described above, although the front-end pages are developed using multiple different front-end development frameworks, the process requires manually importing specified libraries, which is complex and results in low page retrieval efficiency.

[0059] Based on this, embodiments of this application provide a page acquisition method, apparatus, device, computer-readable storage medium, and computer program product, which can improve the flexibility and efficiency of page acquisition. The following describes exemplary applications of the page acquisition device provided in this application. The page acquisition device provided in this application can be implemented as various types of terminals such as smartphones, smartwatches, laptops, tablets, desktop computers, smart TVs, set-top boxes, smart in-vehicle devices, portable music players, personal digital assistants, dedicated messaging devices, portable gaming devices, and smart speakers, or it can be implemented as a server. Furthermore, when the page acquisition device is implemented as a terminal, it can act as a client within the terminal in real time. The following will describe exemplary applications when the page acquisition device is implemented as a terminal.

[0060] See Figure 1 , Figure 1 This is an optional architecture diagram of the page acquisition system provided in the embodiments of this application; as shown... Figure 1As shown, to support a page retrieval application, in the page retrieval system 100, terminal 400 (page retrieval device) connects to server 200 via network 300. Server 200 provides computing services to terminal 400. Network 300 can be a wide area network (WAN), a local area network (LAN), or a combination of both. Additionally, the page retrieval system 100 also includes a database 500 for providing data support to server 200; and... Figure 1 The example shown illustrates a scenario where the database 500 is independent of the server 200. However, the database 500 can also be integrated into the server 200, and this embodiment does not limit this to any particular case.

[0061] Terminal 400 is used to obtain the components to be compiled generated by each component development framework; compile the components to be compiled to obtain page components; present multiple page components corresponding to at least two component development frameworks; and in response to the selection operation for multiple page components, aggregate the selected page components to obtain an application page, wherein the application page is the front-end page of the functional application.

[0062] In some embodiments, server 200 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, content delivery networks (CDNs), and big data and artificial intelligence platforms. Terminal 400 can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. Terminals and servers can be directly or indirectly connected via wired or wireless communication, which is not limited in this embodiment. Additionally, a client can be installed on terminal 400, and terminal 400 executes the page acquisition method provided in this embodiment by running the client.

[0063] See Figure 2 , Figure 2 This is one of the embodiments provided in this application. Figure 1 A schematic diagram of the terminal's structural composition. Figure 2 The terminal 400 shown includes at least one processor 410, a memory 450, at least one network interface 420, and a user interface 430. The various components in the terminal 400 are coupled together via a bus system 440. It is understood that the bus system 440 is used to implement communication between these components. In addition to a data bus, the bus system 440 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 2 The general labeled all buses as Bus System 440.

[0064] Processor 410 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0065] User interface 430 includes one or more output devices 431 that enable the presentation of media content, including one or more speakers and / or one or more visual displays. User interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0066] The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 450 may optionally include one or more storage devices physically located away from the processor 410.

[0067] The memory 450 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 450 described in this application embodiment is intended to include any suitable type of memory.

[0068] In some embodiments of this application, memory 450 is capable of storing data to support various operations. Examples of such data include programs, modules, and data structures, or subsets or supersets thereof, as illustrated below.

[0069] Operating system 451 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks;

[0070] The network communication module 452 is used to reach other computer devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 including: Bluetooth, Wi-Fi, and Universal Serial Bus (USB), etc.

[0071] Presentation module 453 is configured to enable the presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 431 associated with user interface 430 (e.g., a display screen, a speaker, etc.).

[0072] The input processing module 454 is used to detect and translate one or more user inputs or interactions from one or more input devices 432.

[0073] In some embodiments of this application, the page acquisition device provided in this application can be implemented in software. Figure 2 A page acquisition device 455 stored in memory 450 is shown. This device can be software in the form of programs or plug-ins, and includes the following software modules: component acquisition module 4551, component encoding module 4552, component combination module 4553, component aggregation module 4554, page rendering module 4555, page interaction module 4556, page management module 4557, and application management module 4558. These modules are logically connected and can therefore be arbitrarily combined or further divided according to their implemented functions. The functions of each module will be described below.

[0074] In some other embodiments of this application, the page acquisition device provided in this application can be implemented in hardware. As an example, the page acquisition device provided in this application can be a processor in the form of a hardware decoding processor, which is programmed to execute the page acquisition method provided in this application. For example, the processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0075] The following will describe the page acquisition method provided in this application embodiment by referring to exemplary applications and implementations of the page acquisition device provided in the embodiments of this application.

[0076] See Figure 3 , Figure 3 This is an optional flowchart illustrating the page acquisition method provided in the embodiments of this application, which will be combined with... Figure 3 The steps shown are explained.

[0077] S301. Obtain the components to be compiled generated by each component development framework.

[0078] In this embodiment, developers use different component development frameworks to develop components. The page acquisition device acquires the components developed by each component development framework and determines the acquired components developed by each component development framework as components to be compiled. Here, the page acquisition device can be the component to be compiled generated by each component development framework, which is received from other devices. For example, a device running a component development framework can send the component to the page acquisition device after completing component development; it can also be the component to be compiled developed by each component development framework read from a data storage device; etc. This embodiment does not specifically limit this.

[0079] It should be noted that the page acquisition method provided in this application embodiment is applied in a micro-frontend scenario, where the page is composed of aggregated different components; the component development framework is used to develop components to be aggregated into a page; the component to be compiled is the component developed by the component development framework, which is a component waiting to be compiled by the page acquisition device, where compilation refers to a data transformation process. Furthermore, the component to be compiled can be one or both of the elements (functional components) and the page's aggregation logic (template components) in the page; this application embodiment does not specifically limit this.

[0080] S302. Compile the component to be compiled to obtain the page component.

[0081] In this embodiment of the application, after the page acquisition device obtains the component to be compiled, it compiles the component to be compiled to convert it into a format that the page acquisition device can support; wherein, the compiled component to be compiled is the page component, and the data format corresponding to the page component is a data format supported by the page acquisition device.

[0082] It should be noted that different component development frameworks produce different components to be compiled. To ensure compatibility between these components, the page acquisition device compiles the components according to its own data format, thus supporting components developed by multiple frameworks and enabling cross-framework page development. Page components are the basic elements used to aggregate a page; they can be one or both of the elements within the page and the page's aggregation logic. This application does not specifically limit this.

[0083] For example, when the component development framework is "React", the component to be compiled is a ".jsx" format file; however, the page obtains a file in ".js" format that the device can support. Therefore, the ".jsx" format file needs to be compiled to obtain a ".js" format file. Similarly, when the component development framework is "Vue", the component to be compiled is a ".vue" format file; however, the page obtains a file in ".js" format that the device can support. Therefore, the ".vue" format file needs to be compiled to obtain a ".js" format file.

[0084] S303. In at least two component development frameworks, combine the page components corresponding to each component development framework to obtain multiple page components.

[0085] In this embodiment, the page acquisition device acquires the components to be compiled for each component development framework, compiles them into page components, and then combines the page components corresponding to each component development framework to obtain multiple page components. Here, "different component development frameworks" refers to at least two component development frameworks. In other words, multiple page components correspond to at least two component development frameworks.

[0086] S304. Present multiple page components, respond to the selection operation for multiple page components, aggregate the selected page components, and obtain the application page.

[0087] In this embodiment, after obtaining multiple page components, the page acquisition device presents these components to select and aggregate them. Specifically, when a user selects from the presented page components, the page acquisition device receives a selection operation for each component. This selection operation selects the page component to be aggregated into a page. Responding to this selection operation, the page acquisition device obtains the selected page component, which is then used to aggregate the page. The page acquisition device then aggregates this page component, and the resulting aggregation is the application page.

[0088] It should be noted that the application page is the front-end page of the functional application, which is a page aggregated by selecting page components.

[0089] Understandably, by compiling components developed by each of at least two component development frameworks, it becomes possible to simultaneously support multiple page components corresponding to at least two component development frameworks. Then, by visually aggregating multiple page components, the front-end page of the functional application is obtained. In other words, the application page is obtained by aggregating page components developed by different component development frameworks, which is a cross-framework page acquisition method. This improves the flexibility of page acquisition during the micro-frontend implementation process.

[0090] See Figure 4 , Figure 4 This is another optional flowchart illustrating the page acquisition method provided in the embodiments of this application; as shown below. Figure 4 As shown in the embodiment of this application, S304 is followed by S305 to S307; that is, after the page acquisition device responds to the selection operation for multiple page components, aggregates the selected page components to obtain the application page, the page acquisition method further includes S305 to S307. Each step is described below.

[0091] S305. In response to rendering operations on the application page, obtain the rendering logic corresponding to the selected page component.

[0092] It should be noted that after the page acquisition device aggregates the application page, when a user browses the application page, or when the aggregator previews the application page, the page acquisition device receives a rendering operation for the application page. At this time, the page acquisition device responds to the rendering operation and renders the application page. Here, when rendering the application page, the page acquisition device first obtains the rendering logic corresponding to the application page. This rendering logic is the rendering logic corresponding to the selected page components that were aggregated into the application page, and this rendering logic is used to render the aggregation result of the selected page components.

[0093] S306. During the execution of rendering logic, for each page component in the selected page components, load the corresponding framework runtime.

[0094] It should be noted that the page acquisition device renders the application page by executing rendering logic. During this process, since the rendering logic is an aggregation of the rendering information for each selected page component, the page acquisition device loads the runtime of the component development framework corresponding to that page component when executing the rendering logic for that component. The rendering of the page component is then performed based on the loaded runtime. Here, the framework runtime refers to the runtime of the component development framework, and the runtime is the data corresponding to the component development framework used to support the rendering of page components.

[0095] S307. Based on the framework runtime corresponding to each loaded page component, the application page is rendered.

[0096] It should be noted that when the page acquisition device completes the loading of the framework runtime corresponding to each selected page component, the rendering of the selected page component is also completed. At this time, the rendered result is the application page, and thus the presentation of the application page is completed.

[0097] Understandably, the page-fetching device loads the framework runtime corresponding to each selected page component on demand for the application page, ensuring the rendering of the application page.

[0098] In this embodiment of the application, S305 can be implemented through S3051 and S3052; that is, the page acquisition device responds to the rendering operation for the application page and acquires the rendering logic corresponding to the selected page component, including S3051 and S3052. Each step is described below.

[0099] S3051. In response to rendering operations on the application page, obtain the aggregation logic between the various page components in the selected page component.

[0100] It should be noted that after the page acquisition device receives the rendering operation, in response to the rendering operation, it first obtains the aggregation logic between the various page components in the selected page component. This aggregation logic is the layout information between the various pages in the selected page component, which represents the relationship between the various pages in the selected page component.

[0101] S3052. Based on aggregation logic, obtain the implementation logic corresponding to each page component in the selected page components, and combine the obtained implementation logic corresponding to each page component into the rendering logic corresponding to the selected page component.

[0102] In this embodiment, the page acquisition device analyzes the obtained aggregation logic to obtain the aggregation position of each page component in the selected page components, and determines the rendering order of each page component based on the aggregation position. Then, according to the rendering order, the implementation logic corresponding to each page component in the selected page components is obtained, and the obtained implementation logic corresponding to each page component is combined to obtain the rendering logic corresponding to the selected page component. Here, the implementation logic is the implementation information of each page component (e.g., implementation code, "JSON" description), and the implementation logic is the implementation information supported by the page acquisition device, and is unrelated to the implementation information supported by the component development framework corresponding to the page component.

[0103] It should be noted that when the page acquisition device compiles the component to be compiled, it compiles the implementation logic of the component to be compiled to obtain the implementation logic corresponding to the page component. The implementation logic of the component to be compiled is the implementation information corresponding to the component development framework, while the implementation logic of the page component is the implementation information corresponding to the page acquisition device.

[0104] In this embodiment, S307 can be implemented through S3071 to S3073; that is, the page acquisition device presents the application page based on the framework corresponding to each loaded page component during runtime, including S3071 to S3073. Each step is described below.

[0105] S3071. Based on the framework runtime corresponding to each loaded page component, obtain the data to be converted for each page component.

[0106] In this embodiment of the application, when rendering each page component among the selected page components, the page acquisition device also needs to rely on the background data to complete the process. Here, the page acquisition device acquires the background data when the framework is loaded and running. The acquired background data is called the data to be converted, such as the table data in the table component, or the data in the form.

[0107] S3072. Based on the data format of the component development framework corresponding to the page component, perform data conversion on the data to be converted to obtain the data to be displayed.

[0108] It should be noted that, in order to match the data format of the data to be converted with the data format of the component development framework corresponding to the page component, the page acquisition device performs data conversion on the data to be converted based on the data format of the component development framework corresponding to the page component, so as to obtain the data to be displayed that matches the data format of the corresponding component development framework. The data to be displayed is the converted data.

[0109] S3073. Based on the data to be displayed, present the application page.

[0110] In this embodiment of the application, the page acquisition device completes the presentation of the application page by displaying the data to be displayed for each page component in the selected page components while executing the implementation logic.

[0111] Understandably, the page-fetching device uses data conversion to enable the data obtained from the backend to be converted into the data format of the components corresponding to different component development frameworks as needed, providing data support for component rendering and thus improving the feasibility of application page rendering.

[0112] See Figure 5 , Figure 5This is another optional flowchart illustrating the page acquisition method provided in the embodiments of this application; as shown Figure 5 As shown in the embodiment of this application, S307 is followed by S308 and S309; ​​that is, after the page acquisition device renders the application page based on the framework corresponding to each loaded page component, the page acquisition method further includes S308 and S309. Each step will be described below.

[0113] S308. In response to the first application operation performed on the application page, instruct the triggered page component to send a first interaction instruction to the associated page component through the message center.

[0114] In this embodiment, when a user interacts with a page component on an application page, the page acquisition device obtains a first application operation applied to the application page. Since the first application operation obtained by the page acquisition device is used to trigger interaction between other page components and the triggered page component, the page acquisition device, in response to the first application operation, instructs the triggered page component to send a first interaction instruction to the associated page component via a message center. This enables the associated page component to perform interaction between page components based on the first interaction instruction, such as a linked effect on the page. The first interaction instruction is the instruction for the triggered page component to interact with other page components.

[0115] S309. Instruct the associated page component to execute the first interaction instruction, and based on the execution result of the first interaction instruction, present the interaction information corresponding to the associated page component.

[0116] It should be noted that the page obtains the device instruction to the associated page component to execute the first interaction instruction. After the associated page component completes the execution of the first interaction instruction, the interaction between the triggered page component and the associated page component is completed, and thus the interaction information corresponding to the associated page component is presented.

[0117] See also Figure 5 S307 is followed by S310 and S311; that is, after the page acquisition device renders the application page based on the framework corresponding to each loaded page component, the page acquisition method further includes S310 and S311. Each step is described below.

[0118] S310, in response to a second application operation performed on the application page, obtains the second interaction instruction sent by the triggered page component through the message center.

[0119] In this embodiment, when a user interacts with an application page, the page acquisition device receives a second application operation applied to the page. Since this second application operation triggers interaction between the page acquisition device and the triggered page component, the page acquisition device, in response to the second application operation, retrieves a second interaction instruction sent by the triggered page component through a message center. This enables the associated page component to interact with the page acquisition device based on the second interaction instruction, such as refreshing the page or modifying the page route. The second interaction instruction is the instruction used by the triggered page component to interact with the page acquisition device.

[0120] S311. Execute the second interaction instruction, and based on the execution result of the second interaction instruction, perform system interaction processing on the application page.

[0121] It should be noted that the page-fetching device executes the second interaction instruction. Once the second interaction instruction is executed, the interaction between the triggered page component and the page-fetching device is complete, thus completing the processing of the application page. This interaction between the triggered page component and the page-fetching device is a system-level information processing process, hence called system interaction processing; this system interaction processing can be implemented through hook functions.

[0122] Understandably, by adopting the publish-subscribe design pattern and using a message center to enable interactions between page components and between page components and the device that accesses the page, the message center, being a globally unique instance, can ensure the correct delivery of interactive messages.

[0123] In this embodiment, the selection operation includes a template component selection operation and a functional component selection operation. The selected page component includes the selected template component and the selected functional component. The selected target component is used to determine the layout information of the selected functional component. Thus, S304 can be implemented through S3041 and S3042. That is, in response to the selection operation for multiple page components, the page acquisition device aggregates the selected page components to obtain the application page, including S3041 and S3042. Each step is described below.

[0124] S3041. In response to a template component selection operation for multiple page components, obtain the selected template component.

[0125] S3042. In response to the function component selection operation for multiple page components, the selected function components are aggregated based on the selected template component to obtain the application page.

[0126] It should be noted that each application page to be aggregated implements a sub-function of the functional application. Therefore, based on the sub-function corresponding to each application page to be aggregated, the template component corresponding to the application page to be aggregated can be determined, i.e., the selected template component; and based on the sub-function corresponding to the application page to be aggregated and the selected template component, the page component corresponding to the application page to be aggregated can be determined, i.e., the selected target component. Here, the page acquisition device aggregates the selected functional components based on the selected template components, thus completing the aggregation of the application pages to be aggregated. The resulting aggregation is the application page. Specifically, the target component selection operation is used to determine the selected template component, and the functional component selection operation is used to determine the selected functional component.

[0127] In this embodiment of the application, S304 is followed by S312 to S314; that is, after the page acquisition method responds to the selection operation for multiple page components, aggregates the selected page components to obtain the application page, the page acquisition method further includes S312 to S314. Each step is described below.

[0128] S312. Obtain at least one application page corresponding to the functional application.

[0129] It should be noted that the function corresponding to the functional application is implemented through at least one application page; the page acquisition device acquires at least one application page based on the acquisition method of one application page; and when there are multiple application pages, the association between the multiple application pages is established. At this time, the page acquisition device also obtains at least one application page corresponding to the functional application.

[0130] S313. Based on at least one application page, present a list of application pages.

[0131] It should be noted that the presented application page list includes at least one application page and corresponding page settings controls for each application page. These page settings controls include one or more of the following: page information settings controls, component configuration controls, status settings controls, interface configuration controls, and preview controls. Specifically, the page information settings controls are used to trigger the setting of basic information such as the application page's name, size, and route; the component configuration controls are used to trigger the configuration of the page components corresponding to the application page; the status settings controls are used to trigger the application page's usage status, such as online or offline; the interface configuration controls are used to trigger the configuration of the data format for backend data; and the preview controls are used to trigger a preview of the application page.

[0132] S314. In response to a page setup operation performed on a page setup control, perform a page setup operation on the application page corresponding to the page setup control.

[0133] It should be noted that when a page setup operation is applied to the page information setting control within the page setup controls, the device acquires the page to set basic information such as the application page's name, size, and route. When a page setup operation is applied to the component configuration control within the page setup controls, the device acquires the page to configure the page components for the application page. When a page setup operation is applied to the status setting control within the page setup controls, the device acquires the page to set the usage status of the application page. When a page setup operation is applied to the interface configuration control within the page setup controls, the device acquires the page to configure the data format of the backend data for each page component corresponding to the application page. When a page setup operation is applied to the preview control within the page setup controls, the device acquires the page to preview the application page.

[0134] In this embodiment of the application, S312 is followed by S315 to S317; that is, after the page acquisition method acquires at least one application page corresponding to the functional application, the page acquisition method further includes S315 to S317, and each step is described below.

[0135] S315. Obtain at least one functional application.

[0136] S316. Based on at least one functional application, present a list of functional applications.

[0137] It should be noted that the presented list of functional applications includes at least one functional application and an application settings control for each functional application. The application settings control is used to trigger the setting of basic information such as the name and domain name of the functional application.

[0138] S317. In response to an application settings operation performed on the application settings control, perform an application settings operation for the function application corresponding to the application settings control.

[0139] It should be noted that when managing and configuring a functional application by triggering the application settings control, the page acquisition device also receives the application settings operation performed on the application settings control; at this time, the application acquisition device responds to the application settings operation and sets basic information such as the name and domain name of the application page.

[0140] The following will describe an exemplary application of the embodiments of this application in a real-world application scenario.

[0141] See Figure 6 , Figure 6 This is an architecture diagram of an exemplary page retrieval system provided in an embodiment of this application; as shown... Figure 6As shown, the page acquisition system 6-1 includes a functional application terminal 6-11 (at least one functional application), a micro-frontend base system 6-12 (page acquisition device), and a data terminal 6-13. The functional application terminal 6-11 includes a first operation platform 6-111, a video management system 6-112, a browser operation platform 6-113, and an interactive operation platform 6-114 (corresponding to the aforementioned functional applications); the micro-frontend base system 6-12 includes application management 6-121, page management 6-122, template / functional components 6-123, and interface management 6-124; the data terminal 6-13 includes a database 6-131, a Common Gateway Interface (CGI) 6-132, a Remote Procedure Call (RPC) 6-133, and a third-party interface 6-134.

[0142] The following is about Figure 6 The modules in the micro-frontend base system 6-12 will be explained separately.

[0143] Figure 6 Interface management 6-124 in the document is the interface corresponding to templates / functional components (corresponding to the page components mentioned above, including page templates (template components) and functional components). It is used for data adaptation. That is, when the backend data returned from the backend data terminal 6-1 is displayed through the template / functional component, it is used to convert the data format of the backend data into the data format of the template / functional component. This ensures that even if the template / functional component is developed using different frontend development frameworks (component development frameworks), it can still achieve compatibility with the data format of the backend data.

[0144] See Figure 7 , Figure 7 This is a schematic diagram illustrating an exemplary data conversion method provided in an embodiment of this application; as shown... Figure 7 As shown, Figure 6 The interface management 6-124 in the code can be implemented as a "json2json parsing engine" to parse data transformation rules and convert source data 7-1 (source "json", data to be transformed) into target data 7-2 (target "json", data to be displayed). Here, source data 7-1 is... Figure 6 The data returned from the backend in section 6-1 is transformed according to the data format of the frontend development framework corresponding to the template / functional component. Figure 6 The data format of the backend data returned by the data terminal 6-1 is determined, and the target data 7-2 is data that is adapted to the template / functional component.

[0145] For example, see Figure 8 , Figure 8This is a schematic diagram illustrating another exemplary data conversion provided in the embodiments of this application; as shown Figure 8 As shown, when the source data 8-1 is “{foo:{bar:{baz:1}}}” and the data transformation rule 8-2 is “{new_foo:'foo.bar.baz'}”, then the target data 8-3 is {new_foo:1}.

[0146] Figure 6 The templates / functional components 6-123 include page templates and functional components. Page templates include system page templates and custom page templates. Functional components include system functional components and custom functional components. System page templates and system functional components do not require compilation, while custom page templates and custom functional components are configured through compilation. Figure 6 The micro front-end base system in 6-12.

[0147] See Figure 9 , Figure 9 This is a schematic diagram of an exemplary page template provided in an embodiment of this application; as shown... Figure 9 As shown, in application page 9-1, area 9-11 is a table template within a page template, including the page operation area 9-111, the search area 9-112, the information display area 9-113, and the operation column 9-114; among them, the "json" description corresponding to the page operation area 9-111 is:

[0148] {

[0149] type:"table",

[0150] areas:[{

[0151] type:"option", name:"Page Operation Area"

[0152] components:[{type:"component",shape:"button",name:"..."}]

[0153] },

[0154] }

[0155] See Figure 10 , Figure 10 This is a schematic diagram of an exemplary functional component provided in an embodiment of this application; as shown... Figure 10 As shown in the application page 10-1, operation components 10-11, 10-12, and cell component 10-13 are all custom functional components; among them, the "json" description corresponding to cell component 10-13 is:

[0156] {

[0157] "type":"component",

[0158] "shape":"textarea", "text":"Popular high-level.....", "url":"h…: / / …"

[0159] }

[0160] It should be noted that custom page templates and custom functional components are configured through compilation. Figure 6 The process of the micro-front-end base system 6-12 is described in detail. Figure 11 , Figure 11 This is a schematic diagram of an exemplary configuration template / functional component provided in an embodiment of this application; as shown... Figure 11 As shown, this example illustrates templates / functional components 11-21 (e.g., "React" templates / functional components), 11-22 (e.g., "Vue" templates / functional components), and 11-23 (e.g., "Angular" templates / functional components) developed by developer 11-1 using three different front-end development frameworks. After compilation 11-3, the templates / functional components are completed. Figure 6 The visual configuration of the micro-frontend base system 6-12 in the middle, thus, Figure 6 The micro front-end base system 6-12 includes template / functional components 11-41 (compiled template / functional component 11-21), 11-42 (compiled template / functional component 11-22), and 11-43 (compiled template / functional component 11-23).

[0161] Figure 6 Page Management 6-122 in the document is used to generate application pages through visual configuration, and is also used to set the interface, name, route, online and offline status of application pages, as well as preview application pages.

[0162] For example, see Figure 12 , Figure 12 This is a schematic diagram of an exemplary application page management page provided in an embodiment of this application; as shown... Figure 12As shown, the application page management page 12-1 displays a title 12-11, a search control 12-12, and an application page list 12-13. Within the application page list 12-13, each application page is presented through three pieces of information: page name, associated menu, and page identifier. Operations (page settings controls) for each application page include configuration (corresponding to the page information settings controls, component configuration controls, and interface configuration controls mentioned above), offline (corresponding to the status settings controls mentioned above), and preview (corresponding to the preview controls mentioned above). Here, configuration refers to configuring information such as the application page's name, components, and routes. When an application page is online, it is displayed as offline; offline is used to set the application page to an offline state. Conversely, when an application page is offline, it is displayed as online; online is used to set the application page to an online state. Preview is used to preview the application page.

[0163] Figure 6 Application Management 6-121 is used to set the domain name of a functional application, as well as basic information such as the name of the functional application.

[0164] It should be noted that when both the page template and functional components are described using "JSON", Figure 6 Page Management 6-122 and Figure 6 The application management in sections 6-121 is essentially implemented by modifying "json".

[0165] The following is about Figure 6 The process of implementing application page presentation in the micro-frontend base system 6-12 is explained.

[0166] See Figure 13 , Figure 13 This is a schematic diagram of an exemplary rendered application page provided in an embodiment of this application; as shown... Figure 13 As shown, Figure 6 The rendering engine in the micro-frontend base system 6-12 uses the "JSON" description 13-1 of the template / functional component corresponding to the application page to form the rendering logic 13-2. By executing the rendering logic 13-2, the application page 13-3 will be presented, thus realizing the rendering of the application page 13-3.

[0167] in, Figure 13 The rendering of application page 13-3 is based on loading the runtimes (framework runtimes) of different front-end development frameworks. See also Figure 14 , Figure 14 This is a schematic diagram illustrating an exemplary loading framework runtime provided in an embodiment of this application; as shown... Figure 14 As shown, Figure 6 The micro-frontend base system generated in 6-12 Figure 13In application page 13-3, templates / functional components 11-41 need to load runtime 14-21 (e.g., the "React" runtime) during rendering, templates / functional components 11-42 need to load runtime 14-22 (e.g., the "Vue" runtime) during rendering, and templates / functional components 11-43 need to load runtime 14-23 (e.g., the "Angular" runtime) during rendering. It is easy to see that when another application page being rendered does not include the templates / functional components corresponding to one of the front-end development frameworks, the runtime corresponding to the front-end development framework is unloaded.

[0168] The following is about Figure 6 The communication mechanism corresponding to the micro-frontend base system 6-12 in the text is explained. See also Figure 15 , Figure 15 This is an exemplary communication diagram provided in an embodiment of this application; as shown... Figure 15 As shown, Figure 11 Templates / functional components 11-41, 11-42, 11-43 and... Figure 6 The micro-frontend base systems 6-12 all communicate with each other through message center 15-1.

[0169] Understandably, based on the publish-subscribe design pattern, communication between templates / functional components and between templates / functional components and the micro-frontend base system is achieved through a globally unique message center, ensuring the correct delivery of messages. Furthermore, through various hook functions and communication mechanisms, interactions such as component linkage, application page refresh, and route changes can be realized.

[0170] The following description continues to illustrate the exemplary structure of the page acquisition device 455 provided in the embodiments of this application as a software module. In some embodiments, such as Figure 2 As shown, the software module stored in the page fetching device 455 of the memory 450 may include:

[0171] Component acquisition module 4551 is used to acquire the components to be compiled generated by each component development framework;

[0172] The component encoding module 4552 is used to compile the component to be compiled to obtain the page component;

[0173] The component combination module 4553 is used to combine the page components corresponding to each of the at least two component development frameworks to obtain a plurality of page components.

[0174] The component aggregation module 4554 is used to present multiple page components. In response to a selection operation on the multiple page components, the selected page components are aggregated to obtain an application page, wherein the application page is the front-end page of the functional application.

[0175] In this embodiment of the application, the page acquisition device 455 further includes a page presentation module 4555, which is used to acquire the rendering logic corresponding to the selected page component in response to the rendering operation for the application page; during the execution of the rendering logic, for each of the selected page components, the corresponding framework runtime is loaded, wherein the framework runtime is the runtime of the component development framework; and the application page is presented based on the framework runtime corresponding to each loaded page component.

[0176] In this embodiment of the application, the page rendering module 4555 is further configured to, in response to the rendering operation for the application page, obtain the aggregation logic between each page component in the selected page component; based on the aggregation logic, obtain the implementation logic corresponding to each page component in the selected page component, and combine the obtained implementation logic corresponding to each page component into the rendering logic corresponding to the selected page component.

[0177] In this embodiment of the application, the page presentation module 4555 is further configured to: obtain the data to be converted corresponding to each page component based on the framework runtime corresponding to each loaded page component; perform data conversion on the data to be converted based on the data format of the component development framework corresponding to the page component to obtain the data to be displayed; and present the application page based on the data to be displayed.

[0178] In this embodiment of the application, the page acquisition device 455 further includes a page interaction module 4556, which is used to respond to a first application operation performed on the application page, instruct the triggered page component to send a first interaction instruction to the associated page component through the message center; instruct the associated page component to execute the first interaction instruction, and present interactive information corresponding to the associated page component based on the execution result of the first interaction instruction.

[0179] In this embodiment of the application, the page interaction module 4556 is further configured to respond to a second application operation performed on the application page, obtain a second interaction instruction sent by the triggered page component through the message center; execute the second interaction instruction, and perform system interaction processing on the application page based on the execution result of the second interaction instruction.

[0180] In this embodiment, the selection operation includes a template component selection operation and a functional component selection operation. The selected page component includes a selected template component and a selected functional component. The component aggregation module 4554 is further configured to obtain the selected template component in response to the template component selection operation for multiple page components; and to aggregate the selected functional components based on the selected template component in response to the functional component selection operation for multiple page components to obtain the application page.

[0181] In this embodiment, the page acquisition device 455 further includes a page management module 4557, configured to acquire at least one application page corresponding to the functional application; present an application page list based on the at least one application page, wherein the presented application page list includes at least one application page and a page setting control corresponding to each application page, the page setting control including one or more of page information setting controls, component configuration controls, status setting controls, interface configuration controls, and preview controls; and perform the page setting operation on the application page corresponding to the page setting control in response to a page setting operation performed on the page setting control.

[0182] In this embodiment of the application, the page acquisition device 455 further includes an application management module 4558, configured to acquire at least one of the functional applications; present a list of functional applications based on the at least one functional application, wherein the presented list of functional applications includes at least one of the functional applications and an application settings control corresponding to each functional application; and, in response to an application settings operation performed on the application settings control, execute the application settings operation for the functional application corresponding to the application settings control.

[0183] This application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device (page fetching device) reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the page fetching method described above in this application.

[0184] This application provides a computer-readable storage medium storing executable instructions. When these executable instructions are executed by a processor, they cause the processor to execute the page acquisition method provided in this application, for example... Figure 3 The method for retrieving the page is shown.

[0185] In some embodiments of this application, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a device that includes one or any combination of the above-mentioned memories.

[0186] In some embodiments of this application, executable instructions may take the form of programs, software, software modules, scripts, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including being deployed as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0187] As an example, executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborating files (e.g., a file that stores one or more modules, subroutines, or code sections).

[0188] As an example, executable instructions can be deployed to execute on a single computer device (in which case, this single computer device is a page-fetching device), or to execute on multiple computer devices located in one location (in which case, multiple computer devices located in one location are page-fetching devices), or to execute on multiple computer devices distributed across multiple locations and interconnected via a communication network (in which case, multiple computer devices distributed across multiple locations and interconnected via a communication network are page-fetching devices).

[0189] In summary, this application embodiment compiles components developed by each of at least two component development frameworks, enabling the simultaneous support of multiple page components corresponding to at least two component development frameworks. Then, by visually aggregating multiple page components, the front-end page of the functional application is obtained. In other words, the application page is obtained by aggregating page components developed by different component development frameworks, which is a cross-framework page acquisition method. This improves the flexibility of page acquisition during the micro-frontend implementation process.

[0190] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. A method for obtaining a page, characterized in that, include: Obtain the components to be compiled generated by each component development framework; The component to be compiled is then compiled to obtain the page component; In at least two of the component development frameworks, the page components corresponding to each of the component development frameworks are combined to obtain a plurality of page components; Multiple page components are presented, and in response to a selection operation for the multiple page components, the selected page components are aggregated to obtain an application page, wherein the application page is the front-end page of a functional application; In response to a rendering operation on the application page, obtain the rendering logic corresponding to the selected page component; During the execution of the rendering logic, for each of the selected page components, the corresponding framework runtime is loaded, wherein the framework runtime is the runtime of the component development framework; Based on the framework runtime corresponding to each loaded page component, obtain the data to be converted corresponding to each page component; Parse the data conversion rules and convert the data to be converted into data to be displayed, wherein the data to be displayed is data adapted to the template or functional component; Based on the data to be displayed, the application page is presented.

2. The method according to claim 1, characterized in that, The step of obtaining the rendering logic corresponding to the selected page component in response to a rendering operation on the application page includes: In response to the rendering operation for the application page, obtain the aggregation logic between the various page components in the selected page components; Based on the aggregation logic, the implementation logic corresponding to each of the selected page components is obtained, and the obtained implementation logic corresponding to each page component is combined into the rendering logic corresponding to the selected page component.

3. The method according to claim 1 or 2, characterized in that, The data conversion rules, which convert the data to be converted into data to be displayed, include: Based on the data format of the component development framework corresponding to the page component, the data to be converted is converted to obtain the data to be displayed.

4. The method according to claim 1 or 2, characterized in that, After presenting the application page based on the data to be displayed, the method further includes: In response to a first application operation performed on the application page, the triggered page component is instructed to send a first interaction instruction to the associated page component via the message center; The associated page component is instructed to execute the first interaction instruction, and based on the execution result of the first interaction instruction, interactive information corresponding to the associated page component is presented.

5. The method according to claim 4, characterized in that, After presenting the application page based on the data to be displayed, the method further includes: In response to a second application operation performed on the application page, a second interaction instruction sent by the triggered page component is obtained through the message center; The second interactive instruction is executed, and based on the execution result of the second interactive instruction, system interaction processing is performed on the application page.

6. The method according to any one of claims 1 to 2, characterized in that, The selection operation includes a template component selection operation and a functional component selection operation. The selected page components include the selected template component and the selected functional component. The step of responding to a selection operation for multiple page components by aggregating the selected page components to obtain an application page includes: In response to the template component selection operation for the plurality of page components, the selected template component is obtained; In response to the function component selection operation for multiple page components, the selected function components are aggregated based on the selected template component to obtain the application page.

7. The method according to any one of claims 1 to 2, characterized in that, After aggregating the selected page components to obtain the application page in response to a selection operation on multiple page components, the method further includes: Obtain at least one of the application pages corresponding to the aforementioned function; Based on at least one of the application pages, an application page list is presented, wherein the presented application page list includes at least one application page and a page setting control corresponding to each application page, and the page setting control includes one or more of page information setting control, component configuration control, status setting control, interface configuration control and preview control; In response to a page setup operation performed on the page setup control, the page setup operation is performed on the application page corresponding to the page setup control.

8. The method according to claim 7, characterized in that, After obtaining at least one application page corresponding to the functional application, the method further includes: Obtain at least one of the aforementioned functional applications; Based on at least one of the aforementioned functional applications, a list of functional applications is presented, wherein the presented list of functional applications includes at least one of the aforementioned functional applications and an application settings control corresponding to each of the aforementioned functional applications; In response to an application settings operation performed on the application settings control, the application settings operation is performed on the functional application corresponding to the application settings control.

9. A page acquisition device, characterized in that, include: The component acquisition module is used to acquire the components to be compiled generated by each component development framework; The component encoding module is used to compile the component to be compiled to obtain the page component; A component combination module is used to combine the page components corresponding to each of the at least two component development frameworks to obtain multiple page components. The component aggregation module is used to present multiple page components. In response to a selection operation for the multiple page components, the selected page components are aggregated to obtain an application page, wherein the application page is the front-end page of the functional application. The page rendering module is used to respond to the rendering operation for the application page and obtain the rendering logic corresponding to the selected page component. During the execution of the rendering logic, for each of the selected page components, the corresponding framework runtime is loaded, wherein the framework runtime is the runtime of the component development framework; The page rendering module is also used to obtain the data to be converted for each page component based on the framework runtime corresponding to each loaded page component; Parse the data conversion rules and convert the data to be converted into data to be displayed, wherein the data to be displayed is data adapted to the template or functional component; Based on the data to be displayed, the application page is presented.

10. The apparatus according to claim 9, characterized in that, The page rendering module is further configured to, in response to the rendering operation for the application page, obtain the aggregation logic between the various page components in the selected page components; Based on the aggregation logic, the implementation logic corresponding to each of the selected page components is obtained, and the obtained implementation logic corresponding to each page component is combined into the rendering logic corresponding to the selected page component.

11. The apparatus according to claim 9 or 10, characterized in that, The page presentation module is also used to perform data conversion on the data to be converted based on the data format of the component development framework corresponding to the page component, so as to obtain the data to be displayed.

12. The apparatus according to claim 9 or 10, characterized in that, The device further includes: A page interaction module is used to respond to a first application operation performed on the application page and instruct the triggered page component to send a first interaction instruction to the associated page component through the message center. The associated page component is instructed to execute the first interaction instruction, and based on the execution result of the first interaction instruction, interactive information corresponding to the associated page component is presented.

13. The apparatus according to claim 12, characterized in that, The page interaction module is also used to respond to a second application operation performed on the application page by obtaining a second interaction instruction sent by the triggered page component through the message center; The second interactive instruction is executed, and based on the execution result of the second interactive instruction, system interaction processing is performed on the application page.

14. The apparatus according to any one of claims 9 to 10, characterized in that, The selection operation includes a template component selection operation and a functional component selection operation. The selected page components include the selected template component and the selected functional component. The component aggregation module is further configured to obtain the selected template component in response to the template component selection operation for multiple page components; In response to the function component selection operation for multiple page components, the selected function components are aggregated based on the selected template component to obtain the application page.

15. The apparatus according to any one of claims 9 to 10, characterized in that, The device further includes: The page management module is used to obtain at least one application page corresponding to the function application; Based on at least one of the application pages, an application page list is presented, wherein the presented application page list includes at least one application page and a page setting control corresponding to each application page, and the page setting control includes one or more of page information setting control, component configuration control, status setting control, interface configuration control and preview control; In response to a page setup operation performed on the page setup control, the page setup operation is performed on the application page corresponding to the page setup control.

16. The apparatus according to claim 15, characterized in that, The device further includes: The application management module is used to acquire at least one of the aforementioned functional applications; Based on at least one of the aforementioned functional applications, a list of functional applications is presented, wherein the presented list of functional applications includes at least one of the aforementioned functional applications and an application settings control corresponding to each of the aforementioned functional applications; In response to an application settings operation performed on the application settings control, the application settings operation is performed on the functional application corresponding to the application settings control.

17. A page acquisition device, characterized in that, include: Memory, used to store executable instructions; A processor, when executing executable instructions stored in the memory, implements the page fetching method according to any one of claims 1 to 8.

18. A computer-readable storage medium, characterized in that, It stores executable instructions for implementing the page fetching method according to any one of claims 1 to 8 when executed by a processor.

19. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the page acquisition method according to any one of claims 1 to 8.

Images