TW201913361A - Page update method and apparatus - Google Patents

Abstract

The embodiments of the present description provides a page update method and apparatus. The method comprises: a dynamic packaging system acquiring a new page file of a Hybrid App page, packaging the new page file into an offline packet, and sending the offline packet to an offline packet management system, so as to trigger the update of the Hybrid App page by means of the offline packet management system.

Description

Page update method and device

The disclosure relates to the field of computer technology, and in particular to a page update method and apparatus.

Hybrid App (hybrid mode mobile app) refers to the app between web-app and native-app. It has the advantages of "Native App good user interaction experience" and "Web App cross-platform development advantage". Developing a Hybrid App page can include front-end code and back-end code for the page, where the front-end code can be packaged as an offline package and managed by an offline package management system. When the page needs to be updated, the developer can update the offline package in the offline package system; when requesting access to the Hybrid App page, the offline package update of the offline package system can trigger the update of the page.

In view of this, one or more embodiments of the present specification provide a page update method and apparatus to improve the efficiency of page update of a Hybrid App. Specifically, one or more embodiments of the present disclosure are implemented by the following technical solutions: In a first aspect, a page update method is provided, where the method includes: acquiring a new page file of a hybrid mode mobile application Hybrid App page; The new page file is packaged into an offline package; the offline package is sent to an offline package management system to trigger a page update of the Hybrid App by the offline package management system. In a second aspect, a dynamic packaging system is provided, the system comprising: a template engine, configured to acquire a new page file of a hybrid mode mobile application Hybrid App page; and a packaging trigger, configured to package the new page file into an offline package, The offline package is sent to the offline package management system to trigger the page update of the Hybrid App by the offline package management system. In a third aspect, a server device is provided, the device comprising a memory, a processor, and computer instructions stored on the memory and operable on the processor, the processor performing the following steps when executing the instruction: The new page file of the hybrid mode mobile application Hybrid App page; the new page file is packaged into an offline package; the offline package is sent to the offline package management system to trigger the page update of the Hybrid App by the offline package management system. The page updating method and apparatus of one or more embodiments of the present specification can automatically update the offline package in the offline package management system by being packaged into an offline package according to the new page file by the dynamic packaging system and sent to the offline package management system. . The solution can automatically trigger the offline package update when the page file is changed, which reduces the burden on the developer and improves the update efficiency of the Hybrid App offline package.

In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present specification, in the following one or more embodiments of the present specification, in one or more embodiments of the present specification, The technical solutions are described clearly and completely, and it is obvious that the described embodiments are only a part of the embodiments, rather than all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on one or more embodiments of the present specification without departing from the scope of the present invention are intended to be within the scope of the disclosure. Figure 1 illustrates the system architecture of the Hybrid App. Hybrid App is a hybrid application that uses the native and web app capabilities to build an in-app web app on native. As shown in FIG. 1, the client 11 may be a foreground displayed by the Hybrid App page, for example, the web app may be displayed in a native app. The display of the Hybrid App includes a cooperation of the front-end code and the back-end code, and the front-end code can be stored in the offline package management system 12. For example, the front-end code can include a style code that determines a page style, and the style code can be used to determine the page. The layout of each part of the content, or the font and color of the page content, or the shape of a certain area of the page. When the page of the Hybrid App is requested to be displayed, the style of the page can be obtained according to the offline package, and the information of the page is updated by the backend code of the server 13 by the asynchronous request data method such as ajax, thereby realizing the entire Hybrid App. Page display. The method of this example mainly describes the page update caused by the front-end code. With continued reference to FIG. 1, offline packages of the plurality of applications can be managed in the offline package management system 12, for example, web app1, web app2, web app3, and the like. When the page of the Hybrid App page needs to be updated, the offline package of the app in the offline package management system 12 can be updated to trigger the update of the page by the update of the offline package. Figure 2 illustrates a flow of a page update method that can be used to automatically trigger the update of the front-end code in the offline package, as shown in Figure 2, which can be performed by the dynamic packaging system of Figure 1, and can include: In 200, a new page file of the hybrid mode mobile application Hybrid App page is obtained. In this step, the template engine 152 can acquire the new page file 153. For example, the new page file may be a file generated by the template engine 152 according to the page style update, or may be a file generated according to other content updates in the page. In step 202, the new page file is packaged into an offline package. In this step, the packaging trigger 151 can receive the new page file sent by the template engine 152 and automatically package the new page file into the format of the offline package. In step 204, the offline package is sent to the offline package management system to trigger a page update of the Hybrid App by the offline package management system. In this step, after the offline package is packaged, the package trigger 151 may also send the offline package to the offline package management system 12. For example, an offline package of the new front end code of web app 1 can be sent to the offline package management system 12 and the old front end code of the original web app 1 can be replaced. The update of the offline package in the offline package management system can trigger the page update. For example, when the client wants to display the web app1 and request the front-end code from the offline package management system, if the code has been updated, the new front-end code can be displayed. The page update method of the example is automatically sent to the offline package management system by acquiring a new page file by the dynamic packaging system, and packaging the new page file into an offline package, so that the automatic update of the offline package in the offline package management system can be realized. The solution can automatically trigger the offline package update when the page is changed, which reduces the burden on the developer and improves the update efficiency of the Hybrid App offline package. The following is an example of updating the page style in the page to describe how to trigger the offline package update when the page style is updated. The way the page style is updated may be the code that the developer issues the change, or the style configuration by the operator in the template block operation system. As shown in FIG. 1, the template block operation system 14 can be a human-machine interaction system for the operator to modify the page style, and can be provided to the operator's human-machine dialog mode modification page to modify the block or template. The block can be a rectangular area in the page, marked with the html syntax <div></div>, and the template can be a module written in a template language such as Velocity. In order to enable the operator to change the configuration of the block and template of a Hybrid App by the template block operation system, the offline package update of the Hybrid App in the offline package management system 12 can also be automatically triggered to automatically trigger the page. The style change, this example can set up the dynamic packaging system 15, as shown in Figure 1. The dynamic packaging system 15 can automatically update the corresponding offline package in the offline package management system 12 when the operator changes the configuration of the block and the template, thereby implementing dynamic update of the Hybrid App page style. FIG. 3 illustrates a flow of updating a page style according to the dynamic packaging system of FIG. 1, including: In step 300, a front-end developer performs a code release change, or an operator performs a configuration change of a block template. For example, as shown in FIG. 1 , the developer can change the code corresponding to the page style update. For example, to change the layout of the page, or change the display style of a certain part of the page, the corresponding code can be changed, and this part of the code can be called a development change. Code. In another example, the operator may also configure the block or template in the change page by the template block operation system to change the style of the page, such as changing the shape or position of the banner in the page. The corresponding generated code can be called the operational template code. In step 302, the dynamic packaging system obtains a new page file corresponding to the Hybrid App page and an event linkage trigger, and the trigger may be used to notify that an update event corresponding to the page style update has occurred. The developer in step 300 performs the release of the change code, or the operator performs the configuration change of the block template, and pushes the block template of the configuration change to the dynamic packaging system, and the operation of changing the Hybrid App page style can be performed. Called an update event. After the update event occurs, the template engine can generate a new page file. For example, the template engine can generate a new page file according to the page style change corresponding development change code, or can generate a new page according to the block template configuration change corresponding operation template code. The file (ie, the new front-end code), or the template engine can also obtain the corresponding operational template code according to the update event of the block template configuration change, and generate a new page file accordingly. The dynamic packaging system 15 in FIG. 1 can not only receive the above new page file, but also receive an event linkage trigger. The event linkage trigger may be sent when an update event occurs to notify that an update event corresponding to the page style update has occurred. As shown in the example of FIG. 1, when the operator modifies the block or the template, the template block operation system can simultaneously send an event linkage trigger to the packaging trigger of the dynamic packaging system to notify that the configuration change of the template block has occurred; or When the developer changes the style code of the page, the module that changes the code can also send an event linkage trigger to the package trigger of the dynamic packaging system to notify that the code change has occurred. In an example of FIG. 1, the event linkage trigger may be a packing trigger 151 sent to the dynamic packaging system 15, and the packaging trigger 151 will perform the packaging processing of the offline package according to the event linkage trigger. In this step, the template engine 152 can generate a new page file according to the development change code or the operation template code. For example, the template engine 152 may generate a page file of the new Hybrid App page according to the development change code or the operation template code obtained in step 302. As shown in FIG. 1, the template engine 152 obtains a new front-end code 153 based on the development change code or the operational template code. In step 304, the packaging trigger of the dynamic packaging system triggers the new page file into an offline package according to the received event linkage trigger. For example, the package trigger 151 may trigger according to the event linkage, and after waiting for the template engine to complete the update of the front-end code, that is, after generating a new page file, the new page file is packaged as an offline package. In step 306, the packaging trigger of the dynamic packaging system sends the offline package to the offline package management system. For example, referring to FIG. 1, assuming that the updated Hybrid App is web app1, the packaging trigger sends the packaged offline package to web app1 in the offline package management system 12. It is also possible to update the version of the offline package of web app1, the original old offline package version is assumed to be V1, and the updated new offline package version may be V2. In step 308, the update of the Hybrid App page style is triggered by the offline package management system. For example, as in the example of FIG. 1, when a page access request to the Hybrid App is received, the page style can be obtained by the offline package of web app1 in the offline package management system 12, if the offline package has an update, for example, by version V1 Update to version V2, the page style is updated by the offline package, and the page data is obtained by the backend code of the web app1 by means of asynchronously requesting the data, thereby realizing the page display of the entire Hybrid App. The page style update method of the present example can be automatically updated by offline package management system by the new package file generated by the dynamic packaging system according to the page style change, packaged into an offline package and sent to the offline package management system. The solution can enable the operator to automatically update the offline package even if the operator configures the block or template, and realizes the dynamic configuration style of the operation, which also reduces the burden on the developer and improves the update efficiency of the offline package of the Hybrid App. In order to implement the page update method of one or more embodiments of the present specification, FIG. 4 provides a dynamic packaging system, which may include: a template engine 41 and a packaging trigger 42. a template engine 41, configured to acquire a new page file of the hybrid mode mobile application Hybrid App page; a packaging trigger 42 configured to package the new page file into an offline package, and send the offline package to the offline package management system to borrow The update of the Hybrid App page style is triggered by the offline package management system. In one example, the new page file is a file generated by the template engine based on page style updates. For example, the page style update includes: a development code change corresponding to the page style, or a configuration change of the template block. In an example, the packaging trigger 42 is configured to package the new page file into an offline package according to the received event linkage trigger, and package the new page file into an offline package. The update event corresponding to the page style update occurs. In one example, the packaging trigger 42 is further configured to update the version of the offline package when the new page file is packaged into an offline package. The order of execution of the steps in the above-described processes shown in FIG. 2 and FIG. 3 is not limited to the order in the flowchart. In addition, the description of each step may be implemented in the form of software, hardware, or a combination thereof. For example, a person skilled in the art may implement it in the form of a software code, and may be a computer capable of implementing the logic function corresponding to the step. Execute the instruction. When implemented in a software manner, the executable instructions can be stored in memory and executed by a processor in the device. For example, corresponding to the above method, one or more embodiments of the present specification simultaneously provide a server device, which may include a processor, a memory, and a computer command stored on the memory and operable on the processor. By executing the instruction, the processor is configured to: obtain a new page file of the hybrid mode mobile application Hybrid App page; package the new page file into an offline package; and send the offline package to the offline package management The system triggers the update of the Hybrid App page style by the offline package management system. The device or module illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function. A typical implementation device is a computer. The specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, and a game. A console, tablet, wearable device, or a combination of any of these devices. For the convenience of description, the above devices are described as being separately divided into various modules by function. Of course, the functions of the various modules may be implemented in the same or multiple software and/or hardware when implementing one or more embodiments of the present specification. Those skilled in the art will appreciate that one or more embodiments of the present specification can be provided as a method, system, or computer program product. Thus, one or more embodiments of the present specification can take the form of a complete hardware embodiment, a fully software embodiment, or an embodiment incorporating a software and a hardware aspect. Moreover, one or more embodiments of the present specification can be implemented on one or more computer usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer usable code therein. The form of a computer program product. The computer program instructions can also be stored in a computer readable memory that can boot a computer or other programmable data processing device to operate in a particular manner, such that instructions stored in the computer readable memory produce an article of manufacture including the instruction device. The instruction means implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart. These computer program instructions can also be loaded onto a computer or other programmable data processing device to perform a series of operational steps on a computer or other programmable device to produce computer-implemented processing on a computer or other programmable device. The instructions executed on the steps provide steps for implementing the functions specified in one or more flows of the flowchart or in a block or blocks of the flowchart. It is also to be understood that the terms "comprises" or "comprising" or "comprising" or any other variations are intended to encompass a non-exclusive inclusion, such that a process, method, article, Other elements not explicitly listed, or elements that are inherent to such a process, method, commodity, or equipment. An element defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device including the element. One or more embodiments of the present specification can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, a program module includes routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. One or more embodiments of the present specification can also be practiced in a distributed computing environment in which tasks are performed by remote processing devices that are connected by a communication network. In a decentralized computing environment, the program modules can be located in local and remote computer storage media, including storage devices. The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the server device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment. The foregoing description of the specific embodiments of the specification has been described. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the scope of the claims may be performed in a different order than the embodiments and still achieve the desired results. In addition, the processes depicted in the figures do not necessarily require a particular order or a sequential order of presentation to achieve a desired result. In some embodiments, multiplex processing and parallel processing are also possible or may be advantageous. The above description is only a preferred embodiment of one or more embodiments of the present specification, and is not intended to limit the disclosure, and any modifications, equivalents, improvements, etc. are made within the spirit and principles of the disclosure. All should be included in the scope of this disclosure.

11‧‧‧User

12‧‧‧Offline Package Management System

13‧‧‧Server

14‧‧‧Template Block Operation System

15‧‧‧dynamic packaging system

151‧‧‧Package trigger

152‧‧‧Template engine

153‧‧‧ front-end code

200‧‧‧ steps

202‧‧‧Steps

204‧‧‧Steps

300‧‧‧Steps

302‧‧‧Steps

304‧‧‧Steps

306‧‧‧Steps

308‧‧‧Steps

41‧‧‧Template engine

42‧‧‧Package trigger

In order to more clearly illustrate one or more embodiments of the present specification or the technical solutions in the prior art, the drawings to be used in the embodiments or the description of the prior art will be briefly described below, and obviously, the attached in the following description The drawings are merely some of the embodiments described in one or more embodiments of the present specification, and those of ordinary skill in the art may also obtain other drawings in accordance with the drawings without departing from the scope of the invention. 1 is a system architecture of a Hybrid App application provided by one or more embodiments of the present disclosure; FIG. 2 is a flowchart of a page update method provided by one or more embodiments of the present specification; FIG. 3 is one or more implementations of the present specification. The flow of the dynamic packaging system is updated by the example. FIG. 4 is a schematic structural diagram of a dynamic packaging system provided by one or more embodiments of the present specification.

Claims (11)

A page update method, the method comprising: acquiring a new page file of a hybrid mode mobile application Hybrid App page; packaging the new page file into an offline package; and sending the offline package to an offline package management system to be offline The package management system triggers a page update for the Hybrid App. According to the method of claim 1, the obtaining a new page file of the hybrid mode mobile application Hybrid App page comprises: acquiring a file generated according to a page style update. According to the method of claim 2, the page style update includes: a development code change corresponding to the page style, or a configuration change of the template block. According to the method of claim 2, the packaging the new page file into an offline package comprises: packaging the new page file into an offline package according to the received event linkage trigger; The update event corresponding to the page style update occurs. The method of claim 1, further comprising: updating the version of the offline package when the new page file is packaged into an offline package. A dynamic packaging system, the system comprising: a template engine, configured to acquire a new page file of a hybrid mode mobile application Hybrid App page; a packaging trigger, configured to package the new page file into an offline package, and send the offline package To the offline package management system to trigger the page update of the Hybrid App by the offline package management system. According to the system of claim 6, the new page file is a file generated by the template engine according to a page style update. According to the system of claim 7, the page style update includes: a development code change corresponding to the page style, or a configuration change of the template block. According to the system of claim 7, the packaging trigger, when used for packaging a new page file into an offline package, includes: packaging the new page file into an offline according to the received event linkage trigger The event linkage trigger is used to notify that an update event corresponding to the page style update has occurred. According to the system of claim 7, the packaging trigger is further configured to update the version of the offline package when the new page file is packaged into an offline package. A server device, comprising: a memory, a processor, and computer instructions stored on the memory and operable on the processor, the processor implementing the following steps when: executing the hybrid mode mobile application Hybrid App a new page file of the page; packaging the new page file into an offline package; sending the offline package to an offline package management system to trigger a page update of the Hybrid App by the offline package management system.