CN113360341B

CN113360341B - Front-end application maintenance and loading method and device

Info

Publication number: CN113360341B
Application number: CN202110625744.2A
Authority: CN
Inventors: 刘思贤
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2021-06-04
Filing date: 2021-06-04
Publication date: 2024-02-06
Anticipated expiration: 2041-06-04
Also published as: CN113360341A

Abstract

The present disclosure relates to a front-end application maintenance and loading method and apparatus, wherein a front-end application maintenance method is applied to a back-end server having a communication connection with a front-end application, and a display interface of the front-end application includes a plurality of interface units interacting with a user execution interface; the back-end server stores a common interface function module corresponding to a plurality of interface units and at least one individual interface function module corresponding to at least one interface unit in the plurality of interface units respectively; the front-end application maintenance method comprises the following steps: receiving a maintenance instruction of an interface unit in a front-end application; and determining a personalized interface function module corresponding to the interface unit identifier, and executing the maintenance operation on the personalized interface function module. The back-end server can independently maintain the individual interface function modules of the interface unit without reconstructing and updating the whole interface code package, and the maintenance efficiency of the back-end server can be improved due to the small data volume and complexity of the individual interface function modules.

Description

Front-end application maintenance and loading method and device

Technical Field

The disclosure relates to the technical field of internet, and in particular relates to a front-end application maintenance and loading method and device.

Background

In the internet, a communication architecture of a front-end application and a back-end server is generally adopted, and the front-end application includes a plurality of interface units for performing interface interactions with a user. To achieve a smooth user experience, the front-end application may employ a single page application mode.

In the single-page application mode, the back-end server stores an integral interface code package of the front-end application, wherein the integral interface code package comprises interface codes for realizing all interface units in the front-end application, namely, the interface codes of all the interface units are coupled together.

In order to better serve users, the interface units of the front-end application need to be iteratively updated, and interface codes of a certain interface unit need to be deleted or updated during the iterative updating. Because the interface codes of all the interface units in the back-end server are coupled together, when the front-end application is maintained each time, the whole interface code package needs to be reconstructed and updated, and the interface code of a certain interface unit cannot be maintained independently, so that the maintenance efficiency of the interface unit in the back-end server is lower.

Disclosure of Invention

The disclosure provides a front-end application maintenance and loading method and device, which at least solve the problem that the maintenance efficiency of an interface unit in a back-end server is low because a certain interface unit cannot be maintained independently in the related art. The technical scheme of the present disclosure is as follows:

According to a first aspect of an embodiment of the present disclosure, a front-end application maintenance method is provided and applied to a back-end server having a communication connection with a front-end application, where a presentation interface of the front-end application includes a plurality of interface units that interact with a user execution interface;

the back-end server stores the common interface function modules corresponding to the plurality of interface units and at least one individual interface function module corresponding to at least one interface unit in the plurality of interface units respectively;

the front-end application maintenance method comprises the following steps:

receiving a maintenance instruction of an interface unit in the front-end application; wherein the maintenance instruction at least comprises an interface unit identifier and a maintenance operation of the interface unit;

determining a personalized interface function module corresponding to the interface unit identifier;

and executing the maintenance operation on the personality interface function module.

Wherein, if the maintenance operation is a delete operation, the performing the maintenance operation on the personality interface function module includes: deleting the personalized interface function module corresponding to the interface unit identifier;

or,

the maintenance operation is an update operation, the maintenance instruction further includes a latest personality interface function module of the interface unit, and the performing the maintenance operation on the personality interface function module includes: and replacing the existing personality interface function module with the latest personality interface function module.

Before receiving a maintenance instruction of an interface unit in the front-end application, the method further comprises:

determining a common interface code package set corresponding to the plurality of interface units, and constructing the common interface function module based on the common interface code package set;

executing, for each interface unit of at least one interface unit of the plurality of interface units: determining a personalized interface code package corresponding to an interface unit, and constructing a personalized interface function module corresponding to the interface unit based on the personalized interface code package;

and storing the common interface function module and at least one individual interface function module corresponding to at least one interface unit respectively.

Wherein the determining the common interface code packet set corresponding to the plurality of interface units includes:

constructing a common function code block in two or more interface units in the whole interface code package into a common interface code package; wherein the whole interface code comprises functional code blocks of the plurality of interface units;

repeatedly executing the step of constructing the common function code blocks in two or more interface units in the whole interface code package into one common interface code package to obtain a plurality of common interface code packages;

And forming the plurality of common interface code packages into the common interface code package set.

Wherein, the determining a personalized interface code package corresponding to an interface unit includes:

determining an independent interface code package corresponding to an interface unit;

comparing the independent interface code package with the common interface code package set, and determining one or more common interface code packages with intersections of the independent interface code package and the common interface code package set;

deleting one or more common interface code packages from the independent interface code packages to obtain a residual interface code package;

and taking the residual interface code package as a personalized interface code package corresponding to the interface unit.

Wherein the constructing the common interface function module based on the common interface code package set includes:

for at least one interface unit of the plurality of interface units: recording one or more common interface code package identifiers deleted by each interface unit respectively;

setting an initial display interface and a callback function corresponding to the at least one interface unit respectively;

constructing a first loader for loading the personality interface function module;

constructing a common interface function module of the front-end application based on the common interface code packet set;

The common interface function module comprises one or more common interface code package identifications deleted by the at least one interface unit, an initial presentation interface and a callback function, and the first loader.

The constructing the personalized interface function module corresponding to the interface unit based on the personalized interface code package comprises the following steps:

recording the deleting information of one interface unit; wherein the deletion information includes a deletion location of one or more common interface code packages deleted by the interface unit, and the one or more common interface code package identifications;

constructing a second loader for loading the personalized interface code package;

and constructing a personalized interface function module of the interface unit based on the personalized interface code package of the interface unit, the deleting information and the second loader.

According to a second aspect of the present disclosure, there is provided a front-end application loading method applied to a front-end application having a communication connection with a back-end server, a presentation interface of the front-end application including a plurality of interface units interacting with a user execution interface;

The front-end application maintenance method comprises the following steps:

sending an initial loading request to the back-end server;

obtaining an initial loading packet sent by the back-end server; wherein the initial loading package comprises the commonality interface function module;

running the initial loading package to finish the initial loading operation of the front-end application;

and under the condition that the triggering operation of one interface unit in the at least one interface unit is received, acquiring and loading the personalized interface function module of the interface unit from the back-end server.

Wherein, the commonality interface function module includes:

a common interface code packet set formed by a plurality of common function code blocks of two or more interface units in the plurality of interface units;

one or more common interface code package identifications, initial presentation interfaces and callback functions deleted by at least one interface unit; the method comprises the steps of,

and the first loader is used for loading the personality interface function module.

Wherein, under the condition that the triggering operation of one interface unit in the at least one interface unit is received, the personalized interface function module for acquiring and loading the interface unit from the back-end server comprises:

if the triggering operation of one interface unit in the at least one interface unit is received, acquiring a personalized interface function module corresponding to the interface unit from the back-end server;

Determining one or more common interface code package identifiers deleted by the interface unit from the common interface function module;

invoking the first loader, and injecting one or more common interface code packages corresponding to one or more common interface code package identifiers from the common interface function module to the personality interface function module;

and calling a callback function corresponding to the interface unit to drive the personalized interface function module.

The interface unit comprises a personal interface code package, deleting information and a second loader;

wherein the deletion information includes a deletion location of one or more common interface code packages deleted by the interface unit, and the one or more common interface code package identifications.

Wherein, the calling the callback function corresponding to the interface unit, and driving the personalized interface function module comprises:

calling a callback function corresponding to the interface unit to execute the following operations by using the callback function:

for one or more commonality interface code packages injected: and calling the second loader to load a common interface code package, and executing the following judging operation in the loading process:

If the deleting positions corresponding to the common interface code packages in the individual interface code packages have the same function code packages, the common interface code packages are not injected; if the deleting position corresponding to the common interface code packet in the individual interface code packet does not have the same function code packet, adding the common interface code packet in the deleting position;

obtaining an updated personalized interface code package;

and executing the updated personalized interface code package, and displaying the interface unit content.

Wherein, the running the initial loading package, and completing the initial loading operation of the front-end application includes:

operating a common interface code package set in the common interface function module of the initial loading package to obtain an initial interface frame;

and displaying an initial display interface of at least one interface unit in an interface window corresponding to the at least one interface unit in the initial interface frame.

Wherein the initial load package further comprises: the coupling interface code package of other interface units except the at least one interface unit in the front-end application;

the running the initial loading package, and completing the initial loading operation of the front-end application includes:

Displaying an initial display interface of at least one interface unit in an interface window corresponding to the at least one interface unit in the initial interface frame; and executing the coupling interface code package, and displaying the content of the interface unit in the interface windows corresponding to the rest of the interface units in the initial interface frame.

According to a third aspect of the present disclosure, there is provided a front-end application maintenance apparatus applied to a back-end server having a communication connection with a front-end application, a presentation interface of the front-end application including a plurality of interface units that interact with a user execution interface;

the front-end application maintenance device includes:

the receiving unit is configured to execute and receive a maintenance instruction of an interface unit in the front-end application; wherein the maintenance instruction at least comprises an interface unit identifier and a maintenance operation of the interface unit;

a determining unit configured to perform determining a personality interface function module corresponding to the interface unit identifier;

And the execution unit is configured to execute the maintenance operation on the personality interface function module.

The maintenance operation is a deletion operation, and the execution unit is specifically configured to execute deletion of the personalized interface function module corresponding to the interface unit identifier;

or,

and if the maintenance operation is an updating operation, the maintenance instruction further comprises a latest personality interface function module of the interface unit, and the execution unit is specifically configured to execute replacing the existing personality interface function module with the latest personality interface function module.

Wherein, before the receiving unit, further comprises:

a common module unit configured to execute the determination of a common interface code package set corresponding to the plurality of interface units, and construct the common interface function module based on the common interface code package set;

determining a personality module unit configured to perform, for each of at least one interface unit of the plurality of interface units: determining a personalized interface code package corresponding to an interface unit, and constructing a personalized interface function module corresponding to the interface unit based on the personalized interface code package;

And the storage unit is configured to execute and store the common interface function modules and at least one individual interface function module corresponding to at least one interface unit respectively.

The determining common module unit is configured to determine a common interface code packet set corresponding to the plurality of interface units, and specifically configured to:

The personality interface code package corresponding to one interface unit is determined in the personality determining module unit, and is specifically configured to:

The common interface function module is constructed based on the common interface code package set in the common module determining unit, and is specifically configured to:

The personality interface function module corresponding to the interface unit is constructed based on the personality interface code package in the personality module determining unit, and is specifically configured to:

According to a fourth aspect of the disclosure, there is provided a front-end application loading apparatus applied to a front-end application having a communication connection with a back-end server, a presentation interface of the front-end application including a plurality of interface units interacting with a user execution interface;

the front-end application maintenance device includes:

a transmitting unit configured to transmit an initial loading request to the backend server;

the acquisition unit is configured to acquire an initial loading packet sent by the back-end server; wherein the initial loading package comprises the commonality interface function module;

The operation unit is configured to operate the initial loading package and complete the initial loading operation of the front-end application;

the loading unit is configured to acquire and load the personalized interface function module of one interface unit from the back-end server under the condition that the triggering operation of the interface unit is received.

Wherein, the commonality interface function module includes:

Wherein the loading unit is specifically configured to:

the acquisition module unit is configured to acquire a personalized interface function module corresponding to the interface unit from the back-end server if a triggering operation of one interface unit in the at least one interface unit is received;

a determining and identifying unit configured to determine one or more common interface code package identifiers deleted by the interface unit from the common interface function module;

The calling unit is configured to call the first loader, and one or more common interface code packages corresponding to one or more common interface code package identifiers are injected into the personality interface function module from the common interface function module;

and the driving unit is configured to call a callback function corresponding to the interface unit and drive the personalized interface function module.

Wherein the drive unit is specifically configured to:

Obtaining an updated personalized interface code package;

Wherein the operation unit is specifically configured to:

the frame unit is configured to run a common interface code package set in the common interface function module of the initial loading package to obtain an initial interface frame;

and the display unit is configured to display the initial display interface of the at least one interface unit in the interface window corresponding to the at least one interface unit in the initial interface frame.

According to a fifth aspect of the present application there is provided a server comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement a front-end application maintenance method.

According to a sixth aspect of the present application there is provided an electronic device comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement a front-end application loading method.

According to a seventh aspect of the present application, there is provided a computer readable storage medium, which when executed by a processor of a server, enables the processor to perform a front-end application maintenance method.

According to an eighth aspect of the present application, there is provided a computer readable storage medium, which when executed by a processor of an electronic device, causes the processor to perform a front-end application loading method.

According to a ninth aspect of the present application there is provided a computer program product enabling a server to perform a front-end application maintenance method when instructions in the computer program product are executed by a processor of the server.

According to a tenth aspect of the present application, there is provided a computer program product, which when executed by a processor of a server, enables the server to perform a front-end application loading method.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

in the disclosure, a back-end server stores common interface function modules corresponding to a plurality of interface units in a front-end application, and individual interface function modules of at least one interface unit; i.e. the interface codes of at least one interface unit in the back-end server are no longer coupled together, but have separate personality interface function modules.

Therefore, the back-end server can independently maintain the individual interface function module of at least one interface unit without reconstructing and updating the whole interface code package, and compared with the construction and updating of the whole interface code package, the individual interface function module of the single interface unit can improve the maintenance efficiency of the interface unit in the back-end server because the data volume and the complexity of the individual interface function module are smaller than those of the whole interface code package.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.

FIG. 1 is a flow chart illustrating one embodiment of a front end application maintenance method according to one exemplary embodiment;

FIG. 2 is a flow chart illustrating a front end application maintenance method embodiment two according to an exemplary embodiment;

FIG. 3 is a flow chart illustrating one embodiment of a front end application loading method according to one exemplary embodiment;

FIG. 4 is a flow chart illustrating a front end application loading method embodiment two according to an exemplary embodiment;

FIG. 5 is a specific embodiment of a front-end application loading method, according to an exemplary embodiment;

FIG. 6 is a schematic diagram of a front end application maintenance device, according to an example embodiment;

FIG. 7 is a schematic diagram of a front-end application loading apparatus, according to an example embodiment;

FIG. 8 is a block diagram illustrating a front-end application maintenance device, according to an example embodiment;

FIG. 9 is a block diagram illustrating a front-end application loading apparatus according to an example embodiment.

Detailed Description

Technical terms:

single-page application (SPA) is a model of a web application or website that interacts with a user by dynamically rewriting the current interface, rather than reloading the entire current interface from a backend server in a traditional manner. The method avoids interface switching and breaking user experience, so that the front-end application is more similar to a desktop application program, and smooth user experience comparable to the desktop program can be achieved.

In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

Fig. 1 is a flow chart of a first embodiment of a front-end application maintenance method according to an exemplary embodiment for use with a back-end server having a communication connection with a front-end application. Referring to fig. 1, a front-end application maintenance method embodiment first includes the following steps.

In this embodiment, the display interface of the front-end application includes a plurality of interface units that interact with the user execution interface, and the back-end server stores common interface function modules corresponding to the plurality of interface units in the front-end application, and at least one individual interface function module corresponding to at least one interface unit in the plurality of interface units.

The individual interface function modules of at least one interface unit and the overall interface code package are no longer coupled to each other but are independent of each other. Details can be seen in the second embodiment shown in fig. 2, and will not be described again here.

In step S101, a maintenance instruction of an interface unit in the front-end application is received; wherein the maintenance instruction at least comprises an interface unit identifier and a maintenance operation of the interface unit.

The back-end server stores at least one individual interface function module corresponding to at least one interface unit respectively, and can receive a maintenance instruction for one interface unit under the condition that one interface unit needs to be maintained independently.

In order to distinguish between different interface units and between different maintenance operations, the maintenance instructions comprise at least an interface unit identification of the interface unit and a maintenance operation.

In step S102, a personality interface function module corresponding to the interface unit identifier is determined.

In step S103, the maintenance operation is performed on the personality interface function module.

First case: the maintenance operation is a delete operation, and the performing the maintenance operation on the personality interface function module includes: deleting the personalized interface function module corresponding to the interface unit identifier;

second case:

the maintenance operation is an update operation, and the maintenance instruction further includes a latest personality interface function module of the interface unit, and the performing the maintenance operation on the personality interface function module includes: and replacing the existing personality interface function module with the latest personality interface function module.

in the disclosure, a back-end server stores common interface function modules corresponding to a plurality of interface units in a front-end application, and at least one individual interface function module corresponding to at least one interface unit respectively; i.e. the interface codes of at least one interface unit in the back-end server are no longer coupled together, but have separate personality interface function modules.

Fig. 2 is a flowchart of a second embodiment of a front-end application maintenance method according to an exemplary embodiment, applied to a back-end server. Referring to fig. 2, a front-end application maintenance method embodiment includes the following steps.

In step S201, a common interface code package set corresponding to a plurality of interface units is determined. According to one embodiment provided in the present disclosure, the step S201 may be implemented by the following steps:

step S11: and constructing the common function code blocks in two or more interface units in the whole interface code package into a common interface code package.

The back-end server stores an integral interface code package corresponding to a plurality of interface units in the front-end application, namely the integral interface code package comprises interface codes of all the interface units, and the interface codes of all the interface units are coupled together.

It can be understood that some common functions exist among the interface units, and the back-end server can analyze the interface codes in the whole interface code package under the cooperation of technicians and collect code blocks with the common functions in two or more interface units.

And counting code blocks with common functions in two or more interface units to obtain common function code blocks. And packaging the commonality function code blocks into a commonality interface code package.

Step S12: repeating the step of constructing the common function code blocks in two or more interface units in the whole interface code package into one common interface code package to obtain a plurality of common interface code packages.

It will be appreciated that different interface units may have different common function code blocks, so step S11 may be repeatedly performed in order to obtain a plurality of common interface code packages between the different interface units.

Step S13: and forming the plurality of common interface code packages into the common interface code package set.

For ease of description, the plurality of common interface code packages are referred to as a common interface code package set. It will be appreciated that each common interface code package has a common interface code package identifier to illustrate the distinction.

One of the purposes of the step S201 of constructing the common interface code package set is to facilitate the step S202 of determining the personality interface code package of the interface unit.

Step S201 is followed by step S202, and in step S202, execution is performed for each of at least one interface unit among the plurality of interface units: and determining a personalized interface code package corresponding to the interface unit.

Because the independent interface code packages corresponding to one or more interface units have some common parts, the common parts always need to be repeatedly constructed and updated when the interface code packages are independently constructed and updated, and the whole process is not flexible. Therefore, in order to facilitate the maintenance process, the disclosure proposes to determine the personalized interface code package corresponding to the interface unit, where the personalized interface code package does not include the common interface code package.

The execution of one or more interface units is similar, and this step will be described in detail by taking one interface unit as an example. According to one embodiment provided by the present disclosure, step S202 may be implemented by:

step S21: and determining an independent interface code package corresponding to an interface unit.

The backend server may individually construct an independent interface code package of the interface unit independent of the overall interface code package. The independent interface code package can achieve the purpose of being independent of the whole interface code package.

The independent interface code package corresponding to one interface unit and the independent interface code package corresponding to other interface units have some common parts, namely a common interface code package. In order to further improve the maintenance efficiency of the front-end application, the present embodiment does not directly use the independent interface code package of the interface unit.

Step S22: and comparing the independent interface code package with the common interface code package set, and determining one or more common interface code packages with intersections of the independent interface code package and the common interface code package set.

Comparing the independent interface code package of the interface unit with the common interface code package set determined in step S201, and determining an intersection of the independent interface code package and the common interface code package set, that is, one or more common interface code packages having an intersection.

Step S23: and deleting the one or more common interface code packages from the independent interface code packages to obtain the rest interface code packages.

And deleting one or more common interface code packages with intersections from the independent interface code packages of the interface units to obtain the rest interface code packages. That is, excluding the commonality part from the independent interface code package only preserves the personality part.

Step S24: and taking the residual interface code package as a personalized interface code package corresponding to the interface unit.

Since the common interface code package is deleted, only the individual interface code package of the interface unit is in the remaining interface code packages. It will be appreciated that the data volume of the individual interface code packages of the interface unit is smaller than the data volume of the individual interface code packages.

Step S202 proceeds to step S203, and in step S203, the common interface function module is constructed based on the common interface code package set.

According to one embodiment provided in the present disclosure, the step S203 may be implemented by the following steps:

step S31: and respectively recording one or more common interface code package identifiers deleted by the at least one interface unit.

For the need to separately maintain at least one interface unit, since one or more common interface code packages in the independent interface code packages are deleted, the backend server may record the one or more common interface code package identifications deleted by the at least one interface unit for facilitating subsequent retrieval to completion.

Step S32: and setting an initial display interface and a callback function corresponding to the at least one interface unit respectively.

For at least one interface unit which needs to be maintained independently, the personalized interface code package is separated from the whole interface code package, so that the independent maintenance of the interface unit can be realized, and the loading efficiency of the front-end application can be improved.

That is, the personalized interface function module of at least one interface is not required to be loaded when the front-end application is initially loaded, so that the data volume of the front-end application during initial loading can be reduced, and the initial loading efficiency of the front-end application is improved. Reference may be made to the corresponding embodiment of fig. 3, which is not described in detail herein.

In order not to influence the user experience (interface unit incapable of displaying blank window), the initial display interface of at least one interface unit needs to be added so that a static initial display interface can be displayed when the front-end application is initially loaded.

For at least one interface unit, the backend server also needs to construct respective callback functions so as to drive the individual interface function modules of the interface unit by using the callback functions.

Step S33: a first loader for loading the personality interface function module is constructed.

Because the individual interface function module corresponding to the interface unit needs to be loaded, the back-end server needs to construct a first loader for loading the individual interface function module.

Step S34: and based on the common interface code package set, one or more common interface code package identifications deleted by the at least one interface unit, an initial display interface and a callback function, and the first loader, constructing a common interface function module of the front-end application.

Step S203 is followed by step S204, and in step S204, for each interface unit of the at least one interface unit, execution is performed: and constructing a personalized interface function module corresponding to the interface unit based on the personalized interface code package.

The execution of one or more interface units is similar, and this step will be described in detail by taking one interface unit as an example. According to one embodiment provided in the present disclosure, the step S204 may be implemented by the following steps:

step S41: recording the deleting information of one interface unit; wherein the deletion information includes a deletion location of one or more common interface code packages deleted by the interface unit, and the one or more common interface code package identifications.

Because one or more common function codes are deleted from the interface unit, the subsequent interface unit needs to be inserted when running, so that the back-end server records the deletion information of the interface unit, namely the deletion position of one or more common interface code packages deleted by the interface unit, and the one or more common interface code package identifiers.

Step S42: a second loader for loading the personality interface code package is constructed.

The backend server also needs to build a second loader that loads the personality interface code packages so that the interface unit loads the personality interface code packages.

Step S43: and constructing a personalized interface function module of the interface unit based on the personalized interface code package of the interface unit, the deleting information and the second loader.

Step S204 is followed by step S205 in which the common interface function module and the personality interface function module of at least one interface unit are stored.

The back-end server stores the common interface function blocks and the personality interface function modules of at least one interface unit.

the method and the device can determine the common interface function modules corresponding to the plurality of interface units in the front-end application, and determine the individual interface function modules of at least one interface unit, and the rear-end server stores the common interface function modules and the individual interface function modules of at least one interface unit.

Because the individual interface function module of at least one interface unit is separated from the whole interface code package and is not coupled, the individual interface function module of a certain interface unit can be conveniently updated or adjusted independently, and the whole interface code package is not required to be maintained.

And because the interface unit only comprises the personality part and deletes the commonality part corresponding to the personality interface function module, the personality interface function module can be further reduced, and the maintenance efficiency can be further improved when the interface unit is independently updated or independently adjusted.

In addition, because the individual interface functions of at least one interface unit are mutually independent, at least the interface units can be mutually independent for development, the independent operation of the development process is facilitated, the independent online process is realized, the mutual restriction is avoided, and the development efficiency can be improved.

In addition, as the individual interface functions are mutually independent, different interface units can use different third software libraries, the interface units do not need to be mutually influenced, and the limitation in the development process is reduced.

Since the storage of the backend server changes, the front-end application loading process also changes. On the basis of the embodiment shown in fig. 1 and fig. 2, the present disclosure further provides a front-end application loading method, which is applied to a front-end application having a communication connection with a back-end server, where a presentation interface of the front-end application includes a plurality of interface units that interact with a user execution interface.

Fig. 3 is a flowchart of a first embodiment of a front-end application loading method according to an exemplary embodiment, where the front-end application loading method is applied to a front-end application in an electronic device, as shown in fig. 3, and includes the following steps.

In step S301, an initial loading request is sent to a backend server; the back-end server stores the common interface function modules corresponding to the plurality of interface units, and at least one individual interface function module corresponding to at least one interface unit in the plurality of interface units.

The front-end application in the electronic device may send an initial load request to the back-end server.

Wherein, the commonality interface function module includes: a common interface code packet set formed by a plurality of common function code blocks in the plurality of interface units; one or more common interface code package identifications, initial presentation interfaces and callback functions deleted by at least one interface unit; and a first loader for loading the personality interface function module.

The individual interface function module of the interface unit comprises an individual interface code package of the interface unit, deleting information and a second loader; wherein the deletion information includes a deletion location of one or more common interface code packages deleted by the interface unit, and the one or more common interface code package identifications.

In step S302, an initial loading packet sent by the backend server is obtained; wherein the initial loading package comprises the common interface function module.

According to different practical application scenes, two situations can exist:

first case: under the condition that each interface unit in the front-end application needs to be maintained independently, the initial loading package only comprises a common interface function module and does not comprise a personalized interface code package of the interface unit.

Second case: in the case that the interface units in the middle of the front-end application need to be maintained separately, and the other interface units do not need to be maintained separately, the initial loading package comprises a common interface function module and a coupling interface code package of the other interface units.

In step S303, the initial loading packet is executed, so as to complete the initial loading operation of the front-end application.

And the front-end application runs the initial loading package to finish the initial loading operation of the front-end application.

In the first case, the front-end application runs a common interface code package set in the common interface function module of the initial loading package to obtain an initial interface frame; and displaying an initial display interface of at least one interface unit in an interface window corresponding to the at least one interface unit in the initial interface frame.

In the second case, the front-end application runs a common interface code package set in the common interface function module of the initial loading package to obtain an initial interface frame; displaying an initial display interface of at least one interface unit in an interface window corresponding to the at least one interface unit in the initial interface frame; and executing the coupling interface code package, and displaying the content of the interface unit in the interface windows corresponding to the rest of the interface units in the initial interface frame.

In step S304, under the condition that a triggering operation of an interface unit in the at least one interface unit is received, a personality interface function module of the interface unit is obtained and loaded from the backend server.

That is, under the initial loading condition, the individual interface function modules of part or all of the interface units are not loaded temporarily, but under the condition that the interface units are triggered, the individual interface function modules of the interface units are loaded again, so that the purposes of batch loading and initial loading efficiency improvement are realized.

because the back-end server no longer stores the whole interface code package, but stores the common interface function module and the individual interface function module of at least one interface unit, the back-end server can send the whole interface code package in batches instead of sending the whole interface code package, and can send an initial loading package when in initial loading, wherein the initial loading package at least comprises the common interface function module and does not comprise the individual interface function module of at least one interface unit.

Compared with the whole interface code package, the data volume of the individual interface function module of at least one interface unit can be reduced when the whole interface code package is loaded for the first time, so that the front end application efficiency can be improved.

Fig. 4 is a flowchart of a second embodiment of a front-end application loading method according to an exemplary embodiment, where the front-end application loading method is applied to a front-end application in an electronic device as shown in fig. 4.

In this embodiment, the details of the individual interface function module of the interface unit obtained and loaded from the backend server in step S304 in fig. 3 are mainly described, and the rest of the contents may be added to the embodiment shown in fig. 3.

In step S401, if a triggering operation of an interface unit in the at least one interface unit is received, a personality interface function module corresponding to the interface unit is obtained from the backend server.

During the front-end application running process, if the user clicks on one interface unit in at least one interface unit (only the initial display interface does not have interface unit content), the interface unit is triggered. The front-end application sends an acquisition request to the back-end server so as to acquire the personalized interface function module corresponding to the interface unit from the back-end server.

In step S402, determining, from the common interface function module, one or more common interface code package identifiers deleted by the interface unit;

since the personality interface function module previously deletes one or more commonality interface code packages, the front-end application needs to determine, from the commonality interface function module, the identity of the one or more commonality interface code packages deleted before the interface unit.

In step S403, the first loader is invoked, and one or more common interface code packages corresponding to the one or more common interface code package identifiers are injected from the common interface function module into the personality interface function module.

The front-end application calls a first loader, calls one or more common interface code packages corresponding to the one or more common interface code package identifiers from the common interface function module, and then injects the one or more common interface code packages into the individual interface function module of the interface unit so as to complement the integrity of the interface unit.

In step S404, a callback function corresponding to the interface unit is called, and the personality interface function module is driven.

The individual interface function modules may operate independently, so in order to trigger the individual interface function modules of the interface units, callback functions of the interface units may be called, and it may be understood that callback functions of different interface units are different.

The personality interface function module and the commonality interface function module are operated separately, the personality interface function module can use a third party library of the personality interface function module, and the third party library can be different from the third party library of the commonality interface function, so that the drag between the personality interface function module and the commonality interface function module can be reduced, and the code flexibility is improved.

In addition, the advantage that the individual interface function modules can be independently operated is facilitated, and the interface unit can use the common interface code package in the common interface function module or independently construct the common interface code package of the updated version.

The following describes the execution process of the personality interface function module:

step S1: and calling the second loader to load the common interface code package aiming at the injected one or more common interface code packages, and executing the following judging operations in the loading process:

if the deleting positions corresponding to the common interface code packages in the individual interface code packages have the same function code packages, the common interface code packages are not injected; if the same function code package exists in the personality interface code package, the priority of the personality interface code package is higher than that of the commonality interface code package, and the existing same function code package is preferentially used.

If the deleting position corresponding to the common interface code packet in the individual interface code packet does not have the same function code packet, adding the common interface code packet in the deleting position; thus, the common interface code package missing in the personalized interface code package can be complemented.

Step S2: and obtaining the updated personalized interface code package.

After the repeated execution of step S1, the personality interface code package may be perfected.

Step S3: and executing the updated personalized interface code package, and displaying the interface unit content.

And the personalized interface code package is directly operated, the content of the interface unit is displayed in a window of the interface unit, and the loading of the personalized interface code package is completed.

the present disclosure provides a loading process of a personalized interface function module, in which the personalized interface function module can determine whether to use a common interface code package according to whether the deleting position has the same function code package, so that the personalized interface function module has selectivity, and selects whether to use the original common interface code package or use the same function code package updated by itself. This may allow for more flexibility in the personality interface function module.

Referring to fig. 5, a specific embodiment is provided for the present disclosure.

The present disclosure allows for a single host application (i.e., the common interface function module above) to be run in a single page application that runs independently, where the independent module (i.e., the personality interface function module above) can be dynamically loaded from the backend server to run as a sub-application during the running of the host application.

The main application and the sub-application in the single-page application can be mutually isolated and are not interfered with each other, the purposes of isolation and independent loading can be achieved, the back-end server can independently maintain a certain sub-application, the whole single-page application is not required to be maintained, and the method is simple and convenient.

The main application has some shared modules (i.e. the common interface code packages in the common interface function modules mentioned above), and the sub-application has some self-dependent modules (not described in detail in this disclosure).

(1) The sub-applications may be configured as DLL modules (Dynamic Link Library, DLLs, dynamic link library files also known as "application extensions").

The backend server may weback package the DLL modules of the sub-applications, providing an accessible root object for callback functions to call. And the back-end server can exclude code inline compiling from the common function code package shared by the main application by the sub-application, so that inline compiling is not needed, and the purposes of isolation and independence between the sub-application and the main application are realized.

The sub-application provides a callback function as an entry for the main application to render the reaction interface.

(2) The sub-application loader (i.e., the first loader above) is implemented in the main application so that the entry modules of the sub-application can be loaded from the specified resource locations, and the sharing modules required by the sub-application are injected into the sub-application so that the sub-application can be completed into the overall sub-application.

(3) The host application obtains the weback loader of the sub-application (i.e., the first loader above) and injects into the sub-application the modules that need to be shared from the host application.

(4) The main application uses the callback function provided by the sub application to call the root object so as to start the sub application, and draws the real interface and execution logic of the sub application in the main application.

Fig. 6 is a block diagram illustrating a front-end application maintenance device according to an example embodiment. The front-end application maintenance device is applied to a back-end server which is in communication connection with the front-end application, and a display interface of the front-end application comprises a plurality of interface units which interact with a user execution interface;

Referring to fig. 6, the apparatus includes a receiving unit 61, a determining unit 62, and an executing unit 63.

A receiving unit 61 configured to perform receiving a maintenance instruction of an interface unit in the front-end application; wherein the maintenance instruction at least comprises an interface unit identifier and a maintenance operation of the interface unit;

a determining unit 62 configured to perform determining a personalized interface function module corresponding to the interface unit identifier;

and an execution unit 63 configured to execute the maintenance operation on the personality interface function module.

or,

Wherein, before the receiving unit 61, further comprises:

The specific manner in which the plurality of modules perform the operations in the apparatus of the above embodiments has been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

FIG. 7 is a block diagram illustrating a front-end application loading apparatus for a front-end application having a communication connection with a back-end server, a presentation interface of the front-end application including a plurality of interface elements for interacting with a user execution interface, according to an example embodiment.

the front-end application maintenance device includes:

a transmitting unit 71 configured to transmit an initial loading request to the backend server;

an obtaining unit 72 configured to obtain an initial loading packet sent by the backend server; wherein the initial loading package comprises the commonality interface function module;

an operation unit 73 configured to execute the initial loading packet to complete an initial loading operation of the front-end application;

and a loading unit 74 configured to acquire and load the individual interface function module of one interface unit from the back-end server when receiving the trigger operation of the interface unit.

Wherein, the commonality interface function module includes:

Wherein the loading unit is specifically configured to:

Wherein the drive unit is specifically configured to:

obtaining an updated personalized interface code package;

Wherein the operation unit is specifically configured to:

Fig. 8 is a block diagram of a server, according to an example embodiment. Referring to fig. 8, server 800 includes a processing component 822 that further includes one or more processors and memory resources, represented by memory 832, for storing instructions, such as application programs, executable by processing component 822. The application programs stored in memory 832 may include one or more modules each corresponding to a set of instructions. Further, the processing component 822 is configured to execute instructions to perform the front end application maintenance method described above.

The server 800 may also include a power component 826 configured to perform power management of the server 800, a wired or wireless network interface 850 configured to connect the server 800 to a network, and an input output (I/O) interface 858. The server 800 may operate based on an operating system stored in memory 832, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, or the like.

FIG. 9 is a block diagram illustrating a loading apparatus for a front-end application according to an example embodiment. For example, apparatus 900 may be a mobile phone, computer, digital broadcast electronic terminal, messaging device, game console, tablet device, medical device, exercise device, personal digital assistant, or the like.

Referring to fig. 9, apparatus 900 may include one or more of the following components: a processing component 902, a memory 904, a power component 906, a multimedia component 908, an audio component 910, an input/output (I/O) interface 912, a sensor component 914, and a communication component 916.

The processing component 902 generally controls overall operations of the apparatus 900, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 902 may include one or more processors 920 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 902 can include one or more modules that facilitate interaction between the processing component 902 and other components. For example, the processing component 902 can include a multimedia module to facilitate interaction between the multimedia component 908 and the processing component 902.

The memory 904 is configured to store various types of data to support operations at the device 900. Examples of such data include instructions for any application or method operating on the device 900, contact data, phonebook data, messages, pictures, videos, and the like. The memory 904 may be implemented by any type of volatile or nonvolatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

The power supply component 906 provides power to the various components of the device 900. Power supply components 906 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for device 900.

The multimedia component 908 comprises a screen between the device 900 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 908 includes a front-facing camera and/or a rear-facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 900 is in an operational mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 910 is configured to output and/or input audio signals. For example, the audio component 910 includes a Microphone (MIC) configured to receive external audio signals when the device 900 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 904 or transmitted via the communication component 916. In some embodiments, the audio component 910 further includes a speaker for outputting audio signals.

The I/O interface 912 provides an interface between the processing component 902 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.

The sensor assembly 914 includes one or more sensors for providing status assessment of various aspects of the apparatus 900. For example, the sensor assembly 914 may detect the on/off state of the device 900, the relative positioning of the components, such as the display and keypad of the apparatus 900, the sensor assembly 914 may also detect the change in position of the apparatus 900 or one component of the apparatus 900, the presence or absence of user contact with the apparatus 900, the orientation or acceleration/deceleration of the apparatus 900, and the change in temperature of the apparatus 900. The sensor assembly 914 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 914 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 914 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 916 is configured to facilitate communication between the apparatus 900 and other devices in a wired or wireless manner. The apparatus 900 may access a wireless network based on a communication standard, such as WiFi, an operator network (e.g., 2G, 3G, 4G, or 5G), or a combination thereof. In one exemplary embodiment, the communication component 916 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 916 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, apparatus 900 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.

In an exemplary embodiment, a computer-readable storage medium is also provided, such as memory 932, including instructions executable by processor 922 of apparatus 900 to perform the above-described method. Alternatively, the computer-readable storage medium may be 904, the instructions being executable by the processor 920 of the apparatus 900 to perform the above-described methods. Alternatively, the computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. The front-end application maintenance method is characterized by being applied to a back-end server with communication connection with a front-end application, wherein a display interface of the front-end application comprises a plurality of interface units for interacting with a user execution interface;

The front-end application maintenance method comprises the following steps:

executing the maintenance operation on the personality interface function module;

before receiving the maintenance instruction of an interface unit in the front-end application, the method further comprises:

2. The front-end application maintenance method of claim 1, wherein,

the maintenance operation is a delete operation, and the performing the maintenance operation on the personality interface function module includes: deleting the personalized interface function module corresponding to the interface unit identifier;

Or,

3. The front-end application maintenance method of claim 1, wherein the determining the set of common interface code packages for the plurality of interface units comprises:

4. The front-end application maintenance method of claim 3, wherein determining a personality interface code package corresponding to an interface unit comprises:

5. The front-end application maintenance method of claim 4, wherein the constructing the common interface function module based on the set of common interface code packages comprises:

6. The front-end application maintenance method of claim 5, wherein the constructing a personality interface function module corresponding to the interface unit based on the personality interface code package includes:

7. The front-end application loading method is characterized by being applied to a front-end application with communication connection with a back-end server, wherein a display interface of the front-end application comprises a plurality of interface units for interacting with a user execution interface;

The front-end application loading method comprises the following steps:

sending an initial loading request to the back-end server;

under the condition that the triggering operation of one interface unit in the at least one interface unit is received, acquiring and loading a personalized interface function module of the interface unit from the back-end server;

the common interface function module construction process comprises the following steps: determining a common interface code package set corresponding to the plurality of interface units, and constructing the common interface function module based on the common interface code package set; storing the commonality interface function module;

the construction process of the personality interface function module comprises the following steps: executing, for each interface unit of at least one interface unit of the plurality of interface units: determining a personalized interface code package corresponding to an interface unit, and constructing a personalized interface function module corresponding to the interface unit based on the personalized interface code package; at least one individual interface function module corresponding to the at least one interface unit is stored.

8. The front-end application loading method of claim 7, wherein the commonality interface function module comprises:

9. The front-end application loading method according to claim 8, wherein the acquiring and loading the individual interface function module of an interface unit from the back-end server when the trigger operation of the interface unit is received comprises:

10. The front-end application loading method of claim 9, wherein the personality interface function module of the interface unit includes a personality interface code package, delete information, and a second loader of the interface unit;

11. The front-end application loading method of claim 10, wherein the calling the callback function corresponding to the interface unit, driving the personality interface function module comprises:

Obtaining an updated personalized interface code package;

12. The front-end application loading method as recited in claim 8, wherein the running the initial loading package, completing the initial loading operation of the front-end application comprises:

13. The front-end application loading method of claim 8, wherein the initial load package further comprises: the coupling interface code package of other interface units except the at least one interface unit in the front-end application;

14. The front-end application maintenance device is characterized by being applied to a back-end server with communication connection with a front-end application, wherein a display interface of the front-end application comprises a plurality of interface units for interacting with a user execution interface;

the front-end application maintenance device includes:

an execution unit configured to execute the maintenance operation on the personality interface function module;

before the receiving unit, further comprising:

15. The front-end application maintenance device of claim 14,

or,

16. The front-end application maintenance device of claim 14, wherein the determining a common interface code packet set corresponding to the plurality of interface units in the determining common module unit is specifically configured to:

17. The front-end application maintenance device of claim 16, wherein the determining a personality interface code package corresponding to one interface unit in the determining personality module unit is specifically configured to:

18. The front-end application maintenance device of claim 17, wherein the determining commonality module unit constructs the commonality interface function module based on the commonality interface code package set, and is specifically configured to:

19. The front-end application maintenance device of claim 18, wherein the determining personality module unit constructs a personality interface function module corresponding to the interface unit based on the personality interface code package, and is specifically configured to:

20. A front-end application loading device, which is characterized by being applied to a front-end application with communication connection with a back-end server, wherein a display interface of the front-end application comprises a plurality of interface units for interacting with a user execution interface;

the front-end application loading device comprises:

the loading unit is configured to acquire and load a personalized interface function module of one interface unit from the back-end server under the condition that the triggering operation of the interface unit is received;

21. The front-end application loading device of claim 20, wherein the commonality interface function module comprises:

22. The front-end application loading device of claim 21, wherein the loading unit is specifically configured to:

23. The front-end application loading apparatus of claim 22, wherein the personality interface function module of the interface unit includes a personality interface code package, delete information, and a second loader of the interface unit;

24. The front-end application loading device of claim 23, wherein the drive unit is specifically configured to:

Obtaining an updated personalized interface code package;

25. The front-end application loading device of claim 21, wherein the execution unit is specifically configured to:

26. The front-end application loading apparatus of claim 21, wherein the initial load package further comprises: the coupling interface code package of other interface units except the at least one interface unit in the front-end application;

27. A server, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the front-end application maintenance method of any one of claims 1 to 6.

28. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the front-end application loading method of any of claims 7-13.

29. A computer readable storage medium, which when executed by a processor of a server, causes the processor to perform the front-end application maintenance method of any of claims 1 to 6.

30. A computer readable storage medium, which when executed by a processor of an electronic device, causes the processor to perform the front-end application loading method of any of claims 7-13.