CN112035117A

CN112035117A - Page display system, method and device

Info

Publication number: CN112035117A
Application number: CN202010877604.XA
Authority: CN
Inventors: 陈凯鑫
Original assignee: Beijing Sankuai Online Technology Co Ltd
Current assignee: Beijing Sankuai Online Technology Co Ltd
Priority date: 2020-08-27
Filing date: 2020-08-27
Publication date: 2020-12-04

Abstract

The specification discloses a page display system, a page display method and a page display device, wherein a first terminal generates component codes of all components contained in a target page, each component code is compiled into a page code, positions of all the components in the target page are not identical, a server receives and stores all the page codes, a second terminal receives a page access request input by a second user, the target page and all the page areas contained in the target page are determined, a component acquisition request for acquiring the components located in all the page areas is sent, the server determines the page codes corresponding to all the components located in all the page areas and sends the page codes to the second terminal for combination, and the second terminal displays all the page areas according to a combination result. The first user can independently develop each component in each page area, and when the components are developed, the component codes are directly compiled into page codes at the first terminal and the page codes are stored in the server without considering the compatibility problem of each front-end frame.

Description

Page display system, method and device

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a system, a method, and an apparatus for displaying pages.

Background

Currently, front-end development techniques are essential in the field of information technology.

In practical applications, a front-end project may have a plurality of front-end pages, and each front-end page may have rich page contents, so that the front-end project developed by developers generally has the characteristics of more codes and the like. The developer uploads the front-end project code to the server, when a certain part of the front-end project is modified, the code of the whole front-end project needs to be downloaded from the server, and the part needing to be modified is found from a plurality of codes to be modified.

Disclosure of Invention

The embodiment of the specification provides a page display system, a page display method and a page display device, so as to partially solve the problems in the prior art.

The embodiment of the specification adopts the following technical scheme:

the page display system provided by the specification, the system comprises: the system comprises a server, a first terminal and a second terminal; wherein:

the first terminal generates component codes of all components contained in a target page according to the operation of a first user; compiling each component code into a page code respectively, and uploading each page code to the server, wherein the positions of the components in the target page are not identical;

the server receives and stores each page code;

the second terminal receives a page access request input by a second user, determines the target page according to the page access request, and determines each page area contained in the target page; sending a component acquisition request for acquiring a component positioned in each page area to the server aiming at each page area;

the server determines page codes corresponding to the components in the page area according to the component acquisition request, takes the page codes as designated page codes, and sends the designated page codes to the second terminal;

and the second terminal combines all the appointed page codes and displays the page area according to a combination result.

The page display method provided by the specification comprises the following steps:

the second terminal receives a page access request input by a second user;

determining a target page according to the page access request, and determining each page area contained in the target page;

sending a component acquisition request for acquiring a component positioned in each page area to a server;

receiving a page code corresponding to each component located in the page area, which is determined and sent by the server according to the component acquisition request, as an appointed page code, wherein the page code is a page code received and stored by the server and obtained by compiling the component code by a first terminal, and the component code is a component code of each component contained in a target page generated by the first terminal according to the operation of a first user, and the positions of the components in the target page are not completely the same;

combining the appointed page codes;

and displaying the page area according to the combination result.

Optionally, the displaying the page area according to the combination result specifically includes:

mounting the combined result to obtain the page content corresponding to the page area;

and displaying the page content.

Optionally, after the page codes are combined, the method further includes:

and setting a sandbox environment to ensure that the operation of each appointed page code does not influence each other.

the first terminal generates component codes of all components contained in the target page according to the operation of a first user;

compiling each component code into a page code respectively;

uploading each page code to a server so that a second terminal determines each page area contained in the target page; sending an assembly obtaining request for obtaining the assemblies positioned in the page area to the server aiming at each page area, receiving page codes corresponding to the assemblies positioned in the page area and determined and sent by the server as specified page codes, combining the specified page codes, and displaying the page area according to a combination result;

and the positions of the components in the target page are not completely the same, and the target page is determined by the second terminal according to the received page access request input by the second user.

Optionally, generating a component code of each component included in the target page according to the operation of the first user specifically includes:

according to the operation of a first user, aiming at each component contained in the target page, sending an identification acquisition request for acquiring the component identification of the component to the server;

receiving the component identification of the component sent by the server;

and responding to the operation of the first user, and generating component code and component configuration corresponding to the component identification of the component.

Optionally, uploading each page code to the server specifically includes:

determining a component identifier of a component corresponding to each page code as a designated component identifier;

determining the component configuration corresponding to the specified component identification as the specified component configuration;

uploading the page code and the specified component configuration to the server.

the server receives and stores each page code sent by the first terminal;

receiving a component acquisition request which is sent by a second terminal aiming at each page area contained in a target page and is used for acquiring a component positioned in the page area;

determining page codes corresponding to the components in the page area according to the component acquisition request, taking the page codes as designated page codes, sending the designated page codes to the second terminal, so that the second terminal combines the designated page codes, and displaying the page area according to a combination result;

the page code is obtained by the first terminal compiling the component code of each component contained in the target page, the component code is generated by the first terminal according to the operation of a first user, the target page is a page determined by the second terminal according to a received page access request input by a second user, and the positions of the components in the target page are not identical.

Optionally, receiving each page code sent by the first terminal specifically includes:

receiving an identifier acquisition request which is sent by the first terminal according to the operation of the first user and is used for acquiring the identifier of each component contained in the target page;

responding to the identification acquisition request, generating a component identification of the component, sending the component identification of the component to the first terminal, so that the first terminal responds to the operation of the first user, generates a component code and a component configuration corresponding to the component identification of the component, and compiles the component code corresponding to the component identification of the component into a page code;

and receiving the page code and the component configuration of the component corresponding to the component identifier sent by the first terminal aiming at each component identifier.

Optionally, storing each page code sent by the first terminal specifically includes:

determining the page code and the component configuration of the component corresponding to each component identifier;

and storing the page code of the component corresponding to the component identification in a first storage space according to the component identification, and storing the component configuration of the component corresponding to the component identification in a second storage space.

Optionally, the component acquisition request carries a plurality of component identifiers;

sending each designated page code to the second terminal, specifically including:

aiming at each component identifier carried in the component acquisition request, acquiring a specified page code corresponding to the component identifier from the first storage space according to the component identifier, and acquiring a component configuration corresponding to the component identifier from the second storage space;

and sending each appointed page code and each component configuration to the second terminal.

Optionally, the component acquisition request carries at least one of second user information, network information, and device information;

acquiring at least one component configuration from the second storage space according to at least one of the second user information, the network information and the equipment information;

and sending each appointed page code and at least one component configuration to the second terminal.

The present specification provides a page display apparatus, the apparatus comprising:

the page access request receiving module is used for receiving a page access request input by a second user by a second terminal where the device is located;

a page area determining module, configured to determine a target page according to the page access request, and determine each page area included in the target page;

the sending component acquisition request module is used for sending a component acquisition request for acquiring the components located in the page area to the server aiming at each page area;

a page code receiving module, configured to receive, as an assigned page code, a page code corresponding to each component located in the page area and determined and sent by the server according to the component acquisition request, where the page code is a page code obtained by compiling a component code by a first terminal and received and stored by the server, and the component code is a component code of each component included in a target page generated by the first terminal according to an operation of a first user, where positions of the components in the target page are not completely the same;

the combined page code module is used for combining all the appointed page codes;

and the page area display module is used for displaying the page area according to the combination result.

a component code generation module, configured to generate a component code of each component included in a target page according to an operation of a first user by a first terminal where the apparatus is located;

the compiling component code module is used for compiling each component code into a page code;

the page code uploading module is used for uploading each page code to the server so that the second terminal determines each page area contained in the target page; sending an assembly obtaining request for obtaining the assemblies positioned in the page area to the server aiming at each page area, receiving stored page codes corresponding to the assemblies positioned in the page area and determined and sent by the server as specified page codes, combining the specified page codes, and displaying the page area according to a combination result, wherein the positions of the assemblies in the target page are not completely the same, and the target page is the target page determined by the second terminal according to the received page access request input by the second user.

the page code receiving module is used for receiving and storing each page code sent by the first terminal by the server where the device is located;

the receiving component acquisition request module is used for receiving a component acquisition request which is sent by the second terminal aiming at each page area contained in the target page and is used for acquiring the components positioned in the page area;

and the page code sending module is used for determining page codes corresponding to the components in the page area according to the component acquisition request, taking the page codes as designated page codes, sending the designated page codes to the second terminal so that the second terminal can combine the designated page codes, and displaying the page area according to a combination result, wherein the page codes are obtained by compiling the component codes of the components contained in the target page by the first terminal, the component codes are generated by the first terminal according to the operation of a first user, the target page is a page determined by the second terminal according to a received page access request input by a second user, and the positions of the components in the target page are not identical.

The present specification provides a computer-readable storage medium storing a computer program, which when executed by a processor implements the page display method described above.

The electronic device provided by the present specification includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the page display method when executing the program.

The embodiment of the specification adopts at least one technical scheme which can achieve the following beneficial effects:

the present specification provides a page presentation system, which may comprise: the system comprises a server, a first terminal and a second terminal, wherein the first terminal generates component codes of all components contained in a target page according to the operation of a first user, each component code is compiled into a page code, each page code is uploaded to the server, the positions of all the components in the target page are not identical, the server receives and stores all the page codes, the second terminal receives a page access request input by a second user, the target page is determined according to the page access request, and all page areas contained in the target page are determined; and aiming at each page area, sending an assembly acquisition request for acquiring the assembly positioned in the page area to a server, determining page codes corresponding to the assemblies positioned in the page area by the server according to the assembly acquisition request to be used as specified page codes, sending the specified page codes to a second terminal, combining the specified page codes by the second terminal, and displaying the page area according to a combination result.

It can be seen from the above method that, when a first user develops a target page, the target page may be split into multiple page areas, each page area may include one or more components, so that the first user may separately develop each component in each page area, and when developing a component, the component code is compiled into page code directly at a first terminal, and the page code is stored in a server, without considering compatibility issues of front-end frames. When the target page is modified, only the components needing to be modified can be modified, which is equivalent to the development and maintenance of the whole page in the prior art, and the development process is simplified. And when the second user browses the target page, each component in the target page can be quickly acquired from the server, so that the target page is displayed to the second user.

Drawings

The accompanying drawings, which are included to provide a further understanding of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the description serve to explain the specification and not to limit the specification in a non-limiting sense. In the drawings:

fig. 1 is a flowchart of a page display method provided in an embodiment of the present specification;

FIG. 2 is a flowchart of another page display method provided by an embodiment of the present disclosure;

FIG. 3 is a flowchart of another page displaying method provided by an embodiment of the present specification;

FIG. 4 is a schematic diagram of a complete interaction flow of a page display provided by an embodiment of the present specification;

FIG. 5 is a schematic structural diagram of a page displaying apparatus provided in an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of another page displaying apparatus provided in the embodiments of the present disclosure;

FIG. 7 is a schematic structural diagram of another page displaying apparatus provided in the embodiments of the present disclosure;

fig. 8 is a schematic view of an electronic device provided in an embodiment of the present specification.

Detailed Description

In order to make the objects, technical solutions and advantages of the present disclosure more clear, the technical solutions of the present disclosure will be clearly and completely described below with reference to the specific embodiments of the present disclosure and the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present disclosure, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification without any creative effort belong to the protection scope of the present specification.

In the field of front-end development, typically, a first user (i.e., a developer) develops a complete project, and the complete project may contain many functions and have a plurality of front-end pages, so that developing the complete project may require the developer to write a very large amount of code. In addition, since developers can develop under multiple front-end frameworks, the developers also need to consider compatibility between codes written under different front-end frameworks, and the development threshold for the developers is also high. Once a certain place of a project needs to be modified, a developer needs to position the position to be modified in the code of the whole project for modification, so that the development process is complicated.

Therefore, in order to solve the above problems, the present specification provides a page presentation system, which may include a first terminal, a second terminal, and a server. The first user can generate and compile component codes of all components at the first terminal to obtain page codes, the page codes are uploaded to the server, and after the second terminal determines a target page, all the page codes can be obtained from the server and combined, and the target page is displayed according to a combination result. The first user does not need to develop the whole page (hereinafter referred to as a target page) in a whole manner, but can divide the target page into different page areas, each page area comprises one or more components, each component is developed, and when the second terminal needs to display the target page, the components contained in the target page can be obtained from the server and combined, so that the target page is displayed.

In this specification, a first user may be referred to as a front-end page developer, which is simply referred to as a developer, a second user is a general user browsing front-end pages, and the front-end page developed by the first user (i.e., the front-end page browsed by the second user) may be referred to as a target page. The first terminal and the second terminal may include electronic devices such as a desktop computer and a notebook computer, and the server may be a single device or a distributed server formed by a plurality of devices.

The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings.

Fig. 1 is a flowchart of a page display method provided in an embodiment of the present specification, which specifically includes the following steps:

s100: and the first terminal generates the component codes of all the components contained in the target page according to the operation of the first user.

In this specification, when a first user develops a target page, the target page may be divided into different page areas by a first terminal, and each page area includes at least one component. Thus, the first user may develop for each component.

First, the first terminal may send, to each component included in the target page, an identifier acquisition request for acquiring a component identifier of the component to the server according to an operation of the first user. After receiving the identifier acquisition request sent by the first terminal, the server can determine the component identifier of the component and send the component identifier to the first terminal. The component identifier may include a component id (identity document), such as a component serial number, a component version number, and the like, where each component corresponds to a component identifier, and one component identifier may uniquely identify one component. However, it should be noted that a front-end item may include multiple front-end pages, and different front-end pages may need to use the same component, so that there may be a case where multiple different front-end pages include the same component identifier, and the same component may be included in different front-end pages. Wherein the position of each component in the target page is not identical.

This is because, when developing a component, the first user needs to determine a component identifier of the component in the server through the first terminal, and perform component development under the component identifier, so as to store the developed component in the server according to the component identifier, and facilitate the second terminal to obtain the component from the server according to the component identifier. Of course, the first user may also determine the component identifier through the first terminal, but since different first users may determine the same component identifier, the same component identifier may correspond to multiple components, and therefore, the manner in which the component identifier is determined by the server is considered in priority in this specification.

The first terminal may then receive the component identification of the component sent by the server.

Finally, the first terminal responds to the operation of the first user, and generates a component code corresponding to the component identification of the component and the component configuration.

Specifically, for each component included in the target page, after receiving the component identifier of the component sent by the server, the first terminal may store and display the component identifier to the first user, so that the first user generates, through the first terminal, a group price code and a component configuration corresponding to the component identifier, that is, the component code and the component configuration of the component.

The first terminal may be installed with a development tool, and since the first user may develop using different front end frameworks, the development tool in the first terminal may integrate development tools of a plurality of front end frameworks, which may include Vue frameworks, React frameworks, and the like. In addition, the development tool in the first terminal may integrate the development tools of all functions of the various front-end frameworks. When the development target page only needs to use development tools of partial functions of the front-end frame, the development tools in the first terminal also only need to integrate development tools of functions required by development target pages in different front-end frames.

Through the development tool, the first user can write component codes and component configurations, debug the component codes and the component configurations, and in the process of generating the component through the first terminal, the first user can modify the component codes and/or the component configurations of the component through the development tool.

S102: each component code is compiled separately into page code.

Aiming at each component contained in the target page, the first terminal can compile the component code of the component into a page code, wherein the page code can comprise JS (JavaScript) code and the like, the page code does not need to be pre-compiled, only needs the support of a browser, can be used for adding various dynamic functions to the webpage, and provides a smoother and attractive browsing effect for a user.

Each component corresponds to a component identifier, and the component can be composed of a component code and a component configuration, so that after the component code is compiled into a page code, the page code can be uniquely determined by the component identifier, and the component can be composed of the page code and the component configuration, wherein the component code (or the page code) is used for embodying a function which can be realized after the component is executed, and the component configuration information is used for representing specific contents and details which can be embodied after the component code (or the page code) is executed. For example, executing the component code (or page code) corresponding to the a component can realize jumping from the current page to a certain website, then the component code (or page code) is used for realizing the website jumping function of the a component, and the component configuration information is used for indicating the specific address of the website.

S104: uploading each page code to a server so that a second terminal determines each page area contained in the target page; sending an assembly obtaining request for obtaining the assemblies positioned in the page area to the server aiming at each page area, receiving page codes corresponding to the assemblies positioned in the page area and determined and sent by the server as specified page codes, combining the specified page codes, and displaying the page area according to a combination result; and the positions of the components in the target page are not completely the same, and the target page is determined by the second terminal according to the received page access request input by the second user.

After the first terminal compiles the component codes of the components into the page codes, the page codes of the components and the component configurations can be uploaded to the server.

Specifically, for each page code, a component identifier of a component corresponding to the page code may be determined as a designated component identifier, then, a component configuration corresponding to the designated component identifier is determined as a designated component configuration, and the page code and the designated component configuration are uploaded to a server.

That is, for each component, the first terminal may determine a component identifier, a page code, and a component configuration of the component, and the component identifier corresponds to the page code and the component identifier and corresponds to the component configuration, so that the page code and the component configuration of the component may be uploaded to a service according to the component identifier of the component, so that the server stores the page code and the component configuration of the component according to the component identifier of the component. After the server stores the page codes and the component configurations of the components, when a second user browses a target page, the second terminal receives a page access request input by the second user, can determine the target page according to the page access request, determines each page area contained in the target page, and can send a component acquisition request for acquiring the components located in the page area to the server for each page area.

The server stores the page code of the component and the component configuration, and the second terminal obtains the component from the server and presents the content of the target page to the second user, which will be described in detail below.

In the present specification, the above-mentioned content describes the page display method in detail in terms of standing at the first terminal, and in the page display system, in addition to the first terminal, the page display system further includes a second terminal and a server, so that the present specification provides a page display method in terms of standing at the server, as shown in fig. 2.

Fig. 2 is a flowchart of another page display method provided in the embodiment of the present specification, which specifically includes the following steps:

s200: the server receives and stores each page code sent by the first terminal; the page code is obtained by the first terminal compiling the component code of each component contained in the target page, and the component code is generated by the first terminal according to the operation of a first user.

In this specification, the server may receive, by the first terminal, an identifier obtaining request for obtaining a component identifier of each component included in the target page, sent by the first terminal according to an operation of the first user, generate, in response to the identifier obtaining request, the component identifier of the component, and send the component identifier of the component to the first terminal, so that the first terminal generates, in response to the operation of the first user, a component code and a component configuration corresponding to the component identifier of the component, and compiles the component code corresponding to the component identifier of the component into the page code. For each component identifier, the server may receive the page code of the component corresponding to the component identifier and the component configuration sent by the first terminal.

The server may receive identifier acquisition requests sent by the plurality of first terminals, may send a component serial number or a component version number, etc. as a component identifier to the first terminals when determining the component identifier of the component, and may uniquely determine the component due to the component identifier, so that the component identifiers are different from each other in the server. After the server sends the component identifier of the component to the first terminal, the first terminal may generate a component code and a component configuration of the component, may compile the component code of the component into a page code, and may upload the page code and the component configuration of the component to the server.

In the server, a first storage space and a second storage space may be provided. When the server receives each page code sent by the first terminal, the server determines a component identifier corresponding to the page code aiming at each page code, stores the page code in a first storage space according to the component identifier corresponding to the page code, determines a component identifier corresponding to the component configuration aiming at each component configuration when the server receives each component configuration sent by the first terminal, and stores the component configuration in a second storage space according to the component identifier corresponding to the component configuration. That is, after receiving each component sent by the first terminal, the server determines the component identifier of the component for each component, stores the page code of the component in the first storage space according to the component identifier of the component, and stores the component configuration of the component in the second storage space. In addition, the server can also determine the page code and the component configuration of the component corresponding to each component identifier, store the page code of the component corresponding to the component identifier in the first storage space according to the component identifier, and store the component configuration of the component corresponding to the component identifier in the second storage space.

S202: receiving a component acquisition request which is sent by a second terminal aiming at each page area contained in a target page and is used for acquiring a component positioned in the page area; the target page is a page determined by the second terminal according to a received page access request input by the second user, and the positions of the components in the target page are not completely the same.

S204: and determining page codes corresponding to the components in the page area according to the component acquisition request, taking the page codes as designated page codes, sending the designated page codes to the second terminal so that the second terminal combines the designated page codes, and displaying the page area according to a combination result.

After storing the page code and the component configuration in the server, the server may send the component to the first terminal and the second terminal.

First, a server may receive a request for acquiring a component sent by a first terminal, where the request for acquiring the component may carry a component identifier, and the server may determine a page code from a first storage space according to the component identifier, determine a component configuration from a second storage space, and send the page code and the component configuration to the first terminal. After receiving the page code and the component configuration, the first terminal may modify the page code or the component configuration, and upload the modified page code or the modified component configuration to the server again, that is, the first terminal may acquire the component from the server and modify the component, where a component identifier of the modified component may be the same as or different from a component identifier of the component before modification.

In other words, when the second terminal needs to acquire a component from the server, that is, the second terminal determines that the target page needs to be displayed to the second user according to the operation of the second user, the second terminal may determine each page area included in the target page, and send a component acquisition request for acquiring the component located in the page area to the server for each page area. The server may receive a component acquisition request sent by the second terminal, where the component acquisition request also carries the component identifier of each component included in the page area. The server can acquire the designated page code corresponding to the component identifier from the first storage space according to the component identifier for each component identifier carried in the component acquisition request, acquire the component configuration corresponding to the component identifier from the second storage space, and send each designated page code and each component configuration to the second terminal. And after the second terminal receives the page codes and the component configuration, the second terminal can combine the page codes and display the target page according to a combination result.

In addition, when the component configuration is obtained from the server, the component obtaining request may further carry at least one of second user information, network information, and device information. The server can acquire at least one component configuration from the second storage space according to at least one of the second user information, the network information and the equipment information, and send each designated page code and the at least one component configuration to the second terminal. For example, the component is configured to be the number of buttons, when the network speed is high, the component is configured to be five buttons, when the network speed is low, the component is configured to be three buttons, if the server determines that the network speed of the second terminal is low according to the network information carried in the component acquisition request, the server determines that the number of the buttons is three (that is, the component configuration) when the network speed is low, and sends the corresponding component configuration when the network speed is low to the second terminal. For another example, when the second user information is a frequent browsing type, the component is configured as five buttons, when the second user information is an occasional browsing type, the component is configured as three buttons, and if the server determines that the second user information is the occasional browsing type according to the second user information carried in the component acquisition request, the server may determine that the second user information is a frequent browsing type, and may send the component configuration of the three buttons to the second terminal. For another example, when the device information is the first operating system, the component is configured as five buttons, when the device information is the second operating system, the component is configured as three buttons, and if the server determines that the server is the second operating system according to the device information carried in the component acquisition request, the server may determine that the device information is the three buttons, and send the component configuration of the three buttons to the second terminal. The above is only an example of the network information, and when the server acquires component configurations according to other information, and the same type of information and information contents are different, the acquired component configurations are not completely the same, for example, the other information may include a browser version, and when the browser version is the latest version, the acquired component configuration is a full version of the component configuration, and when the browser version is the version to be updated, the acquired component configuration is a reduced version of the component configuration.

In this specification, the above description describes the page display method in detail in terms of standing at the server, and in the page display system, a second terminal is included in addition to the first terminal and the server, so that the specification provides a page display method in terms of standing at the second terminal, as shown in fig. 3.

Fig. 3 is a flowchart of another page display method provided in an embodiment of the present specification, which specifically includes the following steps:

s300: and the second terminal receives a page access request input by a second user.

S302: and determining a target page according to the page access request, and determining each page area contained in the target page.

In this specification, the second terminal may monitor an operation of the second user, and receive a page access request input by the second user according to the operation of the second user. The operation of the second user is not limited, for example, the second user clicks a button, and the page code corresponding to the button implements the page jump function, and the component corresponding to the button is configured as a specific website of the page after the jump.

The page access request input by the second user may carry a page identifier (e.g., a Uniform Resource Locator (URL)), and the second terminal may determine a corresponding page according to the page identifier, which is used as the target page. And after the second terminal determines the target page, each page area contained in the target page can be determined. Because the front-end page may include a page frame and a component identifier, the second terminal may divide a plurality of page areas according to the page frame, and may also divide a plurality of page areas according to the position of each component in the target page, where each page area includes one or more components. It should be noted that, because each page is previously developed and completed by the first user through the first terminal, the target page determined by the second terminal is necessarily one of the target pages previously developed and completed by the first user through the first terminal, and the target page developed and completed by the first user through the first terminal is not necessarily the target page determined by the second terminal.

In addition, the first terminal and the second terminal can divide the target page into a plurality of page areas in the same way, and can also divide the target page into a plurality of page areas in different ways. Regardless of the way of dividing the page areas, each page area comprises at least one component, the first user develops the target page by taking the component as a unit, and the second terminal is also obtained from the server by taking the component as a unit.

S304: and sending a component acquisition request for acquiring the components positioned in the page area to the server for each page area.

S306: and receiving a page code corresponding to each component located in the page area, which is determined and sent by the server according to the component acquisition request, as an appointed page code, wherein the page code is a page code received and stored by the server and obtained by compiling the component code by a first terminal, and the component code is a component code of each component contained in a target page generated by the first terminal according to the operation of a first user, and the positions of the components in the target page are not completely the same.

After the second terminal determines each page area included in the target page, a component acquisition request for acquiring a component located in the page area can be sent to the server for each page area. After receiving the component acquisition request, the server can determine the page codes of the components in the page area as the designated page codes and the component configuration, and send the designated page codes and the component configuration to the second terminal, and the second terminal can receive the designated page codes and the component configuration sent by the server. For the way that the first terminal generates the component code and compiles the component code into the page code to upload to the server, reference may be made to the above contents, and details are not repeated in this specification.

After determining each designated page code and each component configuration, the server can match the component identifier corresponding to each designated page code with the component identifier corresponding to each component configuration, combine the successfully matched designated page code with the component configuration, and send the combined designated page code and the component configuration to the second terminal.

Or the server can send each designated page code and each component configuration to the second terminal, the second terminal matches the component identifier corresponding to each designated page code with the component identifier corresponding to each component configuration, and the successfully matched designated page code is combined with the component configuration.

S308: and combining the specified page codes.

After combining the designated page code with the component configuration, the second terminal may combine each designated page code, and it should be noted that, since the designated page code is previously combined with the component configuration, each component is actually combined when each designated page code is combined here.

Specifically, the second terminal can determine the position of each component in the target page, and combine the components according to the positions of the components in the target page.

S310: and displaying the page area according to the combination result.

After the second terminal combines the designated page codes, that is, after the components are combined, the combined result can be mounted to obtain the page content corresponding to the page area, so that the page content corresponding to the page area is displayed, that is, the page content of the target page is displayed.

Specifically, the specified page code may generate page data, the page data may include a Document Object Model (DOM), and the second terminal may add the page data generated by the specified page code to the page data in the target page, so as to mount the component and obtain the page content of the target page.

In this specification, since the first user performs development of a target page in units of components when developing the target page, there may be a case where the same parameter name is used in different component codes/page codes, and the meanings that the same parameter name may represent in different component codes/page codes are different. After the appointed page codes are combined, in order to avoid the situation that the codes are wrong due to the fact that the same parameter name exists in different components, the second terminal can be provided with a sandbox environment, and when the components run in the sandbox environment, the components do not affect each other. For example, there is a parameter named z in the component X, which indicates the number of buttons, there is a parameter named z in the component Y, which indicates the color of the buttons, if the second terminal does not set the sandbox environment, the parameter z may be in error when the component X and the component Y are running, and when the second terminal sets the sandbox environment, different prefixes may be set in the parameter z in the component X and the component Y, respectively, in the component X, the parameter z may be represented as X _ z, and in the component Y, the parameter z may be represented as Y _ z, and from the page code of the whole target page, there is no same parameter in the component X and the component Y, so that the running of the component X and the component Y does not affect each other.

In this specification, both the first terminal and the second terminal may interact with the server to implement page display, and fig. 4 is a schematic diagram of a complete interaction flow of page display provided in an embodiment of this specification, as shown in fig. 4.

As can be seen from the figure, the first terminal may send, according to the operation of the first user, an identifier obtaining request for obtaining a component identifier of each component included in the target page to the server. After receiving the identifier acquisition request sent by the first terminal, the server can determine the component identifier of the component and send the component identifier to the first terminal. The first terminal can generate component codes and component configurations corresponding to the component identifications according to the operation of the first user, compile the component codes into page codes, and upload the page codes and the component configurations to the server.

After receiving the page codes and the component configuration, the server can store the page codes in the first storage space and store the component configuration in the second storage space according to the component identification.

The second terminal can determine a target page and each page area contained in the target page according to the operation of a second user, and can send an assembly obtaining request for obtaining an assembly located in the page area to the server aiming at each page area.

Based on the page display method shown in fig. 1, an embodiment of the present specification further provides a schematic structural diagram of a page display apparatus, as shown in fig. 5.

Fig. 5 is a schematic structural diagram of a page displaying device provided in an embodiment of the present specification, where the page displaying device includes:

a module 501 for generating component codes, configured to generate component codes of components included in a target page according to an operation of a first user by a first terminal where the apparatus is located;

a compile component code module 502 for compiling each component code into a page code, respectively;

an upload page code module 503, configured to upload each page code to a server, so that the second terminal determines each page area included in the target page; sending an assembly obtaining request for obtaining the assemblies positioned in the page area to the server aiming at each page area, receiving stored page codes corresponding to the assemblies positioned in the page area and determined and sent by the server as specified page codes, combining the specified page codes, and displaying the page area according to a combination result, wherein the positions of the assemblies in the target page are not completely the same, and the target page is the target page determined by the second terminal according to the received page access request input by the second user.

Optionally, the module 501 for generating a component code is specifically configured to, according to an operation of a first user, send, to the server, an identifier obtaining request for obtaining a component identifier of the component, for each component included in the target page; receiving the component identification of the component sent by the server; and responding to the operation of the first user, and generating component code and component configuration corresponding to the component identification of the component.

Optionally, the upload page code module 503 is specifically configured to, for each page code, determine a component identifier of a component corresponding to the page code, where the component identifier is used as a specified component identifier; determining the component configuration corresponding to the specified component identification as the specified component configuration; uploading the page code and the specified component configuration to the server.

Based on the page display method shown in fig. 2, the embodiment of the present specification further provides a schematic structural diagram of another page display apparatus, as shown in fig. 6.

Fig. 6 is a schematic structural diagram of another page displaying apparatus provided in an embodiment of the present specification, where the apparatus includes:

a page code receiving module 601, configured to receive and store each page code sent by the first terminal by a server where the apparatus is located;

a receiving component obtaining request module 602, configured to receive a component obtaining request, which is sent by a second terminal for each page area included in a target page and is used for obtaining a component located in the page area;

a page code sending module 603, configured to determine, according to the component acquisition request, a page code corresponding to each component located in the page area, as an assigned page code, and send the assigned page code to the second terminal, so that the second terminal combines the assigned page codes, and displays the page area according to a combination result, where the page code is obtained by compiling, by the first terminal, the component code of each component included in the target page, the component code is a component code generated by the first terminal according to an operation of a first user, the target page is a page determined by the second terminal according to a received page access request input by a second user, and positions of the components in the target page are not completely the same.

Optionally, the page code receiving module 601 is specifically configured to receive an identifier obtaining request, sent by the first terminal according to the operation of the first user, for obtaining a component identifier of each component included in the target page; responding to the identification acquisition request, generating a component identification of the component, sending the component identification of the component to the first terminal, so that the first terminal responds to the operation of the first user, generates a component code and a component configuration corresponding to the component identification of the component, and compiles the component code corresponding to the component identification of the component into a page code; and receiving the page code and the component configuration of the component corresponding to the component identifier sent by the first terminal aiming at each component identifier.

Optionally, the page code receiving module 601 is specifically configured to, for each component identifier, determine a page code and a component configuration of a component corresponding to the component identifier; and storing the page code of the component corresponding to the component identification in a first storage space according to the component identification, and storing the component configuration of the component corresponding to the component identification in a second storage space.

the page code sending module 603 is specifically configured to, for each component identifier carried in the component acquisition request, acquire, according to the component identifier, a specified page code corresponding to the component identifier from the first storage space, and acquire, from the second storage space, a component configuration corresponding to the component identifier; and sending each appointed page code and each component configuration to the second terminal.

the page code sending module 603 is specifically configured to obtain at least one component configuration from the second storage space according to at least one of the second user information, the network information, and the device information; and sending each appointed page code and at least one component configuration to the second terminal.

Based on the page display method shown in fig. 3, the embodiment of the present specification further provides a schematic structural diagram of another page display apparatus, as shown in fig. 7.

Fig. 7 is a schematic structural diagram of another page displaying device provided in an embodiment of the present specification, the device including:

a page access request receiving module 701, configured to receive, by a second terminal where the apparatus is located, a page access request input by a second user;

a page area determining module 702, configured to determine a target page according to the page access request, and determine each page area included in the target page;

a sending component obtaining request module 703, configured to send, to the server, a component obtaining request for obtaining a component located in each page area;

a page code receiving module 704, configured to receive, as an assigned page code, a page code corresponding to each component located in the page area and determined and sent by the server according to the component acquisition request, where the page code is a page code obtained by compiling a component code by a first terminal and received and stored by the server, and the component code is a component code of each component included in a target page generated by the first terminal according to an operation of a first user, where positions of the components in the target page are not completely the same;

a combined page code module 705, configured to combine each specified page code;

a page area displaying module 706, configured to display the page area according to the combination result.

Optionally, the page area displaying module 706 is specifically configured to mount the combined result to obtain page content corresponding to the page area; and displaying the page content.

Optionally, the apparatus further comprises an isolation module 707;

the isolation module 707 is specifically configured to set a sandbox environment so that operations of the designated page codes are not affected by each other.

The embodiment of the present specification further provides a computer-readable storage medium, where a computer program is stored, and the computer program may be used to execute the page presentation method provided by the foregoing content.

Based on the page display method shown in the above, the embodiment of the present specification further provides a schematic structure diagram of the electronic device shown in fig. 8. As shown in fig. 8, at the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, but may also include hardware required for other services. The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs the computer program to realize the page display method.

Of course, besides the software implementation, the present specification does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may be hardware or logic devices.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.

As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the scope of the claims of the present specification.

Claims

1. A page presentation system, said system comprising: the system comprises a server, a first terminal and a second terminal; wherein:

the server receives and stores each page code;

2. The page display method is characterized by comprising the following steps:

the second terminal receives a page access request input by a second user;

combining the appointed page codes;

and displaying the page area according to the combination result.

3. The method of claim 2, wherein the displaying the page area according to the combined result specifically comprises:

and displaying the page content.

4. A method according to any of claims 2-3, wherein after combining the page codes, the method further comprises:

5. The page display method is characterized by comprising the following steps:

compiling each component code into a page code respectively;

6. The method of claim 5, wherein generating component codes of components included in the target page according to the operation of the first user specifically comprises:

receiving the component identification of the component sent by the server;

7. The method of claim 6, wherein uploading each page code to a server specifically comprises:

8. The page display method is characterized by comprising the following steps:

the server receives and stores each page code sent by the first terminal;

9. The method of claim 8, wherein receiving each page code sent by the first terminal specifically comprises:

10. The method of claim 9, wherein storing each page code sent by the first terminal specifically comprises:

11. The method of claim 10, wherein the component acquisition request carries a number of component identifications;

12. The method according to claim 10, wherein the component acquisition request carries at least one of second user information, network information, and device information;

13. Page display apparatus, characterized in that said apparatus comprises:

14. Page display apparatus, characterized in that said apparatus comprises:

15. Page display apparatus, characterized in that said apparatus comprises:

16. A computer-readable storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method of any of the preceding claims 2-4 or 5-7 or 8-12.

17. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any of the preceding claims 2-4 or 5-7 or 8-12 when executing the program.