本說明書實施例提供一種頁面處理方法、裝置及設備。
為了使本技術領域的人員更好地理解本說明書中的技術方案，下面將結合本說明書實施例中的圖式，對本說明書實施例中的技術方案進行清楚、完整地描述，顯然，所描述的實施例僅僅是本說明書一部分實施例，而不是全部的實施例。基於本說明書中的實施例，本領域普通技術人員在沒有作出創造性勞動前提下所獲得的所有其他實施例，都應當屬於本說明書保護的範圍。
實施例一
如圖1所示，本說明書實施例提供一種頁面處理方法，該方法的執行主體可以為終端設備或伺服器，其中，該終端設備可以如個人電腦等設備，也可以如手機、平板電腦等行動終端設備，該終端設備可以為用戶使用的終端設備。該伺服器可以是獨立的伺服器，也可以是由多個伺服器組成的伺服器集群，而且，該伺服器可以是某項業務的後台伺服器，也可以是某網站(如網路購物網站或支付應用等)的後台伺服器等。該方法可以用於產生終端設備的作業系統中原生使用者介面中的控制項對應的頁面(即本實施例中提到的目標頁面)，且該頁面為基於超文件標示語言(即Hyper Text Markup Language，HTML)開發，其中的超文件標示語言可以包括HTML 2.0、HTML 3.2、HTML 4.0和HTML 5等。為了簡化頁面處理過程和頁面處理效率，本實施例中以執行主體為終端設備為例進行說明，對於伺服器的情況，可以根據下述相關內容處理，在此不再贅述。該方法具體可以包括以下步驟：
在步驟S102中，獲取目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊。
其中，目標使用者介面可以終端設備的作業系統中原生的使用者介面(即UI，User Interface)，終端設備的作業系統可以包括安卓(即Android)作業系統和iOS作業系統等。第一控制項可以是作業系統的使用者介面中的任意控制項，例如按鍵、輸入框控制項、搜索框控制項、日曆控制項或上傳圖片控制項等。排版資訊可以是用於表明控制項在頁面中的大小、位置等相關資訊的資訊，排版資訊可以助於終端設備轉列並顯示頁面。控制項的類型可以根據實際情況設定，例如可以根據控制項的作用和用途進行分類，如按鍵類、輸入框類或上傳圖片類等，在實際應用中，可能並不限於上述分類，還可以基於上述分類結果再進行分類，例如，按鍵類還可以分為圓形按鍵類、矩形按鍵類等，或者，直接將控制項的類型分為圓形按鍵類、矩形按鍵類、輸入框類或上傳圖片類等，本說明書實施例對此不做限定。
在實施中，超文件標示語言是標準通用標記語言下的一個應用，也是一種規範，一種標準，它透過標記符號來標記要顯示的網頁中的各個部分。網頁檔本身是一種文字檔，透過在文字檔中添加標記符，可以指示瀏覽器如何顯示其中的內容(如其中的文字如何處理、畫面如何排布，圖片如何顯示等)。瀏覽器可以按照網頁檔中的內容順序閱讀該網頁檔，然後，根據標記符解釋和顯示其標記的內容。其中，對於不同的瀏覽器，對同一標記符可能會有不完全相同的解釋，因而可能會有不同的顯示效果。超文件標示語言文檔製作不是很複雜，但功能強大，支援不同資料格式的檔鑲入。超文件標示語言可以具備簡易性、可擴展性、操作平台無關性和通用性等主要特點，由於超文件標示語言版本的升級通常採用超集合方式，因此，超文件標示語言可以更加靈活方便，而且超文件標示語言可以使用在廣泛的操作平台(即多種作業系統的平台，如Windows作業系統平台或Mac OS平台等)上，而且，超文件標示語言允許網頁製作人員建立文本與圖像相結合的複雜頁面，無論使用者使用的是何種類型的終端設備或瀏覽器，該頁面均可以被瀏覽。
基於超文件標示語言開發的頁面(即目標頁面)中可以包括較多較複雜的元素，例如地圖等，以基於超文件標示語言開發的目標頁面為例，如果透過該目標頁面顯示地圖，而地圖通常需要使用者進行縮放，在進行縮放的過程中，使用者可能很難透過手指觸控的方式對地圖進行縮放，使用者觸控操作的體驗較差，而且目標頁面的轉列效率低。
而終端設備中的使用者介面通常是由一個或多個控制項構成的，透過不同的控制項可以構建出多個不同的使用者介面，不同的控制項可以實現不同的功能，例如，使用者介面中可以包括地圖控制項，使用者可以透過地圖控制項，透過手指觸控的方式，將地圖控制項中的地圖進行隨意放大或縮小，顯然，終端設備中使用者介面中的控制項能夠表現出更好的觸控操作體驗，使用者介面的轉列效率相對較高。
如果將終端設備中的使用者介面中的控制項能夠在目標頁面中顯示，則可以提高目標頁面的觸控操作的體驗和目標頁面的轉列效率，通常，可以透過將終端設備的作業系統的原生使用者介面(即目標使用者介面)中的控制項覆蓋到上述目標頁面中，其中需要說明的是，在實際應用中，將目標使用者介面中的控制項覆蓋到上述目標頁面中的處理，可以是將目標使用者介面中的控制項覆蓋到目標頁面的Webview控制項中。但是，透過上述覆蓋的方式得到的目標頁面，需要限制目標頁面不能夠進行縮放，因為目標頁面中覆蓋的目標使用者介面中的控制項不能夠隨著目標頁面的縮放而進行縮放，而只能夠保持控制項原來的樣式不變，從而給使用者的使用帶來困擾，使用者體驗較差。為此，本說明書實施例提供一種可以包括使用者介面中的控制項的目標頁面，並且其中的控制項還可以隨著目標頁面的縮放而進行縮放的方案，具體可以包括以下內容：
如圖2A所示，當需要將終端設備的作業系統中的某一個或多個原生使用者介面(即目標使用者介面)使用基於超文件標示語言(本實施例中的超文件標示語言可以以HTML 5為例進行說明)開發的目標頁面進行顯示時，可以透過預先設置的介面獲取目標使用者介面，可以對目標使用者介面進行分析計算，確定目標使用者介面中包含的控制項(即第一控制項)，同時，可以記錄每個第一控制項的大小尺寸和在目標使用者介面中的位置，其中，該位置可以以座標的形式表示，或者，也可以以某一個位置作為中心點，確定第一控制項與該中心點之間的相對位置等。可以使用記錄的每個第一控制項的大小尺寸和在目標使用者介面中的位置等資訊，產生第一控制項在目標使用者介面中的排版資訊。此外，還可以對目標使用者介面中的每個第一控制項進行分析，確定每個第一控制項所屬的類型，例如，包括3個第一控制項，其中一個第一控制項為按鍵，再一個第一控制項為搜索框控制項，第三個第一控制項為上傳圖片控制項，則第一控制項所屬的類型包括按鍵類、搜索框類和上傳圖片類，相應的，對於上述按鍵，可以產生一個按鍵的排版資訊，對於搜索框控制項，可以產生一個搜索框控制項的排版資訊，對於上傳圖片控制項，可以產生一個上傳圖片控制項的排版資訊。
在步驟S104中，根據上述第一控制項的類型和上述排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項。
其中，第二控制項可以是目標頁面所在的瀏覽器中預先儲存的控制項，也可以是目標頁面對應的資料庫或上述瀏覽器所對應的資料庫中預先儲存的控制項，第二控制項可以是目標使用者介面的開發或技術人員創建，由於第二控制項的創建充分考慮了基於超文件標示語言開發的目標頁面的環境，也即是第二控制項需要在目標頁面中使用，可以隨著目標頁面的縮放而進行縮放，而且第二控制項可以是與目標使用者介面中的第一控制項屬於同一類型，兩者相互對應，例如，第一控制項為按鍵，第二控制項也應該為按鍵，而且，第二控制項可以與第一控制項在外觀和功能上完全相同等。排版指令集可以是由一個或多個排版指令構成的集合，每個排版指令可以相互獨立，也可以是相互關聯，如果多個排版指令相互關聯，則該排版指令中還可以包括儲存關聯關係的排版指令的標識等。
在實施中，目標頁面所在的瀏覽器，或者目標頁面對應的資料庫，或者上述瀏覽器所對應的資料庫中，可以預先儲存有與終端設備的作業系統的原生使用者介面中的控制項相對應的控制項。當終端設備透過上述步驟S102的處理確定第一控制項的類型後，可以透過確定的類型，在上述預先儲存的控制項中查找與確定的類型對應的控制項，查找到後，可以將查找到的控制項作為與該第一控制項相對應的第二控制項，然後，可以從透過上述步驟S102的處理得到的排版資訊中，查找該第一控制項在目標使用者介面中的排版資訊，查找到後，可以提取查找到的排版資訊中該第一控制項的大小尺寸和在目標使用者介面中的位置。
可以創建一個空的目標頁面，可以基於目標頁面的固有屬性，並根據該第一控制項的大小尺寸，確定相應的第二控制項的大小尺寸，同時，還可以基於目標頁面的固有屬性，並根據該第一控制項在目標使用者介面中的位置，確定相應的第二控制項在目標頁面中的位置。可以透過目標頁面的固有屬性、第二控制項的大小尺寸和第二控制項在目標頁面中的位置等，產生該第二控制項在目標頁面中的排版資訊，並可以基於產生的排版資訊產生該第二控制項在目標頁面中一個或多個排版指令，得到該第二控制項在目標頁面中的排版指令集。
需要說明的是，可以包括多個第一控制項，相應的第二控制項也應該是多個，而且，第一控制項的數量與第二控制項的數量相等，對於包括多個第二控制項的情況，可以透過上述方式分別獲取每個第二控制項在目標頁面中的排版指令或排版指令集。
在步驟S106中，執行上述排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面。
其中，排版處理可以是在有限的頁面空間裡，將頁面構成元素(如文字、圖片、線條線框和顏色色塊等)，根據特定內容的需要進行組合排列，並運用造型要素及形式原理，把元素排布在頁面中的處理。轉列處理可以是對將要呈現的頁面進行計算，得到頁面的顯示效果的處理。
在實施中，透過上述步驟S104的處理得到第二控制項在目標頁面中的排版指令集後，終端設備可以分別對排版指令集中的排版指令進行解析，以將排版指令集中的排版指令的資料轉換成顯示部件或顯示模組能夠識別的資料，然後，終端設備的示部件或顯示模組可以執行解析後的排版指令，透過解析後的排版指令可以確定第二控制項的相關資訊，並可以從預先儲存的控制項中提取該第二控制項。如圖2B所示，還可以透過解析後的排版指令確定該第二控制項的大小尺寸和第二控制項在目標頁面中的位置等，然後，可以根據確定的大小尺寸和在目標頁面中的位置，在目標頁面中對該第二控制項進行排版處理，得到該第二控制項在目標頁面中的排版結果。可以對每個第二控制項均執行上述處理過程，得到其它第二控制項在目標頁面中的排版結果，可以綜合上述每個第二控制項在目標頁面中的排版結果，得到目標頁面的總體排版結果，最後，可以基於目標頁面的總體排版結果，對目標頁面進行轉列處理，使得總體排版結果的目標頁面得以呈現，從而得到了融合有第二控制項的目標頁面。
基於上述處理，由於第二控制項是能夠融合到目標頁面(而不是如相關技術中覆蓋在目標頁面)中，因此，第二控制項可以隨著目標頁面的縮放而進行縮放，而且，第二控制項是與目標使用者介面中的第一控制項相對應的，並且，第二控制項在目標頁面中的排版也是與第一控制項在目標使用者介面中的排版相對應，這樣，會產生融合有第二控制項的目標頁面與包含第一控制項的目標使用者介面，在呈現或顯示結果上相同或相似(例如兩個頁面的外觀相同或相近)，從而給使用者一種將目標使用者介面(或其中的控制項)轉移到了目標頁面中的感覺，而且，目標頁面中的控制項還可以隨著目標頁面的縮放而進行縮放，提高了使用者體驗。
本說明書實施例提供一種頁面處理方法，應用於目標頁面，該目標頁面基於超文件標示語言開發，透過獲取的目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項，執行該排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面，這樣，將終端設備的作業系統中原生使用者介面(即目標使用者介面)控制項作為目標頁面中顯示控制項的子顯示控制項添加到目標頁面(即基於超文件標示語言開發的頁面)中，而不是將終端設備的作業系統中原生使用者介面控制項簡單覆蓋在目標頁面上，從而達到了將目標使用者介面的控制項融合到目標頁面的效果，使得融合在目標頁面中的第二控制項可以隨著目標頁面進行縮放，提高了使用者體驗。
實施例二
如圖3所示，本說明書實施例提供一種頁面處理方法，該方法的執行主體可以為終端設備或伺服器，其中，該終端設備可以如個人電腦等設備，也可以如手機、平板電腦等行動終端設備，該終端設備可以為用戶使用的終端設備。該伺服器可以是獨立的伺服器，也可以是由多個伺服器組成的伺服器集群，而且，該伺服器可以是某項業務的後台伺服器，也可以是某網站(如網路購物網站或支付應用等)的後台伺服器等。該方法可以用於產生終端設備的作業系統中原生使用者介面中的控制項對應的頁面(即本實施例中提到的目標頁面)，且該頁面為基於超文件標示語言(即Hyper Text Markup Language，HTML)開發，其中的超文件標示語言可以包括HTML 2.0、HTML 3.2、HTML 4.0和HTML 5等。為了簡化頁面處理過程和頁面處理效率，本實施例中以執行主體為終端設備為例進行說明，對於伺服器的情況，可以根據下述相關內容處理，在此不再贅述。該方法具體可以包括以下步驟：
在步驟S302中，呼叫預設的程式設計介面，獲取目標使用者介面中的第一控制項的類型，以及第一控制項在使用者介面中的排版資訊。
其中，程式設計介面可以是由一個或多個預先定義的函數構成，目的是提供應用程式與開發人員(或技術人員)基於某軟體或硬體得以接達一組常式的能力，同時又無需接達原始程式碼或理解內部工作機制的細節等，具體可以為JSAPI(JavaScript Application Programming Interface，Java描述語言應用程式設計發展介面)等。
在實施中，當需要將終端設備的作業系統中的某一個或多個原生使用者介面(即目標使用者介面)使用基於超文件標示語言(本實施例中的超文件標示語言可以以HTML 5為例進行說明)開發的目標頁面進行顯示時，可以呼叫預設的程式設計介面(如JSAPI等)，以獲取目標使用者介面，並可以對目標使用者介面進行分析計算，確定目標使用者介面中包含的控制項(即第一控制項)，同時，可以記錄每個第一控制項的大小尺寸和在目標使用者介面中的位置。可以使用記錄的每個第一控制項的大小尺寸和在目標使用者介面中的位置等資訊，產生第一控制項在目標使用者介面中的排版資訊。此外，還可以對目標使用者介面中的每個第一控制項進行分析，確定每個第一控制項所屬的類型。
在步驟S304中，根據上述第一控制項的類型和上述排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項。
上述步驟S304的步驟內容與上述實施例一中步驟S104的步驟內容相同，上述步驟S304的具體處理過程可以參見上述實施例一中步驟S104的相關內容，在此不再贅述。
在步驟S306中，執行上述排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面。
上述步驟S306的步驟內容與上述實施例一中步驟S106的步驟內容相同，上述步驟S306的具體處理過程可以參見上述實施例一中步驟S106的相關內容，在此不再贅述。
此外，透過上述方式得到融合有第二控制項的目標頁面後，還可以對目標頁面中的第二控制項進行管理，得到處理後的目標頁面，具體可以參見下述步驟S308和步驟S310的處理。
在步驟S308中，接收對目標頁面中的第二控制項的管理指令，該管理指令可以包括刪除指令和狀態修改指令等。
其中，狀態修改指令可以是將第二控制項由一種狀態修改為另一種狀態，例如，將第二控制項由未觸發狀態修改為被觸發狀態等。
在實施中，當需要對目標頁面中的一個或多個第二控制項進行刪除時，可以觸發目標頁面所在的瀏覽器中或目標頁面中提供的第二控制項管理按鍵，此時，可以產生對目標頁面中該一個或多個第二控制項的刪除指令，終端設備可以接收對目標頁面中該一個或多個第二控制項的刪除指令。
另外，當需要對目標頁面中的一個或多個第二控制項的狀態進行修改時，可以觸發目標頁面所在的瀏覽器中或目標頁面中提供的第二控制項管理按鍵，此時，可以獲取第二控制項當前的狀態資訊，以及修改後的狀態資訊，可以基於上述資訊，產生對目標頁面中該一個或多個第二控制項的狀態修改指令，終端設備可以接收對目標頁面中該一個或多個第二控制項的狀態修改指令。
在步驟S310中，根據上述管理指令，對目標頁面中的第二控制項執行相應的操作。
在實施中，當接收到對目標頁面中該一個或多個第二控制項的刪除指令時，可以獲取需要刪除的該一個或多個第二控制項的標識，並以此可以從目標頁面中查找到相應的一個或多個第二控制項，可以將該一個或多個第二控制項從目標頁面中刪除。
當接收到對目標頁面中該一個或多個第二控制項的狀態修改指令時，可以獲取需要進行狀態修改的該一個或多個第二控制項的標識，並以此可以從目標頁面中查找到相應的一個或多個第二控制項，可以將該一個或多個第二控制項由當前的狀態資訊對應的狀態修改為修改後的狀態資訊對應的狀態。
本說明書實施例提供一種頁面處理方法，應用於目標頁面，該目標頁面基於超文件標示語言開發，透過獲取的目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項，執行該排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面，這樣，將終端設備的作業系統中原生使用者介面(即目標使用者介面)控制項作為目標頁面中顯示控制項的子顯示控制項添加到目標頁面(即基於超文件標示語言開發的頁面)中，而不是將終端設備的作業系統中原生使用者介面控制項簡單覆蓋在目標頁面上，從而達到了將目標使用者介面的控制項融合到目標頁面的效果，使得融合在目標頁面中的第二控制項可以隨著目標頁面進行縮放，提高了用戶體驗。
上述實施例一和實施例二是以終端設備(或終端設備中安裝的瀏覽器，或上述瀏覽器中的目標頁面)為執行主體進行詳細說明的，其中，目標頁面既需要獲取目標使用者介面中的第一控制項的相關資訊，還需要對上述獲取的相關資訊進行處理，以及轉列顯示目標頁面等處理，在實際應用中，還可以將該目標頁面根據其具備的不同功能，將其劃分為不同的模組執行，以下實施例三和實施例四將上述目標頁面分為頁面管理模組、全域初始化模組和頁面轉列模組進行了說明，具體參見下述內容，其中，頁面管理模組可以以NBComponentManager表示，全域初始化模組可以以NBComponentJSLoader表示，頁面轉列模組可以以NBComponentViews表示，目標頁面可以以Webview表示，Webview可以是終端設備的作業系統中承載與展示基於超文件標示語言(如HTML 5等)開發的目標頁面的UI控制項。此外，上述目標頁面不僅僅可以劃分為上述三個模組，還可以將其進行更加細緻的劃分，劃分為三個以上的模組，另外，即使將上述目標頁面劃分為三個模組，也可以不僅僅劃分為頁面管理模組、全域初始化模組和頁面轉列模組，還可以根據目標頁面的功能，將目標頁面劃分為其它類型的三個不同的模組，對於上述情況，其具體處理過程可以參考下述內容執行。
實施例三
如圖4所示，本說明書實施例提供一種頁面處理方法，該方法的執行主體可以為終端設備或伺服器，其中，該終端設備可以如個人電腦等設備，也可以如手機、平板電腦等行動終端設備，該終端設備可以為用戶使用的終端設備。該伺服器可以是獨立的伺服器，也可以是由多個伺服器組成的伺服器集群，而且，該伺服器可以是某項業務的後台伺服器，也可以是某網站(如網路購物網站或支付應用等)的後台伺服器等。該方法可以用於產生終端設備的作業系統中原生使用者介面中的控制項對應的頁面(即本實施例中提到的目標頁面)，且該頁面為基於超文件標示語言(即Hyper Text Markup Language，HTML)開發，其中的超文件標示語言可以包括HTML 2.0、HTML 3.2、HTML 4.0和HTML 5等。為了簡化頁面處理過程和頁面處理效率，本實施例中以執行主體為終端設備為例進行說明，對於伺服器的情況，可以根據下述相關內容處理，在此不再贅述，此外，該方法的執行主體具體可以為終端設備中目標頁面中的頁面管理模組(即NBComponentManager
)。該方法具體可以包括以下步驟：
在步驟S402中，呼叫全域初始化模組，以獲取目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，並根據上述類型和該排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項。
其中，全域初始化模組(即NBComponentJSLoader)可以運行於Webview中，用於計算並產生排版指令集。頁面管理模組NBComponentManager的主要作用可以是與全域初始化模組NBComponentJSLoader進行通信，以獲取排版指令集，並管理頁面轉列模組NBComponentViews的顯示。
在實施中，如圖5所示，目標頁面中可以包括6個部分，分別為頁面管理模組NBComponentManager、全域初始化模組NBComponentJSLoader、頁面轉列模組
NBComponentViews、Webview、控制項管理模組
NBComponentViewManager、程式設計介面JSAPI等，其
中，控制項管理模組NBComponentViewManager是
NBComponentView的外掛程式化管理器，用戶可以開發並註冊自訂的NBComponentViews等。
當需要將終端設備的作業系統中的某一個或多個原生使用者介面(即目標使用者介面)使用基於超文件標示語言(本實施例中的超文件標示語言可以以HTML 5為例進行說明)開發的目標頁面進行顯示時，頁面管理模組
NBComponentManager可以呼叫全域初始化模組
NBComponentJSLoader，NBComponentJSLoader可以獲取目標使用者介面，並可以對目標使用者介面進行分析計算，確定目標使用者介面中包含的控制項(即第一控制項)，同時，可以記錄每個第一控制項的大小尺寸和在目標使用者介面中的位置。可以使用記錄的每個第一控制項的大小尺寸和在目標使用者介面中的位置等資訊，產生第一控制項在目標使用者介面中的排版資訊。此外，還可以對目標使用者介面中的每個第一控制項進行分析，確定每個第一控制項所屬的類型。
頁面轉列模組NBComponentViews中可以預先儲存有與終端設備的作業系統的原生使用者介面中的控制項相對應的控制項。當NBComponentJSLoader透過上述處理確定第一控制項的類型後，可以透過確定的類型，在上述預先儲存的控制項中查找與確定的類型對應的第二控制項，然後，NBComponentJSLoader可以從得到的排版資訊中，查找該第一控制項在目標使用者介面中的排版資訊，從而得到該第一控制項的大小尺寸和在目標使用者介面中的位置。
NBComponentJSLoader可以根據該第一控制項的大小尺寸，確定相應的第二控制項的大小尺寸，同時，NBComponentJSLoader還可以根據該第一控制項在目標使用者介面中的位置，確定相應的第二控制項在目標頁面中的位置。NBComponentJSLoader可以透過第二控制項的大小尺寸和第二控制項在目標頁面中的位置等，產生該第二控制項在目標頁面中的排版指令集。
在步驟S404中，接收全域初始化模組發送的上述排版指令集。
在步驟S406中，解析上述排版指令集中的排版指令，得到解析後的排版指令。
在實施中，由於NBComponentJSLoader產生的排版指令集中的排版指令的資料是NBComponentViews無法識別的資料，這樣，NBComponentViews將無法執行該排版指令進行排版處理和轉列處理，得到相應的目標頁面，為此，NBComponentManager可以對排版指令集中的排版指令進行解析，以得到能夠被NBComponentViews識別的解析後的排版指令。
在步驟S408中，創建頁面轉列模組，並將上述解析後的排版指令發送給頁面轉列模組，以使該頁面轉列模組根據解析後的排版指令得到融合有第二控制項的目標頁面。
在實施中，NBComponentManager排版指令集中的排版指令的過程中，可以創建對應的NBComponentViews，並將該NBComponentViews融合到Webview上。然後，可以將NBComponentManager解析後的排版指令發送給
NBComponentViews。NBComponentViews可以處理解析後的排版指令，可以根據解析後的排版指令中的資料和屬性，獲取第二控制項，並將第二控制項融合到目標頁面(即HTML 5頁面)中，並顯示該目標頁面(即HTML 5頁面)。
如圖6所示，本說明書實施例提供一種頁面處理方法，該方法的執行主體可以為終端設備或伺服器，其中，該終端設備可以如個人電腦等設備，也可以如手機、平板電腦等行動終端設備，該終端設備可以為用戶使用的終端設備。該伺服器可以是獨立的伺服器，也可以是由多個伺服器組成的伺服器集群，而且，該伺服器可以是某項業務的後台伺服器，也可以是某網站(如網路購物網站或支付應用等)的後台伺服器等。該方法可以用於產生終端設備的作業系統中原生使用者介面中的控制項對應的頁面(即本實施例中提到的目標頁面)，且該頁面為基於超文件標示語言(即Hyper Text Markup Language，HTML)開發，其中的超文件標示語言可以包括HTML 2.0、HTML 3.2、HTML 4.0和HTML 5等。為了簡化頁面處理過程和頁面處理效率，本實施例中以執行主體為終端設備為例進行說明，對於伺服器的情況，可以根據下述相關內容處理，在此不再贅述，此外，該方法的執行主體具體可以為終端設備中目標頁面中的全域初始化模組(即
NBComponentJSLoader)。該方法具體可以包括以下步驟：
在步驟S602中，向頁面管理模組發送程式設計介面呼叫指令。
在步驟S604中，根據頁面管理模組的呼叫指示，獲取目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，並根據該類型和該排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項。
在步驟S606中，向頁面管理模組發送上述排版指令集。
如圖7所示，本說明書實施例提供一種頁面處理方法，該方法的執行主體可以為終端設備或伺服器，其中，該終端設備可以如個人電腦等設備，也可以如手機、平板電腦等行動終端設備，該終端設備可以為用戶使用的終端設備。該伺服器可以是獨立的伺服器，也可以是由多個伺服器組成的伺服器集群，而且，該伺服器可以是某項業務的後台伺服器，也可以是某網站(如網路購物網站或支付應用等)的後台伺服器等。該方法可以用於產生終端設備的作業系統中原生使用者介面中的控制項對應的頁面(即本實施例中提到的目標頁面)，且該頁面為基於超文件標示語言(即Hyper Text Markup Language，HTML)開發，其中的超文件標示語言可以包括HTML 2.0、HTML 3.2、HTML 4.0和HTML 5等。為了簡化頁面處理過程和頁面處理效率，本實施例中以執行主體為終端設備為例進行說明，對於伺服器的情況，可以根據下述相關內容處理，在此不再贅述，此外，該方法的執行主體具體可以為終端設備中目標頁面中的頁面轉列模組NBComponentViews。該方法具體可以包括以下步驟：
在步驟S702中，接收頁面管理模組發送的排版指令，該排版指令是頁面管理模組對全域初始化模組產生並發送的目標頁面的排版指令集進行解析後得到。
在步驟S704中，執行上述排版指令，從預先儲存的控制項庫中獲取該排版指令對應的第二控制項，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面，第二控制項是目標使用者介面中的第一控制項的類型對應的控制項。
其中，預先儲存的控制項庫可以設置於頁面轉列模組NBComponentViews中，NBComponentViews中可以包括一套可以融入基於超文件標示語言(如HTML 5)開發的目標頁面的終端設備的作業系統的原生UI控制項庫(或原生UI控制項集)。
本說明書實施例提供一種頁面處理方法，應用於目標頁面，該目標頁面基於超文件標示語言開發，透過獲取的目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項，執行該排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面，這樣，將終端設備的作業系統中原生使用者介面(即目標使用者介面)控制項作為目標頁面中顯示控制項的子顯示控制項添加到目標頁面(即基於超文件標示語言開發的頁面)中，而不是將終端設備的作業系統中原生使用者介面控制項簡單覆蓋在目標頁面上，從而達到了將目標使用者介面的控制項融合到目標頁面的效果，使得融合在目標頁面中的第二控制項可以隨著目標頁面進行縮放，提高了用戶體驗。
實施例四
如圖8所示，本說明書實施例提供一種頁面處理方法，該方法的執行主體可以為終端設備或伺服器，其中，該終端設備可以如個人電腦等設備，也可以如手機、平板電腦等行動終端設備，該終端設備可以為用戶使用的終端設備。該伺服器可以是獨立的伺服器，也可以是由多個伺服器組成的伺服器集群，而且，該伺服器可以是某項業務的後台伺服器，也可以是某網站(如網路購物網站或支付應用等)的後台伺服器等。該方法可以用於產生終端設備的作業系統中原生使用者介面中的控制項對應的頁面(即本實施例中提到的目標頁面)，且該頁面為基於超文件標示語言(即Hyper Text Markup Language，HTML)開發，其中的超文件標示語言可以包括HTML 2.0、HTML 3.2、HTML 4.0和HTML 5等。為了簡化頁面處理過程和頁面處理效率，本實施例中以執行主體為終端設備為例進行說明，對於伺服器的情況，可以根據下述相關內容處理，在此不再贅述，此外，該方法具體可以由終端設備中目標頁面中的頁面管理模組(即NBComponentManager)、全域初始化模組(NBComponentJSLoader)和頁面轉列模組(NBComponentViews)共同執行。該方法具體可以包括以下步驟：
在步驟S802中，全域初始化模組向頁面管理模組發送程式設計介面呼叫指令。
在實施中，在基於超文件標示語言(如HTML 5)開發的目標頁面創建的同時，全域初始化模組
NBComponentJSLoader可以進行初始化處理，並可以將NBComponentJSLoader存於當前的目標頁面的上下文中，NBComponentJSLoader初始化完畢後，可以向頁面管理模組NBComponentManager發出通知消息，
NBComponentManager接收到該通知消息夠，可以進行初始化處理。NBComponentManager初始化完成後，
NBComponentJSLoader可以向NBComponentManager發送JSAPI呼叫指令(即Call Render JSAPI)。
在步驟S804中，頁面管理模組呼叫全域初始化模組。
在步驟S806中，全域初始化模組根據頁面管理模組的呼叫指示，獲取目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，並根據該類型和該排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項。
在步驟S808中，全域初始化模組向頁面管理模組發送排版指令集。
在步驟S810中，頁面管理模組解析該排版指令集中的排版指令，得到解析後的排版指令。
在步驟S812中，頁面管理模組創建頁面轉列模組，並將該解析後的排版指令發送給頁面轉列模組。
在步驟S814中，頁面轉列模組執行解析後的排版指令，從預先儲存的控制項庫中獲取該排版指令對應的第二控制項，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面。
需要說明的是，頁面轉列模組完成上述排版處理和轉列處理，得到融合有第二控制項的目標頁面後，可以向全域初始化模組發送目標頁面轉列完成的通知消息。
在執行上述步驟S812中頁面管理模組創建頁面轉列模組的過程中，可以同時創建頁面轉列模組的生命週期，以管理頁面轉列模組的顯示、隱藏和銷毀等，具體可以參見下述步驟S816~步驟S826的處理。
在步驟S816中，頁面管理模組創建頁面轉列模組的生命週期。
在實施中，如果目標頁面為首次創建，
NBComponentViews會收到終端設備的作業系統中的原生UI控制項被融合到Webview上的通知，用來處理與終端設備的作業系統中的原生UI控制項相關的初始化工作。
在步驟S818中，當接收到全域初始化模組發送的生命週期不可見的通知消息時，頁面管理模組將頁面轉列模組的生命週期設置為不可見狀態。
其中，不可見狀態可以是將頁面轉列模組的生命週期進行暫停等處理，在實際應用中，生命週期不可見的通知消息可以以onWebViewPause的通知消息表示，
onWebViewPause可以由WebView不可見的生命週期函數構成，用來處理與終端設備的作業系統中的原生UI控制項相關的生命週期。
在實施中，當終端設備處於螢幕鎖定或壓後台等狀態時，全域初始化模組可以產生生命週期不可見的通知消息(即onWebViewPause)，並可以將其發送給頁面管理模組NBComponentManager。NBComponentManager接收到全域初始化模組發送的onWebViewPause的通知消息時，可以將onWebViewPause發送給頁面轉列模組
NBComponentViews，並回呼NBComponentViews將
NBComponentViews的生命週期設置為不可見狀態。
在步驟S820中，當接收到全域初始化模組發送的生命週期恢復可見的通知消息時，頁面管理模組將頁面轉列模組的生命週期設置為可見狀態。
其中，可見狀態可以是將頁面轉列模組的生命週期恢復有效等處理，在實際應用中，生命週期可見的通知消息可以以onWebViewResume的通知消息表示，
onWebViewResume可以由WebView可見的生命週期函數構成，用來處理與終端設備的作業系統中的原生UI控制項相關的生命週期。
在實施中，當終端設備處於解鎖或回前台等狀態時，全域初始化模組可以產生生命週期可見的通知消息(即onWebViewResume)，並可以將其發送給頁面管理模組NBComponentManager。NBComponentManager接收到
onWebViewResume的通知消息時，可以將
onWebViewResume發送給NBComponentViews，並回呼NBComponentViews將NBComponentViews的生命週期設置為可見狀態。
在步驟S822中，當接收到全域初始化模組發送的第二控制項被移除或目標頁面被銷毀的通知消息時，頁面管理模組銷毀頁面轉列模組的生命週期。
其中，在實際應用中，第二控制項被移除可以以onEmbedViewDetachedFromWebView表示，
onEmbedViewDetachedFromWebView可以表示終端設備的作業系統中的原生UI控制項被移除的生命週期函數。目標頁面被銷毀可以以onWebViewDestory表示，
onWebViewDestory可以表示WebView銷毀的生命週期函數。
在實施中，當目標頁面被銷毀時，全域初始化模組可以產生onEmbedViewDetachedFromWebView和
onWebViewDestory的通知消息，並可以將其發送給頁面管理模組NBComponentManager。NBComponentManager接收到onEmbedViewDetachedFromWebView和
onWebViewDestory的通知消息時，可以將
onEmbedViewDetachedFromWebView和onWebViewDestory發送給NBComponentViews，並回呼NBComponentViews將NBComponentViews的生命週期銷毀。
在步驟S824中，頁面管理模組呼叫頁面轉列模組。
在步驟S826中，根據頁面轉列模組的呼叫指示，在全域初始化模組檢測到第二控制項被移除或目標頁面被銷毀時，頁面轉列模組釋放並回收第二控制項。
本說明書實施例提供一種頁面處理方法，應用於目標頁面，該目標頁面基於超文件標示語言開發，透過獲取的目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項，執行該排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面，這樣，將終端設備的作業系統中原生使用者介面(即目標使用者介面)控制項作為目標頁面中顯示控制項的子顯示控制項添加到目標頁面(即基於超文件標示語言開發的頁面)中，而不是將終端設備的作業系統中原生使用者介面控制項簡單覆蓋在目標頁面上，從而達到了將目標使用者介面的控制項融合到目標頁面的效果，使得融合在目標頁面中的第二控制項可以隨著目標頁面進行縮放，提高了用戶體驗。
實施例五
以上為本說明書實施例提供的頁面處理方法，基於同樣的思路，本說明書實施例還提供一種頁面處理裝置，所述裝置中包括目標頁面，所述目標頁面基於超文件標示語言開發，如圖9所示。
該頁面處理裝置包括：資訊獲取模組901、排版指令產生模組902和處理模組903，其中：
資訊獲取模組901，用於獲取目標使用者介面中的第一控制項的類型，以及所述第一控制項在所述目標使用者介面中的排版資訊；
排版指令產生模組902，用於根據所述第一控制項的類型和所述排版資訊，產生所述類型對應的第二控制項在所述目標頁面中的排版指令集，所述第二控制項為預先儲存，且可融合在所述目標頁面中的控制項；
處理模組903，用於執行所述排版指令集中的排版指令，在所述目標頁面中對所述第二控制項進行排版處理和轉列處理，得到融合有所述第二控制項的目標頁面。
本說明書實施例中，所述資訊獲取模組901，用於呼叫預設的程式設計介面，獲取目標使用者介面中的第一控制項的類型，以及所述第一控制項在所述使用者介面中的排版資訊。
本說明書實施例中，所述裝置還包括：
指令接收模組，用於接收對所述目標頁面中的所述第二控制項的管理指令，所述管理指令包括刪除指令和狀態修改指令；
指令執行模組，用於根據所述管理指令，對所述目標頁面中的所述第二控制項執行相應的操作。
本說明書實施例提供一種頁面處理裝置，包括目標頁面，該目標頁面基於超文件標示語言開發，透過獲取的目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項，執行該排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面，這樣，將終端設備的作業系統中原生使用者介面(即目標使用者介面)控制項作為目標頁面中顯示控制項的子顯示控制項添加到目標頁面(即基於超文件標示語言開發的頁面)中，而不是將終端設備的作業系統中原生使用者介面控制項簡單覆蓋在目標頁面上，從而達到了將目標使用者介面的控制項融合到目標頁面的效果，使得融合在目標頁面中的第二控制項可以隨著目標頁面進行縮放，提高了用戶體驗。
實施例六
基於同樣的思路，本說明書實施例還提供一種頁面處理裝置中的頁面管理模組，所述頁面管理模組設置於目標頁面中，所述目標頁面基於超文件標示語言開發，所述目標頁面中還包括全域初始化模組，如圖10所示。
該頁面處理裝置包括：第一呼叫單元1001、指令集接收單元1002、解析單元1003和指令發送單元1004，其中：
第一呼叫單元1001，用於呼叫所述全域初始化模組，以獲取目標使用者介面中的第一控制項的類型，以及所述第一控制項在所述目標使用者介面中的排版資訊，並根據所述類型和所述排版資訊，產生所述類型對應的第二控制項在所述目標頁面中的排版指令集，所述第二控制項為預先儲存，且可融合在所述目標頁面中的控制項；
指令集接收單元1002，用於接收所述全域初始化模組發送的所述排版指令集；
解析單元1003，用於解析所述排版指令集中的排版指令，得到解析後的排版指令；
指令發送單元1004，用於創建頁面轉列模組，並將所述解析後的排版指令發送給所述頁面轉列模組，以使所述頁面轉列模組根據所述解析後的排版指令得到融合有所述第二控制項的目標頁面。
本說明書實施例中，所述第一呼叫單元1001，包括：
指令接收子單元，用於接收所述全域初始化模組發送的程式設計介面呼叫指令；
呼叫子單元，用於呼叫所述全域初始化模組。
本說明書實施例中，所述頁面管理模組還包括：
生命週期創建單元，用於創建所述頁面轉列模組的生命週期；
第一設置單元，用於當接收到所述全域初始化模組發送的所述生命週期不可見的通知消息時，將所述頁面轉列模組的生命週期設置為不可見狀態；
第二設置單元，用於當接收到所述全域初始化模組發送的所述生命週期恢復可見的通知消息時，將所述頁面轉列模組的生命週期設置為可見狀態。
本說明書實施例中，所述頁面管理模組還包括：
銷毀單元，用於當接收到所述全域初始化模組發送的所述第二控制項被移除或所述目標頁面被銷毀的通知消息時，銷毀所述頁面轉列模組的生命週期；
第二呼叫單元，用於呼叫所述頁面轉列模組釋放並回收所述第二控制項。
本說明書實施例提供一種頁面處理裝置中的頁面管理模組，設置於目標頁面，該目標頁面基於超文件標示語言開發，透過獲取的目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項，執行該排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面，這樣，將終端設備的作業系統中原生使用者介面(即目標使用者介面)控制項作為目標頁面中顯示控制項的子顯示控制項添加到目標頁面(即基於超文件標示語言開發的頁面)中，而不是將終端設備的作業系統中原生使用者介面控制項簡單覆蓋在目標頁面上，從而達到了將目標使用者介面的控制項融合到目標頁面的效果，使得融合在目標頁面中的第二控制項可以隨著目標頁面進行縮放，提高了用戶體驗。
實施例七
基於同樣的思路，本說明書實施例還提供一種頁面處理裝置中的全域初始化模組，所述全域初始化模組設置於目標頁面中，所述目標頁面基於超文件標示語言開發，所述目標頁面中還包括頁面管理模組，如圖11所示。
該頁面處理裝置包括：指令發送單元1101、資訊獲取單元1102和請求發送模組1103，其中：
指令發送單元1101，用於向所述頁面管理模組發送程式設計介面呼叫指令；
資訊獲取單元1102，用於根據所述頁面管理模組的呼叫指示，獲取目標使用者介面中的第一控制項的類型，以及所述第一控制項在所述目標使用者介面中的排版資訊，並根據所述類型和所述排版資訊，產生所述類型對應的第二控制項在所述目標頁面中的排版指令集，所述第二控制項為預先儲存，且可融合在所述目標頁面中的控制項；
指令集發送單元1103，用於向所述頁面管理模組發送所述排版指令集。
本說明書實施例提供一種頁面處理裝置中的全域初始化模組，設置於目標頁面，該目標頁面基於超文件標示語言開發，透過獲取的目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項，執行該排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面，這樣，將終端設備的作業系統中原生使用者介面(即目標使用者介面)控制項作為目標頁面中顯示控制項的子顯示控制項添加到目標頁面(即基於超文件標示語言開發的頁面)中，而不是將終端設備的作業系統中原生使用者介面控制項簡單覆蓋在目標頁面上，從而達到了將目標使用者介面的控制項融合到目標頁面的效果，使得融合在目標頁面中的第二控制項可以隨著目標頁面進行縮放，提高了使用者體驗。
實施例八
基於同樣的思路，本說明書實施例還提供一種頁面處理裝置中的頁面轉列模組，所述頁面轉列模組設置於目標頁面中，所述目標頁面基於超文件標示語言開發，所述目標頁面中還包括頁面管理模組和全域初始化模組，如圖12所示。
該頁面處理裝置包括：指令接收單元1201和指令執行單元1202，其中：
指令接收單元1201，用於接收所述頁面管理模組發送的排版指令，所述排版指令是所述頁面管理模組對所述全域初始化模組產生並發送的所述目標頁面的排版指令集進行解析後得到；
指令執行單元1202，用於執行所述排版指令，從預先儲存的控制項庫中獲取所述排版指令對應的第二控制項，在所述目標頁面中對所述第二控制項進行排版處理和轉列處理，得到融合有所述第二控制項的目標頁面，所述第二控制項是目標使用者介面中的第一控制項的類型對應的控制項。
本說明書實施例中，所述頁面轉列模組還包括：
控制項釋放單元，用於根據所述頁面轉列模組的呼叫指示，在所述全域初始化模組檢測到所述第二控制項被移除或所述目標頁面被銷毀時，釋放並回收所述第二控制項。
本說明書實施例提供一種頁面處理裝置中的頁面轉列模組，設置於目標頁面，該目標頁面基於超文件標示語言開發，透過獲取的目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項，執行該排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面，這樣，將終端設備的作業系統中原生使用者介面(即目標使用者介面)控制項作為目標頁面中顯示控制項的子顯示控制項添加到目標頁面(即基於超文件標示語言開發的頁面)中，而不是將終端設備的作業系統中原生使用者介面控制項簡單覆蓋在目標頁面上，從而達到了將目標使用者介面的控制項融合到目標頁面的效果，使得融合在目標頁面中的第二控制項可以隨著目標頁面進行縮放，提高了用戶體驗。
實施例九
基於同樣的思路，本說明書實施例還提供一種頁面處理設備，如圖13所示。
所述頁面處理設備可以為上述實施例提供的終端設備。
頁面處理設備可因配置或性能不同而產生比較大的差異，可以包括一個或一個以上的處理器1301和記憶體1302，記憶體1302中可以儲存有一個或一個以上儲存應用程式或資料。其中，記憶體1302可以是短暫儲存或持久儲存。儲存在記憶體1302的應用程式可以包括一個或一個以上模組(圖示未示出)，每個模組可以包括對頁面處理設備中的一系列電腦可執行指令。更進一步地，處理器1301可以設置為與記憶體1302通信，在頁面處理設備上執行記憶體1302中的一系列電腦可執行指令。頁面處理設備還可以包括一個或一個以上電源1303，一個或一個以上有線或無線網路介面1304，一個或一個以上輸入輸出介面1305，一個或一個以上鍵盤1306。
具體在本實施例中，頁面處理設備包括有記憶體，以及一個或一個以上的程式，其中一個或者一個以上程式儲存於記憶體中，且一個或者一個以上程式可以包括一個或一個以上模組，且每個模組可以包括對頁面處理設備中的一系列電腦可執行指令，且經配置以由一個或者一個以上處理器執行該一個或者一個以上套裝程式含用於進行以下電腦可執行指令：
獲取目標使用者介面中的第一控制項的類型，以及所述第一控制項在所述目標使用者介面中的排版資訊；
根據所述第一控制項的類型和所述排版資訊，產生所述類型對應的第二控制項在所述目標頁面中的排版指令集，所述第二控制項為預先儲存，且可融合在目標頁面中的控制項，目標頁面，所述目標頁面基於超文件標示語言開發；
執行所述排版指令集中的排版指令，在所述目標頁面中對所述第二控制項進行排版處理和轉列處理，得到融合有所述第二控制項的目標頁面。
可選地，所述獲取目標使用者介面中的第一控制項的類型，以及所述第一控制項在所述使用者介面中的排版資訊，包括：
呼叫預設的程式設計介面，獲取目標使用者介面中的第一控制項的類型，以及所述第一控制項在所述使用者介面中的排版資訊。
可選地，還包括：
接收對所述目標頁面中的所述第二控制項的管理指令，所述管理指令包括刪除指令和狀態修改指令；
根據所述管理指令，對所述目標頁面中的所述第二控制項執行相應的操作。
本說明書實施例提供一種頁面處理設備，包括目標頁面，該目標頁面基於超文件標示語言開發，透過獲取的目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項，執行該排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面，這樣，將終端設備的作業系統中原生使用者介面(即目標使用者介面)控制項作為目標頁面中顯示控制項的子顯示控制項添加到目標頁面(即基於超文件標示語言開發的頁面)中，而不是將終端設備的作業系統中原生使用者介面控制項簡單覆蓋在目標頁面上，從而達到了將目標使用者介面的控制項融合到目標頁面的效果，使得融合在目標頁面中的第二控制項可以隨著目標頁面進行縮放，提高了用戶體驗。
實施例十
基於同樣的思路，本說明書實施例還提供一種頁面處理設備，如圖14所示。
所述頁面處理設備可以為上述實施例提供的終端設備。
頁面處理設備可因配置或性能不同而產生比較大的差異，可以包括一個或一個以上的處理器1401和記憶體1402，記憶體1402中可以儲存有一個或一個以上儲存應用程式或資料。其中，記憶體1402可以是短暫儲存或持久儲存。儲存在記憶體1402的應用程式可以包括一個或一個以上模組(圖示未示出)，每個模組可以包括對頁面處理設備中的一系列電腦可執行指令。更進一步地，處理器1401可以設置為與記憶體1402通信，在頁面處理設備上執行記憶體1402中的一系列電腦可執行指令。頁面處理設備還可以包括一個或一個以上電源1403，一個或一個以上有線或無線網路介面1404，一個或一個以上輸入輸出介面1405，一個或一個以上鍵盤1406。
具體在本實施例中，頁面處理設備包括有記憶體，以及一個或一個以上的程式，其中一個或者一個以上程式儲存於記憶體中，且一個或者一個以上程式可以包括一個或一個以上模組，且每個模組可以包括對頁面處理設備中的一系列電腦可執行指令，且經配置以由一個或者一個以上處理器執行該一個或者一個以上套裝程式含用於進行以下電腦可執行指令：
應用於目標頁面，所述目標頁面基於超文件標示語言開發，所述目標頁面中包括全域初始化模組，包括：
呼叫所述全域初始化模組，以獲取目標使用者介面中的第一控制項的類型，以及所述第一控制項在所述目標使用者介面中的排版資訊，並根據所述類型和所述排版資訊，產生所述類型對應的第二控制項在所述目標頁面中的排版指令集，所述第二控制項為預先儲存，且可融合在所述目標頁面中的控制項；
接收所述全域初始化模組發送的所述排版指令集；
解析所述排版指令集中的排版指令，得到解析後的排版指令；
創建頁面轉列模組，並將所述解析後的排版指令發送給所述頁面轉列模組，以使所述頁面轉列模組根據所述解析後的排版指令得到融合有所述第二控制項的目標頁面。
可選地，所述呼叫所述全域初始化模組，包括：
接收所述全域初始化模組發送的程式設計介面呼叫指令；
呼叫所述全域初始化模組。
可選地，所述創建頁面轉列模組之後，所述方法還包括：
創建所述頁面轉列模組的生命週期；
當接收到所述全域初始化模組發送的所述生命週期不可見的通知消息時，將所述頁面轉列模組的生命週期設置為不可見狀態；
當接收到所述全域初始化模組發送的所述生命週期恢復可見的通知消息時，將所述頁面轉列模組的生命週期設置為可見狀態。
可選地，所述方法還包括：
當接收到所述全域初始化模組發送的所述第二控制項被移除或所述目標頁面被銷毀的通知消息時，銷毀所述頁面轉列模組的生命週期；
呼叫所述頁面轉列模組釋放並回收所述第二控制項。
具體在本實施例中，頁面處理設備包括有記憶體，以及一個或一個以上的程式，其中一個或者一個以上程式儲存於記憶體中，且一個或者一個以上程式可以包括一個或一個以上模組，且每個模組可以包括對頁面處理設備中的一系列電腦可執行指令，且經配置以由一個或者一個以上處理器執行該一個或者一個以上套裝程式含用於進行以下電腦可執行指令：
應用於目標頁面，所述目標頁面基於超文件標示語言開發，所述目標頁面中包括頁面管理模組，包括：
向所述頁面管理模組發送程式設計介面呼叫指令；
根據所述頁面管理模組的呼叫指示，獲取目標使用者介面中的第一控制項的類型，以及所述第一控制項在所述目標使用者介面中的排版資訊，並根據所述類型和所述排版資訊，產生所述類型對應的第二控制項在所述目標頁面中的排版指令集，所述第二控制項為預先儲存，且可融合在所述目標頁面中的控制項；
向所述頁面管理模組發送所述排版指令集。
具體在本實施例中，頁面處理設備包括有記憶體，以及一個或一個以上的程式，其中一個或者一個以上程式儲存於記憶體中，且一個或者一個以上程式可以包括一個或一個以上模組，且每個模組可以包括對頁面處理設備中的一系列電腦可執行指令，且經配置以由一個或者一個以上處理器執行該一個或者一個以上套裝程式含用於進行以下電腦可執行指令：
應用於目標頁面，所述目標頁面基於超文件標示語言開發，所述目標頁面中包括頁面管理模組和全域初始化模組，包括：
接收所述頁面管理模組發送的排版指令，所述排版指令是所述頁面管理模組對所述全域初始化模組產生並發送的所述目標頁面的排版指令集進行解析後得到；
執行所述排版指令，從預先儲存的控制項庫中獲取所述排版指令對應的第二控制項，在所述目標頁面中對所述第二控制項進行排版處理和轉列處理，得到融合有所述第二控制項的目標頁面，所述第二控制項是目標使用者介面中的第一控制項的類型對應的控制項。
可選地，所述方法還包括：
根據所述頁面轉列模組的呼叫指示，在所述全域初始化模組檢測到所述第二控制項被移除或所述目標頁面被銷毀時，釋放並回收所述第二控制項。
本說明書實施例提供一種頁面處理設備，包括目標頁面，該目標頁面基於超文件標示語言開發，透過獲取的目標使用者介面中的第一控制項的類型，以及第一控制項在目標使用者介面中的排版資訊，產生該類型對應的第二控制項在目標頁面中的排版指令集，第二控制項為預先儲存，且可融合在目標頁面中的控制項，執行該排版指令集中的排版指令，在目標頁面中對第二控制項進行排版處理和轉列處理，得到融合有第二控制項的目標頁面，這樣，將終端設備的作業系統中原生使用者介面(即目標使用者介面)控制項作為目標頁面中顯示控制項的子顯示控制項添加到目標頁面(即基於超文件標示語言開發的頁面)中，而不是將終端設備的作業系統中原生使用者介面控制項簡單覆蓋在目標頁面上，從而達到了將目標使用者介面的控制項融合到目標頁面的效果，使得融合在目標頁面中的第二控制項可以隨著目標頁面進行縮放，提高了用戶體驗。
上述對本說明書特定實施例進行了描述。其它實施例在所附申請專利範圍的範圍內。在一些情況下，在申請專利範圍中記載的動作或步驟可以按照不同於實施例中的順序來執行並且仍然可以實現期望的結果。另外，在圖式中描繪的過程不一定要求示出的特定順序或者連續順序才能實現期望的結果。在某些實施方式中，多工處理和並行處理也是可以的或者可能是有利的。
在20世紀90年代，對於一個技術的改進可以很明顯地區分是硬體上的改進(例如，對二極體、電晶體、開關等電路結構的改進)還是軟體上的改進(對於方法流程的改進)。然而，隨著技術的發展，當今的很多方法流程的改進已經可以視為硬體電路結構的直接改進。設計人員幾乎都透過將改進的方法流程程式設計到硬體電路中來得到相應的硬體電路結構。因此，不能說一個方法流程的改進就不能用硬體實體模組來實現。例如，可程式設計邏輯器件(Programmable Logic Device，PLD)(例如現場可程式設計閘陣列(Field Programmable Gate Array，FPGA))就是這樣一種積體電路，其邏輯功能由使用者對器件程式設計來確定。由設計人員自行程式設計來把一個數位系統“整合”在一片PLD上，而不需要請晶片製造廠商來設計和製作專用的積體電路晶片。而且，如今，取代手工地製作積體電路晶片，這種程式設計也多半改用“邏輯編譯器(logic compiler)”軟體來實現，它與程式開發撰寫時所用的軟體編譯器相類似，而要編譯之前的原始代碼也得用特定的程式設計語言來撰寫，此稱之為硬體描述語言(Hardware Description Language，HDL)，而HDL也並非僅有一種，而是有許多種，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description
Language)、Confluence、CUPL(Cornell University
Programming Language)、HDCal、JHDL(Java Hardware
Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)與Verilog。本領域技術人員也應該清楚，只需要將方法流程用上述幾種硬體描述語言稍作邏輯程式設計並程式設計到積體電路中，就可以很容易得到實現該邏輯方法流程的硬體電路。
控制器可以按任何適當的方式實現，例如，控制器可以採取例如微處理器或處理器以及儲存可由該(微)處理器執行的電腦可讀程式碼(例如軟體或韌體)的電腦可讀媒體、邏輯閘、開關、專用積體電路(Application Specific Integrated Circuit，ASIC)、可程式設計邏輯控制器和嵌入微控制器的形式，控制器的例子包括但不限於以下微控制器：ARC 625D、Atmel AT91SAM、Microchip
PIC18F26K20 以及Silicone Labs C8051F320，記憶體控制器還可以被實現為記憶體的控制邏輯的一部分。本領域技術人員也知道，除了以純電腦可讀程式碼方式實現控制器以外，完全可以透過將方法步驟進行邏輯程式設計來使得控制器以邏輯閘、開關、專用積體電路、可程式設計邏輯控制器和嵌入微控制器等的形式來實現相同功能。因此這種控制器可以被認為是一種硬體部件，而對其內包括的用於實現各種功能的裝置也可以視為硬體部件內的結構。或者甚至，可以將用於實現各種功能的裝置視為既可以是實現方法的軟體模組又可以是硬體部件內的結構。
上述實施例闡明的系統、裝置、模組或單元，具體可以由電腦晶片或實體實現，或者由具有某種功能的產品來實現。一種典型的實現設備為電腦。具體的，電腦例如可以為個人電腦、膝上型電腦、行動電話、相機電話、智慧型電話、個人數位助理、媒體播放機、導航設備、電子郵件設備、遊戲控制台、平板電腦、可穿戴設備或者這些設備中的任何設備的組合。
為了描述的方便，描述以上裝置時以功能分為各種單元分別描述。當然，在實施本說明書一個或多個實施例時可以把各單元的功能在同一個或多個軟體和/或硬體中實現。
本領域內的技術人員應明白，本說明書的實施例可提供為方法、系統、或電腦程式產品。因此，本說明書一個或多個實施例可採用完全硬體實施例、完全軟體實施例、或結合軟體和硬體方面的實施例的形式。而且，本說明書一個或多個實施例可採用在一個或多個其中包含有電腦可用程式碼的電腦可用儲存媒體(包括但不限於磁碟記憶體、CD-ROM、光學記憶體等)上實施的電腦程式產品的形式。
本說明書的實施例是參照根據本說明書實施例的方法、設備(系統)、和電腦程式產品的流程圖和/或方塊圖來描述的。應理解可由電腦程式指令實現流程圖和/或方塊圖中的每一流程和/或方塊、以及流程圖和/或方塊圖中的流程和/或方塊的結合。可提供這些電腦程式指令到通用電腦、專用電腦、嵌入式處理機或其他可程式設計資料處理設備的處理器以產生一個機器，使得透過電腦或其他可程式設計資料處理設備的處理器執行的指令產生用於實現在流程圖一個流程或多個流程和/或方塊圖一個方塊或多個方塊中指定的功能的裝置。
這些電腦程式指令也可儲存在能引導電腦或其他可程式設計資料處理設備以特定方式工作的電腦可讀記憶體中，使得儲存在該電腦可讀記憶體中的指令產生包括指令裝置的製造品，該指令裝置實現在流程圖一個流程或多個流程和/或方塊圖一個方塊或多個方塊中指定的功能。
這些電腦程式指令也可裝載到電腦或其他可程式設計資料處理設備上，使得在電腦或其他可程式設計設備上執行一系列操作步驟以產生電腦實現的處理，從而在電腦或其他可程式設計設備上執行的指令提供用於實現在流程圖一個流程或多個流程和/或方塊圖一個方塊或多個方塊中指定的功能的步驟。
在一個典型的配置中，計算設備包括一個或多個處理器(CPU)、輸入/輸出介面、網路介面和記憶體。
記憶體可能包括電腦可讀媒體中的非永久性記憶體，隨機存取記憶體(RAM)和/或非易失性記憶體等形式，如唯讀記憶體(ROM)或快閃記憶體(flash RAM)。記憶體是電腦可讀媒體的示例。
電腦可讀媒體包括永久性和非永久性、可移動和非可移動媒體可以由任何方法或技術來實現資訊儲存。資訊可以是電腦可讀指令、資料結構、程式的模組或其他資料。電腦的儲存媒體的例子包括，但不限於相變記憶體(PRAM)、靜態隨機存取記憶體(SRAM)、動態隨機存取記憶體(DRAM)、其他類型的隨機存取記憶體(RAM)、唯讀記憶體(ROM)、電可擦除可程式設計唯讀記憶體(EEPROM)、快閃記憶體或其他記憶體技術、唯讀光碟唯讀記憶體(CD-ROM)、數位多功能光碟(DVD)或其他光學儲存、磁盒式磁帶，磁帶磁片儲存或其他磁性存放裝置或任何其他非傳輸媒體，可用於儲存可以被計算設備接達的資訊。按照本文中的界定，電腦可讀媒體不包括暫存電腦可讀媒體(transitory media)，如調變的資料信號和載波。
還需要說明的是，術語“包括”、“包含”或者其任何其他變體意在涵蓋非排他性的包含，從而使得包括一系列要素的過程、方法、商品或者設備不僅包括那些要素，而且還包括沒有明確列出的其他要素，或者是還包括為這種過程、方法、商品或者設備所固有的要素。在沒有更多限制的情況下，由語句“包括一個……”限定的要素，並不排除在包括所述要素的過程、方法、商品或者設備中還存在另外的相同要素。
本領域技術人員應明白，本說明書的實施例可提供為方法、系統或電腦程式產品。因此，本說明書一個或多個實施例可採用完全硬體實施例、完全軟體實施例或結合軟體和硬體方面的實施例的形式。而且，本說明書一個或多個實施例可採用在一個或多個其中包含有電腦可用程式碼的電腦可用儲存媒體(包括但不限於磁碟記憶體、CD-ROM、光學記憶體等)上實施的電腦程式產品的形式。
本說明書一個或多個實施例可以在由電腦執行的電腦可執行指令的一般上下文中描述，例如程式模組。一般地，程式模組包括執行特定任務或實現特定抽象資料類型的常式、程式、物件、元件、資料結構等等。也可以在分散式運算環境中實踐本說明書一個或多個實施例，在這些分散式運算環境中，由透過通信網路而被連接的遠端處理設備來執行任務。在分散式運算環境中，程式模組可以位於包括存放裝置在內的本地和遠端電腦儲存媒體中。
本說明書中的各個實施例均採用遞進的方式描述，各個實施例之間相同相似的部分互相參見即可，每個實施例重點說明的都是與其他實施例的不同之處。尤其，對於系統實施例而言，由於其基本相似於方法實施例，所以描述的比較簡單，相關之處參見方法實施例的部分說明即可。
以上所述僅為本說明書的實施例而已，並不用於限制本說明書。對於本領域技術人員來說，本說明書可以有各種更改和變化。凡在本說明書的精神和原理之內所作的任何修改、等同替換、改進等，均應包含在本說明書的申請專利範圍之內。Embodiments of this specification provide a page processing method, device, and equipment.
In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be described clearly and completely in conjunction with the drawings in the embodiments of this specification. Obviously, the described The embodiments are only a part of the embodiments of this specification, but not all the embodiments. Based on the embodiments in this specification, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the scope of protection of this specification.
Example one
As shown in FIG. 1, an embodiment of the present specification provides a page processing method. The method may be executed by a terminal device or a server, where the terminal device may be a device such as a personal computer, or may be mobile such as a mobile phone or a tablet A terminal device, which may be a terminal device used by a user. The server can be an independent server or a server cluster composed of multiple servers, and the server can be a back-end server for a business or a website (such as an online shopping website) Or payment application, etc.) background server, etc. This method can be used to generate a page corresponding to the control item in the native user interface in the operating system of the terminal device (that is, the target page mentioned in this embodiment), and the page is based on the hypertext markup language (that is, Hyper Text Markup Language, HTML) development, which can include HTML 2. 0, HTML 3. 2. HTML 4. 0 and HTML 5 etc. In order to simplify the page processing process and the page processing efficiency, in this embodiment, the execution body is taken as an example of the terminal device as an example for description. For the case of the server, it can be processed according to the following related content, which will not be repeated here. The method may specifically include the following steps:
In step S102, the type of the first control item in the target user interface and the layout information of the first control item in the target user interface are obtained.
The target user interface may be a native user interface (UI, User Interface) in the operating system of the terminal device. The operating system of the terminal device may include an Android operating system and an iOS operating system. The first control item may be any control item in the user interface of the operating system, such as a button, an input box control item, a search box control item, a calendar control item, or an upload image control item. The typesetting information may be information indicating the size and position of the control item on the page, and the typesetting information may help the terminal device to reorder and display the page. The type of control item can be set according to the actual situation, for example, it can be classified according to the role and use of the control item, such as button type, input box type or upload picture type, etc. In practical applications, it may not be limited to the above classification, but can also be based on The above classification results are further classified. For example, the key types can also be classified into round key types, rectangular key types, etc., or the types of control items can be directly classified into round key types, rectangular key types, input frame types, or uploading pictures Classes, etc., this embodiment of the specification does not limit this.
In the implementation, the hyper-file markup language is an application under the standard universal markup language, and is also a specification, a standard, which marks various parts of the webpage to be displayed through markup symbols. The web page file itself is a text file. By adding tags to the text file, you can instruct the browser how to display the content (such as how to process the text, how to arrange the screen, how to display the picture, etc.). The browser can read the webpage file in the order of the content in the webpage file, and then interpret and display its marked content according to the tag. Among them, for different browsers, the same tag may have different interpretations, and thus may have different display effects. The creation of hyper-document markup language documents is not very complicated, but it is powerful and supports the insertion of files in different data formats. Hyperfile markup language can have the main features of simplicity, extensibility, operating platform independence and versatility. Since the upgrade of hyperfile markup language version usually adopts super collection method, the hyperfile markup language can be more flexible and convenient, and Hyper-File Markup Language can be used on a wide range of operating platforms (that is, platforms with multiple operating systems, such as Windows operating system platform or Mac OS platform, etc.). Moreover, Hyper-File Markup Language allows web page creators to create a combination of text and images. Complex pages can be browsed no matter what type of terminal device or browser the user is using.
A page developed based on the hyperfile markup language (ie, the target page) may include more complicated elements, such as a map, etc. Taking the target page developed based on the hyperfile markup language as an example, if a map is displayed through the target page, the map Usually, the user is required to zoom. During the zooming process, the user may have difficulty zooming the map by finger touch, the user's experience of touch operation is poor, and the efficiency of the target page is low.
The user interface in the terminal device is usually composed of one or more control items. Through different control items, multiple different user interfaces can be constructed. Different control items can achieve different functions, for example, the user The interface can include a map control item. The user can zoom in or zoom out the map in the map control item at will through the map control item and the method of finger touch. Obviously, the control item in the user interface in the terminal device can express For a better touch operation experience, the user interface has a relatively high conversion efficiency.
If the control items in the user interface of the terminal device can be displayed on the target page, the touch operation experience of the target page and the efficiency of the target page can be improved. Generally, the operating system of the terminal device can be The control items in the native user interface (that is, the target user interface) are overwritten on the above target page. What needs to be explained is that in actual applications, the control items in the target user interface are overwritten on the above target page. , Can be the control items in the target user interface to cover the Webview control items on the target page. However, the target page obtained through the above coverage method needs to limit the target page from being able to zoom, because the control items in the target user interface covered in the target page cannot be zoomed with the zoom of the target page, but only Keep the original style of the control item unchanged, which will cause trouble to the user and the user experience is poor. To this end, the embodiments of the present specification provide a target page that can include the control items in the user interface, and the control items therein can also be scaled as the target page is scaled, which may specifically include the following:
As shown in FIG. 2A, when it is necessary to use one or more native user interfaces (that is, target user interfaces) in the operating system of the terminal device based on the hyper-file markup language (the hyper-file markup language in this embodiment can be HTML 5 is used as an example.) When the developed target page is displayed, the target user interface can be obtained through the preset interface. The target user interface can be analyzed and calculated to determine the control items included in the target user interface (that is, the first A control item), at the same time, you can record the size and position of each first control item in the target user interface, where the position can be expressed in the form of coordinates, or a certain position can be used as the center point To determine the relative position between the first control item and the center point. The size and size of each first control item recorded and its position in the target user interface can be used to generate the layout information of the first control item in the target user interface. In addition, each first control item in the target user interface can also be analyzed to determine the type of each first control item, for example, including three first control items, one of which is a button, Another first control item is the search box control item, and the third first control item is the upload image control item, then the types to which the first control item belongs include the key class, the search box class, and the uploaded image class. Correspondingly, for the above Press the button to generate the layout information of a button. For the search box control item, you can generate the layout information of the search box control item. For the upload image control item, you can generate the layout information of the uploaded image control item.
In step S104, according to the type of the first control item and the typesetting information, a typesetting instruction set of the second control item corresponding to the type in the target page is generated. The second control item is pre-stored and can be fused on the target page Controls in.
The second control item may be a control item pre-stored in the browser where the target page is located, or a pre-stored control item in the database corresponding to the target page or the database corresponding to the above-mentioned browser, the second control item It can be the development of the target user interface or the creation of the technical staff. Since the creation of the second control item fully considers the environment of the target page developed based on the hyperfile markup language, that is, the second control item needs to be used in the target page, you can Zoom in and out as the target page zooms, and the second control item may be of the same type as the first control item in the target user interface, and the two correspond to each other. For example, the first control item is a button, the second control item It should also be a button, and the second control item can be identical in appearance and function with the first control item. The typesetting instruction set may be a set composed of one or more typesetting instructions, each typesetting instruction may be independent of each other, or may be related to each other. If multiple typesetting instructions are related to each other, the typesetting instructions may also include a storage relationship Identification of typesetting instructions, etc.
In the implementation, the browser where the target page is located, or the database corresponding to the target page, or the database corresponding to the above browser, may be pre-stored with the control items in the native user interface of the operating system of the terminal device The corresponding control item. After the terminal device determines the type of the first control item through the process of step S102, it can search for the control item corresponding to the determined type among the previously stored control items through the determined type. As the second control item corresponding to the first control item, and then, from the typesetting information obtained through the process of step S102 above, the typesetting information of the first control item in the target user interface can be found, After finding, the size and size of the first control item and the position in the target user interface in the found typesetting information can be extracted.
An empty target page can be created, based on the intrinsic attributes of the target page, and the size of the corresponding second control item can be determined according to the size of the first control item, and also based on the intrinsic attributes of the target page, and According to the position of the first control item in the target user interface, the position of the corresponding second control item in the target page is determined. The layout information of the second control item in the target page can be generated through the inherent properties of the target page, the size of the second control item, and the position of the second control item in the target page, and can be generated based on the generated layout information The second control item has one or more typesetting instructions on the target page to obtain the typesetting instruction set of the second control item on the target page.
It should be noted that multiple first control items can be included, and corresponding second control items should also be multiple. Moreover, the number of first control items is equal to the number of second control items. In the case of the item, the typesetting instruction or typesetting instruction set of each second control item in the target page can be separately obtained through the above-mentioned method.
In step S106, the typesetting instruction in the above typesetting instruction set is executed, and typesetting processing and reordering processing are performed on the second control item in the target page to obtain a target page fused with the second control item.
Among them, the typesetting process can be in a limited page space, the page composition elements (such as text, pictures, line frame and color blocks, etc.), according to the needs of specific content, combined arrangement, and the use of modeling elements and form principles, The processing of arranging elements on the page. The inversion process may be a process of calculating the page to be presented to obtain the display effect of the page.
In implementation, after obtaining the typesetting instruction set of the second control item in the target page through the processing in step S104, the terminal device may separately analyze the typesetting instruction in the typesetting instruction set to convert the data of the typesetting instruction in the typesetting instruction set Data that can be recognized by the display component or display module, and then the display component or display module of the terminal device can execute the parsed typesetting instruction, and the relevant information of the second control item can be determined through the parsed typesetting instruction, and can be selected from The second control item is extracted from the pre-stored control items. As shown in FIG. 2B, the size and size of the second control item and the position of the second control item in the target page can also be determined through the parsed typesetting instructions, and then, according to the determined size and size in the target page Position, performing typesetting processing on the second control item in the target page to obtain the typesetting result of the second control item in the target page. The above process can be executed for each second control item to obtain the typesetting result of the other second control items in the target page, and the typesetting result of each second control item in the target page can be synthesized to obtain the total of the target page For the typesetting result, finally, the target page can be transposed based on the overall typesetting result of the target page, so that the target page of the overall typesetting result can be presented, thereby obtaining the target page fused with the second control item.
Based on the above processing, since the second control item can be integrated into the target page (instead of being overlaid on the target page as in the related art), the second control item can be scaled as the target page is scaled, and the second The control item corresponds to the first control item in the target user interface, and the layout of the second control item in the target page also corresponds to the layout of the first control item in the target user interface. Generate a target page fused with the second control item and the target user interface containing the first control item, the presentation or display results are the same or similar (for example, the appearance of the two pages are the same or similar), so as to give the user a way to target The feeling that the user interface (or the control items therein) is transferred to the target page, and the control items in the target page can also be zoomed as the target page zooms, which improves the user experience.
An embodiment of the present specification provides a page processing method, which is applied to a target page, which is developed based on a hyper-file markup language, by acquiring the type of the first control item in the target user interface, and the first control item in the target user The typesetting information in the interface generates the typesetting instruction set of the second control item corresponding to the type in the target page. The second control item is a control item pre-stored and can be fused in the target page to execute the typesetting in the typesetting instruction set Instruction to perform typesetting and translation processing on the second control item in the target page to obtain the target page fused with the second control item. In this way, the native user interface (ie, target user interface) in the operating system of the terminal device is obtained The control item is added to the target page (that is, a page developed based on the hyperfile markup language) as a sub-display control item of the display control item in the target page, instead of simply covering the native user interface control item in the operating system of the terminal device on the target On the page, the effect of merging the control items of the target user interface to the target page is achieved, so that the second control item fused in the target page can be zoomed with the target page, which improves the user experience.
Example 2
As shown in FIG. 3, an embodiment of the present specification provides a page processing method. The method can be executed by a terminal device or a server, where the terminal device can be a device such as a personal computer, or can be mobile such as a mobile phone or a tablet A terminal device, which may be a terminal device used by a user. The server can be an independent server or a server cluster composed of multiple servers, and the server can be a back-end server for a business or a website (such as an online shopping website) Or payment application, etc.) background server, etc. This method can be used to generate a page corresponding to the control item in the native user interface in the operating system of the terminal device (that is, the target page mentioned in this embodiment), and the page is based on the hypertext markup language (that is, Hyper Text Markup Language, HTML) development, which can include HTML 2. 0, HTML 3. 2. HTML 4. 0 and HTML 5 etc. In order to simplify the page processing process and the page processing efficiency, in this embodiment, the execution body is taken as an example of the terminal device as an example for description. For the case of the server, it can be processed according to the following related content, which will not be repeated here. The method may specifically include the following steps:
In step S302, the default programming interface is called to obtain the type of the first control item in the target user interface and the layout information of the first control item in the user interface.
Among them, the programming interface can be composed of one or more pre-defined functions, the purpose is to provide applications and developers (or technical staff) based on a software or hardware to access a set of routines without the need for Access to the original code or understand the details of the internal working mechanism, etc., can be specifically JSAPI (JavaScript Application Programming Interface, Java description language application programming development interface).
In the implementation, when one or more native user interfaces (ie, target user interfaces) in the operating system of the terminal device need to be used based on the hypertext markup language (the hypertext markup language in this embodiment may be HTML 5 For example) When the developed target page is displayed, you can call the default programming interface (such as JSAPI, etc.) to obtain the target user interface, and can analyze and calculate the target user interface to determine the target user interface The control items contained in (ie, the first control item), at the same time, you can record the size and position of each first control item in the target user interface. The size and size of each first control item recorded and its position in the target user interface can be used to generate the layout information of the first control item in the target user interface. In addition, each first control item in the target user interface may be analyzed to determine the type to which each first control item belongs.
In step S304, according to the type of the first control item and the typesetting information, a typesetting instruction set of the second control item corresponding to the type on the target page is generated. The second control item is pre-stored and can be fused on the target page Controls in.
The content of the step S304 is the same as the content of the step S104 in the first embodiment. For the specific processing procedure of the step S304, reference may be made to the relevant content of the step S104 in the first embodiment, and details are not described herein.
In step S306, the typesetting instruction in the above typesetting instruction set is executed, and typesetting processing and reordering processing are performed on the second control item in the target page to obtain a target page fused with the second control item.
The content of the step S306 is the same as the content of the step S106 in the first embodiment. For the specific processing procedure of the step S306, reference may be made to the relevant content of the step S106 in the first embodiment, and details are not described herein.
In addition, after obtaining the target page fused with the second control item through the above method, the second control item in the target page can also be managed to obtain the processed target page. For details, refer to the processing in step S308 and step S310 described below .
In step S308, a management instruction for the second control item in the target page is received, and the management instruction may include a deletion instruction and a state modification instruction.
The state modification instruction may be to modify the second control item from one state to another state, for example, to modify the second control item from an untriggered state to a triggered state, and so on.
In implementation, when one or more second control items in the target page need to be deleted, the second control item management button provided in the browser where the target page is located or provided in the target page can be triggered. For the deletion instruction of the one or more second control items in the target page, the terminal device may receive the deletion instruction for the one or more second control items in the target page.
In addition, when the state of one or more second control items in the target page needs to be modified, the second control item management button provided in the browser where the target page is located or provided in the target page can be triggered. Based on the above information, the current state information of the second control item and the modified state information can generate a state modification instruction for the one or more second control items in the target page, and the terminal device can receive the Or multiple state modification instructions of the second control item.
In step S310, according to the above management instruction, a corresponding operation is performed on the second control item in the target page.
In implementation, when receiving the delete instruction of the one or more second control items in the target page, the identifier of the one or more second control items that need to be deleted can be obtained, and from this can be removed from the target page When the corresponding one or more second control items are found, the one or more second control items can be deleted from the target page.
When the state modification instruction for the one or more second control items in the target page is received, the identifier of the one or more second control items that need to be modified in state can be obtained, and thus can be found from the target page To the corresponding one or more second control items, the one or more second control items can be modified from the state corresponding to the current state information to the state corresponding to the modified state information.
An embodiment of the present specification provides a page processing method, which is applied to a target page, which is developed based on a hyper-file markup language, by acquiring the type of the first control item in the target user interface, and the first control item in the target user The typesetting information in the interface generates the typesetting instruction set of the second control item corresponding to the type in the target page. The second control item is a control item pre-stored and can be fused in the target page to execute the typesetting in the typesetting instruction set Instruction to perform typesetting and translation processing on the second control item in the target page to obtain the target page fused with the second control item. In this way, the native user interface (ie, target user interface) in the operating system of the terminal device is obtained The control item is added to the target page (that is, a page developed based on the hyperfile markup language) as a sub-display control item of the display control item in the target page, instead of simply covering the native user interface control item in the operating system of the terminal device on the target On the page, the effect of merging the control items of the target user interface to the target page is achieved, so that the second control item fused in the target page can be zoomed with the target page, which improves the user experience.
The first embodiment and the second embodiment are described in detail by taking the terminal device (or the browser installed in the terminal device, or the target page in the browser) as the execution subject, wherein the target page needs to obtain the target user interface The related information of the first control item in the page also needs to process the related information obtained above, and display the target page in turn. In actual applications, the target page can also be used according to its different functions. It is divided into different modules for execution. The following third and fourth embodiments describe the above target page as a page management module, a global initialization module and a page reversal module. For details, please refer to the following content. The management module can be represented by NBComponentManager, the global initialization module can be represented by NBComponentJSLoader, the page reversing module can be represented by NBComponentViews, the target page can be represented by Webview, and the webview can be carried and displayed in the operating system of the terminal device based on the hyperfile label UI control items for target pages developed in languages (such as HTML 5 etc.). In addition, the above target page can be divided not only into the above three modules, but can also be divided into more detailed modules into more than three modules. In addition, even if the above target page is divided into three modules, It can not only be divided into page management module, global initialization module and page rotation module, but also can be divided into other types of three different modules according to the function of the target page. For the above situation, its specific The processing procedure can be performed by referring to the following.
Example Three
As shown in FIG. 4, the embodiment of the present specification provides a page processing method. The method can be executed by a terminal device or a server, wherein the terminal device can be a device such as a personal computer, or can be mobile such as a mobile phone or a tablet A terminal device, which may be a terminal device used by a user. The server can be an independent server or a server cluster composed of multiple servers, and the server can be a back-end server for a business or a website (such as an online shopping website) Or payment application, etc.) background server, etc. This method can be used to generate a page corresponding to the control item in the native user interface in the operating system of the terminal device (that is, the target page mentioned in this embodiment), and the page is based on the hypertext markup language (that is, Hyper Text Markup Language, HTML) development, which can include HTML 2. 0, HTML 3. 2. HTML 4. 0 and HTML 5 etc. In order to simplify the page processing process and page processing efficiency, this embodiment takes the execution body as the terminal device as an example for description. For the case of the server, it can be processed according to the following related content, which will not be repeated here. In addition, the method The execution subject may specifically be a page management module (that is, NBComponentManager) in the target page in the terminal device
). The method may specifically include the following steps:
In step S402, the global initialization module is called to obtain the type of the first control item in the target user interface and the layout information of the first control item in the target user interface, and according to the above type and the layout information, The typesetting instruction set of the second control item corresponding to the type in the target page is generated. The second control item is a control item that is pre-stored and can be fused in the target page.
Among them, the global initialization module (that is, NBComponentJSLoader) can be run in Webview to calculate and generate typesetting instruction sets. The main function of the page management module NBComponentManager can be to communicate with the global initialization module NBComponentJSLoader to obtain the typesetting instruction set and manage the display of the page index module NBComponentViews.
In the implementation, as shown in FIG. 5, the target page may include six parts, namely a page management module NBComponentManager, a global initialization module NBComponentJSLoader, and a page reversal module
NBComponentViews, Webview, control item management module
NBComponentViewManager, programming interface JSAPI, etc.
In, the control item management module NBComponentViewManager is
NBComponentView's plug-in program manager, users can develop and register custom NBComponentViews, etc.
When it is necessary to use one or more native user interfaces (that is, the target user interface) in the operating system of the terminal device based on the hyper-document markup language (the hyper-document markup language in this embodiment can be explained using HTML 5 as an example) ) When the developed target page is displayed, the page management module
NBComponentManager can call the global initialization module
NBComponentJSLoader, NBComponentJSLoader can obtain the target user interface, and can analyze and calculate the target user interface to determine the control items (that is, the first control item) included in the target user interface, and at the same time, can record each first control item Size and location in the target user interface. The size and size of each first control item recorded and its position in the target user interface can be used to generate the layout information of the first control item in the target user interface. In addition, each first control item in the target user interface may be analyzed to determine the type to which each first control item belongs.
The page rotation module NBComponentViews may pre-store the control items corresponding to the control items in the native user interface of the operating system of the terminal device. After NBComponentJSLoader determines the type of the first control item through the above processing, it can search for the second control item corresponding to the determined type among the previously stored control items through the determined type, and then, NBComponentJSLoader can obtain from the obtained layout information To find the layout information of the first control item in the target user interface, so as to obtain the size and position of the first control item in the target user interface.
NBComponentJSLoader can determine the size of the corresponding second control item according to the size of the first control item, and at the same time, NBComponentJSLoader can also determine the corresponding second control item according to the position of the first control item in the target user interface Position on the target page. NBComponentJSLoader can generate the typesetting instruction set of the second control item in the target page through the size and size of the second control item and the position of the second control item in the target page.
In step S404, the above typesetting instruction set sent by the global initialization module is received.
In step S406, the typesetting instructions in the above typesetting instruction set are analyzed to obtain the analyzed typesetting instructions.
In the implementation, the information of the typesetting instructions in the typesetting instruction set generated by NBComponentJSLoader is not recognized by NBComponentViews. In this way, NBComponentViews will not be able to execute the typesetting instructions for typesetting processing and indexing processing, and obtain the corresponding target page. For this reason, NBComponentManager The typesetting instructions in the typesetting instruction set can be analyzed to obtain the parsed typesetting instructions that can be recognized by NBComponentViews.
In step S408, a page reordering module is created, and the parsed typesetting instruction described above is sent to the page reordering module, so that the page reordering module obtains the second control item fused according to the parsed typesetting instruction. Target page.
In the implementation, in the process of typesetting instructions in the NBComponentManager typesetting instruction set, corresponding NBComponentViews may be created, and the NBComponentViews may be integrated into the Webview. Then, you can send the typesetting instructions parsed by NBComponentManager to
NBComponentViews. NBComponentViews can process the parsed typesetting instructions, and can obtain the second control item according to the data and attributes in the parsed typesetting instruction, and merge the second control item into the target page (that is, HTML 5 page), and display the target Page (ie HTML 5 page).
As shown in FIG. 6, the embodiment of the present specification provides a page processing method. The method can be executed by a terminal device or a server, where the terminal device can be a device such as a personal computer, or can be mobile such as a mobile phone or a tablet A terminal device, which may be a terminal device used by a user. The server can be an independent server or a server cluster composed of multiple servers, and the server can be a back-end server for a business or a website (such as an online shopping website) Or payment application, etc.) background server, etc. This method can be used to generate a page corresponding to the control item in the native user interface in the operating system of the terminal device (that is, the target page mentioned in this embodiment), and the page is based on the hypertext markup language (that is, Hyper Text Markup Language, HTML) development, which can include HTML 2. 0, HTML 3. 2. HTML 4. 0 and HTML 5 etc. In order to simplify the page processing process and page processing efficiency, this embodiment takes the execution body as the terminal device as an example for description. For the case of the server, it can be processed according to the following related content, which will not be repeated here. In addition, the method The execution subject can specifically be the global initialization module (i.e.
NBComponentJSLoader). The method may specifically include the following steps:
In step S602, a programming interface call command is sent to the page management module.
In step S604, according to the call instruction of the page management module, the type of the first control item in the target user interface and the layout information of the first control item in the target user interface are obtained, and according to the type and the typesetting Information, the typesetting instruction set of the second control item corresponding to the type in the target page is generated. The second control item is a control item that is pre-stored and can be fused in the target page.
In step S606, the above typesetting instruction set is sent to the page management module.
As shown in FIG. 7, an embodiment of the present specification provides a page processing method. The method can be executed by a terminal device or a server, where the terminal device can be a device such as a personal computer, or can be mobile such as a mobile phone or a tablet A terminal device, which may be a terminal device used by a user. The server can be an independent server or a server cluster composed of multiple servers, and the server can be a back-end server for a business or a website (such as an online shopping website) Or payment application, etc.) background server, etc. This method can be used to generate a page corresponding to the control item in the native user interface in the operating system of the terminal device (that is, the target page mentioned in this embodiment), and the page is based on the hypertext markup language (that is, Hyper Text Markup Language, HTML) development, which can include HTML 2. 0, HTML 3. 2. HTML 4. 0 and HTML 5 etc. In order to simplify the page processing process and page processing efficiency, this embodiment takes the execution body as the terminal device as an example for description. For the case of the server, it can be processed according to the following related content, which will not be repeated here. In addition, the method The execution subject may specifically be the page reversing module NBComponentViews in the target page in the terminal device. The method may specifically include the following steps:
In step S702, receiving the typesetting instruction sent by the page management module, the typesetting instruction is obtained after the page management module parses the typesetting instruction set of the target page generated and sent by the global initialization module.
In step S704, the above typesetting instruction is executed, the second control item corresponding to the typesetting instruction is obtained from the pre-stored control item library, and typesetting processing and transposition processing are performed on the second control item in the target page to obtain a fusion The target page of the second control item. The second control item is a control item corresponding to the type of the first control item in the target user interface.
Among them, the pre-stored control item library can be set in the page reversing module NBComponentViews, and NBComponentViews can include a set of native UIs that can be integrated into the operating system of the terminal device based on the target page developed based on the hyperfile markup language (such as HTML 5) Control item library (or native UI control item set).
An embodiment of the present specification provides a page processing method, which is applied to a target page, which is developed based on a hyper-file markup language, by acquiring the type of the first control item in the target user interface, and the first control item in the target user The typesetting information in the interface generates the typesetting instruction set of the second control item corresponding to the type in the target page. The second control item is a control item pre-stored and can be fused in the target page to execute the typesetting in the typesetting instruction set Instruction to perform typesetting and translation processing on the second control item in the target page to obtain the target page fused with the second control item. In this way, the native user interface (ie, target user interface) in the operating system of the terminal device is obtained The control item is added to the target page (that is, a page developed based on the hyperfile markup language) as a sub-display control item of the display control item in the target page, instead of simply covering the native user interface control item in the operating system of the terminal device on the target On the page, the effect of merging the control items of the target user interface to the target page is achieved, so that the second control item fused in the target page can be zoomed with the target page, which improves the user experience.
Example 4
As shown in FIG. 8, an embodiment of the present specification provides a page processing method. The method can be executed by a terminal device or a server, where the terminal device can be a device such as a personal computer, or can be mobile such as a mobile phone or a tablet A terminal device, which may be a terminal device used by a user. The server can be an independent server or a server cluster composed of multiple servers, and the server can be a back-end server for a business or a website (such as an online shopping website) Or payment application, etc.) background server, etc. This method can be used to generate a page corresponding to the control item in the native user interface in the operating system of the terminal device (that is, the target page mentioned in this embodiment), and the page is based on the hypertext markup language (that is, Hyper Text Markup Language, HTML) development, which can include HTML 2. 0, HTML 3. 2. HTML 4. 0 and HTML 5 etc. In order to simplify the page processing process and page processing efficiency, this embodiment takes the execution body as the terminal device as an example for description. For the case of the server, it can be processed according to the following related content, which is not repeated here. In addition, the method is specific It can be jointly executed by the page management module (that is, NBComponentManager), the global initialization module (NBComponentJSLoader), and the page turning module (NBComponentViews) in the target page in the terminal device. The method may specifically include the following steps:
In step S802, the global initialization module sends a programming interface call command to the page management module.
In the implementation, when the target page developed based on the hypertext markup language (such as HTML 5) is created, the global initialization module
NBComponentJSLoader can be initialized and can store NBComponentJSLoader in the context of the current target page. After NBComponentJSLoader is initialized, it can send a notification message to the page management module NBComponentManager,
After receiving the notification message, the NBComponentManager can perform initialization processing. After NBComponentManager is initialized,
NBComponentJSLoader can send JSAPI call instructions (ie Call Render JSAPI) to NBComponentManager.
In step S804, the page management module calls the global initialization module.
In step S806, the global initialization module obtains the type of the first control item in the target user interface and the layout information of the first control item in the target user interface according to the call instruction of the page management module, and according to the The type and the typesetting information generate a typesetting instruction set of the second control item corresponding to the type in the target page. The second control item is a control item that is pre-stored and can be fused in the target page.
In step S808, the global initialization module sends a typesetting instruction set to the page management module.
In step S810, the page management module parses the typesetting instructions in the typesetting instruction set to obtain the parsed typesetting instructions.
In step S812, the page management module creates a page rotation module, and sends the parsed typesetting instruction to the page rotation module.
In step S814, the page reordering module executes the parsed typesetting instruction, obtains the second control item corresponding to the typesetting instruction from the pre-stored control item library, and performs typesetting processing and conversion on the second control item in the target page Column processing to get the target page fused with the second control item.
It should be noted that after the page reordering module completes the above-mentioned typesetting processing and reordering processing, and obtains the target page fused with the second control item, it can send a notification message that the target page reordering is completed to the global initialization module.
During the process of creating the page reversal module in the page management module in step S812, the life cycle of the page reversal module can be simultaneously created to manage the display, hiding, and destruction of the page reversal module. For details, see The processing from step S816 to step S826 described below.
In step S816, the page management module creates a life cycle of the page reordering module.
In implementation, if the target page is created for the first time,
NBComponentViews will receive a notification that the native UI control items in the terminal device's operating system have been fused into the Webview to handle the initialization work related to the native UI control items in the terminal device's operating system.
In step S818, when receiving the notification message of invisible life cycle sent by the global initialization module, the page management module sets the life cycle of the page reversal module to an invisible state.
Among them, the invisible state may be processing such as suspending the life cycle of the page reordering module. In actual applications, the notification message of the invisible life cycle may be represented by the notification message of onWebViewPause,
onWebViewPause can be composed of invisible life cycle functions of WebView, used to handle the life cycle related to the native UI control items in the operating system of the terminal device.
In the implementation, when the terminal device is in the state of screen lock or background suppression, the global initialization module can generate a notification message (that is, onWebViewPause) whose life cycle is invisible, and can send it to the page management module NBComponentManager. When NBComponentManager receives the onWebViewPause notification message sent by the global initialization module, it can send onWebViewPause to the page inversion module
NBComponentViews, and call back NBComponentViews will
The life cycle of NBComponentViews is set to invisible.
In step S820, when receiving the notification message sent by the global initialization module that the life cycle is visible again, the page management module sets the life cycle of the page reversing module to the visible state.
Among them, the visible state can be processing such as restoring the life cycle of the page reordering module. In practical applications, the notification message that is visible in the life cycle can be represented by the notification message of onWebViewResume,
onWebViewResume can be composed of the lifecycle functions visible in WebView, used to handle the lifecycle related to the native UI control items in the operating system of the terminal device.
In the implementation, when the terminal device is unlocked or returned to the foreground, the global initialization module can generate a notification message (that is, onWebViewResume) that is visible in the life cycle, and can send it to the page management module NBComponentManager. NBComponentManager received
When the notification message of onWebViewResume, you can change
onWebViewResume is sent to NBComponentViews, and calls back NBComponentViews to set the life cycle of NBComponentViews to the visible state.
In step S822, when receiving the notification message sent by the global initialization module that the second control item is removed or the target page is destroyed, the page management module destroys the life cycle of the page reordering module.
Among them, in actual application, the second control item is removed can be expressed as onEmbedViewDetachedFromWebView,
onEmbedViewDetachedFromWebView can represent the life cycle function where the native UI control item in the operating system of the terminal device is removed. The target page is destroyed can be expressed as onWebViewDestory,
onWebViewDestory can represent the life cycle function of WebView destruction.
In the implementation, when the target page is destroyed, the global initialization module can generate onEmbedViewDetachedFromWebView and
OnWebViewDestory notification message, and can be sent to the page management module NBComponentManager. NBComponentManager received onEmbedViewDetachedFromWebView and
When the notification message of onWebViewDestory, you can change
onEmbedViewDetachedFromWebView and onWebViewDestory are sent to NBComponentViews, and call back NBComponentViews to destroy the life cycle of NBComponentViews.
In step S824, the page management module calls the page reversing module.
In step S826, according to the call instruction of the page rotation module, when the global initialization module detects that the second control item is removed or the target page is destroyed, the page rotation module releases and recovers the second control item.
An embodiment of the present specification provides a page processing method, which is applied to a target page, which is developed based on a hyper-file markup language, by acquiring the type of the first control item in the target user interface, and the first control item in the target user The typesetting information in the interface generates the typesetting instruction set of the second control item corresponding to the type in the target page. The second control item is a control item pre-stored and can be fused in the target page to execute the typesetting in the typesetting instruction set Instruction to perform typesetting and translation processing on the second control item in the target page to obtain the target page fused with the second control item. In this way, the native user interface (ie, target user interface) in the operating system of the terminal device is obtained The control item is added to the target page (that is, a page developed based on the hyperfile markup language) as a sub-display control item of the display control item in the target page, instead of simply covering the native user interface control item in the operating system of the terminal device on the target On the page, the effect of merging the control items of the target user interface to the target page is achieved, so that the second control item fused in the target page can be zoomed with the target page, which improves the user experience.
Example 5
The above is the page processing method provided by the embodiment of the specification. Based on the same idea, the embodiment of the specification further provides a page processing device, which includes a target page, and the target page is developed based on the hyper-file markup language, as shown in FIG. 9 As shown.
The page processing device includes: an information acquisition module 901, a typesetting instruction generation module 902, and a processing module 903, wherein:
The information obtaining module 901 is used to obtain the type of the first control item in the target user interface and the typesetting information of the first control item in the target user interface;
The typesetting instruction generating module 902 is configured to generate a typesetting instruction set of the second control item corresponding to the type in the target page according to the type of the first control item and the typesetting information, and the second control The item is a control item stored in advance and can be fused in the target page;
The processing module 903 is configured to execute a typesetting instruction in the typesetting instruction set, perform typesetting processing and reordering processing on the second control item in the target page to obtain a target page fused with the second control item .
In the embodiment of the present specification, the information acquisition module 901 is used to call a preset programming interface to acquire the type of the first control item in the target user interface, and the first control item is in the user Typesetting information in the interface.
In the embodiment of the present specification, the device further includes:
An instruction receiving module, configured to receive a management instruction for the second control item in the target page, the management instruction including a deletion instruction and a state modification instruction;
The instruction execution module is configured to perform a corresponding operation on the second control item in the target page according to the management instruction.
An embodiment of the present specification provides a page processing device including a target page, which is developed based on a hyper-document markup language, through acquiring the type of the first control item in the target user interface, and the first control item in the target user interface The typesetting information in the page generates the typesetting instruction set of the second control item corresponding to the type in the target page. The second control item is a control item that is pre-stored and can be fused in the target page to execute the typesetting instruction in the typesetting instruction set , The second control item is typeset and converted in the target page to obtain the target page fused with the second control item, so that the native user interface (ie, the target user interface) in the operating system of the terminal device is controlled The item is added as a sub-display control item of the display control item in the target page to the target page (that is, a page developed based on the hyperfile markup language), instead of simply overwriting the native user interface control item in the operating system of the terminal device on the target page In order to achieve the effect of fusing the control items of the target user interface into the target page, the second control item integrated in the target page can be zoomed with the target page, which improves the user experience.
Example Six
Based on the same idea, an embodiment of the present specification also provides a page management module in a page processing device. The page management module is set in a target page. The target page is developed based on a hyper-file markup language. The target page Also includes the global initialization module, as shown in Figure 10.
The page processing device includes: a first calling unit 1001, an instruction set receiving unit 1002, a parsing unit 1003, and an instruction sending unit 1004, wherein:
The first calling unit 1001 is used to call the global initialization module to obtain the type of the first control item in the target user interface and the layout information of the first control item in the target user interface, And generating a typesetting instruction set of the second control item corresponding to the type in the target page according to the type and the typesetting information, the second control item is pre-stored and can be fused on the target page Controls in
The instruction set receiving unit 1002 is configured to receive the typesetting instruction set sent by the global initialization module;
The parsing unit 1003 is configured to parse the typesetting instructions in the typesetting instruction set to obtain the parsed typesetting instructions;
The instruction sending unit 1004 is used to create a page reordering module and send the parsed typesetting instruction to the page reordering module, so that the page reordering module according to the parsed typesetting instruction A target page fused with the second control item is obtained.
In the embodiment of the present specification, the first calling unit 1001 includes:
An instruction receiving subunit, used for receiving a programming interface call instruction sent by the global initialization module;
The calling subunit is used to call the global initialization module.
In the embodiment of the present specification, the page management module further includes:
A life cycle creation unit, used to create the life cycle of the page reordering module;
A first setting unit, configured to set the life cycle of the page reversing module to an invisible state when receiving the notification message of the life cycle invisibility sent by the global initialization module;
The second setting unit is configured to set the life cycle of the page reversing module to a visible state when receiving the notification message of the life cycle restoration visible sent by the global initialization module.
In the embodiment of the present specification, the page management module further includes:
A destruction unit, configured to destroy the life cycle of the page reordering module when receiving the notification message sent by the global initialization module that the second control item is removed or the target page is destroyed;
The second calling unit is used to call the page reversing module to release and recover the second control item.
An embodiment of the present specification provides a page management module in a page processing device, which is set on a target page, the target page is developed based on a hyper-file markup language, through acquiring the type of the first control item in the target user interface, and the first The typesetting information of the control item in the target user interface generates the typesetting instruction set of the second control item corresponding to the type in the target page. The second control item is a control item that is pre-stored and can be fused in the target page to execute The typesetting instruction in the typesetting instruction set performs typesetting processing and reordering processing on the second control item in the target page to obtain the target page fused with the second control item. In this way, the native user interface in the operating system of the terminal device ( That is, the target user interface) control item is added to the target page (that is, the page developed based on the hyperfile markup language) as a sub-display control item of the display control item in the target page, rather than the native user interface in the operating system of the terminal device The control items are simply overlaid on the target page, so as to achieve the effect of integrating the control items of the target user interface into the target page, so that the second control item fused in the target page can be zoomed with the target page, improving the user experience .
Example 7
Based on the same idea, an embodiment of this specification also provides a global initialization module in a page processing device, the global initialization module is set in a target page, and the target page is developed based on a hyper-file markup language, and the target page Also includes a page management module, as shown in Figure 11.
The page processing device includes: an instruction sending unit 1101, an information obtaining unit 1102, and a request sending module 1103, wherein:
An instruction sending unit 1101, configured to send a programming interface call instruction to the page management module;
The information obtaining unit 1102 is configured to obtain the type of the first control item in the target user interface and the layout information of the first control item in the target user interface according to the call instruction of the page management module And generate a typesetting instruction set of the second control item corresponding to the type in the target page according to the type and the typesetting information, the second control item is pre-stored and can be integrated in the target Control items in the page;
The instruction set sending unit 1103 is configured to send the typesetting instruction set to the page management module.
An embodiment of the present specification provides a global initialization module in a page processing device, which is set on a target page, which is developed based on a hyper-file markup language, through acquiring the type of the first control item in the target user interface, and the first The typesetting information of the control item in the target user interface generates the typesetting instruction set of the second control item corresponding to the type in the target page. The second control item is a control item that is pre-stored and can be fused in the target page to execute The typesetting instruction in the typesetting instruction set performs typesetting processing and reordering processing on the second control item in the target page to obtain the target page fused with the second control item. In this way, the native user interface in the operating system of the terminal device ( That is, the target user interface) control item is added to the target page (that is, the page developed based on the hyperfile markup language) as a sub-display control item of the display control item in the target page, rather than the native user interface in the operating system of the terminal device The control items are simply covered on the target page, so as to achieve the effect of fusing the control items of the target user interface to the target page, so that the second control item fused in the target page can be zoomed with the target page, which improves the user Experience.
Example 8
Based on the same idea, an embodiment of the present specification also provides a page reversing module in a page processing device, the page reversing module is set in a target page, and the target page is developed based on a hyperfile markup language, and the target The page also includes a page management module and a global initialization module, as shown in Figure 12.
The page processing device includes: an instruction receiving unit 1201 and an instruction execution unit 1202, wherein:
The instruction receiving unit 1201 is configured to receive the typesetting instruction sent by the page management module. The typesetting instruction is performed by the page management module on the typesetting instruction set of the target page generated and sent by the global initialization module Obtained after analysis;
The instruction execution unit 1202 is configured to execute the typesetting instruction, obtain a second control item corresponding to the typesetting instruction from a pre-stored control item library, and perform typesetting processing on the second control item in the target page and The reordering process obtains a target page fused with the second control item, where the second control item is a control item corresponding to the type of the first control item in the target user interface.
In the embodiment of the present specification, the page turning module further includes:
The control item release unit is configured to release and recover the location when the global initialization module detects that the second control item is removed or the target page is destroyed according to the call instruction of the page rotation module Describe the second control item.
An embodiment of the present specification provides a page reversing module in a page processing device, which is set on a target page, the target page is developed based on a hyper-file markup language, through acquiring the type of the first control item in the target user interface, and the first The typesetting information of a control item in the target user interface generates the typesetting instruction set of the second control item corresponding to the type in the target page. The second control item is a control item that is pre-stored and can be fused in the target page. Execute the typesetting instruction in the typesetting instruction set, perform typesetting processing and column processing on the second control item in the target page to obtain the target page fused with the second control item, so that the native user interface in the operating system of the terminal device (That is, the target user interface) the control item is added to the target page (that is, the page developed based on the hyperfile markup language) as a sub-display control item of the display control item in the target page, rather than the native user in the operating system of the terminal device The interface control items are simply overlaid on the target page, so as to achieve the effect of fusing the control items of the target user interface to the target page, so that the second control item integrated in the target page can be zoomed with the target page, which improves the user Experience.
Example 9
Based on the same idea, an embodiment of this specification also provides a page processing device, as shown in FIG. 13.
The page processing device may be the terminal device provided in the foregoing embodiment.
The page processing device may have a relatively large difference due to different configurations or performances, and may include one or more processors 1301 and a memory 1302. The memory 1302 may store one or more storage applications or data. Among them, the memory 1302 may be short-term storage or permanent storage. The application program stored in the memory 1302 may include one or more modules (not shown), and each module may include a series of computer-executable instructions in the page processing device. Furthermore, the processor 1301 may be configured to communicate with the memory 1302 and execute a series of computer-executable instructions in the memory 1302 on the page processing device. The page processing device may further include one or more power supplies 1303, one or more wired or wireless network interfaces 1304, one or more input/output interfaces 1305, and one or more keyboards 1306.
Specifically in this embodiment, the page processing device includes a memory and one or more programs, where one or more programs are stored in the memory, and one or more programs may include one or more modules, And each module may include a series of computer-executable instructions for the page processing device, and is configured to be executed by one or more processors. The one or more packaged programs contain the following computer-executable instructions:
Obtaining the type of the first control item in the target user interface, and the typesetting information of the first control item in the target user interface;
According to the type of the first control item and the typesetting information, a typesetting instruction set of the second control item corresponding to the type in the target page is generated, and the second control item is pre-stored and can be integrated in The control item in the target page, the target page, the target page is developed based on the hyperfile markup language;
The typesetting instruction in the typesetting instruction set is executed, and the second control item is typeset processed and transposed in the target page to obtain a target page fused with the second control item.
Optionally, the type of the first control item in the target user interface and the typesetting information of the first control item in the user interface include:
Call the default programming interface to obtain the type of the first control item in the target user interface and the layout information of the first control item in the user interface.
Optionally, it also includes:
Receiving a management instruction for the second control item in the target page, the management instruction including a deletion instruction and a state modification instruction;
According to the management instruction, perform a corresponding operation on the second control item in the target page.
An embodiment of the present specification provides a page processing device, including a target page, the target page is developed based on a hyper-document markup language, through acquiring the type of the first control item in the target user interface, and the first control item in the target user interface The typesetting information in the page generates the typesetting instruction set of the second control item corresponding to the type in the target page. The second control item is a control item that is pre-stored and can be fused in the target page to execute the typesetting instruction in the typesetting instruction set , The second control item is typeset and converted in the target page to obtain the target page fused with the second control item, so that the native user interface (ie, the target user interface) in the operating system of the terminal device is controlled The item is added as a sub-display control item of the display control item in the target page to the target page (that is, a page developed based on the hyperfile markup language), instead of simply overwriting the native user interface control item in the operating system of the terminal device on the target page In order to achieve the effect of fusing the control items of the target user interface into the target page, the second control item integrated in the target page can be zoomed with the target page, which improves the user experience.
Example 10
Based on the same idea, an embodiment of this specification also provides a page processing device, as shown in FIG. 14.
The page processing device may be the terminal device provided in the foregoing embodiment.
The page processing device may have a relatively large difference due to different configurations or performances, and may include one or more processors 1401 and a memory 1402. The memory 1402 may store one or more storage applications or data. Among them, the memory 1402 may be short-term storage or permanent storage. The application program stored in the memory 1402 may include one or more modules (not shown), and each module may include a series of computer-executable instructions in the page processing device. Furthermore, the processor 1401 may be configured to communicate with the memory 1402 and execute a series of computer-executable instructions in the memory 1402 on the page processing device. The page processing device may further include one or more power supplies 1403, one or more wired or wireless network interfaces 1404, one or more input/output interfaces 1405, and one or more keyboards 1406.
Specifically in this embodiment, the page processing device includes a memory and one or more programs, where one or more programs are stored in the memory, and one or more programs may include one or more modules, And each module may include a series of computer-executable instructions for the page processing device, and is configured to be executed by one or more processors. The one or more packaged programs contain the following computer-executable instructions:
Applied to a target page, the target page is developed based on hyper-file markup language, and the target page includes a global initialization module, including:
Calling the global initialization module to obtain the type of the first control item in the target user interface and the layout information of the first control item in the target user interface, and according to the type and the Typesetting information to generate a typesetting instruction set of the second control item corresponding to the type in the target page, the second control item is a control item pre-stored and can be fused in the target page;
Receiving the typesetting instruction set sent by the global initialization module;
Parse the typesetting instructions in the typesetting instruction set to obtain the parsed typesetting instructions;
Creating a page reordering module, and sending the parsed typesetting instruction to the page reordering module, so that the page reordering module obtains the second fusion according to the parsed typesetting instruction The target page of the control.
Optionally, the calling the global initialization module includes:
Receiving a programming interface call command sent by the global initialization module;
Call the global initialization module.
Optionally, after the page inversion module is created, the method further includes:
Creating the life cycle of the page reordering module;
When receiving the notification message of the invisible life cycle sent by the global initialization module, setting the life cycle of the page reversing module to an invisible state;
When receiving the notification message of the life cycle restoration visible sent by the global initialization module, the life cycle of the page reversing module is set to a visible state.
Optionally, the method further includes:
When receiving the notification message sent by the global initialization module that the second control item is removed or the target page is destroyed, destroying the life cycle of the page reordering module;
Call the page transfer module to release and recover the second control item.
Specifically in this embodiment, the page processing device includes a memory and one or more programs, where one or more programs are stored in the memory, and one or more programs may include one or more modules, And each module may include a series of computer-executable instructions for the page processing device, and is configured to be executed by one or more processors. The one or more packaged programs contain the following computer-executable instructions:
Applied to a target page, the target page is developed based on hyper-file markup language, and the target page includes a page management module, including:
Send programming interface calling commands to the page management module;
Acquiring the type of the first control item in the target user interface and the layout information of the first control item in the target user interface according to the call instruction of the page management module, and according to the type and The typesetting information generates a typesetting instruction set of the second control item corresponding to the type in the target page, the second control item is a control item that is pre-stored and can be fused in the target page;
Sending the typesetting instruction set to the page management module.
Specifically in this embodiment, the page processing device includes a memory and one or more programs, where one or more programs are stored in the memory, and one or more programs may include one or more modules, And each module may include a series of computer-executable instructions for the page processing device, and is configured to be executed by one or more processors. The one or more packaged programs contain the following computer-executable instructions:
Applied to the target page, the target page is developed based on the hyperfile markup language, and the target page includes a page management module and a global initialization module, including:
Receiving a typesetting instruction sent by the page management module, the typesetting instruction is obtained by the page management module parsing the typesetting instruction set of the target page generated and sent by the global initialization module;
Execute the typesetting instruction, obtain the second control item corresponding to the typesetting instruction from the pre-stored control item library, and perform typesetting processing and transposition processing on the second control item in the target page to obtain a fusion A target page of the second control item, where the second control item is a control item corresponding to the type of the first control item in the target user interface.
Optionally, the method further includes:
According to the call instruction of the page rotation module, when the global initialization module detects that the second control item is removed or the target page is destroyed, the second control item is released and recovered.
An embodiment of the present specification provides a page processing device, including a target page, the target page is developed based on a hyper-document markup language, through acquiring the type of the first control item in the target user interface, and the first control item in the target user interface The typesetting information in the page generates the typesetting instruction set of the second control item corresponding to the type in the target page. The second control item is a control item that is pre-stored and can be fused in the target page to execute the typesetting instruction in the typesetting instruction set , The second control item is typeset and converted in the target page to obtain the target page fused with the second control item, so that the native user interface (ie, the target user interface) in the operating system of the terminal device is controlled The item is added as a sub-display control item of the display control item in the target page to the target page (that is, a page developed based on the hyperfile markup language), instead of simply overwriting the native user interface control item in the operating system of the terminal device on the target page In order to achieve the effect of fusing the control items of the target user interface into the target page, the second control item integrated in the target page can be zoomed with the target page, which improves the user experience.
The foregoing describes specific embodiments of the present specification. Other embodiments are within the scope of the attached patent application. In some cases, the actions or steps described in the scope of the patent application may be performed in a different order than in the embodiment and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require the particular order shown or sequential order to achieve the desired results. In some embodiments, multiplexing and parallel processing are also possible or may be advantageous.
In the 1990s, the improvement of a technology can be clearly distinguished from the improvement of hardware (for example, the improvement of the circuit structure of diodes, transistors, switches, etc.) or the improvement of software (for the process flow Improve). However, with the development of technology, the improvement of many methods and processes can be regarded as a direct improvement of the hardware circuit structure. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method and process cannot be achieved with hardware physical modules. For example, a programmable logic device (Programmable Logic Device, PLD) (such as a field programmable gate array (Field Programmable Gate Array, FPGA)) is such an integrated circuit, whose logic function is determined by the user programming the device . It is up to the designer to program a digital system to "integrate" a PLD without having to ask a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, this kind of programming is also mostly implemented with "logic compiler" software, which is similar to the software compiler used when writing program development. The original code before compilation must also be written in a specific programming language, which is called the hardware description language (Hardware Description Language, HDL), and HDL is not only one, but there are many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description
Language), Confluence, CUPL (Cornell University
Programming Language), HDCal, JHDL (Java Hardware
Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. At present, the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that it is easy to obtain the hardware circuit that implements the logic method flow by only slightly programming the method flow using the above hardware description languages and programming it into the integrated circuit.
The controller can be implemented in any suitable way, for example, the controller can take, for example, a microprocessor or processor and a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor Media, logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers and embedded microcontrollers. Examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip
PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that, in addition to implementing the controller in a pure computer-readable program code manner, the logic steps of the method steps can be completely controlled to make the controller controlled by logic gates, switches, dedicated integrated circuits, and programmable logic To achieve the same function in the form of a controller and embedded microcontroller. Therefore, such a controller can be regarded as a hardware component, and the device for implementing various functions included therein can also be regarded as a structure within the hardware component. Or even, the device for realizing various functions can be regarded as both a software module of the implementation method and a structure in the hardware component.
The system, device, module or unit explained in the above embodiments may be implemented by a computer chip or entity, or by a product with a certain function. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a mobile phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, and a wearable device Or any combination of these devices.
For the convenience of description, when describing the above device, the functions are divided into various units and described separately. Of course, when implementing one or more embodiments of this specification, the functions of each unit may be implemented in the same software or multiple hardware and/or hardware.
Those skilled in the art should understand that the embodiments of the present specification may be provided as methods, systems, or computer program products. Therefore, one or more embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more embodiments of this 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 program code In the form of computer program products.
The embodiments of the present specification are described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present specification. It should be understood that each flow and/or block in the flowchart and/or block diagram and a combination of the flow and/or block in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processors of general-purpose computers, special-purpose computers, embedded processors, or other programmable data processing equipment to produce a machine that allows instructions executed by the processor of the computer or other programmable data processing equipment Generate means for implementing the functions specified in one block or multiple blocks of a flowchart or a flow and/or a block diagram.
These computer program instructions can also be stored in a computer readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce a manufactured product including an instruction device The instruction device implements the functions specified in one block or multiple blocks in one flow or multiple processes in the flowchart and/or one block in the block diagram.
These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operating steps can be performed on the computer or other programmable device to generate computer-implemented processing, and thus on the computer or other programmable device The instructions executed on provide steps for implementing the functions specified in one block or multiple blocks of the flowchart one flow or multiple flows and/or block diagrams.
In a typical configuration, the computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
Memory may include non-permanent memory, random access memory (RAM) and/or non-volatile memory in computer-readable media, such as read-only memory (ROM) or flash memory ( flash RAM). Memory is an example of computer-readable media.
Computer-readable media, including permanent and non-permanent, removable and non-removable media, can be stored by any method or technology. The information can be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM) , Read-only memory (ROM), electrically erasable and programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only disc read-only memory (CD-ROM), digital multifunction Optical discs (DVDs) or other optical storage, magnetic cassette tapes, magnetic tape storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
It should also be noted that the terms "include", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device that includes a series of elements includes not only those elements, but also includes Other elements not explicitly listed, or include elements inherent to this process, method, commodity, or equipment. Without more restrictions, the element defined by the sentence "include one..." does not exclude that there are other identical elements in the process, method, commodity, or equipment that includes the element.
Those skilled in the art should understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, one or more embodiments of this specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, one or more embodiments of this 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 program code In the form of computer program products.
One or more embodiments of this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of this specification can also be practiced in a distributed computing environment in which remote processing devices connected through a communication network perform tasks. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.
The embodiments in this specification are described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant part can be referred to the description of the method embodiment.
The above are only examples of this specification and are not intended to limit this specification. For those skilled in the art, this specification may have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included in the patent application scope of this specification.