H5 container manager processing method based on NavPathStack class

Abstract

The invention discloses an H5 container manager processing method based on a NavPath Stack class, and the processing method comprises the following steps: based on the H5 container manager of the NavPath Stack class, firstly integrating the code of the H5 container manager of the NavPath Stack class into an app; when the H5 calls the open container and the closed container for bridging, a method in the NavPathStack type H5 container manager is executed; and opening the H5 page according to the transmitted parameters, and returning to a specified page or returning to the specified page or returning and refreshing contents among different pages while opening the H5 page. The page can be flexibly opened or closed; and smooth and seamless page jump and state management of the user in the process can be ensured.

Description

Technical Field

[0001] The present invention relates to the field of mobile banking, and in particular to an H5 container manager processing method based on the NavPathStack class. Background Art

[0002] When users use mobile banking apps to complete certain business operation processes, some business processes require opening 5 to 6 pages to complete, opening a certain page and then returning to a specified page, or returning between different pages and refreshing the content. For example, account registration process, real-name authentication process, loan application process, shareholder meeting process, cloud certificate opening process, and smart reminder process. The H5 container manager is essential to meet the needs of complex business operation page processes. The H5 container manager supports the customization of these complex operations and can flexibly open or close pages to ensure that the page jump and status management of users in the process are smooth and seamless.

[0003] Existing technical solutions:

[0004] 1. H5 developers use JavaScript to implement a container manager to open multiple pages and return and refresh content between different pages.

[0005] 2. By integrating third-party container manager frameworks such as Apache Cordova / PhoneGap or ProgressiveWebApps (PWAs).

[0006] 3. Purchase a third-party container manager platform, pay for access, and configure the opening and closing of containers and the return between different pages on the service platform. Summary of the invention

[0007] In view of the above problems, the present invention is proposed to provide an H5 container manager processing method based on the NavPathStack class that overcomes the above problems or at least partially solves the above problems.

[0008] According to one aspect of the present invention, a method for processing an H5 container manager based on the NavPathStack class is provided, the method comprising:

[0009] Based on the H5 container manager of the NavPathStack class, first integrate the H5 container manager code of the NavPathStack class into the app;

[0010] When H5 calls to open or close the container bridge, the method in the H5 container manager of the NavPathStack class is executed;

[0011] According to the passed parameters, the H5 page is opened, and the H5 page is opened and returned to the specified page at the same time, or returned between different pages and refreshed the content.

[0012] Optionally, the H5 container manager uses the parameter type passed by calling the openNewH5Container bridge to open the container type classification, specifically including:

[0013] Open the new container normally;

[0014] Close all current containers and open new containers;

[0015] Close the current container and open a new container;

[0016] Close all containers after the passed container ID and open a new container.

[0017] Optionally, the H5 container manager uses the parameters passed by calling the closeH5Container bridge to classify the closed container type, including:

[0018] When the containerId value is allContainer, close all containers and return to the container entry page;

[0019] When the containerId value is empty, return to the previous container page;

[0020] When the containerId value is A, return to the page whose containerId is A.

[0021] Optionally, the refresh content specifically includes:

[0022] According to the needReload parameter passed when calling the bridge, when the needReload value is true, refresh the container page.

[0023] Optionally, the processing method further includes: assembling a parameter model BOBPageInfo according to the parameters passed when calling the bridge, and passing it to the container as a parameter when opening the container.

[0024] Optionally, the pushPath method of the NavPathStack class opens a new container, and the replacePath method closes the current container and opens a new container.

[0025] Optionally, the getAllPathName method of the NavPathStack class obtains all page stack information.

[0026] Optionally, the page stack information is traversed, and the passed parameter shutContainerId is compared with the parameter containerId of the current page information. When they are equal, the popToIndex method of the NavPathStack class is called to return to the page with the specified container ID.

[0027] Optionally, the pop method of the NavPathStack class closes a page, and when the popToIndex method parameter (index) is -1, all containers are closed.

[0028] The present invention provides a method for processing an H5 container manager based on the NavPathStack class, the method comprising: based on the H5 container manager of the NavPathStack class, first integrating the H5 container manager code of the NavPathStack class into the app; when H5 calls the container opening and closing bridge, executing the method in the H5 container manager of the NavPathStack class; according to the passed parameters, executing the opening of the H5 page, returning to the specified page while opening the H5 page, returning to the specified page or returning between different pages and refreshing the content. The page can be opened or closed flexibly; ensuring that the page jump and state management of the user in the process are smooth and seamless.

[0029] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative work.

[0031] Figure 1 A flowchart of an H5 container manager processing method based on the NavPathStack class provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0032] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0033] The terms "comprises" and "having" and any variations thereof in the description embodiments, claims and drawings of the present invention are intended to cover non-exclusive inclusions, for example, including a series of steps or units.

[0034] The technical solution of the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0035] like Figure 1 As shown, an H5 container manager processing method based on the NavPathStack class includes:

[0036] Based on the H5 container manager of the NavPathStack class, first integrate the H5 container manager code of the NavPathStack class into the app. When H5 calls the container opening and closing bridge, the methods in the H5 container manager of the NavPathStack class are executed. According to the passed parameters, the H5 page is opened, and the H5 page is opened and returned to the specified page at the same time, or returned between different pages and refreshed.

[0037] Use the parameter (type) passed by calling the openNewH5Container bridge to classify the container types: 1. Open a new container normally; 2. Close all current containers and open a new container; 3. Close the current container and open a new container; 4. Close all containers after the passed container ID and open a new container.

[0038] Use the parameter (containerId) passed by calling the closeH5Container bridge to classify the container type. The classifications are: When the containerId value is allContainer, close all containers and return to the container entry page. When the containerId value is empty, return to the previous container page. When the containerId value is A, return to the page where the containerId is A.

[0039] According to the parameter (needReload) passed when calling the bridge, when the needReload value is true, refresh the container page.

[0040] Assemble the parameter model BOBPageInfo according to the parameters (pageTitle, url, containerId) passed when calling the bridge, and pass it to the container as a parameter when opening the container.

[0041] Call the pushPath method of the NavPathStack class to open a new container, the replacePath method to close the current container, and open a new container.

[0042] Call the getAllPathName method of the NavPathStack class to obtain all page stack information.

[0043] Traverse all the obtained page stack information, compare the passed parameter (shutContainerId) with the parameter (containerId) of the current page information, and when they are equal, call the popToIndex method of the NavPathStack class to return to the page with the specified container ID.

[0044] Call the pop method of the NavPathStack class to close a page. When the popToIndex method parameter (index) is -1, all containers are closed.

[0045] Use autoreleasepool to automatically release the pool and recycle multiple calls to open the container bridge to avoid excessive memory and occupy the mobile phone's running memory.

[0046] When calling the container bridge multiple times, avoid competition, use GCD queue management, and call in order.

[0047] The present invention achieves:

[0048] The H5 container manager based on the NavPathStack class is directly implanted into the app. H5 does not need to modify the bridge call method and can directly use the previous method to call the bridge.

[0049] Introducing the H5 container manager of the NavPathStack class reduces the JavaScript code integrated on the H5 side, reduces the size of the package, improves the loading and rendering speed, and optimizes the user experience.

[0050] The H5 container manager of the NavPathStack class is introduced to be compatible with different mobile phone models and different mobile phone system versions.

[0051] Realize opening of H5 page, realize returning to the specified page while opening H5 page, realize returning to the specified page or returning between different pages and refreshing the content.

[0052] Flexibly customize complex banking business operation scenarios and page functions that businesses want to open and close.

[0053] When the H5 container manager of the NavPathStack class is called multiple times, an automatic release pool is created to prevent excessive memory usage and occupying the mobile phone's running memory.

[0054] The H5 container manager using the NavPathStack class can easily call native functions, such as mobile phone camera, photo album, positioning, voice, and address book native functions.

[0055] H5 passes parameters when calling the container opening and closing bridge, and the app executes the methods in the H5 container manager of the NavPathStack class.

[0056] The app opens pages, closes pages, returns between different pages, and refreshes content based on the passed parameters.

[0057] The H5 container manager based on the NavPathStack class and the H5 end code isolation improve the security of the app.

[0058] The H5 container manager based on the NavPathStack class flexibly collects and manages logs, such as creating log files, opening log files, archiving logs, and saving logs.

[0059] Beneficial effects:

[0060] 1. Lightweight H5 container manager, no other redundant code.

[0061] 2. Support customization of complex operation processes and jump functions that the business wants to achieve.

[0062] 3. Ability to open or close pages flexibly.

[0063] 4. Ensure that the user's page jumps and status management in the process are smooth and seamless.

[0064] The above specific implementation methods further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A H5 container manager processing method based on the NavPathStack class, characterized in that: The processing method comprises: Based on the H5 container manager of the NavPathStack class, first integrate the H5 container manager code of the NavPathStack class into the app; When H5 calls to open or close the container bridge, the method in the H5 container manager of the NavPathStack class is executed; According to the passed parameters, the H5 page is opened, and the H5 page is opened and returned to the specified page at the same time, or returned between different pages and refreshed the content.

2. According to claim 1, a H5 container manager processing method based on the NavPathStack class is characterized in that: The H5 container manager uses the parameter type passed by calling the openNewH5Container bridge to classify the container types, including: Open the new container normally; Close all current containers and open new containers; Close the current container and open a new container; Close all containers after the passed container ID and open a new container.

3. According to the H5 container manager processing method based on the NavPathStack class of claim 1, it is characterized in that: The H5 container manager uses the parameters passed by calling the closeH5Container bridge to classify the closed container types, including: When the containerId value is allContainer, close all containers and return to the container entry page; When the containerId value is empty, return to the previous container page; When the containerId value is A, return to the page whose containerId is A.

4. According to the H5 container manager processing method based on the NavPathStack class of claim 1, it is characterized in that: The refresh content specifically includes: According to the needReload parameter passed when calling the bridge, when the needReload value is true, refresh the container page.

5. The H5 container manager processing method based on the NavPathStack class according to claim 1 is characterized in that: The processing method also includes: The parameter model BOBPageInfo is assembled according to the parameters passed when calling the bridge, and is passed to the container as a parameter when opening the container.

6. The H5 container manager processing method based on the NavPathStack class according to claim 1 is characterized in that: The pushPath method of the NavPathStack class opens a new container, and the replacePath method closes the current container and opens a new container.

7. The H5 container manager processing method based on the NavPathStack class according to claim 1 is characterized in that: The getAllPathName method of the NavPathStack class obtains all page stack information.

8. The H5 container manager processing method based on the NavPathStack class according to claim 7 is characterized in that: The page stack information is traversed, and the passed parameter shutContainerId is compared with the parameter containerId of the current page information. When they are equal, the popToIndex method of the NavPathStack class is called to return to the page with the specified container ID.

9. The H5 container manager processing method based on the NavPathStack class according to claim 1, characterized in that: The pop method of the NavPathStack class closes a page, and when the parameter index of the popToIndex method is -1, all containers are closed.

Images