CN111258559A - Hybrid application multi-level page routing skip method based on reach Native - Google Patents
Hybrid application multi-level page routing skip method based on reach Native Download PDFInfo
- Publication number
- CN111258559A CN111258559A CN202010106359.2A CN202010106359A CN111258559A CN 111258559 A CN111258559 A CN 111258559A CN 202010106359 A CN202010106359 A CN 202010106359A CN 111258559 A CN111258559 A CN 111258559A
- Authority
- CN
- China
- Prior art keywords
- page
- jump
- route
- native
- pages
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
Abstract
The invention discloses a hybrid application multi-level page route skipping method based on React Native, which uniquely identifies each level of Native pages and React Native pages by short routes, the Native pages and the React Native pages are registered in a routing table by the short routes, the cross-level location and skipping of the pages are realized by verifying the short routes in page skipping request URLs and combining the judgment on page types on the basis of not increasing or even reducing manual code compiling, the later skipping rule change only needs to maintain the routing table without considering code addition, the multi-level skipping among the React Native pages is aimed at the multi-level skipping between the React Native pages, all React Native pages are informed of skipping execution waiting for monitoring, a navigator is directly called to execute skipping actions regardless of the page levels, the total amount of written codes in the conventional page skipping is reduced, and the cross-level location and skipping of the pages are realized.
Description
Technical Field
The invention relates to the field of mobile development, in particular to a hybrid application multi-level page routing skip method based on a real Native.
Background
A multi-level page is a description of the structural relationship of web site pages, and any web site is based on the three levels of structure.
The hybrid application is a mixture of native applications and Web applications, wherein the native applications are capable of running directly on the current operating system
General application
Using the program; the Web application is a webpage application which needs to run in a browser; the combination of the two is usually a native application embedded with a browser.
The fact Native is an excellent tool for developing mixed applications, is a cross-platform mobile application development framework which is sourced in Facebook in 2015 4, is a derivative product of a JS framework fact which is sourced earlier in Facebook on a Native mobile application platform, and currently supports two platforms of iOS and android. The fact Native produced either "web applications", or "HTML 5 applications", or "hybrid applications". The end product is a real mobile application that is almost indistinguishable from use experience compared to applications written in Objective-C or Java. The basic UI components used by the reach Native are completely consistent with the Native application.
In daily real Native hybrid application development, page jumping is a basic operation. Due to the complexity of the service, many hops involve a service scenario where the hops are located at one time across multiple pages. If the traditional jump mode is used, the defects exist: one is code redundancy, and many repeated codes exist, for example, a read Native page needs to jump to a Native page and a bridge must be created, then Android and IOS terminals need to realize the function of jumping to the Native page by the bridge method, and a bridge is created every time a Native page is jumped newly! This is certainly fatal and does not facilitate long-term maintenance of the project. Another aspect is that the real Native hybrid application is a hybrid of the real Native technology and Native technology (Native mobile application platform), there is no direct jump positioning method between the two technologies, and if direct jump positioning across multiple levels of pages is involved, it is difficult to achieve based on the existing technology. For example, page a is a primary page, page B is a ReactNative page is a secondary page, and page C is a ReactNative page is a tertiary page. If the page A is to be shifted to the page C, the conventional technical scheme can only be used for shifting the page C step by step, namely, the page C is shifted after the page B is shifted
In view of the above problems, no perfect and open solution is available on the market.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provides a hybrid application multi-level page route skipping method based on read Native, which uniquely identifies each level of Native pages and read Native pages by short routes, the Native pages and the read Native pages are registered in a route table by the short routes, the short routes in the URL of a page skipping request are verified, the page type is judged, the cross-level positioning and skipping of the page are realized on the basis of not increasing or even reducing manual code writing, and later skipping rule change only needs to maintain the route table without considering increasing codes.
In order to solve the technical problems, the technical scheme of the invention is that a multi-level page route skipping method based on read Native hybrid application uniquely identifies each level of Native pages and read Native pages by route short chains, the Native pages and the read Native pages are registered in a route table by the route short chains, the cross-level positioning and skipping of the pages are realized by verifying the route short chains in page skipping request URLs and combining the judgment on page types on the basis of not increasing or even reducing manual code compiling, and the page skipping rule change of the pages of the web page later only needs to maintain the route table without considering the increase of page skipping codes, and the specific steps comprise:
step 1: in the hybrid application, webpage pages of all levels are registered in a routing table in a mode of registering short routes, the webpage pages comprise a Native page and a read Native page (hereinafter referred to as RN page), and the short routes are unique address identifiers of the webpage pages;
based on the registered short routes in the routing table, storing the mapping relation between the short routes of the pages of each level into a (third-party) route jump system, wherein the mapping relation is the jump relation between the original pages of different levels and the RN pages of different levels;
the routing table and the routing jump system are configured on a native mobile application platform (native terminal), and the native terminal is a page set general name developed by Android and IOS native technologies; and the route skipping system is selected as an android terminal ARouter and an IOS terminal MGJRouter according to the operating system of the mobile application. Executing a jump action of jumping to a native page by calling a third-party route jump system;
particularly, in the step 1, the two-dimensional code (regarded as the special webpage) is also registered in the routing table in a short-chain routing form, the short-chain routing of the two-dimensional code is obtained by scanning the code, and the two-dimensional code performs page positioning and skipping according to the short-chain routing;
step 2: a read Native terminal (RN terminal for short) monitors an RN page jump execution notice of a route jump system, when the RN page jump execution notice is monitored, a current page calls a read-Navigation navigator, and page operation is executed in an RN page stack and page jump operation is implemented according to the jump type of the RN page analyzed from a routing table of the route jump system; the skip type is defined according to a route skip method provided by a read-Navigation navigator;
particularly, the jump types specifically include push jump, place jump and navigator jump, and the corresponding page operations include page addition, page replacement and page traversal;
the page is newly added: a target RN page is newly added at the stack top of the RN page stack;
and the page replacement comprises the following steps: directly replacing the current page in the RN page stack;
the page traversal: traversing a target page in the RN page stack, if the target page exists, directly jumping to the target page and pushing out all RN pages above the target page, and if the target page does not exist in the RN page stack, adding a target RN page at the top of the stack and jumping;
particularly, the listening event in step 2 is compiled into a high-order component, which is configured at the RN end, all RN pages inherit the high-order component, and the high-order component (high-order component) is similar to a high-order function, so that the code has more reusability, logical and abstract characteristics, and can hijack the render method, and also can control the protocols and the state.
And step 3: the RN end establishes a data transmission channel between the RN end and the primary end by calling a bridging method, and writes an interface of the calling step 4 into the bridging method;
and 4, step 4: acquiring a jump request initiated by a current page, analyzing a jump address URL of a target page, and positioning and jumping the page according to the type of the target page by verifying the validity of the URL and whether the page is registered or not and judging the jump logic for identifying the type of the current page and the type of the target page;
if so, directly calling the route skipping system in the step 1, directly positioning to a target page according to the mapping relation between short chains of the page route, and executing skipping; if so, jumping to an RN page, when the current page is a primary page, newly adding 1 RN page stack, and adding a target page in the page stack; when the current page is the RN page, calling a read-Navigation navigator according to the step 2 to execute page operation on the RN page stack where the current page is located;
the step 4 specifically comprises the following steps:
step 4-1: acquiring a page jump request URL initiated by a current page, verifying the validity of the URL, and directly refusing jump access if the URL is illegal; if the process is legal, turning to the step 4-2:
step 4-2: analyzing the URL to obtain a short route, judging whether a page is registered in the routing table in the step 1 according to whether the short route is matched with the short route in the routing table, and if the matching fails, creating a new window to load an HTML5 page corresponding to the URL; if the matching is successful, turning to the step 4-3;
step 4-3: calling a routing table, inquiring whether to record the jump limitation of the target page according to the short chain of the route, and if so, executing preorder limitation operation according to the limitation content; if not, executing step 3-4;
step 4-4: identifying the type of a target page, inquiring the type of the target page recorded by the short route chain in the routing table, if the target page is marked as a primary page in the routing table, directly calling the route skipping system in the step 1 to skip directly; if the target page is marked as the RN page in the routing table, executing the step 4-5;
and 4-5: identifying the type of the current page, if the current page is a native page, creating an RN page stack, and directly placing a target RN page in the RN page stack to execute jumping; if the current page is the RN page, establishing a page jump execution notice, and executing the step 2;
writing a global class by the skip logic of the step 4 and configuring the global class at a primary end, actively calling a bridging method when a current page is an RN page, and directly calling the skip logic class to execute skip judgment and page skip when page skip occurs each time;
has the advantages that:
the invention uniquely identifies a multi-level Native page and an RN page by a short route chain, identifies the page and the page type by acquiring the short route chain in the URL of an analysis jump request, aims at multi-level jump among React Native pages, and directly calls a navigator to execute a jump action under the condition of no matter the page level, thereby reducing the total amount of codes required to be written in the traditional page jump, realizing cross-level positioning and jump of the page on the basis of not increasing or even reducing manually written codes, and changing the later jump rule only by maintaining a route table without considering the increase of the codes; the invention also realizes the acquisition of the short route chain by scanning the code by using the short route chain identification two-dimensional code, thereby realizing the rapid positioning of the target page.
Drawings
FIG. 1 is a flowchart of a method for implementing read Native hybrid application multi-level page routing skip in an embodiment of the present invention;
FIG. 2 is a flow chart illustrating the jump logic determination in multi-level page jump according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a system for read Native hybrid application multi-level page routing skip according to an embodiment of the present invention.
Detailed Description
The invention will be further described with reference to the drawings and the exemplary embodiments:
fig. 1 is a flowchart of a method for implementing read Native hybrid application multi-level page route hopping in the embodiment of the present invention, and the specific steps include:
step S1: in the hybrid application, all levels of pages are registered in a routing table in a short-chain route registration mode; based on the registered short routes in the route table, storing the jump mapping relation among the short routes of each level page in a route jump system;
and the route skipping system is selected as an android terminal ARouter and an IOS terminal MGJRouter according to the operating system of the mobile application. Executing a jump action of jumping to a native page by calling a third-party route jump system;
step S2: when a read Native terminal (RN terminal for short) monitors an RN page jump execution notice, a current page calls a read-Navigation navigator when the RN page jump execution notice is monitored, and page jump operation is implemented by executing page operation in an RN page stack according to the jump type of the RN page analyzed from a routing table; the skip type is defined according to a route skip method provided by a read-Navigation navigator;
the jump types specifically comprise push jump, place jump and navigator jump, and the corresponding page operations comprise page addition, page replacement and page traversal; the page is newly added: a target RN page is newly added at the stack top of the RN page stack; and the page replacement comprises the following steps: directly replacing the current page in the RN page stack; the page traversal: traversing a target page in the RN page stack, if the target page exists, directly jumping to the target page and pushing out all RN pages above the target page, and if the target page does not exist in the RN page stack, adding a target RN page at the top of the stack and jumping;
step S3: the RN end establishes a data transmission channel between the RN end and the primary end by calling a bridging method, and writes an interface of the calling step 4 into the bridging method; the bridging method in the embodiment of the invention inherits the ReactContexttBaseJavaModule basic bridging module of ReactNative, annotates the self-defined method in the bridging through @ ReactMethod, and is different from other bridging codes in that the method name of each bridging method is unique, and the code in each bridging method is also unique.
The main codes are as follows:
step S4: acquiring a jump request initiated by a current page, analyzing a jump address URL of a target page, and positioning and jumping the page according to the type of the target page by verifying the validity of the URL and whether the page is registered or not and judging the jump logic for identifying the type of the current page and the type of the target page;
if so, directly calling the route skipping system in the step 1, directly positioning to a target page according to the mapping relation between short chains of the page route, and executing skipping; if so, jumping to an RN page, when the current page is a primary page, newly adding 1 RN page stack, and adding a target page in the page stack; when the current page is the RN page, calling a read-Navigation navigator according to the step 2 to execute page operation on the RN page stack where the current page is located;
the step S4, referring to fig. 2, specifically includes:
step S4-1: acquiring a page jump request URL initiated by a current page, verifying the validity of the URL, and directly refusing jump access if the URL is illegal; if the process is legal, go to step S4-2:
step S4-2: analyzing the URL to obtain a short route, judging whether the page is registered in the routing table of the step S1 according to whether the short route is matched with the short route in the routing table, and if the matching fails, creating a new window to load an HTML5 page corresponding to the URL; if the matching is successful, the step S4-3 is carried out;
step S4-3: calling a routing table, inquiring whether to record the jump limitation of the target page according to the short chain of the route, and if so, executing preorder limitation operation according to the limitation content; if not, executing step S3-4;
step S4-4: identifying the type of a target page, inquiring the type of the target page recorded by the short route chain in the routing table, if the target page is marked as a primary page in the routing table, directly calling the route skipping system in the step 1 to skip directly; if the target page is marked as the RN page in the routing table, executing the step 4-5;
step S4-5: identifying the type of the current page, if the current page is a native page, creating an RN page stack, and directly placing a target RN page in the RN page stack to execute jumping; if the current page is the RN page, creating a page jump execution notification, and executing the step S2;
the method is also suitable for page skipping based on two-dimension code scanning, specifically, the two-dimension code is registered in a routing table in a route short-chain form, and when the page corresponding to the two-dimension code is a primary page, after the skipping logic judgment of the step S4, a third-party route skipping system is called to skip directly according to the step S1; when the page corresponding to the two-dimensional code is the RN page, after the jump logic judgment of the step S4, calling a read-Navigation navigator to execute jump according to the step S2;
fig. 3 is a schematic diagram of a system structure for performing route hopping based on a read Native hybrid application multi-level page, including an origin and a read Native, where the origin is a generic name of a Native page set developed by Android and IOS Native technologies, and the Read Native (RN) is a generic name of a read Native page set developed by using a read Native technology;
the RN end is provided with a read-Navigation navigator, a monitoring tool and a bridging tool, the monitoring tool is used for monitoring a jump execution notice of a jump target RN page sent by the RN page, the monitoring event of the step S2 is compiled into the monitoring tool in a high-order component form, all RN pages inherit the high-order components, and the high-order components (high-order components) are similar to high-order functions, so that the codes have reusability, logicality and abstract characteristics, a render method can be hijacked, and the programs and the state can be controlled; the bridging tool is used for data communication connection of the RN end and the original end and calling the jump logic tool;
the native terminal is configured with a routing table, a third-party route skipping system and a skipping logic tool, and the routing short chain of each level of native page and RN page is recorded in the routing table; the third-party route skip system records skip mapping relations among pages of each level; the jump logic tool is used for processing and controlling direct jump of a multi-level page based on a page jump request URL, a global class is compiled by the jump logic from the step S4-1 to the step S4-5 to serve as the jump logic tool, when the current page is an RN page, a bridging tool is actively called, and when page jump occurs each time, the jump logic class is directly called to execute jump judgment and page jump;
the above embodiments do not limit the present invention in any way, and all other modifications and applications that can be made to the above embodiments in equivalent ways are within the scope of the present invention.
Claims (5)
1. A route jump method of multilevel pages based on React Native mixed application is characterized in that each level of Native pages and React Native pages are uniquely identified by short routes, the Native pages and the React Native pages are registered in a routing table by the short routes, the page cross-level positioning and jump are realized by verifying the short routes in a page jump request URL and combining with the judgment of page types on the basis of not increasing or even reducing manual code compiling, and later, the page jump rule change of the webpage only needs to maintain the routing table without considering the increase of page jump codes, and the specific steps comprise:
step 1: the method comprises the steps that webpage pages of all levels in the hybrid application are registered in a routing table in a mode of registering a short route, the webpage pages comprise a Native page and a read Native page, namely an RN page, and the short route is a unique address identifier of the webpage page; based on the registered short routes in the routing table, storing the mapping relation between the short routes of the pages of each level into a third-party route jump system, wherein the mapping relation is the jump relation between the original pages of different levels and the RN pages of different levels;
the routing table and the routing skip system are configured on a native mobile application platform, namely a native terminal, and the native terminal is a page set general name developed by Android and IOS native technologies; the route skipping system selects an android terminal ARouter and an IOS terminal MGJRouter according to an operating system of the mobile application; executing a jump action of jumping to a native page or an opposite jump action by calling a third-party route jump system;
step 2: the method comprises the steps that a read Native end, namely an RN end, monitors an RN page jump execution notice of a route jump system, and when the RN page jump execution notice is monitored, a current page calls a read-Navigation navigator, and page operation is executed in an RN page stack and page jump operation is implemented according to the jump type of an RN page analyzed from a routing table of the route jump system; the skip type is defined according to a route skip method provided by a read-Navigation navigator;
and step 3: the RN end establishes a data transmission channel between the RN end and the primary end by calling a bridging method, and writes an interface of the calling step 4 into the bridging method;
and 4, step 4: acquiring a jump request initiated by a current page, analyzing a jump address URL of a target page, and positioning and jumping the page according to the type of the target page by verifying the validity of the URL and whether the page is registered or not and judging the jump logic for identifying the type of the current page and the type of the target page;
if so, directly calling the route skipping system in the step 1, directly positioning to a target page according to the mapping relation between short chains of the page route, and executing skipping; if so, jumping to an RN page, when the current page is a primary page, newly adding 1 RN page stack, and adding a target page in the page stack; and when the current page is the RN page, calling a read-Navigation navigator according to the step 2 to execute page operation on the RN page stack where the current page is located.
2. The read Native based hybrid application multi-level page route hopping method as claimed in claim 1, wherein: in the step 1, the two-dimensional code is also registered in the routing table in a short route chain form, and the short route chain of the two-dimensional code is acquired by scanning the code.
3. The read Native based hybrid application multi-level page route hopping method as claimed in claim 2, wherein: the jump type in the step 2 specifically comprises push jump, place jump and navigator jump, and the corresponding page operation comprises page addition, page replacement and page traversal;
the page is newly added: a target RN page is newly added at the stack top of the RN page stack;
and the page replacement comprises the following steps: directly replacing the current page in the RN page stack;
the page traversal: traversing a target page in the RN page stack, if the target page exists, directly jumping to the target page and pushing out all RN pages above the target page, and if the target page does not exist in the RN page stack, adding a target RN page at the top of the stack and jumping;
and (3) compiling the monitoring event in the step (2) into a high-order component, configuring the high-order component at the RN end, and inheriting the high-order component by all RN pages.
4. The read Native based hybrid application multi-level page route hopping method as claimed in claim 3, wherein: the step 4 specifically includes the steps of,
step 4-1: acquiring a page jump request URL initiated by a current page, verifying the validity of the URL, and directly refusing jump access if the URL is illegal; if the process is legal, turning to the step 4-2:
step 4-2: analyzing the URL to obtain a short route, judging whether a page is registered in the routing table in the step 1 according to whether the short route is matched with the short route in the routing table, and if the matching fails, creating a new window to load an HTML5 page corresponding to the URL; if the matching is successful, turning to the step 4-3;
step 4-3: calling a routing table, inquiring whether to record the jump limitation of the target page according to the short chain of the route, and if so, executing preorder limitation operation according to the limitation content; if not, executing step 3-4;
step 4-4: identifying the type of a target page, inquiring the type of the target page recorded by the short route chain in the routing table, if the target page is marked as a primary page in the routing table, directly calling the route skipping system in the step 1 to skip directly; if the target page is marked as the RN page in the routing table, executing the step 4-5;
and 4-5: identifying the type of the current page, if the current page is a native page, creating an RN page stack, and directly placing a target RN page in the RN page stack to execute jumping; if the current page is the RN page, a page jump execution notice is created, and step 2 is executed.
5. The read Native based hybrid application multi-level page route hopping method as claimed in claim 4, wherein: and (4) writing the global class of the jump logic from the step 4-1 to the step 4-5 and configuring the global class at a native end, and directly calling the jump logic class to execute jump judgment and page jump when a page jumps.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010106359.2A CN111258559B (en) | 2020-02-21 | 2020-02-21 | Hybrid application multi-level page routing skip method based on fact Native |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010106359.2A CN111258559B (en) | 2020-02-21 | 2020-02-21 | Hybrid application multi-level page routing skip method based on fact Native |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111258559A true CN111258559A (en) | 2020-06-09 |
| CN111258559B CN111258559B (en) | 2022-07-19 |
Family
ID=70945701
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010106359.2A Active CN111258559B (en) | 2020-02-21 | 2020-02-21 | Hybrid application multi-level page routing skip method based on fact Native |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111258559B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112162677A (en) * | 2020-09-11 | 2021-01-01 | 北京浪潮数据技术有限公司 | Menu page label positioning method, device, equipment and storage medium |
| CN112417337A (en) * | 2020-11-27 | 2021-02-26 | 贝壳技术有限公司 | Page jump implementation method and device, electronic equipment and storage medium |
| CN112905933A (en) * | 2021-01-29 | 2021-06-04 | 挂号网（杭州）科技有限公司 | Page jump method and device, electronic equipment and storage medium |
| CN112988284A (en) * | 2021-05-13 | 2021-06-18 | 太平金融科技服务（上海）有限公司 | Application program starting method and device, computer equipment and storage medium |
| CN113064583A (en) * | 2021-04-14 | 2021-07-02 | 深圳市活力天汇科技股份有限公司 | Multi-level page routing skip method and device, computer equipment and storage medium |
| CN113296859A (en) * | 2021-04-28 | 2021-08-24 | 青岛海尔科技有限公司 | Page loading method and device, storage medium and electronic device |
| CN114567585A (en) * | 2022-02-28 | 2022-05-31 | 上海掌门科技有限公司 | Method and equipment for determining routing level information of routing equipment |
| CN114924816A (en) * | 2022-04-08 | 2022-08-19 | 青岛海尔科技有限公司 | Page jump method, storage medium and electronic device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109740090A (en) * | 2018-12-25 | 2019-05-10 | 南京天溯自动化控制系统有限公司 | A kind of android page return jump method and its system based on mixed developing |
| CN110347942A (en) * | 2019-05-31 | 2019-10-18 | 深圳壹账通智能科技有限公司 | Method for page jump, device, storage medium and computer equipment |
| CN110555181A (en) * | 2018-03-30 | 2019-12-10 | 武汉斗鱼网络科技有限公司 | Page cross-skip method and device |
-
2020
- 2020-02-21 CN CN202010106359.2A patent/CN111258559B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110555181A (en) * | 2018-03-30 | 2019-12-10 | 武汉斗鱼网络科技有限公司 | Page cross-skip method and device |
| CN109740090A (en) * | 2018-12-25 | 2019-05-10 | 南京天溯自动化控制系统有限公司 | A kind of android page return jump method and its system based on mixed developing |
| CN110347942A (en) * | 2019-05-31 | 2019-10-18 | 深圳壹账通智能科技有限公司 | Method for page jump, device, storage medium and computer equipment |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112162677A (en) * | 2020-09-11 | 2021-01-01 | 北京浪潮数据技术有限公司 | Menu page label positioning method, device, equipment and storage medium |
| CN112417337A (en) * | 2020-11-27 | 2021-02-26 | 贝壳技术有限公司 | Page jump implementation method and device, electronic equipment and storage medium |
| CN112905933A (en) * | 2021-01-29 | 2021-06-04 | 挂号网（杭州）科技有限公司 | Page jump method and device, electronic equipment and storage medium |
| CN113064583A (en) * | 2021-04-14 | 2021-07-02 | 深圳市活力天汇科技股份有限公司 | Multi-level page routing skip method and device, computer equipment and storage medium |
| CN113064583B (en) * | 2021-04-14 | 2024-04-16 | 深圳市活力天汇科技股份有限公司 | Multistage page route jump method, device, computer equipment and storage medium |
| CN113296859A (en) * | 2021-04-28 | 2021-08-24 | 青岛海尔科技有限公司 | Page loading method and device, storage medium and electronic device |
| CN112988284A (en) * | 2021-05-13 | 2021-06-18 | 太平金融科技服务（上海）有限公司 | Application program starting method and device, computer equipment and storage medium |
| CN114567585A (en) * | 2022-02-28 | 2022-05-31 | 上海掌门科技有限公司 | Method and equipment for determining routing level information of routing equipment |
| CN114567585B (en) * | 2022-02-28 | 2024-05-03 | 上海掌门科技有限公司 | Method and device for determining routing level information of routing device |
| CN114924816A (en) * | 2022-04-08 | 2022-08-19 | 青岛海尔科技有限公司 | Page jump method, storage medium and electronic device |
| CN114924816B (en) * | 2022-04-08 | 2023-06-09 | 青岛海尔科技有限公司 | Page jump method, storage medium and electronic device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111258559B (en) | 2022-07-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111258559B (en) | Hybrid application multi-level page routing skip method based on fact Native | |
| CN107870821B (en) | Cross-platform calling method and system for application program | |
| WO2021073636A1 (en) | Code conflict resolution system and method, devices, apparatus, and medium | |
| CN102567516B (en) | Script loading method and device | |
| US20090285382A1 (en) | Method, device and system for routing | |
| CN106874035B (en) | Method for updating application (app) built-in H5 and framework thereof | |
| CN1784883A (en) | System and method for handshaking between wireless devices and servers | |
| CN110636537B (en) | TTCN-3-based multi-card mobile terminal test system and method thereof | |
| CN106294113A (en) | A kind of creation method based on programmable type testing service and device | |
| CN104021082A (en) | Remote debugging method and device for browser | |
| CN110308880B (en) | Log printing method, system, computer device and computer readable storage medium | |
| CN106775781B (en) | Method and device for reducing application installation packages and electronic equipment | |
| CN101937356A (en) | Method for compiling WebKit browser and device thereof | |
| CN111722841A (en) | Software componentization implementation method under IOS platform | |
| CN105867862A (en) | Application program interface display method and device | |
| CN103607702A (en) | A method and system for carrying out communication among different platforms in short message service | |
| CN103379145B (en) | The method, apparatus and system of information processing | |
| WO2016173070A1 (en) | Terminal network searching method and terminal | |
| CN106330519A (en) | Communication method and system for messages among network management systems | |
| CN110175043A (en) | The generation method and device of protocol interface code release update notification | |
| CN114201399A (en) | Method, device, equipment and storage medium for identifying influence range of program change | |
| CN111770487B (en) | Access Point Name (APN) information configuration method, equipment and medium | |
| CN110958160B (en) | Website detection method, device and system and computer readable storage medium | |
| US20060053102A1 (en) | Method of executing java application and mobile communication terminal using the same | |
| CN113821246A (en) | Software non-inductive incremental updating method, device, system and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |