CN111488151B - Page interaction method and device among Android modules - Google Patents
Page interaction method and device among Android modules Download PDFInfo
- Publication number
- CN111488151B CN111488151B CN202010309560.0A CN202010309560A CN111488151B CN 111488151 B CN111488151 B CN 111488151B CN 202010309560 A CN202010309560 A CN 202010309560A CN 111488151 B CN111488151 B CN 111488151B
- Authority
- CN
- China
- Prior art keywords
- page
- data
- class name
- android
- component
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a method and a device for page interaction among Android modules, wherein the method comprises the following steps: configuring meta-data labels for pages in Android management xml in the Android module; determining a mapping relation between the class name and the page identifier of the target page according to the class name and the page identifier in the meta-data tag of the target page to be interacted; acquiring an instruction to be skipped, and determining whether data information to be transferred exists; determining the class name of the target page to be skipped according to the mapping relation and the page identification in the current page if the data information to be transferred does not exist; and determining the Intent component according to the class name of the target page to be skipped, and completing the communication between Android modules. According to the application, by setting the mapping relation between the class name of the target page and the page identifier, after the class name of the target page to be jumped is determined according to the page identifier in the current page to obtain the Intnt component, the Intnt component can be utilized to call the jumped page to complete communication among modules, so that the communication method is simple to use, does not need to introduce a three-party library, does not influence the compiling time, is convenient to configure and has strong maintainability.
Description
Technical Field
The application relates to the field of computer development, in particular to a method and a device for page interaction among Android modules.
Background
With the gradual expansion of App functional modules, in order to better support the development iteration requirement of App matrix, componentized architecture has become more and more popular. In the modular architecture, the service modules are decoupled and cannot directly depend on code, but there is always a real interaction requirement between the modules, for example, a mall module needs to call up the function of the login module.
On the premise of large Android componentization architecture, in order to achieve the purpose of inter-module communication, the current common scheme is as follows: implicit call-up, reflex call-up, and third party open source schemes represented by aroter. However, all three schemes have corresponding disadvantages:
1. implicit call-up: the scheme is based on implicit Intent of Android, and does not explicitly specify a target page, but allows the system to decide which page to call according to the filter. The disadvantage of this solution is that it requires to configure each page with a different filter and filtering conditions, which is cumbersome to maintain and prone to errors, especially not conducive to interaction and collaborative development between the individual modules. 2. Reflection tuning: the scheme needs to obtain the class of the target page by reflection according to the appointed class name, and then the jump is completed. This solution has mainly two drawbacks: firstly, because of the reflection, the system has some influence on performance, secondly, the scheme needs to explicitly specify the complete class name of the target page, and different modules are always mutually unknown, and on the other hand, once a certain module modifies the package name or class name, if the synchronous starting is not timely carried out, the scheme can be invalid. 3. Third party open source scheme represented by aroter: the implementation scheme of the framework is generally based on annotation, the annotation is added to a target page needing to be jumped, the annotation comprises a module path and a name, the annotation is analyzed in the compiling period, java files maintaining a route mapping relation are generated through tools such as Java Poet, and subsequent module communication can be completed through the mapping relation. However, the scheme needs to introduce a third party library in code engineering, which can negatively affect the APK package; influence the compiling speed of APK; the third party library has higher integration cost and upper hand cost, and is not beneficial to maintenance and expansion.
Disclosure of Invention
In order to solve the problems in the background technology, the application provides a method and a device for page interaction between Android modules.
In a first aspect, the present application provides a method for page interaction between Android modules, where the method includes:
configuring meta-data labels for pages in Android management xml in the Android module;
determining a mapping relation between the class name and the page identifier of the target page according to the class name and the page identifier in the meta-data tag of the target page to be interacted;
acquiring an instruction to be skipped, and determining whether data information to be transferred exists;
determining the class name of the target page to be skipped according to the mapping relation and the page identification in the current page if the data information to be transferred does not exist;
and determining the Intent component according to the class name of the target page to be skipped, and completing the communication between Android modules.
Further, according to the class name of the target page to be skipped, completing the communication between the Android modules includes:
obtaining an Intent component according to the class name of the target page to be skipped;
and calling the page to be jumped by utilizing the Intint component to complete the communication between the Android modules.
Further, obtaining the instruction to be skipped, and determining whether the data information to be transferred exists further includes:
if the data information to be transferred exists, the URL is obtained by utilizing the page jump protocol and the page identification in the current page;
converting the URL into URI format information;
the URI format information is set within the intelt component.
Further, setting the URI format information within the intelt component further includes:
placing the serialized data to be transmitted in a Bundle mechanism;
and the URI format information and the data to be transferred in the Bundle mechanism are arranged in the Intent component together.
Further, the co-setting of the URI format information and the data to be transferred in the Bundle mechanism in the intel component includes:
if the data information to be transmitted is determined to be in the Map format;
converting the URL into URI format information;
splicing the data information to be transmitted with the URI information to obtain spliced first data;
and the spliced first data and the data to be transmitted in the Bundle mechanism are arranged in the Intent component together.
In a second aspect, the present application provides a device for page interaction between Android modules, where the device includes:
the meta-data tag module is configured and used for configuring a meta-data tag for a page in Android management xml in the Android module;
the mapping relation determining module is used for determining the mapping relation between the class name of the target page and the page identifier according to the class name of the target page to be interacted and the page identifier in meta-data tag information;
the jump instruction acquisition module is used for acquiring an instruction to be jumped and determining whether data information to be transferred exists or not;
determining a class name module of the target page to be skipped, wherein the class name module is used for determining that the data information to be transferred does not exist, and determining the class name of the target page to be skipped according to the mapping relation and the page identification in the current page;
and the inter-module communication module is used for determining the Intnt component according to the class name of the target page to be jumped and completing the communication between the Android modules.
Further, the inter-module communication module includes:
the method comprises the steps of determining an Intnt component unit, and obtaining an Intnt component according to the class name of a target page to be jumped;
and the call-up page unit is used for calling up the page to be skipped by utilizing the Intint component and completing the communication among the Android modules.
Further, the jump instruction acquisition module further includes:
the URL obtaining unit is used for obtaining a URL by utilizing a page jump protocol and a page identifier in a current page if the data information to be transferred exists;
a conversion unit for converting the URL into URI format information;
and the unit is arranged in the Intint component and is used for setting the URI format information in the Intint component.
In a third aspect, the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the steps of the method for page interaction between Android modules provided in the first aspect when the program is executed by the processor.
In a fourth aspect, the present application provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method for page interaction between Android modules provided in the first aspect.
According to the method and the device for page interaction between Android modules, provided by the application, by setting the mapping relation between the class names of the target pages and the page identifications, after the class names of the target pages to be jumped are determined to obtain the Intnt component according to the page identifications in the current page, the Intnt component can be utilized to call the jumped pages to complete communication between modules, so that the method and the device are very simple to use, do not need to introduce a three-party library, do not influence APK compiling time, are fast in operation, convenient to configure and high in maintainability.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of a method for page interaction between Android modules according to an embodiment of the present application;
fig. 2 is an overall flow diagram of page interaction between Android modules according to an embodiment of the present application;
FIG. 3 is a block diagram of a device for page interaction between Android modules, which is provided by an embodiment of the application;
fig. 4 is a block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order that those skilled in the art will better understand the present application, a technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate in order to describe the embodiments of the application herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other. The application will be described in detail below with reference to the drawings in connection with embodiments.
On the premise of large Android componentization architecture, in order to achieve the purpose of inter-module communication, the current common scheme is as follows: implicit call-up, reflex call-up, and third party open source schemes represented by aroter. However, all three solutions have corresponding disadvantages, and in order to solve the above problem, an embodiment of the present application provides a method for page interaction between Android modules, as shown in fig. 1, the method includes:
step S101, configuring meta-data labels for pages in Android management xml in an Android module;
step S102, determining the mapping relation between the class name and the page identifier of the target page according to the class name and the page identifier in the meta-data tag of the target page to be interacted;
step S103, obtaining an instruction to be skipped and determining whether data information to be transferred exists;
step S104, determining the class name of the target page to be jumped according to the mapping relation and the page identification in the current page if the data information to be transferred does not exist;
step S105, determining an Intnt component according to the class name of the target page to be jumped, and completing communication among Android modules.
Specifically, a plurality of modules are arranged under an Android architecture, and when the modules communicate, a meta-data tag is generally configured for a page in Android management xml in the modules, wherein the Android management xml is an information description file of the whole application program, and Activity, service, contentProvider and BroadcastReceiver component information contained in the application program are defined. Each application must contain an android management.
And reading all meta-data tags when the APP is started, and acquiring page identifiers in the meta-data tags. The class name of the target page is contained in each page, a mapping relation corresponding to one is found according to the page identification and the class name of the target page, for example, a login interface is taken as an example, and the configuration is carried out for the login page in a login module AndroidManifest.xml:
<meta-data
android:name＝“pageName”
android:value＝“Login”/>；
class name of corresponding page target page: android: name= ", ui. Loginacity", here the page identifier (pageName) is Login, and there is a mapping relationship between Login and loginacity.
And acquiring an instruction to be skipped according to the service request, determining whether data information to be transferred exists or not, if the data information does not need to be transferred, determining the class name of the target page to be skipped according to the mapping relation and the page identification in the current page, determining an Intnt component according to the class name of the target page to be skipped, calling the to be skipped by using the Intnt component, and completing the communication among Android modules. The Intent is mainly used for solving the communication among various components of the Android application.
According to the method for page interaction between Android modules, provided by the embodiment of the application, by setting the mapping relation between the class name of the target page and the page identifier, after the class name of the target page to be jumped is determined to obtain the Intnt component according to the page identifier in the current page, the Intnt component can be utilized to call the jumped page to complete communication between modules, so that the method is very simple to use, does not need to introduce a three-party library, does not influence APK compiling time, and is fast in operation, convenient to configure and high in maintainability.
Based on the content of the above embodiments, as an alternative embodiment: the obtaining the instruction to be skipped, and determining whether the data information to be transferred exists further comprises:
if the data information to be transferred exists, the URL is obtained by utilizing the page jump protocol and the page identification in the current page;
converting the URL into URI format information;
the URI format information is set within the intelt component.
Specifically, the page jump protocol is a schema protocol of the Android system. From the acquisition of the URL using the page jump protocol and the page identification within the current page, e.g., invoking a landing page, a URL similar to this may be constructed: huanbei:// Login, where Login is the moduleName configured above, and huanbei is the schema of App, which can be customized. And converting the URL into URI format information, and setting the URI format information in an Intent component for data transmission.
Based on the content of the above embodiments, as an alternative embodiment: the setting of the URI format information within the Intent component further includes:
placing the serialized data to be transmitted in a Bundle mechanism;
and the URI format information and the data to be transferred in the Bundle mechanism are arranged in the Intent component together.
Specifically, some complex serialized data is placed in a Bundle mechanism, where the Bundle mechanism is a "container" used to transfer the data, and the data stored in the Bundle mechanism exists in the form of key-value (key-value pair). The URI format information and data to be transferred in the Bundle mechanism are arranged in the Intint component together, wherein the URI format information is converted data, and the data in the Bundle mechanism is data with the original format reserved and is analyzed through the Bundle mechanism.
Based on the content of the above embodiments, as an alternative embodiment: the step of jointly setting the URI format information and the data to be transferred in the Bundle mechanism in the Intint component comprises the following steps:
if the data information to be transmitted is determined to be in the Map format;
converting the URL into URI format information;
splicing the data information to be transmitted with the URI information to obtain spliced first data;
and the spliced first data and the data to be transmitted in the Bundle mechanism are arranged in the Intent component together.
Specifically, when it is determined that parameters in Map format are included in data to be transferred, the data in Map format are spliced behind URI information, for example, huanbei:// logink1=v1 & k2=v2, and as first spliced data, the spliced data, that is, the data to be transferred in the example, huanbei:// logink1=v1 & k2=v2 and the Bundle mechanism are jointly arranged in an intelnt component.
Based on the content of the above embodiments, as an alternative embodiment: as shown in fig. 2, fig. 2 is an overall flow chart provided in the embodiment of the present application, and specific steps are as follows:
firstly, configuring < meta-data > tag information of a page in android management.xml of different modules, reading the < meta-data > tag information of the page when the APP is started, acquiring a class name of a target page from an interactive page, acquiring a page identifier from meta-data, obtaining a global mapping table, jumping pages to be jumped according to service requirements, using schema and page identifiers of the current page, constructing a URL, calling the target page based on the URL, transmitting data to be transmitted, judging whether Map format data exist in the data to be transmitted, if so, converting the URL into URI format information, and splicing the Map format data to the URI; if the URL does not exist, the URL is only converted into URI format information, an Intent component is determined according to the class name of the target page to be jumped, the Intent component comprises URI format data and data to be transferred in a Bundle mechanism, the page to be jumped is called according to the Intent component, and communication among Android modules is finished.
According to still another aspect of the present application, referring to fig. 3, fig. 3 is a block diagram of an apparatus for page interaction between Android modules according to an embodiment of the present application. The device is used for completing page interaction among the Android modules provided by the embodiment of the application in the embodiments. Therefore, the description and the definition in the method for page interaction between Android modules provided by the embodiment of the application in the foregoing embodiments can be used for understanding each execution module in the embodiment of the application.
The device comprises:
the configuration meta-data tag module 301 is configured to configure meta-data tags for pages in Android management xml in the Android module;
the mapping relation determining module 302 is configured to determine a mapping relation between a class name and a page identifier of a target page according to the class name and the page identifier in meta-data tag information of the target page to be interacted;
the jump instruction obtaining module 303 is configured to obtain an instruction to be jumped, and determine whether there is data information to be transferred;
the target page class name module 304 is configured to determine that there is no data information to be transferred, and determine a class name of the target page to be skipped according to the mapping relationship and the page identifier in the current page;
the inter-module communication module 305 is configured to determine an Intnt component according to the class name of the target page to be skipped, and complete communication between Android modules.
Specifically, the specific process of implementing the functions of each module in the apparatus of this embodiment may refer to the relevant description in the corresponding method embodiment, which is not repeated herein.
According to the device for page interaction among Android modules, provided by the embodiment of the application, by setting the mapping relation between the class name of the target page and the page identifier, after the class name of the target page to be jumped is determined to obtain the Intnt component according to the page identifier in the current page, the Intnt component can be utilized to call the jumped page to complete communication among the modules, so that the device is very simple to use, does not need to introduce a three-party library, does not influence APK compiling time, and is fast in operation, convenient to configure and high in maintainability.
Based on the content of the above embodiments, as an alternative embodiment: the inter-module communication module includes:
the method comprises the steps of determining an Intnt component unit, and obtaining an Intnt component according to the class name of a target page to be jumped;
and the call-up page unit is used for calling up the page to be skipped by utilizing the Intint component and completing the communication among the Android modules.
Specifically, the specific process of implementing the functions of each module in the apparatus of this embodiment may refer to the relevant description in the corresponding method embodiment, which is not repeated herein.
Based on the content of the above embodiments, as an alternative embodiment: the jump instruction acquisition module further includes:
the URL obtaining unit is used for obtaining a URL by utilizing a page jump protocol and a page identifier in a current page if the data information to be transferred exists;
a conversion unit for converting the URL into URI format information;
and the unit is arranged in the Intint component and is used for setting the URI format information in the Intint component.
Specifically, the specific process of implementing the functions of each module in the apparatus of this embodiment may refer to the relevant description in the corresponding method embodiment, which is not repeated herein.
Fig. 4 is a block diagram of an electronic device according to an embodiment of the present application, as shown in fig. 4, where the device includes: a processor 401, a memory 402, and a bus 403;
wherein the processor 401 and the memory 402 respectively complete communication with each other through the bus 403; the processor 401 is configured to call up program instructions in the memory 402 to execute the method for page interaction between Android modules provided in the foregoing embodiment, for example, includes: configuring meta-data labels for pages in Android management xml in the Android module; determining a mapping relation between the class name and the page identifier of the target page according to the class name and the page identifier in the meta-data tag of the target page to be interacted; acquiring an instruction to be skipped, and determining whether data information to be transferred exists; determining the class name of the target page to be skipped according to the mapping relation and the page identification in the current page if the data information to be transferred does not exist; and determining the Intent component according to the class name of the target page to be skipped, and completing the communication between Android modules.
The embodiment of the application provides a non-transitory computer readable storage medium, on which a computer program is stored, which when executed by a processor, realizes the steps of a method for page interaction between Android modules. Examples include: configuring meta-data labels for pages in Android management xml in the Android module; determining a mapping relation between the class name and the page identifier of the target page according to the class name and the page identifier in the meta-data tag of the target page to be interacted; acquiring an instruction to be skipped, and determining whether data information to be transferred exists; determining the class name of the target page to be skipped according to the mapping relation and the page identification in the current page if the data information to be transferred does not exist; and determining the Intent component according to the class name of the target page to be skipped, and completing the communication between Android modules.
The apparatus embodiments described above are merely illustrative, wherein elements illustrated as separate elements may or may not be physically separate, and elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present application without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on such understanding, the foregoing technical solutions may be embodied essentially or in part in the form of a software product, which may be stored in a computer-readable storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the various embodiments or methods of some parts of the embodiments.
Finally, the principles and embodiments of the present application have been described with reference to specific examples, which are intended to be illustrative only of the methods and core ideas of the present application; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (4)
1. The method for page interaction between Android modules is characterized by comprising the following steps:
configuring meta-data labels for pages in Android management xml in the Android module;
determining a mapping relation between the class name and the page identifier of the target page according to the class name and the page identifier in the meta-data tag of the target page to be interacted;
acquiring an instruction to be skipped, and determining whether data information to be transferred exists;
determining the class name of the target page to be skipped according to the mapping relation and the page identification in the current page if the data information to be transferred does not exist;
determining an Intint component according to the class name of the target page to be jumped, and completing communication among Android modules;
the step of completing the communication between the Android modules according to the class name of the target page to be skipped comprises the following steps:
obtaining an Intint component according to the class name of the target page to be jumped;
the method comprises the steps that an Intint component is utilized to call a page to be jumped, and communication among Android modules is completed;
the obtaining the instruction to be skipped, and determining whether the data information to be transferred exists further includes:
if the data information to be transferred exists, the URL is obtained by utilizing the page jump protocol and the page identification in the current page;
converting the URL into URI format information;
setting the URI format information in an Intent component;
the setting the URI format information in the Intent component further includes:
placing the serialized data to be transmitted in a Bundle mechanism;
the URI format information and data to be transferred in the Bundle mechanism are arranged in an Intent component together;
the commonly setting the URI format information and the data to be transferred in the Bundle mechanism in the Intint component includes:
if the data information to be transmitted is determined to be in the Map format;
converting the URL into URI format information;
splicing the data information to be transmitted with the URI information to obtain spliced first data;
and the spliced first data and the data to be transmitted in the Bundle mechanism are arranged in the Intent component together.
2. An apparatus for page interaction between Android modules, the apparatus comprising:
the meta-data tag module is configured and used for configuring a meta-data tag for a page in Android management xml in the Android module;
the mapping relation determining module is used for determining the mapping relation between the class name of the target page and the page identifier according to the class name of the target page to be interacted and the page identifier in meta-data tag information;
the jump instruction acquisition module is used for acquiring an instruction to be jumped and determining whether data information to be transferred exists or not;
determining a class name module of the target page to be skipped, wherein the class name module is used for determining that the data information to be transferred does not exist, and determining the class name of the target page to be skipped according to the mapping relation and the page identification in the current page;
the inter-module communication module is used for determining an Intnt component according to the class name of the target page to be skipped and completing communication among Android modules;
the inter-module communication module includes:
determining an Intint component unit, which is used for obtaining an Intint component according to the class name of the target page to be skipped;
the call-up page unit is used for calling up a page to be skipped by utilizing the Intent component to complete communication among Android modules;
the jump instruction acquisition module further includes:
the URL obtaining unit is used for obtaining a URL by utilizing a page jump protocol and a page identifier in a current page if the data information to be transferred exists;
a conversion unit for converting the URL into URI format information;
the unit is arranged in the Intint component and is used for arranging the URI format information in the Intint component;
the setting the URI format information in the Intent component further includes:
placing the serialized data to be transmitted in a Bundle mechanism;
the URI format information and data to be transferred in the Bundle mechanism are arranged in an Intent component together;
the commonly setting the URI format information and the data to be transferred in the Bundle mechanism in the Intint component includes:
if the data information to be transmitted is determined to be in the Map format;
converting the URL into URI format information;
splicing the data information to be transmitted with the URI information to obtain spliced first data;
and the spliced first data and the data to be transmitted in the Bundle mechanism are arranged in the Intent component together.
3. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor performs the steps of the method of page interaction between Android modules as claimed in claim 1 when the program is executed by the processor.
4. A non-transitory computer readable storage medium having stored thereon a computer program, which when executed by a processor, performs the steps of the method of page interaction between Android modules as claimed in claim 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010309560.0A CN111488151B (en) | 2020-04-17 | 2020-04-17 | Page interaction method and device among Android modules |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010309560.0A CN111488151B (en) | 2020-04-17 | 2020-04-17 | Page interaction method and device among Android modules |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111488151A CN111488151A (en) | 2020-08-04 |
| CN111488151B true CN111488151B (en) | 2023-09-26 |
Family
ID=71794918
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010309560.0A Active CN111488151B (en) | 2020-04-17 | 2020-04-17 | Page interaction method and device among Android modules |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111488151B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111966939A (en) * | 2020-09-18 | 2020-11-20 | 北京百度网讯科技有限公司 | Page skipping method and device |
| CN115563187B (en) * | 2022-10-17 | 2023-08-04 | 中航信移动科技有限公司 | Data conversion method, storage medium and electronic equipment |
| CN117742865A (en) * | 2023-12-21 | 2024-03-22 | 无忧创想(武汉)信息技术有限公司 | Application program jump method, device, equipment and medium suitable for multiple scenes |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103559065A (en) * | 2013-11-13 | 2014-02-05 | 广东欧珀移动通信有限公司 | Method and system for OTA (Over-the-Air Technology) upgrade |
| WO2018064902A1 (en) * | 2016-10-09 | 2018-04-12 | 中兴通讯股份有限公司 | Method and system for one-click accessing to app designated module |
| CN108121568A (en) * | 2017-11-30 | 2018-06-05 | 五八有限公司 | Arouse method and device, electronic equipment and the readable storage medium storing program for executing of APP |
| CN109597663A (en) * | 2018-09-06 | 2019-04-09 | 北京微播视界科技有限公司 | Page info processing method, device and electronic equipment |
| CN109766082A (en) * | 2017-11-09 | 2019-05-17 | 北京京东尚科信息技术有限公司 | The method and apparatus that the application program page jumps |
| CN109783742A (en) * | 2018-12-14 | 2019-05-21 | 平安科技（深圳）有限公司 | For developing method for page jump, device and the computer equipment of auxiliary |
| WO2019184053A1 (en) * | 2018-03-28 | 2019-10-03 | 华为技术有限公司 | Method and terminal for browsing page of application |
| WO2019228034A1 (en) * | 2018-05-30 | 2019-12-05 | 杭州海康威视数字技术股份有限公司 | Method and apparatus for data synchronization |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7331014B2 (en) * | 2003-05-16 | 2008-02-12 | Microsoft Corporation | Declarative mechanism for defining a hierarchy of objects |
-
2020
- 2020-04-17 CN CN202010309560.0A patent/CN111488151B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103559065A (en) * | 2013-11-13 | 2014-02-05 | 广东欧珀移动通信有限公司 | Method and system for OTA (Over-the-Air Technology) upgrade |
| WO2018064902A1 (en) * | 2016-10-09 | 2018-04-12 | 中兴通讯股份有限公司 | Method and system for one-click accessing to app designated module |
| CN109766082A (en) * | 2017-11-09 | 2019-05-17 | 北京京东尚科信息技术有限公司 | The method and apparatus that the application program page jumps |
| CN108121568A (en) * | 2017-11-30 | 2018-06-05 | 五八有限公司 | Arouse method and device, electronic equipment and the readable storage medium storing program for executing of APP |
| WO2019184053A1 (en) * | 2018-03-28 | 2019-10-03 | 华为技术有限公司 | Method and terminal for browsing page of application |
| WO2019228034A1 (en) * | 2018-05-30 | 2019-12-05 | 杭州海康威视数字技术股份有限公司 | Method and apparatus for data synchronization |
| CN109597663A (en) * | 2018-09-06 | 2019-04-09 | 北京微播视界科技有限公司 | Page info processing method, device and electronic equipment |
| CN109783742A (en) * | 2018-12-14 | 2019-05-21 | 平安科技（深圳）有限公司 | For developing method for page jump, device and the computer equipment of auxiliary |
Non-Patent Citations (1)
| Title |
|---|
| 周广清 ; 刘建平 ; .ASP.NET页面跳转和参数传递.医疗卫生装备.2015,(03),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111488151A (en) | 2020-08-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111488151B (en) | Page interaction method and device among Android modules | |
| CN110806863A (en) | Interface document generation method and device, electronic equipment and storage medium | |
| CN109739523B (en) | Application program packaging method and device, storage medium and terminal | |
| CN103077024B (en) | A kind of device and method supporting the on-demand customization of SaaS application flow and operation | |
| US8209341B2 (en) | Configurable transformation macro | |
| US8756407B2 (en) | Configuration rule prototyping tool | |
| CN110351325B (en) | Data processing method and related equipment | |
| CN105138448A (en) | Method and device for page test at front end | |
| US20060235928A1 (en) | System and method for creating a mapping document for binding messages between an application and an associated backend server | |
| US10817284B2 (en) | Melding of mediation flow service component architecture (SCA) components | |
| WO2019085290A1 (en) | Test preparation method and apparatus, terminal device, and storage medium | |
| CN108965375B (en) | Service call proxy control system, method, server and readable storage medium | |
| CN108810164A (en) | A kind of device for supporting the on-demand customization of SaaS application flows and operation | |
| CN110109671B (en) | Webpack label size and style conversion method and device | |
| Bocciarelli et al. | A SaaS-based automated framework to build and execute distributed simulations from SysML models | |
| CN107239265B (en) | Binding method and device of Java function and C function | |
| CN108460002A (en) | Affiliate's automatic butt method, apparatus, equipment and storage medium | |
| CN110825622A (en) | Software testing method, device, equipment and computer readable medium | |
| CN115934093A (en) | Applet cross-terminal application method, related device and computer storage medium | |
| CN109543122B (en) | Content synchronization method, device, storage medium and electronic device | |
| CN109426571B (en) | Method, system, storage medium, processor and apparatus for function call and data access | |
| WO2020150009A1 (en) | Profile data store automation via bots | |
| US11983516B2 (en) | Method for executing code portions on execution resources | |
| CN102591697B (en) | Perform user space formula method and use its computer system | |
| CN116719525A (en) | Configuration information generation method and device, electronic equipment and computer 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 |