CN116932950A

CN116932950A - Page loading method, device, equipment and computer readable storage medium

Info

Publication number: CN116932950A
Application number: CN202210332032.6A
Authority: CN
Inventors: 陈泽凯; 蔡荧园
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2022-03-30
Filing date: 2022-03-30
Publication date: 2023-10-24

Abstract

The application provides a page loading method, a page loading device, page loading equipment and a computer readable storage medium; the embodiment of the application can be applied to various scenes such as cloud technology, artificial intelligence, intelligent traffic, vehicle-mounted and the like, and relates to the cloud technology; the method comprises the following steps: responding to an access operation of a target access portal for an active page, generating a page loading request, wherein the target access portal is any one of a plurality of access portals corresponding to a plurality of running platforms, and the plurality of access portals are issued by configuration equipment for the active page; sending a page loading request to cloud equipment; receiving a page configuration file returned by the cloud device aiming at a page loading request; analyzing the page configuration file through a page processing engine corresponding to the target access inlet to obtain a component list and configuration information, and rendering an active page based on the component list and the configuration information; and displaying the rendered active page. By the method and the device, the running platform supporting loading of the active page can be increased.

Description

Page loading method, device, equipment and computer readable storage medium

Technical Field

The present application relates to cloud technologies, and in particular, to a method, an apparatus, a device, and a computer readable storage medium for loading pages.

Background

The development of online retail industry has enabled users to order their own favorite items without going home. In the on-line retail industry, users are often attracted by way of configuring and distributing active pages.

In the related art, the configuration of the active page is mainly realized based on a Web page (Web), namely, development is required on the Web page through hypertext markup language (Hyper Text Markup Language, HTML), and then a browser component is used for parsing and rendering to obtain the active page. However, in this way, the active page needs to run under the web page platform, i.e. there is a greater restriction on the loading of the active page, resulting in fewer running platforms capable of supporting loading the active page.

Disclosure of Invention

The embodiment of the application provides a page loading method, a device, equipment, a computer readable storage medium and a program product, which can increase an operation platform supporting loading of active pages.

The technical scheme of the embodiment of the application is realized as follows:

The embodiment of the application provides a page loading method, which comprises the following steps:

generating a page loading request in response to an access operation of a target access portal for an active page; the target access portal is any one of a plurality of access portals corresponding to a plurality of operation platforms, and the plurality of access portals are issued by configuration equipment aiming at the active page;

sending the page loading request to cloud equipment;

receiving a page configuration file returned by the cloud device for the page loading request;

analyzing the page configuration file through a page processing engine corresponding to the target access inlet to obtain a component list and configuration information, and rendering the active page based on the component list and the configuration information;

and displaying the rendered active page.

receiving a page configuration file uploaded by configuration equipment;

generating a plurality of access entries corresponding to a plurality of operation platforms aiming at the page configuration file, and returning the access entries to the configuration equipment;

receiving a page loading request sent by client equipment; the page load request is generated by the client device in response to an access operation for a target access portal of the active page; the target access portal is any one of a plurality of the access portals;

Responding to the page loading request, and acquiring a page configuration file corresponding to the active page;

and returning the page configuration file to the client equipment so that the client equipment can analyze the page configuration file into a component list and configuration information through a page processing engine corresponding to the target access entry, and rendering and displaying the active page based on the component list and the configuration information.

responsive to a selected operation for a component type in a selection area of a configuration interface, presenting candidate components for the component type in a component area of the configuration interface;

determining a target component from the candidate components in response to a drag operation of dragging the candidate components from the component area to a preview area, and displaying an active page formed based on the target component in the preview area;

in response to the operation of storing the active page, integrating a component list and configuration information of the active page into a page configuration file with a tree structure, and uploading the page configuration file to a cloud device;

Receiving a plurality of access entries under a plurality of operation platforms returned by the cloud device aiming at the page configuration file;

and issuing a plurality of access portals to client equipment so that the client equipment responds to the access operation of a target access portal in the access portals of the active page, generating a page loading request, analyzing a page configuration file returned by cloud equipment according to the page loading request through a page processing engine corresponding to the target access portal to obtain a component list and configuration information, and rendering and displaying the active page based on the component list and the configuration information.

The embodiment of the application provides a page loading device, which comprises:

the request generation module is used for responding to the access operation of the target access entrance of the active page and generating a page loading request; the target access portal is any one of a plurality of access portals corresponding to a plurality of operation platforms, and the plurality of access portals are issued by configuration equipment aiming at the active page;

the first sending module is used for sending the page loading request to cloud equipment;

The first receiving module is used for receiving a page configuration file returned by the cloud device aiming at the page loading request;

the page rendering module is used for analyzing the page configuration file through a page processing engine corresponding to the target access inlet to obtain a component list and configuration information, and rendering the active page based on the component list and the configuration information;

and the page display module is used for displaying the rendered active page.

In some embodiments of the present application, the page rendering module is further configured to pull, by the page processing engine, a target component included in the component list; rendering the target component by using the page processing engine to obtain an initial page; and adjusting the initial page according to the configuration information by the page processing engine to obtain the active page.

In some embodiments of the application, a plurality of the operating platforms includes: application software, a web program running on the application software, a browser, and at least two of web pages embedded in the web program.

In some embodiments of the present application, the page loading apparatus further includes: a component storage module; the first receiving module is further configured to receive a plurality of component packages corresponding to a plurality of operation platforms sent by the cloud device before generating a page loading request in response to an access operation of a target access portal for an active page;

The component storage module is used for storing a plurality of component packages into a local storage space;

the page rendering module is further configured to locate, by the page processing engine, a matching component package that is hit in the component list from among the plurality of component packages in the local storage space; and extracting target components contained in the component list from the matched component package by using the page processing engine.

the second receiving module is used for receiving the page configuration file uploaded by the configuration equipment;

the access generation module is used for generating a plurality of access accesses corresponding to a plurality of operation platforms aiming at the page configuration file;

the second sending module is used for returning a plurality of access portals to the configuration equipment;

the second receiving module is further used for receiving a page loading request sent by the client device; the page load request is generated by the client device in response to an access operation for a target access portal of the active page; the target access portal is any one of a plurality of the access portals;

the file acquisition module is used for responding to the page loading request and acquiring a page configuration file corresponding to the active page;

The second sending module is further configured to return the page configuration file to the client device, so that the client device parses the page configuration file into a component list and configuration information through a page processing engine corresponding to the target access entry, and renders and displays the active page based on the component list and the configuration information.

In some embodiments of the present application, the page loading apparatus further includes: a component package generating module; the file acquisition module is further used for acquiring a component configuration file before the page configuration file uploaded by the configuration equipment is received; the component configuration file records attribute information, a code file, an appearance template and component data of sub-components contained in the component in a tree structure, wherein the attribute information at least comprises icons, titles, configuration information, description contents, types and labels of the component;

the component package generating module is used for creating components according to the component configuration file, and packaging the created components to obtain an initial component package; converting the initial component package into a plurality of component packages corresponding to a plurality of operation platforms;

The second sending module is further configured to send the plurality of component packages to a client device.

the information display module is used for responding to the selection operation of the component type in the selection area of the configuration interface and displaying candidate components of the component type in the component area of the configuration interface; determining a target component from the candidate components in response to a drag operation of dragging the candidate components from the component area to a preview area, and displaying an active page formed based on the target component in the preview area;

the configuration generation module is used for responding to the save operation of the active page and integrating the component list and the configuration information of the active page into a page configuration file with a tree structure;

the third sending module is used for uploading the page configuration file to the cloud device;

the third receiving module is used for receiving a plurality of access entries under a plurality of operation platforms returned by the cloud device aiming at the page configuration file;

the third sending module is further configured to issue a plurality of access portals to a client device, so that the client device responds to an access operation of a target access portal in the access portals of the active page, generates a page loading request, and analyzes a page configuration file returned by a cloud device according to the page loading request through a page processing engine corresponding to the target access portal to obtain a component list and configuration information, and renders the active page based on the component list and the configuration information and displays the active page.

In some embodiments of the application, the configuration generation module is further configured to create a root node for the active page; creating a first node under the root node for the component list and a second node under the root node for the configuration information; and saving a tree structure formed by the root node, the first node and the second node to obtain the page configuration file.

An embodiment of the present application provides a client device, including:

a first memory for storing executable instructions;

the first processor is configured to implement the page loading method at the client device side according to the embodiment of the present application when executing the executable instruction stored in the first memory.

The embodiment of the application provides cloud equipment, which comprises:

a second memory for storing executable instructions;

and the second processor is used for realizing the page loading method of the cloud equipment side when executing the executable instructions stored in the second memory.

The embodiment of the application provides configuration equipment, which comprises the following components:

a third memory for storing executable instructions;

and the third processor is used for realizing the page loading method of the configuration equipment side when executing the executable instructions stored in the third memory.

The embodiment of the application provides a computer readable storage medium, which stores executable instructions for realizing the page loading method of a client device side provided by the embodiment of the application when a first processor is caused to execute, for realizing the page loading method of a cloud device side provided by the embodiment of the application when a second processor is caused to execute, and for realizing the page loading method of a configuration device side provided by the embodiment of the application when a third processor is caused to execute.

The embodiment of the application provides a computer program product, which comprises a computer program or an instruction, when the computer program or the instruction is executed by a first processor, the method for loading the page on the client device side provided by the embodiment of the application is realized, when the computer program or the instruction is executed by a second processor, the method for loading the page on the cloud device side provided by the embodiment of the application is realized, and when the computer program or the instruction is executed by a third processor, the method for loading the page on the configuration device side provided by the embodiment of the application is realized.

The embodiment of the application has the following beneficial effects: when an access operation for any one of the access portals is detected, a page loading request is generated so as to pull a page configuration file of the active page from the cloud device through the page loading request, and then the page configuration file is processed through any one of the access portals, namely a page processing engine corresponding to the target access portal, so that the active page is obtained.

Drawings

FIG. 1 is a schematic diagram of a page loading system according to an embodiment of the present application;

fig. 2A is a schematic structural diagram of the terminal 400 in fig. 1 according to an embodiment of the present application;

fig. 2B is a schematic structural diagram of the server 200 in fig. 1 according to an embodiment of the present application;

fig. 2C is a schematic structural diagram of the terminal 500 in fig. 1 according to an embodiment of the present application;

FIG. 3 is a schematic flow chart of a page loading method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a configuration interface provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of generating an active page provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of a plurality of access portals provided by an embodiment of the present application;

FIG. 7A is a schematic diagram of an active page provided by an embodiment of the present application;

FIG. 7B is another schematic diagram of an active page provided by an embodiment of the present application;

FIG. 7C is a further schematic illustration of an active page provided by an embodiment of the present application;

FIG. 7D is yet another schematic illustration of an active page provided by an embodiment of the present application;

FIG. 8 is another schematic flow chart of a page loading method according to an embodiment of the present application;

FIG. 9 is a schematic diagram of a component configuration file according to an embodiment of the present application;

FIG. 10 is a schematic diagram of an attribute configuration page provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of a page configuration file provided by an embodiment of the present application;

FIG. 12 is a flow chart of a process from build to load for a page provided by an embodiment of the present application;

FIG. 13 is a schematic view of a UI structure of a component provided by an embodiment of the application;

FIG. 14 is a schematic diagram of a component compiler provided by an embodiment of the present application;

figure 15 is a schematic diagram of a build page DSL provided by an embodiment of the present application;

figure 16 is a schematic diagram of the process of looking up components for DSL engines at each end provided in an embodiment of the present application;

fig. 17 is a schematic diagram of a page rendering process according to an embodiment of the present application.

Detailed Description

The present application will be further described in detail with reference to the accompanying drawings, for the purpose of making the objects, technical solutions and advantages of the present application more apparent, and the described embodiments should not be construed as limiting the present application, and all other embodiments obtained by those skilled in the art without making any inventive effort are within the scope of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is to be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments and can be combined with one another without conflict.

In the following description, the terms "first", "second", "third" and the like are merely used to distinguish similar objects and do not represent a particular ordering of the objects, it being understood that the "first", "second", "third" may be interchanged with a particular order or sequence, as permitted, to enable embodiments of the application described herein to be practiced otherwise than as illustrated or described herein.

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

Before describing embodiments of the present application in further detail, the terms and terminology involved in the embodiments of the present application will be described, and the terms and terminology involved in the embodiments of the present application will be used in the following explanation.

1) Cloud Technology (Cloud Technology) refers to a hosting Technology for integrating hardware, software, network and other series resources in a wide area network or a local area network to realize calculation, storage, processing and sharing of data.

2) Active pages, which refer to web pages in an online retail scene that are used to attract the user's interests, such that the user performs conversion operations on the active pages, such as browsing pages, collecting, forwarding, ordering, and the like.

3) In response to a condition or conditions that are used to represent the conditions or states upon which an operation is performed, one or more operations performed may be in real-time or with a set delay when the condition or state is satisfied; without being specifically described, there is no limitation in the execution sequence of the plurality of operations performed.

4) DSL (Domain-Specific Language, domain-specific) is a programming language with limited expressive capabilities that is Domain-specific.

5) The UI (interface) tree, which is used to describe the tree structure of the interactive interface, is generally represented by using a data exchange format such as JSON (JavaScript Object Notation, object profile) YAML (non-markup language).

6) And the DSL engine is used for pulling, analyzing and rendering DSL and the core module for displaying the rendered DSL.

7) AST (Abstract Syntax Tree ), which is an abstract representation of the syntax structure of source code, represents the syntax structure of a nominal language in the form of a tree, each node on the tree representing a structure in the source code.

In the related art, the configuration of the active page is mainly realized based on a Web page (Web), namely, development is required on the Web page through hypertext markup language (Hyper Text Markup Language, HTML), and then a browser component is used for parsing and rendering to obtain the active page.

However, in this way, the active page must run under the web page platform, i.e., there is a greater restriction to loading of the active page, resulting in fewer running platforms capable of supporting loading of the active page.

In addition, the parsing and rendering by the browser component requires a lot of time, which can result in slower loading of the active pages.

The embodiment of the application provides a page loading method, a page loading device, page loading equipment and a computer readable storage medium, which can increase an operation platform supporting loading of active pages. The exemplary applications of the client device, the configuration device and the cloud device provided by the embodiments of the present application are described below, where the client device and the configuration device provided by the embodiments of the present application may be implemented as various types of terminals, such as a notebook computer, a tablet computer, a desktop computer, a mobile device, and the cloud device may be implemented as a server. In the following, an exemplary application when the device client device is implemented as a terminal, the configuration device is implemented as a terminal, and the cloud device is implemented as a server will be described.

Referring to fig. 1, fig. 1 is a schematic diagram of an architecture of a page loading system according to an embodiment of the present application. In order to support a page loading application, in the page loading system 100, the terminal 400 (client device) and the terminal 500 (configuration device) are connected to the server 200 (cloud device) through the network 300, where the network 300 may be a wide area network or a local area network, or a combination of the two. In the page loading system 100, a database 600 may be further provided, and the database 600 may be integrated in the server 200 or may be independent of the server 200. Fig. 1 shows a case where the database 600 is independent of the server 200.

The terminal 500 is used to configure an active page. The terminal 500 displays candidate components of the component type in the component area of the configuration interface in response to a selected operation for the component type in the selection area of the configuration interface displayed in the graphical interface 500-1; determining a target component from the candidate components in response to a drag operation of dragging the candidate components from the component area to the preview area, and displaying an active page formed based on the target component in the preview area; in response to the save operation on the active page, integrating the component list and the configuration information of the active page into a page configuration file according to a tree structure, and uploading the page configuration file to the server 200; receiving a plurality of access entries under a plurality of operation platforms returned by the server 200 for the page configuration file; a plurality of access portals are issued to the terminal 400.

The terminal 400 is used to load an active page. The terminal 400 responds to the access operation of the target access portal aiming at the active page, and generates a page loading request, wherein the target access portal is any one of a plurality of access portals corresponding to a plurality of running platforms, and the plurality of access portals are issued by configuration equipment aiming at the active page; sending a page load request to the server 200; receiving a page configuration file returned by the server 200 for the page loading request; analyzing the page configuration file through a page processing engine corresponding to the target access inlet to obtain a component list and configuration information, and rendering an active page based on the component list and the configuration information; the rendered active page is shown in graphical interface 400-1.

The server 200 is configured to receive a page configuration file uploaded by the terminal 500; generating a plurality of access portals corresponding to a plurality of operation platforms for the page configuration file, and returning the access portals to the terminal 500; receiving a page loading request sent by the terminal 400, wherein the page loading request is generated by the terminal 400 in response to an access operation aiming at a target access entrance; responding to a page loading request, and acquiring a page configuration file corresponding to an active page; the page profile is returned to the terminal 400.

In some embodiments, the server 200 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, and basic cloud computing services such as big data and artificial intelligence platforms. The terminals 400 and 500 may be, but are not limited to, smart phones, tablet computers, notebook computers, desktop computers, smart speakers, smart watches, smart home appliances, car terminals, etc. The terminal and the server may be directly or indirectly connected through wired or wireless communication, which is not limited in the embodiment of the present application.

Referring to fig. 2A, fig. 2A is a schematic structural diagram of the terminal 400 (an implementation manner of the client device) in fig. 1 provided by an embodiment of the present application, and the terminal 400 shown in fig. 2A includes: at least one first processor 410, a first memory 450, at least one first network interface 420, and a first user interface 430. The various components in terminal 400 are coupled together by a first bus system 440. It is appreciated that the first bus system 440 is used to enable connected communication between these components. The first bus system 440 includes a power bus, a control bus, and a status signal bus in addition to a data bus. But for clarity of illustration, the various buses are labeled as first bus system 440 in fig. 2A.

The first processor 410 may be an integrated circuit chip having signal processing capabilities such as a general purpose processor, a digital signal processor (DSP, digital Signal Processor), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like, wherein the general purpose processor may be a microprocessor or any conventional processor or the like.

The first user interface 430 includes one or more first output devices 431, including one or more speakers and/or one or more visual displays, that enable presentation of media content. The first user interface 430 also includes one or more first 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.

The first memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard drives, optical drives, and the like. The first memory 450 optionally includes one or more storage devices physically remote from the first processor 410.

The first memory 450 includes volatile memory or nonvolatile memory, and may also include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read Only Memory (ROM), and the volatile Memory may be a random access Memory (RAM, random Access Me mory). The first memory 450 described in embodiments of the present application is intended to comprise any suitable type of memory.

In some embodiments, the first memory 450 is capable of storing data to support various operations, examples of which include programs, modules and data structures, or subsets or supersets thereof, as exemplified below.

A first operating system 451 including system programs, such as a framework layer, a core library layer, a driver layer, etc., for handling various basic system services and performing hardware-related tasks, for implementing various basic services and handling hardware-based tasks;

a first network communication module 452 for reaching other computing devices via one or more (wired or wireless) first network interfaces 420, the exemplary first network interface 420 comprising: bluetooth, wireless compatibility authentication (Wi-Fi), universal serial bus (USB, universal Serial Bus), and the like;

a first presentation module 453 for enabling presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more first output devices 431 (e.g., a display screen, a speaker, etc.) associated with the first user interface 430;

a first input processing module 454 for detecting one or more user inputs or interactions from one of the one or more first input devices 432 and translating the detected inputs or interactions.

In some embodiments, the page loading device provided in the embodiments of the present application may be implemented in software, and fig. 2A shows the page loading device 455 stored in the first memory 450, which may be software in the form of a program and a plug-in, and includes the following software modules: the request generation module 4551, the first transmission module 4552, the first reception module 4553, the page rendering module 4554, the page presentation module 4555, and the component storage module 4556 are logical, and thus may be arbitrarily combined or further split according to the implemented functions. The functions of the respective modules will be described hereinafter.

Referring to fig. 2B, fig. 2B is a schematic structural diagram of the server 200 (an implementation manner of the cloud device) in fig. 1 according to an embodiment of the present application, where the server 200 shown in fig. 2B includes: at least one second processor 210, a second memory 250, at least one second network interface 220, and a second user interface 230. The various components in server 200 are coupled together by a second bus system 240. It is appreciated that the second bus system 240 is used to enable connected communications between these components. The second bus system 240 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration the various buses are labeled in fig. 2B as a second bus system 240.

The second processor 210 may be an integrated circuit chip with signal processing capabilities such as a general purpose processor, a digital signal processor (DSP, digital Signal Processor), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc., where the general purpose processor may be a microprocessor or any conventional processor, etc.

The second user interface 230 includes one or more second output devices 231, including one or more speakers and/or one or more visual displays, that enable presentation of media content. The second user interface 230 also includes one or more second input devices 232 including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

The second memory 250 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard drives, optical drives, and the like. The second memory 250 optionally includes one or more storage devices physically remote from the second processor 210.

The second memory 250 includes volatile memory or nonvolatile memory, and may also include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read Only Memory (ROM), and the volatile Memory may be a random access Memory (RAM, random Access Me mory). The second memory 250 described in embodiments of the present application is intended to comprise any suitable type of memory.

In some embodiments, the secondary memory 250 is capable of storing data to support various operations, examples of which include programs, modules and data structures, or subsets or supersets thereof, as exemplified below.

A second operating system 251 including system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;

a second network communication module 252 for reaching other computing devices via one or more (wired or wireless) second network interfaces 220, the exemplary second network interface 220 comprising: bluetooth, wireless compatibility authentication (Wi-Fi), universal serial bus (USB, universal Serial Bus), and the like;

a second rendering module 253 for enabling the rendering of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more second output devices 231 (e.g., a display screen, a speaker, etc.) associated with the second user interface 230;

a second input processing module 254 for detecting one or more user inputs or interactions from one of the one or more second input devices 232 and translating the detected inputs or interactions.

In some embodiments, the page loading device provided in the embodiments of the present application may be implemented in a software manner, and fig. 2B shows the page loading device 255 stored in the second memory 250, which may be software in the form of a program and a plug-in, and includes the following software modules: the second receiving module 2551, the entry generating module 2552, the second transmitting module 2553, the file obtaining module 2554, and the package generating module 2555 are logical, and thus may be arbitrarily combined or further split according to the implemented functions. The functions of the respective modules will be described hereinafter.

Referring to fig. 2C, fig. 2C is a schematic structural diagram of the terminal 500 (an implementation manner of the configuration device) in fig. 1 provided by an embodiment of the present application, and the terminal 500 shown in fig. 2C includes: at least one third processor 510, a third memory 550, at least one third network interface 520, and a third user interface 530. The various components in terminal 500 are coupled together by a third bus system 540. It is appreciated that the third bus system 540 is used to enable connected communications between these components. The third bus system 540 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration the various buses are labeled as a third bus system 540 in fig. 2C.

The third processor 510 may be an integrated circuit chip with signal processing capabilities such as a general purpose processor, a digital signal processor (DSP, digital Signal Processor), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc., where the general purpose processor may be a microprocessor or any conventional processor, etc.

The third user interface 530 includes one or more third output devices 531 that enable presentation of media content, including one or more speakers and/or one or more visual displays. The third user interface 530 also includes one or more third input devices 532, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

The third memory 550 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard drives, optical drives, and the like. The third memory 550 may optionally include one or more storage devices physically remote from the third processor 510.

The third memory 550 includes volatile memory or nonvolatile memory, and may also include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read Only Memory (ROM), and the volatile Memory may be a random access Memory (RAM, random Access Me mory). The third memory 550 described in embodiments of the present application is intended to comprise any suitable type of memory.

In some embodiments, the third memory 550 is capable of storing data to support various operations, examples of which include programs, modules and data structures, or subsets or supersets thereof, as exemplified below.

A third operating system 551 including system programs for handling various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and handling hardware-based tasks;

a third network communication module 552 for reaching other computing devices via one or more (wired or wireless) third network interfaces 520, the exemplary third network interface 520 comprising: bluetooth, wireless compatibility authentication (Wi-Fi), universal serial bus (USB, universal Serial Bus), and the like;

a third rendering module 553 for enabling the rendering of information (e.g., a user interface for operating a peripheral device and displaying content and information) via one or more third output devices 531 (e.g., a display screen, speakers, etc.) associated with a third user interface 530;

a third input processing module 554 for detecting one or more user inputs or interactions from one of the one or more third input devices 532 and translating the detected inputs or interactions.

In some embodiments, the page loading device provided in the embodiments of the present application may be implemented in a software manner, and fig. 2C shows a page loading device 555 stored in a third memory 550, which may be software in the form of a program, a plug-in, or the like, including the following software modules: the information presentation module 5551, the configuration generation module 5552, the third transmission module 5553 and the third reception module 5554 are logical, and thus may be arbitrarily combined or further split according to the implemented functions. The functions of the respective modules will be described hereinafter.

In some embodiments, the terminal or the server may implement the page loading method provided by the embodiments of the present application by running a computer program. For example, the computer program may be a native program or a software module in an operating system; may be a local (Native) Application (APP), i.e. a program that needs to be installed in an operating system to run, such as an online retail APP; or may be an applet, i.e., a program that can be run only by being downloaded into a browser environment, e.g., an applet that supports online retail; but also an applet that can be embedded in any APP. In general, the computer programs described above may be any form of application, module or plug-in.

The embodiment of the application can be applied to various scenes such as cloud technology, artificial intelligence, intelligent traffic, vehicle-mounted and the like. The page loading method provided by the embodiment of the application will be described below in connection with exemplary applications and implementations of the terminal provided by the embodiment of the application.

Referring to fig. 3, fig. 3 is a schematic flow chart of a page loading method according to an embodiment of the present application, and the steps shown in fig. 3 will be described.

S101, the configuration device responds to the selection operation of the component type in the selection area of the configuration interface, and the candidate component of the component type is displayed in the component area of the configuration interface.

The embodiment of the application is realized in the scene that the configuration equipment configures the active page, and the client equipment accesses and loads the active page, so that the active page is configured once, and the effect of the active page can be loaded and displayed on various different operation platforms. Firstly, after the configuration equipment starts to configure the active page, the configuration equipment enters the configuration interface. In the configuration interface, a selection area for selecting a component type and a component area for displaying different components under the same component type are provided. Different component types may be presented in the selection area in the form of tabs or virtual keys; different components under the same component type are presented in a component area in the form of a list or tab. In the configuration interface, a preview area is further provided, and the preview area is used for previewing the active page.

The configuration device detects the operation of the user on the configuration interface, and judges the processing required to be realized by the user according to the position where the operation occurs, and responds. When the configuration device detects a selection operation on a certain component type in the selection area of the configuration interface, components belonging to the component type are acquired in response to the selection operation, the components are determined as candidate components and displayed in the component area for a user to select a target component for page building.

It is understood that the selecting operation may be clicking, double clicking, sliding, or long pressing, which is not limited herein. The size and the position of the selection area, the component area and the preview area in the configuration interface can be set according to actual situations, and the embodiment of the application is not limited herein.

Fig. 4 is a schematic diagram of a configuration interface provided by an embodiment of the present application. On the left side of the configuration interface 4-1, a selection area 4-11 is provided, in which selection area 4-11 a number of different component types are shown, e.g. shelf style 4-111, diversion component 4-112, global element 4-113, etc. When the configuration device detects that the user selects the shelf style 4-111, the components 4-121, 4-122 and 4-123 belonging to the shelf style 4-111 are displayed in the component area 4-12 as candidate components for the user to select a target component.

S102, the configuration device responds to a dragging operation of dragging the candidate component from the component area to the preview area, determines a target component from the candidate component, and displays an active page formed based on the target component in the preview area.

After the candidate component is displayed, the configuration device detects whether the user performs a drag operation on the candidate component. When the configuration device detects a drag operation for a certain candidate component and the track of the drag operation is to drag the candidate component from the component area to the preview area, the configuration device determines that the candidate component is a target component, and then forms an active page based on the target component and displays the active page in the preview area for the user to preview the active page.

In some embodiments, the user has built a temporary page (e.g., a rudiment of an active page) through other rounds of drag operations, at which point the configuration device may re-add the target component to the temporary page to obtain the active page.

In other embodiments, the configuration device may obtain a preset page corresponding to the target component, and load the preset page directly as an active page into the preview area.

Exemplary, based on fig. 4, referring to fig. 5, fig. 5 is a schematic diagram of generating an active page according to an embodiment of the present application. After the user drags the component 4-121 in the component area 4-12 to the preview area 4-13, the configuration terminal displays the active page 4-2 formed based on the component 4-121 in the preview area 4-13. The configuration interface in fig. 5 may also include configuration areas 4-14 to facilitate configuration of the components in preview areas 4-13 by a user.

S103, the configuration equipment responds to the storage operation of the active page, integrates the component list and the configuration information of the active page into a page configuration file with a tree structure, and uploads the page configuration file to the cloud equipment.

When the configuration equipment detects the save operation of a user on the active page, the configuration equipment acquires component lists of all components forming the active page, acquires the page configuration condition of the active page, namely acquires configuration information, and integrates the component lists and the configuration information according to a tree structure to obtain a page configuration file. Then, the configuration device sends the page configuration file to the cloud device through the network, and the cloud device receives the page configuration file uploaded by the configuration device.

It should be noted that, in the embodiment of the present application, the page configuration file may be in YAML format or AST format, and the embodiment of the present application is not limited herein.

S104, the cloud device generates a plurality of access entries corresponding to a plurality of operation platforms according to the page configuration file, and returns the access entries to the configuration device.

After receiving the page configuration file, the cloud device generates a corresponding access entry for each of the multiple operation platforms, so as to obtain multiple access entries. And then, the cloud device returns the plurality of access portals to the configuration device, and the configuration device receives the plurality of access portals of the cloud device under the plurality of operation platforms returned by the page configuration file.

It should be noted that, when the active page is loaded by different operation platforms, the required dependency items are different, for example, when the application software and the network program load the same web page, the parsing mode, the rendering mode and the like of the configuration file for the web page may be different, so that it is required to determine which operation platform the user needs to load the active page by the access portal, and therefore, the cloud device may generate different access portals for different operation platforms.

In an embodiment of the present application, the plurality of operation platforms at least includes: application software, a web program running on the application software, a browser, and at least two of web pages embedded in the web program. The application software can be an APP installed in the client device, the network program running in the application software can be an applet running in the APP, and a browser embedded in the network program can be regarded as a webpage embedded in the applet.

It will be appreciated that the access portal may be a scanned code, such as a two-dimensional code, a bar code, etc., or may be a link address, such as a website address, an applet address, etc., and embodiments of the present application are not limited in this regard.

Fig. 6 is a schematic diagram illustrating a plurality of access portals according to an embodiment of the present application. The cloud device may generate, for the page configuration file, an access portal 6-1 under the applet platform, an access portal 6-2 embedded under the applet web page platform, an access portal 6-3 under the browser platform, and an access portal 6-4 common to the applet, the application software, the browser, and the web page embedded in the applet.

S105, the client device receives an access operation of the configuration device in response to a target access entry for the active page, and generates a page loading request.

The target access portal is any one of a plurality of access portals corresponding to a plurality of operation platforms, and the plurality of access portals are issued by configuration equipment aiming at an active page. That is, after receiving the multiple access portals, the configuration device issues the multiple access portals to the client device, so that the client device generates a page loading request in response to an access operation for a target access portal in the multiple access portals of the active page, and requests a page configuration file corresponding to the active page from the cloud device through the page loading request. At this time, the user performs an access operation with respect to any one of the access portals, that is, with respect to the target access portal, and the client device generates a page load request for pulling the page profile of the active page in response to the access operation.

It may be appreciated that when the access entry is a link address, the access operation may be a click, double click, etc. operation for the link address; when the access entry is a scan code, the access operation may be a scan operation for the scan code.

In the embodiment of the application, the configuration device can directly send the multiple access portals to the client device to finish the release of the multiple access portals to the client device, or can release the multiple access portals to the client device through information popularization (for example, attaching a two-dimensional code of an active page to a propaganda document), information release (for example, searching a corresponding group for the active page, adding a link address to an information stream and sending the link address to the group) and the like on a network, and the application is not limited in detail.

S106, the client device sends the page loading request to the cloud device.

The cloud device receives a page loading request sent by the client device, wherein the page loading request is generated by the client device in response to an access operation of a target access portal for an active page, and the target access portal is any one of a plurality of access portals.

S107, the cloud device responds to the page loading request to acquire a page configuration file corresponding to the active page.

After receiving the page loading request, the cloud device responds to the page loading request, and obtains a page configuration file generated by the configuration device for the active page from a storage space or a database so as to provide the page configuration file for the client device.

S108, the client device receives a page configuration file returned by the cloud device for the page loading request.

After the cloud device acquires the page configuration file, the page configuration file is returned to the client device, so that the client device processes the page configuration file through a page processing engine corresponding to the target access entrance, and an active page is rendered.

S109, the client device analyzes the page configuration file through a page processing engine corresponding to the target access entry to obtain a component list and configuration information, and renders an active page based on the component list and the configuration information.

After receiving the page configuration file, the client device invokes the page processing engine corresponding to the target access entry from a plurality of different processing engines, then analyzes the component list and the configuration information from the page configuration file by utilizing the invoked page processing engine, and determines which components form the active page through the component list, and determines the page configuration condition of the active page through the configuration information, namely, the style, the attribute and the like of the active page, then renders the components forming the active page, and adds the page configuration to obtain the active page.

S110, the client equipment displays the rendered active page.

Finally, the client device selects the active page obtained through rendering to be displayed in the display interface, so that the loading process of the active page is realized.

Fig. 7A is a schematic diagram of an active page provided by an embodiment of the present application, and fig. 7B is another schematic diagram of an active page provided by an embodiment of the present application. The active page 7-1 of fig. 7A and the active page 7B are loaded by application software, but the active page 7-1 is loaded in APP running in operating system a, the active page 7-2 is loaded in application software running in operating system B, i.e. the versions of the application software of the active page 7-1 and the active page 7-2 are different, the style and content of the pages are similar or even identical.

FIG. 7C is a further schematic illustration of an active page provided by an embodiment of the present application. The active page 7-3 in fig. 7C is loaded by the browser, and the category of the item, such as the hand account 7-31, is displayed in the active page 7-3. FIG. 7D is a further schematic diagram of an active page provided by an embodiment of the present application, wherein the active page 7-4 is loaded by an applet and can be closed by a closing identification of the applet.

It can be understood that, compared with the related art, the active page must run under the web page platform, so that there are fewer running platforms supporting loading of the active page, in the embodiment of the present application, the active page has multiple access portals corresponding to multiple running platforms, when an access operation for any one of the multiple access portals is detected, a page loading request is generated, so that a page configuration file of the active page is pulled from the cloud device through the page loading request, and then the page configuration file is processed through any one access portal, that is, a page processing engine corresponding to the target access portal, so as to obtain the active page. In addition, the multiple operation platforms include other platforms except the web page platform, and when the processing speed of the page processing engine corresponding to the other platforms is faster than that of the web page platform browser component, the loading efficiency of the active page is improved.

Referring to fig. 8, fig. 8 is another flow chart of the page loading method according to the embodiment of the present application. In some embodiments of the present application, the client device renders the active page based on the component list and the configuration information, that is, the specific implementation process of S109 may include: S1091-S1093 as follows:

s1091, the client device pulls the target component contained in the component list through the page processing engine.

After the client device calls the page processing engine to analyze the page configuration file into the component list and the configuration information, the page processing engine continues to analyze the component list to obtain the names, numbers and the like of the components contained in the active page, and then the components corresponding to the names or numbers of the components are pulled from the component package to obtain the target components.

S1092, the client device renders the target component by using the page processing engine to obtain an initial page.

The client device continues to utilize the page processing engine to analyze the attribute information of the target component (the attribute information of the target component is stored in a page configuration file in the form of sub-nodes of the component), determine the position information and the appearance information of the target component, then render the target component into an empty page so as to restore the position, the appearance and other information of the target component in the empty page, and obtain the initial page after the rendering is finished.

In some embodiments, the target component is already determined in the page at development time, i.e., the location information of the target component is determined at development time, so that the client device automatically sets the target component at its corresponding location when rendering the target component by the page processing engine. In other embodiments, the location information of the target component in the page is specified by the user, e.g., the location of the target component is adjusted in the preview page by a drag operation or the like.

S1093, the client device adjusts the initial page according to the configuration information through the page processing engine to obtain an active page.

After the client device obtains the initial page through the page processing engine, the client device can continue to adjust the initial page through the page processing engine according to the configuration information, for example, adjust the overall style of the initial page, add sharing links to the initial page, and the like, and after the adjustment is completed, the client device obtains the active page.

In the embodiment of the application, the client device pulls the target component contained in the component list through the page processing engine matched with the target access inlet, then renders the target component, and fine-tunes the initial page obtained by rendering according to the configuration information, so as to obtain the active page which can be finally presented to the user. Thus, the method can load the active page on any operation platform.

In some embodiments of the present application, before the cloud device receives the page configuration file uploaded by the configuration device, i.e. before S103, the method may further include: s201 to S204 are as follows:

s201, the cloud device acquires a component configuration file.

The cloud device acquires a component configuration file, wherein the component configuration file records attribute information, a code file, an appearance template and component data of sub-components contained in the component in a tree structure, and the attribute information at least comprises icons, titles, configuration information, description content, types and labels of the component. The cloud device can configure and generate the components based on the component configuration files after the component configuration files are clear.

Fig. 9 is a schematic structural diagram of a component configuration file according to an embodiment of the present application. In the component configuration file, the component 9-1 is taken as a root node, the attribute information 9-11 of the component 9-1, the sub-component 9-12 of the component 9-1, the sub-component 9-13, the code logic 9-14 and the appearance template 9-15 of the component 9-1 are taken as nodes under the root node, then the code file 9-121 and the appearance template 9-122 of the sub-component 9-12 are taken as sub-nodes under the corresponding nodes of the sub-component 9-12, and the code file 9-131 and the appearance template 9-132 of the sub-component 9-13 are taken as sub-nodes under the corresponding nodes of the sub-component 9-13.

In some embodiments, the attribute information of the component may be obtained by a component creator through writing a code, and in some embodiments, the attribute information of the component may be obtained by the component creator through converting content filled in an attribute configuration page displayed at a front end corresponding to the cloud device. The embodiments of the present application are not limited herein.

Fig. 10 is a schematic diagram of an attribute configuration page according to an embodiment of the present application. In the attribute configuration page 10-1, an attribute tab 10-11, a style tab 10-12, a matching tab 10-13, and a buried point reporting tab 10-14 are provided. The component creator can perform corresponding configuration by selecting the corresponding tab to obtain attribute information. For example, in FIG. 10, when the component creator selects the properties tab 10-11, the component name 10-111, the appearance selection area 10-112, and the coupon setting area 10-113 appear to facilitate the corresponding configuration by the component creator.

S202, the cloud device creates the components according to the component configuration file, and packages the created components to obtain an initial component package.

The cloud device analyzes the component configuration file to determine attribute information, an appearance template, a code file and component data of sub-components embedded in the component, namely, determine specific configuration of the component, generate the component by using the specific configuration of the component, and package the generated component to obtain an initial component package containing the created component.

S203, the cloud device converts the initial package into a plurality of packages corresponding to a plurality of operation platforms, and sends the packages to the client device.

The cloud device analyzes the grammar of the components in the initial component package, determines the grammar logic of the initial component package, then processes the grammar logic of the components in the initial component package through character string replacement and the like, adjusts the codes of the components in the initial component package under the condition of not changing the grammar logic of the components in the initial component package, enables the components to operate on different operation platforms, compiles the adjusted codes again to obtain component packages capable of normally operating on each operation platform, and accordingly obtains a plurality of component packages, and then sends the plurality of component packages to the client device through a network. And the client equipment receives a plurality of component packages corresponding to the plurality of operation platforms sent by the cloud equipment.

S204, the client device stores the plurality of component packages in a local storage space.

After receiving the multiple component packages, the client device stores the multiple component packages so as to conveniently search the component packages corresponding to the target access entrance for subsequent calling and find the target component which can be called from the component packages.

In this case, the specific implementation procedure of pulling, by the client device through the page processing engine, the target component included in the component list, that is, S1091, may include: s1091a-S1091b are as follows:

S1091a, the client device locates the matching component package hit in the component list from the multiple component packages in the local storage space through the page processing engine.

S1091b, the client device extracts the target component contained in the component list from the matching component package by using the page processing engine.

When the client device pulls the target component contained in the component list through the page processing engine, the page processing engine is utilized to locate the component package containing the component corresponding to the component list from a plurality of component packages, determine the component package as a matching component package, and then search the target component specified by the component list from the matching component package.

In the embodiment of the application, the cloud device creates the initial component package according to the component configuration information, then converts the initial component package into the component package applicable to different operation platforms, and then sends the component package to the client device. Therefore, the package which can be operated on different operation platforms can be obtained on the basis of only one-time component development, so that the subsequent client equipment can conveniently call the components when the different platforms load the active pages.

Of course, in other embodiments, the cloud device may store a plurality of component packages corresponding to a plurality of running platforms in the database, or in a storage space of the cloud device itself, so when the client device sends a page loading request to the cloud device, the client device issues the page configuration file and the target access entry, that is, the matching component package corresponding to the running platform on which the client device needs to load the active page, to the client device, so that the client device searches for the target file included in the component list from the matching component package.

In some embodiments of the present application, the configuration device integrates the component list and the configuration information of the active page into a tree-structured page configuration file, i.e. the specific implementation process of S103 may include: s1031 to S1033 are as follows:

s1031, the configuration device creates a root node for the active page.

S1032, the configuration device creates a first node under the root node for the component list and a second node under the root node for the configuration information.

The configuration equipment utilizes a root node in the tree structure to represent the active page, establishes a first node for identifying the component list and a second node for representing configuration information under the root node, and at the moment, the root node is a father node of the first node and the second node, so that the tree structure is primarily formed.

It can be understood that the component list further includes information of a plurality of components, and the configuration information further includes information of sharing type, style and the like of the page, and at this time, the configuration device further adds child nodes to the first node and the second node respectively, so as to obtain a deeper tree structure.

That is, when the configuration device integrates the component list and the configuration information according to the tree structure, the active page is represented by the root node, then corresponding nodes are respectively built for the configuration information and the component list, the nodes are added below the root node, then corresponding sub-nodes are built for each content belonging to the configuration information and are added below the corresponding nodes of the configuration information, and meanwhile, corresponding sub-nodes are built for each component in the component list and are added below the corresponding nodes of the component list. And repeating the steps until each piece of content in the configuration information and each piece of content in the component list have corresponding sub-nodes, thereby completing the integration of the tree structure.

Exemplary, fig. 11 is a schematic diagram of a page configuration file provided in an embodiment of the present application. Under the root node 11-1 corresponding to the active page, there are two nodes, namely configuration information 11-11 and component list 11-12. Under the configuration information 11-11, three child nodes are respectively shared information 11-111, page patterns 11-112 and data reporting information 11-113; under the component list 11-12, there are components 11-121 as child nodes, and under the components 11-121, there are three child nodes of component description 11-1211, component style 11-1212, and data report information 11-1213.

S1033, the configuration equipment stores a tree structure formed by the root node, the first node and the second node to obtain a page configuration file.

The configuration equipment writes the tree structure formed by the root node, the first node and the second node into an empty text file or code file to save the tree structure, and after the writing is completed, the page configuration file is obtained.

In the embodiment of the application, the configuration equipment constructs the tree structure through the logical relationship among the root node, the first node and the second node, and stores the tree structure as the page configuration file, so that the structure of each content in the page configuration file is clear, and the deconstructing processing of the client equipment is convenient.

In the following, an exemplary application of the embodiment of the present application in a practical application scenario will be described.

The embodiment of the application is realized in the scene of carrying out page building aiming at the online retail preferential activities and loading the built preferential pages (active pages). Figure 12 is a flow chart of a process from build to load for a page provided by an embodiment of the present application. Referring to fig. 12, the process includes:

s301, a server (cloud device) develops a component through a component DSL (component profile).

At this point, the multi-port (multiple operating platform) component can be developed with the same set of component DSL.

S302, the server compiles the developed components into component codes which can be operated by DSL engines (page processing engines) at each end.

S303, the server places the component package (a plurality of component packages) of each end in a local built-in or cloud pulling mode.

The local built-in means that the component package is directly written into engineering codes of all the ends, and the cloud pulling means that all the ends download the component package from the server.

S304, configuring and generating a page DSL (page configuration file) by the editing end (configuration device) in a dragging component mode, and notifying a server to generate page addresses (a plurality of access entries) of all ends.

S305, the client (client device) opens a certain page address and obtains the page DSL from the server.

S306, the client calls a corresponding DSL engine to process the obtained page DSL.

S307, the client calls the DSL engine, renders the page and displays the page.

It should be noted that, in order to enable the configuration end, the client and the server to identify and exchange DSL pages, DSL pages are generally specified in a data exchange format, for example, by YAML format, to identify the data structure in a indented manner, so as to present the UI tree hierarchy of the pages.

A page is typically composed of two modules, a page configuration (configuration information) and a component list. The configuration terminal uses the root node to represent the page, and uses the child node under the root node to represent the page configuration and the component list respectively. Under the page configuration node, there may be multiple sub-nodes describing the composition of the page configuration, for example, for the sharing information (such as sharing links, sharing pictures, sharing titles, sharing contents, etc.) and the data reporting information in the page configuration, the configuration end establishes corresponding sub-nodes, where the sub-nodes are located under the page configuration node.

The sub node is set under the component list node, one sub node represents one component, one component can be composed of component identification, component description information, component type, component configuration attribute and component data reporting information, and the configuration end establishes the sub node for the contents.

It should be further noted that, the component is represented by a type child node under the node corresponding to the component, for example, for a picture component type, each end needs to be implemented by a picture component, that is, the implementation logic of the picture component is scattered at each end, which may not be consistent. In this regard, it is necessary to unify the component generation process at each end by the component DSL.

For example, for a file directory of components of one couple-list-v 2, under the root directory, a node representing attributes of the components, a node representing business logic of the components, a node representing UI presentation of the implementation components, and sub-components of the components of couple-list-v 2, couple-item-1, couple-item-2, and couple-item-with-desc, each sub-component may represent its UI presentation, i.e., support the component nesting component, using a similar file structure as couple-list-v 2.

Among the properties of the component may be included an icon, a title label, a configurable item config, a description content desc, a tag, etc. of the component, and the configurable item config may be configured through an interface similar to that of fig. 10.

The node of the business logic of the component is used for storing the code logic of the component, a defined UI template can be arranged in the node for realizing the UI display of the component, data information is acquired through the symbol variable of the template, and sub-components of the sub-component 1, the sub-component 2 and the sub-component of the sub-component.

Fig. 13 is a schematic diagram of UI structures of components provided in an embodiment of the present application. In the UI structure of the component 13-1, a type 13-2 and a sub-component list 13-3 may be included, and in the sub-component list 13-3, two sub-nodes, namely a sub-component 13-4 and a sub-component 13-5, are included. The sub-component 13-4 contains the type 13-6 sub-node and the sub-component list 13-7 sub-node, and the sub-component 13-5 contains the type 13-8 and the sub-component list 13-9. As can be seen in FIG. 13, the components can nest with one another, and the file structure and content of the child components are similar to those of the parent component.

In the embodiment of the application, the server compiles the component DSL through the component compiler and generates the component codes which can be operated by the DSL engines at each end, and the process can be realized based on compiling modes such as AST grammar analysis, character string replacement and the like.

FIG. 14 is a schematic diagram illustrating the processing of a component compiler provided by an embodiment of the present application. The component compiler 14-1 reads in the component DSL14-2, compiles the component DSL14-2, and then converts the compiled component package into a component package that can be interpreted and run by the DSL engines of the web platform 14-3 (browser), applet platform 14-4 (network program running in application software), and APP platform 14-5 (application software).

It will be appreciated that the process of configuring a terminal build page is equivalent to the process of configuring a generate page DSL. A page is composed of a plurality of components, and when a component is added to the page by a drag operation, it is equivalent to adding a child node representing the component under the component list node.

Exemplary, based on fig. 11, referring to fig. 15, fig. 15 is a schematic diagram of a building page DSL provided by an embodiment of the present application. When a component is added to the page by a drag operation, it is equivalent to adding a new component 15-1 as a child node under the component list 11-12. The component 15-1 also has 3 child nodes below it, a component description 15-11, a component style 15-12, and a data reporting information 15-13 for the component 15-1, respectively.

The component is the actual running component code developed and compiled by the component DSL, which is ultimately passed to the DSL engine for interpretation and operation. Each end is used to interpret and run the DSL engine of the page DSL differently, i.e. each end has a DSL engine of each end. When the different DSL engines search the required components based on the page DSL, the corresponding component package (matching component package) is searched first, then the required components are searched in the corresponding component package, and finally the components are analyzed and operated.

Fig. 16 is a schematic diagram illustrating a process of looking up components by a DSL engine at each end provided in an embodiment of the present application. As can be seen from fig. 16, the DSL engine 16-1 of the web platform searches for a component from the component package 16-2 corresponding to the web platform, the DSL engine 16-3 of the applet platform searches for a component from the component package 16-4 corresponding to the applet platform, the DSL engine 16-5 of the instant messaging APP searches for a component from the component package 16-6 corresponding to the DSL engine, and the DSL engine 16-7 of the shopping APP searches for a component from the component package 16-8 corresponding to the DSL engine.

Fig. 17 is a schematic diagram of a page rendering process according to an embodiment of the present application. Referring to fig. 17, the process includes:

s401, the client opens the webpage address.

S402, the client pulls the page DSL from the server.

S403, the client calls the DSL engine to analyze the page DSL.

S404, the client acquires the component package through the DSL engine.

S405, the client parses the component package into components capable of running through the DSL engine.

In this case, the DSL engine may be dynamically resolved or may be statically resolved.

S406, the client renders the component by using the DSL engine to obtain the page.

Continuing with the description below of an exemplary architecture of the page loading device 455 implemented as a software module provided by embodiments of the present application, in some embodiments, as shown in FIG. 2A, the software modules stored in the page loading device 455 of the first memory 450 may include:

A request generation module 4551 for generating a page load request in response to an access operation to a target access portal of an active page; the target access portal is any one of a plurality of access portals corresponding to a plurality of running platforms, and the plurality of access portals are issued by configuration equipment for the active page;

the first sending module 4552 is configured to send the page loading request to a cloud device;

a first receiving module 4553, configured to receive a page configuration file returned by the cloud device for the page loading request;

the page rendering module 4554 is configured to parse the page configuration file through a page processing engine corresponding to the target access entry to obtain a component list and configuration information, and render the active page based on the component list and the configuration information;

and the page display module 4555 is used for displaying the rendered active page.

In some embodiments of the present application, the page rendering module 4554 is further configured to pull, by the page processing engine, a target component included in the component list; rendering the target component by using the page processing engine to obtain an initial page; and adjusting the initial page according to the configuration information by the page processing engine to obtain the active page.

In some embodiments of the present application, the page loading device 455 further includes: a component storage module 4556; the first receiving module 4551 is further configured to receive a plurality of component packages corresponding to a plurality of operation platforms sent by the cloud device before generating a page loading request in response to an access operation of a target access entry for an active page;

the component storage module 4556 is configured to store a plurality of the component packages in a local storage space;

the page rendering module 4554 is further configured to locate, by the page processing engine, a matching package in the component list hit from among the plurality of packages in the local storage space; and extracting target components contained in the component list from the matched component package by using the page processing engine.

Continuing with the description below of an exemplary architecture of the page loading device 255 implemented as a software module provided by embodiments of the present application, in some embodiments, as shown in fig. 2B, the software modules stored in the page loading device 255 of the second memory 250 may include:

A second receiving module 2551, configured to receive a page configuration file uploaded by the configuration device;

the entry generation module 2552 is configured to generate, for the page configuration file, a plurality of access entries corresponding to a plurality of operation platforms;

a second sending module 2553, configured to return a plurality of the access entries to the configuration device;

the second receiving module 2551 is further configured to receive a page loading request sent by the client device; the page load request is generated by the client device in response to an access operation for a target access portal of the active page; the target access portal is any one of a plurality of the access portals;

a file obtaining module 2554, configured to obtain a page configuration file corresponding to the active page in response to the page loading request;

the second sending module 2553 is further configured to return the page configuration file to the client device, so that the client device parses the page configuration file into a component list and configuration information through a page processing engine corresponding to the target access entry, and renders and displays the active page based on the component list and the configuration information.

In some embodiments of the present application, the page loading device 255 further includes: a package generation module 2555; the file obtaining module 2554 is further configured to obtain a component configuration file before the receiving the page configuration file uploaded by the configuration device; the component configuration file records attribute information, a code file, an appearance template and component data of sub-components contained in the component in a tree structure, wherein the attribute information at least comprises icons, titles, configuration information, description contents, types and labels of the component;

the component package generating module 2555 is configured to create a component according to the component configuration file, and package the created component to obtain an initial component package; converting the initial component package into a plurality of component packages corresponding to a plurality of operation platforms;

the second sending module 2553 is further configured to send the plurality of component packages to a client device.

Continuing with the description below of an exemplary architecture of page loader 555 implemented as a software module provided by embodiments of the present application, in some embodiments, as shown in FIG. 2C, the software modules stored in page loader 555 of memory 550 may include:

An information presentation module 5551 for presenting candidate components of a component type in a component area of a configuration interface in response to a selected operation for the component type in the selection area of the configuration interface; determining a target component from the candidate components in response to a drag operation of dragging the candidate components from the component area to a preview area, and displaying an active page formed based on the target component in the preview area;

a configuration generating module 5552, configured to integrate the component list and the configuration information of the active page into a page configuration file with a tree structure in response to a save operation on the active page;

a third sending module 5553, configured to upload the page configuration file to a cloud device;

a third receiving module 5554, configured to receive multiple access entries under multiple operation platforms returned by the cloud device for the page configuration file;

the third sending module 5553 is further configured to issue a plurality of access portals to a client device, so that the client device generates a page loading request in response to an access operation for a target access portal in the access portals of the active page, and parses, by using a page processing engine corresponding to the target access portal, a page configuration file returned by a cloud device for the page loading request, to obtain a component list and configuration information, and render and display the active page based on the component list and the configuration information.

In some embodiments of the application, the configuration generation module 5552 is further configured to create a root node for the active page; creating a first node under the root node for the component list and a second node under the root node for the configuration information; and saving a tree structure formed by the root node, the first node and the second node to obtain the page configuration file.

Embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The first processor of the client device reads the computer instructions from the computer readable storage medium, and the first processor executes the computer instructions, so that the client device executes the page loading method according to the embodiment of the application; the second processor of the cloud device reads the computer instruction from the computer readable storage medium, and the second processor executes the computer instruction, so that the cloud device executes the page loading method according to the embodiment of the application; the third processor of the configuration device reads the computer instructions from the computer-readable storage medium, and the third processor executes the computer instructions, so that the configuration device executes the page loading method according to the embodiment of the present application.

The embodiment of the application provides a computer readable storage medium storing executable instructions, wherein the executable instructions are stored, when the executable instructions are executed by a first processor, the first processor is caused to execute a page loading method on a client device side provided by the embodiment of the application, or when the executable instructions are executed by a second processor, the second processor is caused to execute a page loading method on a cloud device side provided by the embodiment of the application, or when the executable instructions are executed by a third processor, the third processor is caused to execute a page loading method on a configuration device side provided by the embodiment of the application.

In some embodiments, the computer readable storage medium may be FRAM, ROM, PROM, EP ROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; but may be a variety of devices including one or any combination of the above memories.

In some embodiments, the executable instructions may be in the form of programs, software modules, scripts, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and they may be deployed in any form, including as stand-alone programs or as modules, components, subroutines, or other units suitable for use in a computing environment.

As an example, the executable instructions may, but need not, correspond to files in a file system, may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a hypertext markup language (HTML, hyper Text Markup Language) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).

As an example, the executable instructions may be deployed to execute on one computing device (any of a client device, a cloud device, and a configuration device), or on multiple computing devices located at one site, or on multiple computing devices distributed across multiple sites and interconnected by a communication network.

In summary, according to the embodiment of the present application, the active page has multiple access portals corresponding to multiple operation platforms, when an access operation for any one of the multiple access portals is detected, a page loading request is generated, so that a page configuration file of the active page is pulled from the cloud device through the page loading request, and then the page configuration file is processed through any one access portal, that is, a page processing engine corresponding to the target access portal, so as to obtain the active page. In addition, the multiple operation platforms include other platforms except the web page platform, and when the processing speed of the page processing engine corresponding to the other platforms is faster than that of the web page platform browser component, the loading efficiency of the active page is improved.

The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A method of page loading, the method comprising:

sending the page loading request to cloud equipment;

and displaying the rendered active page.

2. The method of claim 1, wherein the rendering the active page based on the component list and the configuration information comprises:

Pulling, by the page processing engine, a target component included in the component list;

rendering the target component by using the page processing engine to obtain an initial page;

and adjusting the initial page according to the configuration information by the page processing engine to obtain the active page.

3. The method of claim 2, wherein the plurality of operating platforms comprises: application software, a web program running on the application software, a browser, and at least two of web pages embedded in the web program.

4. A method according to claim 3, wherein, prior to generating a page load request in response to an access operation to a target access entry for an active page, the method further comprises:

receiving a plurality of component packages corresponding to a plurality of operation platforms sent by the cloud device;

storing a plurality of the component packages to a local storage space;

the pulling, by the page processing engine, the target component included in the component list includes:

locating, by the page processing engine, a matching package of the component list hits from among the plurality of packages of the local storage space;

And extracting the target component contained in the component list from the matched component package by using the page processing engine.

5. A method of page loading, the method comprising:

receiving a page configuration file uploaded by configuration equipment;

6. The method of claim 5, wherein prior to receiving the page profile uploaded by the configuration device, the method further comprises:

acquiring a component configuration file; the component configuration file records attribute information, a code file, an appearance template and component data of sub-components contained in the component in a tree structure, wherein the attribute information at least comprises icons, titles, configuration information, description contents, types and labels of the component;

creating a component according to the component configuration file, and packaging the created component to obtain an initial component package;

and converting the initial component package into a plurality of component packages corresponding to a plurality of operation platforms, and sending the plurality of component packages to client equipment.

7. A method of page loading, the method comprising:

8. The method of claim 7, wherein integrating the component list and configuration information of the active page into a tree structured page profile comprises:

creating a root node for the active page;

creating a first node under the root node for the component list and a second node under the root node for the configuration information;

And saving a tree structure formed by the root node, the first node and the second node to obtain the page configuration file.

9. A page loading apparatus, the apparatus comprising:

and the page display module is used for displaying the rendered active page.

10. A page loading apparatus, the apparatus comprising:

11. A page loading apparatus, the apparatus comprising:

12. A client device, the client device comprising:

a first memory for storing executable instructions;

a first processor configured to implement the page loading method of any one of claims 1 to 4 when executing executable instructions stored in the first memory.

13. A cloud device, the cloud device comprising:

a second memory for storing executable instructions;

a second processor, configured to implement the page loading method according to claim 5 or 6 when executing the executable instructions stored in the second memory.

14. A configuration device, the configuration device comprising:

a third memory for storing executable instructions;

a third processor, configured to implement the page loading method according to claim 7 or 8 when executing the executable instructions stored in the third memory.

15. A computer readable storage medium storing executable instructions which when executed by a first processor implement the page loading method of any one of claims 1 to 4, when executed by a second processor implement the page loading method of claim 5 or 6, and when executed by a third processor implement the page loading method of claim 7 or 8.