TW201913361A - Page update method and apparatus - Google Patents
Page update method and apparatus Download PDFInfo
- Publication number
- TW201913361A TW201913361A TW107116976A TW107116976A TW201913361A TW 201913361 A TW201913361 A TW 201913361A TW 107116976 A TW107116976 A TW 107116976A TW 107116976 A TW107116976 A TW 107116976A TW 201913361 A TW201913361 A TW 201913361A
- Authority
- TW
- Taiwan
- Prior art keywords
- page
- update
- offline package
- offline
- file
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
本揭露關於電腦技術領域,特別關於一種頁面更新方法和裝置。The disclosure relates to the field of computer technology, and in particular to a page update method and apparatus.
Hybrid App(混合模式移動應用)是指介於web-app、native-app這兩者之間的app,兼具“Native App良好用戶互動體驗的優勢”和“Web App跨平臺開發的優勢”。開發一個Hybrid App頁面可以包括該頁面的前端代碼和後端代碼,其中,前端代碼可以打包成離線包形式,並藉由離線包管理系統進行管理。當頁面需要更新時,可以由開發人員更新離線包系統中的離線包;當請求存取Hybrid App頁面時,離線包系統的離線包更新可以觸發頁面的更新。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.
有鑑於此,本說明書一個或多個實施例提供一種頁面更新方法和裝置,以提高Hybrid App的頁面更新的效率。 具體地,本說明書一個或多個實施例是藉由如下技術方案實現的: 第一態樣,提供一種頁面更新方法,所述方法包括: 獲取混合模式移動應用Hybrid App頁面的新頁面文件; 將所述新頁面文件打包成離線包; 將所述離線包發送至離線包管理系統,以藉由離線包管理系統觸發Hybrid App的頁面更新。 第二態樣,提供一種動態打包系統,所述系統包括: 模版引擎,用於獲取混合模式移動應用Hybrid App頁面的新頁面文件; 打包觸發器,用於所述新頁面文件打包成離線包,並將離線包發送至離線包管理系統,以藉由離線包管理系統觸發Hybrid App的頁面更新。 第三態樣,提供一種伺服端設備,所述設備包括記憶體、處理器,以及儲存在記憶體上並可在處理器上運行的電腦指令,所述處理器執行指令時實現以下步驟: 獲取混合模式移動應用Hybrid App頁面的新頁面文件; 將所述新頁面文件打包成離線包; 將所述離線包發送至離線包管理系統,以藉由離線包管理系統觸發Hybrid App的頁面更新。 本說明書一個或多個實施例的頁面更新方法和裝置,藉由由動態打包系統根據新頁面文件打包成離線包並發送至離線包管理系統,可以實現離線包管理系統中的離線包的自動更新。該方案能夠使得當頁面文件變更時能夠自動觸發離線包的更新,減輕了開發人員的負擔,提高了Hybrid App離線包的更新效率。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.
為了使本技術領域的人員更好地理解本說明書一個或多個實施例中的技術方案,下面將結合本說明書一個或多個實施例中的附圖,對本說明書一個或多個實施例中的技術方案進行清楚、完整地描述,顯然,所描述的實施例僅僅是一部分實施例,而不是全部的實施例。基於本說明書一個或多個實施例,本領域普通技術人員在沒有作出進步性勞動前提下所獲得的所有其他實施例,都應當屬於本揭露保護的範圍。 圖1示例了Hybrid App應用的系統架構,Hybrid App是一種混合應用,運用native和web app的能力,在native上構建應用內web app的應用。如圖1所示,用戶端11可以是Hybrid App頁面展示的前臺,例如,可以是在一個native app中顯示web app。 該Hybrid App的顯示包括前端代碼和後端代碼的配合,可以將前端代碼儲存在離線包管理系統12中,例如,前端代碼中可以包括決定頁面樣式的樣式代碼,該樣式代碼可以用於確定頁面中的各部分內容的佈局安排,或者頁面內容的字體和顏色,或者頁面中某一個區域的展示形狀等。當請求顯示Hybrid App的頁面時,可以根據離線包獲取如何顯示頁面的樣式,並藉由ajax等非同步請求資料方式,由伺服端13的後端代碼更新頁面的資料,從而實現整個Hybrid App的頁面展示。本例子的方法主要描述前端代碼導致的頁面更新。 請繼續參見圖1,離線包管理系統12中可以管理多個應用的離線包,例如,web app1、web app2、web app3等。當Hybrid App頁面的頁面需要更新時,可以更新離線包管理系統12中該app的離線包,以藉由離線包的更新觸發頁面的更新。 圖2示例了一個頁面更新方法的流程,該方法可以用於自動觸發離線包中前端代碼的更新,如圖2所示,該方法可以由圖1中的動態打包系統執行,可以包括: 在步驟200中,獲取混合模式移動應用Hybrid App頁面的新頁面文件。 本步驟中,模版引擎152可以獲取到新頁面文件153。例如,該新頁面文件可以是模版引擎152根據頁面樣式更新生成的文件,或者也可以是根據頁面中其他內容更新生成的文件。 在步驟202中,將所述新頁面文件打包成離線包。 本步驟中,打包觸發器151可以接收到模版引擎152發送的新頁面文件,並將該新頁面文件自動打包成離線包的格式。 在步驟204中,將所述離線包發送至離線包管理系統,以藉由離線包管理系統觸發Hybrid App的頁面更新。 本步驟中,打包觸發器151在打包離線包後,還可以將離線包發送至離線包管理系統12。例如,可以將web app 1的新前端代碼的離線包發送至離線包管理系統12,並替換掉原來web app 1的舊前端代碼。離線包管理系統中的離線包的更新可以觸發頁面更新,例如,當用戶端要展示web app1,向離線包管理系統請求前端代碼時,若代碼已經更新,可以使用新的前端代碼展示。 本例子的頁面更新方法,藉由由動態打包系統獲取新頁面文件,並將新頁面文件打包成離線包,自動發送至離線包管理系統,使得可以實現離線包管理系統中的離線包的自動更新,該方案能夠使得當頁面變更時能夠自動觸發離線包的更新,減輕了開發人員的負擔,提高了Hybrid App離線包的更新效率。 如下以頁面中的頁面樣式的更新為例,描述當頁面樣式更新時,如何觸發離線包更新的流程。其中,頁面樣式更新的方式,可以是開發人員發布變更的代碼,或者由運營人員在模版區塊運營系統進行樣式配置。 如圖1所示,模版區塊運營系統14可以是一個供運營人員修改頁面樣式的人機互動系統,可以提供給運營人員人機對話模式修改頁面中的區塊或者模版。其中,區塊可以是頁面中的某個矩形區域,使用html語法<div></div>進行標記,模版可以是使用velocity等模版語言編寫的模組。為了使得運營人員在藉由模版區塊運營系統對某個Hybrid App進行區塊和模版的配置變更時,同樣能自動觸發離線包管理系統12中該Hybrid App的離線包的更新,以自動觸發頁面樣式的變更,本例子可以設置動態打包系統15,如圖1所示。 動態打包系統15可以實現在運營人員進行區塊和模版的配置變更時,自動更新離線包管理系統12中對應的離線包,從而實現Hybrid App頁面樣式的動態更新。圖3示例了一個根據圖1的動態打包系統更新頁面樣式的流程,包括: 在步驟300中,前端開發人員進行代碼發布變更,或者運營人員進行區塊模版的配置變更。 例如,如圖1示例,開發人員可以進行頁面樣式更新對應的代碼變更,例如,要改變頁面的佈局,或者改變頁面某一部分的顯示樣式,可以變更對應的代碼,可以稱這部分代碼為開發變更代碼。 在另一例子中,也可以由運營人員藉由模版區塊運營系統,配置變更頁面中的區塊或者模版,從而改變頁面的樣式,例如改變頁面中的廣告條的形狀或者位置。對應生成的代碼可以稱為運營模版代碼。 在步驟302中,動態打包系統獲取到Hybrid App頁面對應的新頁面文件和事件聯動觸發,該觸發可以用於通知發生了頁面樣式更新對應的更新事件。 其中,步驟300中的開發人員進行變更代碼的發布,或者,運營人員進行區塊模版的配置變更,並將配置變更的區塊模版向動態打包系統推送,這些變更Hybrid App頁面樣式的操作都可以稱為更新事件。更新事件發生後,模版引擎可以生成新頁面文件,例如,模版引擎可以根據頁面樣式變更對應的開發變更代碼生成新頁面文件,或者,還可以根據區塊模版配置變更對應的運營模版代碼生成新頁面文件(即新前端代碼),又或者,模版引擎還可以根據區塊模版配置變更的更新事件得到對應的運營模版代碼,並據此生成新頁面文件。 圖1中的動態打包系統15不僅可以接收到上述的新頁面文件,還可以接收到事件聯動觸發。事件聯動觸發可以是在發生更新事件時發送,用於通知發生了頁面樣式更新對應的更新事件。如圖1的示例,當運營人員修改了區塊或者模版時,模版區塊運營系統可以同時向動態打包系統的打包觸發器發送事件聯動觸發,用於通知發生了模版區塊的配置變更;或者,當開發人員變更了頁面的樣式代碼時,變更代碼的模組也可以向動態打包系統的打包觸發器發送事件聯動觸發,用於通知發生了代碼變更。在圖1的一個例子中,事件聯動觸發可以是發送至動態打包系統15中的打包觸發器151,打包觸發器151根據該事件聯動觸發,將進行離線包的打包處理。 本步驟中,模版引擎152可以根據開發變更代碼或者運營模版代碼,生成新頁面文件。例如,模版引擎152可以根據步驟302中得到的開發變更代碼或者運營模版代碼,生成新的Hybrid App頁面的頁面文件。如圖1所示,即模版引擎152根據開發變更代碼或者運營模版代碼得到新的前端代碼153。 在步驟304中,動態打包系統的打包觸發器根據接收到的事件聯動觸發,將所述新頁面文件打包成離線包。 例如,打包觸發器151可以根據事件聯動觸發,在等待模版引擎完成前端代碼的更新後,即生成新頁面文件後,將該新頁面文件進行離線包的打包。 在步驟306中,動態打包系統的打包觸發器將所述離線包發送至離線包管理系統。例如,結合圖1來看,假設本次更新的Hybrid App是web app1,則打包觸發器將打包的離線包發送至離線包管理系統12中的web app1。還可以將web app1的離線包的版本進行更新,原有的舊離線包版本假設是V1,更新後的新離線包版本可以是V2。 在步驟308中,藉由離線包管理系統觸發Hybrid App頁面樣式的更新。 例如,如圖1的示例,當接收到對Hybrid App的頁面存取請求時,可以由離線包管理系統12中的web app1的離線包獲取頁面樣式,如果該離線包有更新,例如由版本V1更新到版本V2,則藉由離線包更新頁面樣式,並藉由非同步請求資料的方式由web app1的後端代碼獲取頁面資料,從而實現整個Hybrid App的頁面展示。 本例子的頁面樣式更新方法,藉由由動態打包系統根據頁面樣式變更生成的新頁面文件,打包成離線包並發送至離線包管理系統,可以實現離線包管理系統中的離線包的自動更新。該方案能夠使得即使是運營人員配置區塊或模版,也同樣能夠自動觸發離線包的更新,實現運營動態配置樣式,也減輕了開發人員的負擔,提高了Hybrid App的離線包的更新效率。 為了實現本說明書一個或多個實施例的頁面更新方法,圖4提供了一種動態打包系統,可以包括:模版引擎41和打包觸發器42。 模版引擎41,用於獲取混合模式移動應用Hybrid App頁面的新頁面文件; 打包觸發器42,用於將所述新頁面文件打包成離線包,並將離線包發送至離線包管理系統,以藉由離線包管理系統觸發Hybrid App頁面樣式的更新。 在一個例子中,所述新頁面文件是由所述模版引擎根據頁面樣式更新生成的文件。例如,所述頁面樣式更新,包括:頁面樣式對應的開發代碼變更,或者,模版區塊的配置變更。 在一個例子中,打包觸發器42,在用於將新頁面文件打包成離線包時,包括:根據接收到的事件聯動觸發,將所述新頁面文件打包成離線包;所述事件聯動觸發用於通知發生了所述頁面樣式更新對應的更新事件。 在一個例子中,所述打包觸發器42,還用於將所述新頁面文件打包成離線包時,還更新所述離線包的版本。 上述圖2和圖3所示流程中的各個步驟,其執行順序不限制於流程圖中的順序。此外,各個步驟的描述,可以實現為軟體、硬體或者其結合的形式,例如,本領域技術人員可以將其實現為軟體代碼的形式,可以為能夠實現所述步驟對應的邏輯功能的電腦可執行指令。當其以軟體的方式實現時,所述的可執行指令可以儲存在記憶體中,並被設備中的處理器執行。 例如,對應於上述方法,本說明書一個或多個實施例同時提供一種伺服端設備,該設備可以包括處理器、記憶體、以及儲存在記憶體上並可在處理器上運行的電腦指令,所述處理器藉由執行所述指令,用於實現如下步驟:獲取混合模式移動應用Hybrid App頁面的新頁面文件;將所述新頁面文件打包成離線包;將所述離線包發送至離線包管理系統,以藉由離線包管理系統觸發Hybrid App頁面樣式的更新。 上述實施例闡明的裝置或模組,具體可以由電腦晶片或實體實現,或者由具有某種功能的產品來實現。一種典型的實現設備為電腦,電腦的具體形式可以是個人電腦、膝上型電腦、蜂巢式電話、相機電話、智慧型電話、個人數位助理、媒體播放機、導航設備、電子郵件收發設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任意幾種設備的組合。 為了描述的方便,描述以上裝置時以功能分為各種模組分別描述。當然,在實施本說明書一個或多個實施例時可以把各模組的功能在同一個或多個軟體和/或硬體中實現。 本領域內的技術人員應明白,本說明書一個或多個實施例可提供為方法、系統、或電腦程式產品。因此,本說明書一個或多個實施例可採用完全硬體實施例、完全軟體實施例、或結合軟體和硬體態樣的實施例的形式。而且,本說明書一個或多個實施例可採用在一個或多個其中包含有電腦可用程式碼的電腦可用儲存媒體(包括但不限於磁碟記憶體、CD-ROM、光學記憶體等)上實施的電腦程式產品的形式。 這些電腦程式指令也可儲存在能引導電腦或其他可程式設計資料處理設備以特定方式工作的電腦可讀記憶體中,使得儲存在該電腦可讀記憶體中的指令產生包括指令裝置的製造品,該指令裝置實現在流程圖一個流程或多個流程和/或方塊圖一個方塊或多個方塊中指定的功能。 這些電腦程式指令也可裝載到電腦或其他可程式設計資料處理設備上,使得在電腦或其他可程式設計設備上執行一系列操作步驟以產生電腦實現的處理,從而在電腦或其他可程式設計設備上執行的指令提供用於實現在流程圖一個流程或多個流程和/或方塊圖一個方塊或多個方塊中指定的功能的步驟。 還需要說明的是,術語“包括”、“包含”或者其任何其他變體意在涵蓋非排他性的包含,從而使得包括一系列要素的過程、方法、商品或者設備不僅包括那些要素,而且還包括沒有明確列出的其他要素,或者是還包括為這種過程、方法、商品或者設備所固有的要素。在沒有更多限制的情況下,由語句“包括一個……”限定的要素,並不排除在包括所述要素的過程、方法、商品或者設備中還存在另外的相同要素。 本說明書一個或多個實施例可以在由電腦執行的電腦可執行指令的一般上下文中描述,例如程式模組。一般地,程式模組包括執行特定任務或實現特定抽象資料類型的常式、程式、物件、元件、資料結構等等。也可以在分散式運算環境中實踐本說明書一個或多個實施例,在這些分散式運算環境中,由藉由通訊網路而被連接的遠端處理設備來執行任務。在分散式運算環境中,程式模組可以位於包括存放裝置在內的本地和遠端電腦儲存媒體中。 本說明書中的各個實施例均採用遞進的方式描述,各個實施例之間相同相似的部分互相參見即可,每個實施例重點說明的都是與其他實施例的不同之處。尤其,對於伺服端設備實施例而言,由於其基本相似於方法實施例,所以描述的比較簡單,相關之處參見方法實施例的部分說明即可。 上述對本說明書特定實施例進行了描述。其它實施例在所附申請專利範圍的範圍內。在一些情況下,在申請專利範圍中記載的動作或步驟可以按照不同於實施例中的順序來執行並且仍然可以實現期望的結果。另外,在附圖中描繪的過程不一定要求顯示的特定順序或者連續順序才能實現期望的結果。在某些實施方式中,多工處理和並行處理也是可以的或者可能是有利的。 以上所述僅為本說明書一個或多個實施例的較佳實施例而已,並不用以限制本揭露,凡在本揭露的精神和原則之內,所做的任何修改、等同替換、改進等,均應包含在本揭露保護的範圍之內。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‧‧‧用戶端11‧‧‧User
12‧‧‧離線包管理系統12‧‧‧Offline Package Management System
13‧‧‧伺服端13‧‧‧Server
14‧‧‧模版區塊運營系統14‧‧‧Template Block Operation System
15‧‧‧動態打包系統15‧‧‧dynamic packaging system
151‧‧‧打包觸發器151‧‧‧Package trigger
152‧‧‧模版引擎152‧‧‧Template engine
153‧‧‧前端代碼153‧‧‧ front-end code
200‧‧‧步驟200‧‧‧ steps
202‧‧‧步驟202‧‧‧Steps
204‧‧‧步驟204‧‧‧Steps
300‧‧‧步驟300‧‧‧Steps
302‧‧‧步驟302‧‧‧Steps
304‧‧‧步驟304‧‧‧Steps
306‧‧‧步驟306‧‧‧Steps
308‧‧‧步驟308‧‧‧Steps
41‧‧‧模版引擎41‧‧‧Template engine
42‧‧‧打包觸發器42‧‧‧Package trigger
為了更清楚地說明本說明書一個或多個實施例或現有技術中的技術方案,下面將對實施例或現有技術描述中所需要使用的附圖作簡單地介紹,顯而易見地,下面描述中的附圖僅僅是本說明書一個或多個實施例中記載的一些實施例,對於本領域普通技術人員來講,在不付出進步性勞動性的前提下,還可以根據這些附圖獲得其他的附圖。 圖1為本說明書一個或多個實施例提供的Hybrid App應用的系統架構; 圖2為本說明書一個或多個實施例提供的頁面更新方法的流程圖; 圖3為本說明書一個或多個實施例提供的動態打包系統更新頁面樣式的流程; 圖4為本說明書一個或多個實施例提供的動態打包系統的結構示意圖。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)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710713596.3A CN107608691A (en) | 2017-08-18 | 2017-08-18 | A kind of method for updating pages and device |
??201710713596.3 | 2017-08-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
TW201913361A true TW201913361A (en) | 2019-04-01 |
Family
ID=61065540
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
TW107116976A TW201913361A (en) | 2017-08-18 | 2018-05-18 | Page update method and apparatus |
Country Status (3)
Country | Link |
---|---|
CN (1) | CN107608691A (en) |
TW (1) | TW201913361A (en) |
WO (1) | WO2019034066A1 (en) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107608691A (en) * | 2017-08-18 | 2018-01-19 | 阿里巴巴集团控股有限公司 | A kind of method for updating pages and device |
CN108776592B (en) * | 2018-05-23 | 2022-04-05 | 北京五八信息技术有限公司 | Page construction method, device, equipment and storage medium |
CN108804120B (en) * | 2018-05-23 | 2022-04-05 | 北京五八信息技术有限公司 | Page construction method, device, equipment and storage medium |
CN108845810B (en) * | 2018-05-23 | 2022-04-22 | 北京五八信息技术有限公司 | Method and device for dynamically updating application, electronic equipment and storage medium |
CN111538926A (en) * | 2020-04-20 | 2020-08-14 | 北京达佳互联信息技术有限公司 | Automatic offline package publishing method and device, electronic equipment and storage medium |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013100990A1 (en) * | 2011-12-28 | 2013-07-04 | Intel Corporation | Hybrid mobile interactions for native apps and web apps |
CN104216926A (en) * | 2013-06-05 | 2014-12-17 | 上海缪思信息科技有限公司 | Page generating method, template engine and processor |
CN103701909B (en) * | 2013-12-26 | 2018-06-26 | 乐视致新电子科技(天津)有限公司 | The rapid generation and system of Video Applications |
CN106020906A (en) * | 2016-05-31 | 2016-10-12 | 广东能龙教育股份有限公司 | Client side hot updating method based on Cordova |
CN107608691A (en) * | 2017-08-18 | 2018-01-19 | 阿里巴巴集团控股有限公司 | A kind of method for updating pages and device |
-
2017
- 2017-08-18 CN CN201710713596.3A patent/CN107608691A/en active Pending
-
2018
- 2018-05-18 TW TW107116976A patent/TW201913361A/en unknown
- 2018-08-15 WO PCT/CN2018/100559 patent/WO2019034066A1/en active Application Filing
Also Published As
Publication number | Publication date |
---|---|
WO2019034066A1 (en) | 2019-02-21 |
CN107608691A (en) | 2018-01-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11164280B2 (en) | Graphics layer processing in a multiple operating systems framework | |
TW201913361A (en) | Page update method and apparatus | |
US9229759B2 (en) | Virtual machine provisioning using replicated containers | |
US9672140B1 (en) | Processing special requests at dedicated application containers | |
CN109643252B (en) | Middleware interface and middleware interface generator | |
TW201911020A (en) | Page update method and device | |
US10372443B2 (en) | Multi-platform pattern-based user interfaces | |
US11360765B2 (en) | Metadata driven serverless functions in a multitenant environment | |
TW201732626A (en) | Method and device for acquiring application resource | |
US20210117386A1 (en) | Host-level persistent volume management for container clouds | |
US20220334809A1 (en) | Process flow builder for extensible web component sequences | |
JP7048663B2 (en) | Code execution methods, devices, rendering devices, storage media, and programs | |
US20130074068A1 (en) | Method, System, and Computer Program for Implementing a Customizable Virtual Appliance | |
US20130007184A1 (en) | Message oriented middleware with integrated rules engine | |
CN111865649A (en) | Method and apparatus for processing media content, computer device and storage medium | |
US10536512B2 (en) | Dynamic graph adaptation for stream processing over hybrid, physically disparate analytics platforms | |
KR20160022362A (en) | Synchronization points for state information | |
US11625242B1 (en) | Automated generation of dependency hierarchy based on input and output requirements of information | |
JP2021068414A (en) | Wrapping method, registration method, device, rendering device, and program | |
Kang et al. | Modelling mobile agent applications in UML 2.0 activity diagrams | |
US20220245206A1 (en) | Process flow builder for user-configurable web component sequences | |
CN117296042A (en) | Application management platform for super-fusion cloud infrastructure | |
JP7106778B1 (en) | BLOCKCHAIN SYSTEM EXECUTION METHOD, APPARATUS, DEVICE, AND STORAGE MEDIUM | |
US20240143340A1 (en) | Hybrid multi-tenant framework for reconfiguring software components | |
EP4394593A1 (en) | Skin changing method and apparatus for display interface, vehicle and storage medium |