CN111488151A - Method and device for page interaction among Android modules - Google Patents
Method and device for page interaction among Android modules Download PDFInfo
- Publication number
- CN111488151A CN111488151A CN202010309560.0A CN202010309560A CN111488151A CN 111488151 A CN111488151 A CN 111488151A CN 202010309560 A CN202010309560 A CN 202010309560A CN 111488151 A CN111488151 A CN 111488151A
- Authority
- CN
- China
- Prior art keywords
- page
- data
- class name
- android
- determining
- 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/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 invention provides a method and a device for page interaction between Android modules, wherein the method comprises the following steps: configuring a meta-data tag for a page in Android Manifest.xml in an Android module; determining a mapping relation between the class name and the page identification of the target page according to the class name of the target page to be interacted and the page identification in the meta-data label; acquiring a command to be jumped, and determining whether data information to be transmitted exists or not; determining the class name of a 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; and determining an Intent component according to the class name of the target page to be jumped, and completing the communication between the Android modules. According to the method, the mapping relation between the class name and the page identifier of the target page is set, so that after the class name of the target page to be jumped is determined to obtain the Intent component according to the page identifier in the current page, the jump page can be called by the Intent component to complete communication between modules, the method is simple to use, does not need to introduce a three-party library, does not influence compiling time, is convenient to configure, and is high in maintainability.
Description
Technical Field
The invention 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 function modules, in order to better support the development iteration requirement of App matrixes, the componentized architecture is more and more popular. In a modular architecture design, business modules are decoupled and cannot be directly depended on through codes, but interaction requirements often exist among the modules, for example, a mall module needs to invoke the function of a login module.
On the premise of Android componentization architecture, in order to achieve the purpose of inter-module communication, the currently common schemes include: implicit tune-up, reflex tune-up, and third party open source solutions typified by ARouter. However, the above three schemes all have corresponding disadvantages:
1. implicit recall: the scheme is based on the implicit Intent of Android, and the system determines which page to call according to the filter instead of explicitly specifying the target page. The scheme has the defects that filters and filtering conditions which are different from each other need to be configured for each page, the maintenance is troublesome, errors are easy to occur, and the interaction and the collaborative development among independent modules are particularly not facilitated. 2. Reflection turning-up: according to the scheme, the class of the target page is obtained by reflection according to the specified class name, and then jumping is completed. This solution has two main drawbacks: firstly, the system has some influence on performance because of reflection, secondly, the scheme needs to explicitly specify the complete class name of the target page, different modules are often not known to each other, and on the other hand, once a module modifies the package name or the class name, if the module does not synchronously start in time, the scheme will fail. 3. A third-party open source scheme represented by ARouter: the implementation scheme of the frame is usually 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 during compiling, a Java file maintaining a routing mapping relation is generated through a JavaPoet and other tools, and subsequent module communication can be completed through the mapping relation. However, the scheme needs to introduce a third-party library into code engineering, and can generate negative influence on the APK inclusion volume; influence the compilation speed of the APK; the integration cost and the cost of the third-party library are high, and maintenance and expansion are not facilitated.
Disclosure of Invention
In order to solve the problems in the background art, the invention provides a method and a device for page interaction between Android modules.
In a first aspect, the invention provides a method for page interaction between Android modules, which includes:
configuring a meta-data tag for a page in Android Manifest.xml in an Android module;
determining a mapping relation between the class name and the page identification of the target page according to the class name of the target page to be interacted and the page identification in the meta-data label;
acquiring a command to be jumped, and determining whether data information to be transmitted exists or not;
determining the class name of a 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;
and determining an Intent component according to the class name of the target page to be jumped, and completing the communication between the Android modules.
Further, according to the class name of the target page to be jumped, completing the communication between the Android modules comprises the following steps:
obtaining an Intent component according to the class name of the target page to be skipped;
and calling the page to be jumped by using the Intent component to complete the communication between the Android modules.
Further, obtaining the instruction to be skipped and determining whether the data information to be transmitted exists further includes:
if the data information to be transmitted is determined to exist, UR L is obtained by using a page jump protocol and a page identifier in a current page;
converting UR L into URI format information;
the URI format information is set in the Intent component.
Further, setting the URI format information in the Intent component further includes:
placing the serialized data to be transmitted into a Bundle mechanism;
and setting the URI format information and the data to be transmitted in the Bundle mechanism in an Intent component together.
Further, the step of setting the URI format information and the data to be transmitted in the Bundle mechanism together in the Intent component includes:
if the data information to be transmitted is determined to be in a Map format;
then UR L is converted to URI format information;
splicing the data information to be transmitted with the URI information to obtain spliced first data;
and setting the spliced first data and the data to be transmitted in the Bundle mechanism in the Intent component together.
In a second aspect, the present invention provides a device for page interaction between Android modules, where the device includes:
configuring a meta-data tag module for configuring a meta-data tag for a page in Android Manifest.xml in the Android module;
the mapping relation determining module is used for determining the mapping relation between the class name and the page identifier of the target page according to the class name of the target page to be interacted and the page identifier in the meta-data tag information;
the jump instruction acquisition module is used for acquiring the instruction to be jumped and determining whether the data information to be transmitted exists or not;
the system comprises a module for determining the class name of a target page to be skipped, a module for determining the class name of the target page to be skipped if the data information to be transmitted does not exist, and a module for determining the class name of the target page to be skipped according to the mapping relation and the page identifier in the current page;
and the inter-module communication module is used for determining the Intent component according to the class name of the target page to be jumped and finishing the communication between the Android modules.
Further, the inter-module communication module includes:
determining an Intent component unit, and obtaining an Intent component according to the class name of a target page to be skipped;
and the page turning-up and jumping unit is used for calling up the page to be jumped by using the Intent component to complete the communication between the Android modules.
Further, the jump instruction obtaining module further includes:
an UR L obtaining unit, configured to, if it is determined that there is data information to be transferred, obtain UR L by using a page jump protocol and a page identifier in a current page;
a conversion unit for converting UR L into URI format information;
and the unit is arranged in the Intent component and is used for setting the URI format information in the Intent component.
In a third aspect, the present invention provides an electronic device, which includes a memory, a processor, and a computer program that is stored in the memory and is 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 executing the program.
In a fourth aspect, the present invention provides a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program, 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 the Android modules, the mapping relation between the class name of the target page and the page identifier is set, so that after the class name of the target page to be skipped is determined according to the page identifier in the current page to obtain the Intent component, the Intent component can be used for calling the jump page to complete communication between the modules, and therefore 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 quick to operate, convenient to configure and strong in maintainability.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for page interaction between Android modules according to an embodiment of the present invention;
fig. 2 is a schematic overall flow chart of page interaction between Android modules according to an embodiment of the present invention;
fig. 3 is a block diagram of a device for page interaction between Android modules according to an embodiment of the present invention;
fig. 4 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be used. 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 the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
On the premise of Android componentization architecture, in order to achieve the purpose of inter-module communication, the currently common schemes include: implicit tune-up, reflex tune-up, and third party open source solutions typified by ARouter. However, the three schemes all have corresponding disadvantages, and in order to solve the above problems, an embodiment of the present invention provides a method for page interaction between Android modules, as shown in fig. 1, the method includes:
s101, configuring a meta-data tag for a page in Android Manifest.xml in an Android module;
step S102, determining a mapping relation between the class name and the page identification of the target page according to the class name of the target page to be interacted and the page identification in the meta-data label;
step S103, acquiring a command to be jumped, and determining whether data information to be transmitted exists;
step S104, determining that the data information to be transmitted does not exist, and determining the class name of the target page to be jumped according to the mapping relation and the page identification in the current page;
and S105, determining an Intent component according to the class name of the target page to be jumped, and completing the communication between the Android modules.
Specifically, a plurality of modules are arranged under an Android architecture, in the embodiment of the invention, when the modules communicate, a meta-data tag is usually configured on a page in an Android management.xml in the module, wherein the Android management.xml is an information description file of the whole application program and defines Activity, Service, ContentProvider and broadcastupdate component information contained in the application program. Xml files must be contained under the root directory for each application, and the file name cannot be modified.
And reading all meta-data tags when the APP is started, and acquiring page identifications in the meta-data tags. Each page contains the class name of the target page, and a one-to-one mapping relation is found according to the page identifier and the class name of the target page, for example, a login interface is taken as an example, and the mapping relation is configured for the login page in a login module android manifest.
<meta-data
android:name＝“pageName”
android:value＝“Login”/>；
The class name of the corresponding page target page is android, name is ui, L online activity, the page identifier (pageName) is L online, and mapping relationship exists between L online and L online activity.
And acquiring a command to be jumped according to the service request, determining whether the data information to be transferred exists or not, and if the data information does not need to be transferred, determining the class name of the target page to be jumped according to the mapping relation and the page identifier in the current page, determining the Intent component according to the class name of the target page to be jumped, calling the target page to be jumped by using the Intent component, and completing the communication between the Android modules. The Intent is mainly to solve 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 invention, 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 skipped is determined to obtain the Intent component according to the page identifier in the current page, the jump page can be called by the Intent component to complete communication between the 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, is quick to operate, is convenient to configure, and has strong maintainability.
Based on the content of the above embodiments, as an alternative embodiment: acquiring a to-be-jumped instruction, and determining whether data information to be transmitted exists further comprises:
if the data information to be transmitted is determined to exist, UR L is obtained by using a page jump protocol and a page identifier in a current page;
converting UR L into URI format information;
the URI format information is set in the Intent component.
According to the method, a UR L is obtained by utilizing a page jump protocol and page identification in a current page, for example, a login page is called, so that a UR L, a huangbei:// L, wherein L, the huangbei is the above configured moduleName, the huangbei is App's scheme, and the UR L is converted into URI format information and then is arranged in an Intent component for data transmission.
Based on the content of the above embodiments, as an alternative embodiment: setting the URI format information in the Intent component further comprises:
placing the serialized data to be transmitted into a Bundle mechanism;
and setting the URI format information and the data to be transmitted in the Bundle mechanism in an Intent component together.
Specifically, some complex serialized data is placed in a Bundle mechanism, wherein the Bundle mechanism is a "container" for transferring data, and the data stored in the Bundle mechanism exists in the form of key-value pairs. The URI format information and the data to be transmitted in the Bundle mechanism are arranged in the Intent component together, wherein the URI format information is converted data, and the data in the Bundle mechanism is data with original format and is analyzed through the Bundle mechanism.
Based on the content of the above embodiments, as an alternative embodiment: the method for setting the URI format information and the data to be transmitted in the Bundle mechanism in the Intent component comprises the following steps:
if the data information to be transmitted is determined to be in a Map format;
then UR L is converted to URI format information;
splicing the data information to be transmitted with the URI information to obtain spliced first data;
and setting the spliced first data and the data to be transmitted in the Bundle mechanism in the Intent component together.
Specifically, when it is determined that the data to be transmitted contains parameters in the Map format, the data in the Map format is spliced behind URI information, for example, huangbei:// login? k1 ═ v1& k2 ═ v2, as the first data after splicing, the data after splicing, that is, huangbei:// login? The k1 v1& k2 v2 and the data to be transmitted in the Bundle mechanism are commonly arranged in the Intent component.
Based on the content of the above embodiments, as an alternative embodiment: as shown in fig. 2, fig. 2 is a schematic overall flow chart provided by the embodiment of the present invention, and the specific steps are as follows:
starting, configuring a < meta-data > tag for a page in Android Manifest.xml of different modules, reading < meta-data > tag information of the page when APP starts, acquiring class names of target pages from interactive pages, acquiring page identifiers from meta-data, acquiring a global mapping table, jumping to-be-jumped pages according to business requirements, using scheme and the page identifiers of the current pages, constructing UR L, calling the target pages based on UR L, transferring data to be transferred, judging whether Map format data exist in the data to be transferred, converting UR L into URI format information if the Map format data exist, splicing the Map format data after the URI, converting UR L into URI format information if the Map format data do not exist, determining an Intent component according to the class names of the target pages to be transferred, wherein the Intent component comprises the URI format data and the data to be transferred in a Bundle mechanism, starting the Android pages according to the Intent component, and finishing communication between Android modules, and ending.
According to another aspect of the present invention, an apparatus for page interaction between Android modules is provided in an embodiment of the present invention, referring to fig. 3, where fig. 3 is a block diagram of the apparatus for page interaction between Android modules provided in the embodiment of the present invention. The device is used for completing page interaction between the Android modules provided by the embodiment of the invention in the embodiments. Therefore, the description and definition in the method for page interaction between Android modules provided in the embodiments of the present invention in the foregoing embodiments may be used for understanding each execution module in the embodiments of the present invention.
The device includes:
a meta-data tag configuration module 301, configured to configure a meta-data tag for a page in Android manifest.xml in the Android module;
the mapping relationship determining module 302 is configured to determine a mapping relationship between a class name and a page identifier of a target page according to the class name of the target page to be interacted and the page identifier in the meta-data tag information;
a jump instruction obtaining module 303, configured to obtain an instruction to be jumped, and determine whether data information to be transmitted exists;
a module 304 for determining the class name of the target page to be skipped, configured to determine that there is no data information to be transferred, and determine the class name of the target page to be skipped according to the mapping relationship and the page identifier in the current page;
and the inter-module communication module 305 is used for determining an Intent component according to the class name of the target page to be skipped to complete the communication between the Android modules.
Specifically, the specific process of each module in the apparatus of this embodiment to implement its function may refer to the related description in the corresponding method embodiment, and is not described herein again.
According to the device for page interaction between Android modules, provided by the embodiment of the invention, 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 skipped is determined to obtain the Intent component according to the page identifier in the current page, the jump page can be called by the Intent component to complete the communication between the modules, so that the device is very simple to use, does not need to introduce a three-party library, does not influence the APK compiling time, is quick to operate, is convenient to configure, and has strong maintainability.
Based on the content of the above embodiments, as an alternative embodiment: the inter-module communication module includes:
determining an Intent component unit, and obtaining an Intent component according to the class name of a target page to be skipped;
and the page turning-up and jumping unit is used for calling up the page to be jumped by using the Intent component to complete the communication between the Android modules.
Specifically, the specific process of each module in the apparatus of this embodiment to implement its function may refer to the related description in the corresponding method embodiment, and is not described herein again.
Based on the content of the above embodiments, as an alternative embodiment: the jump instruction obtaining module further comprises:
an UR L obtaining unit, configured to, if it is determined that there is data information to be transferred, obtain UR L by using a page jump protocol and a page identifier in a current page;
a conversion unit for converting UR L into URI format information;
and the unit is arranged in the Intent component and is used for setting the URI format information in the Intent component.
Specifically, the specific process of each module in the apparatus of this embodiment to implement its function may refer to the related description in the corresponding method embodiment, and is not described herein again.
Fig. 4 is a block diagram of an electronic device according to an embodiment of the present invention, and as shown in fig. 4, the electronic device includes: a processor 401, a memory 402, and a bus 403;
the processor 401 and the memory 402 respectively complete communication with each other through the bus 403; the processor 401 is configured to invoke the program instructions in the memory 402 to execute the method for page interaction between Android modules provided in the foregoing embodiment, for example, the method includes: configuring a meta-data tag for a page in Android Manifest.xml in an Android module; determining a mapping relation between the class name and the page identification of the target page according to the class name of the target page to be interacted and the page identification in the meta-data label; acquiring a command to be jumped, and determining whether data information to be transmitted exists or not; determining the class name of a 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; and determining an Intent component according to the class name of the target page to be jumped, and completing the communication between the Android modules.
The embodiment of the invention provides a non-transitory computer readable storage medium, wherein a computer program is stored on the non-transitory computer readable storage medium, and the steps of the method for realizing page interaction between Android modules are realized when the computer program is executed by a processor. Examples include: configuring a meta-data tag for a page in Android Manifest.xml in an Android module; determining a mapping relation between the class name and the page identification of the target page according to the class name of the target page to be interacted and the page identification in the meta-data label; acquiring a command to be jumped, and determining whether data information to be transmitted exists or not; determining the class name of a 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; and determining an Intent component according to the class name of the target page to be jumped, and completing the communication between the Android modules.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods of the various embodiments or some parts of the embodiments.
Finally, the principle and the implementation of the present invention are explained by applying the specific embodiments in the present invention, and the above description of the embodiments is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (10)
1. A method for page interaction between Android modules is characterized by comprising the following steps:
configuring a meta-data tag for a page in Android Manifest.xml in an Android module;
determining a mapping relation between the class name and the page identification of the target page according to the class name of the target page to be interacted and the page identification in the meta-data label;
acquiring a command to be jumped, and determining whether data information to be transmitted exists or not;
determining the class name of a 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;
and determining an Intent component according to the class name of the target page to be jumped, and completing the communication between the Android modules.
2. The method according to claim 1, wherein the completing the communication between the Android modules according to the class name of the target page to be jumped comprises:
obtaining an Intent component according to the class name of the target page to be skipped;
and calling the page to be jumped by using the Intent component to complete the communication between the Android modules.
3. The method of claim 1, wherein the obtaining the instruction to be jumped to determine whether the data information to be transferred exists further comprises:
if the data information to be transmitted is determined to exist, UR L is obtained by using a page jump protocol and a page identifier in a current page;
converting UR L into URI format information;
and setting the URI format information in an Intent component.
4. The method of claim 3, wherein placing the URI format information within an Intent component further comprises:
placing the serialized data to be transmitted into a Bundle mechanism;
and setting the URI format information and the data to be transmitted in the Bundle mechanism in an Intent component together.
5. The method of claim 4, wherein the commonly arranging the URI format information and the data to be transferred in the Bundle mechanism in the Intent component comprises:
if the data information to be transmitted is determined to be in a Map format;
converting said UR L into URI format information;
splicing the data information to be transmitted with the URI information to obtain spliced first data;
and setting the spliced first data and the data to be transmitted in the Bundle mechanism in the Intent component together.
6. An apparatus for page interaction between Android modules, the apparatus comprising:
configuring a meta-data tag module for configuring a meta-data tag for a page in Android Manifest.xml in the Android module;
the mapping relation determining module is used for determining the mapping relation between the class name and the page identifier of the target page according to the class name of the target page to be interacted and the page identifier in the meta-data tag information;
the jump instruction acquisition module is used for acquiring the instruction to be jumped and determining whether the data information to be transmitted exists or not;
the page class name module for determining a target page to be skipped is used for determining that the data information to be transmitted does not exist, and determining the class name of the target page to be skipped according to the mapping relation and the page identifier in the current page;
and the inter-module communication module is used for determining the Intent component according to the class name of the target page to be jumped and finishing the communication between the Android modules.
7. The apparatus of claim 6, wherein the inter-module communication module comprises:
determining an Intent component unit, which is used for obtaining an Intent component according to the class name of the target page to be skipped;
and the page turning-up and jumping unit is used for calling up the page to be jumped by using the Intent component to complete the communication between the Android modules.
8. The apparatus of claim 6, wherein the jump instruction fetch module further comprises:
an UR L obtaining unit, configured to, if it is determined that there is data information to be transferred, obtain UR L by using a page jump protocol and a page identifier in a current page;
a conversion unit for converting UR L into URI format information;
and the unit is arranged in the Intent component and is used for setting the URI format information in the Intent component.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the method for page interaction between Android modules as claimed in any of claims 1 to 5 when executing the program.
10. A non-transitory computer readable storage medium, on which a computer program is stored, which, when being executed by a processor, performs the steps of the method for page interaction between Android modules as claimed in any of claims 1 to 5.
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 true CN111488151A (en) | 2020-08-04 |
| CN111488151B 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) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111966939A (en) * | 2020-09-18 | 2020-11-20 | 北京百度网讯科技有限公司 | Page skipping method and device |
| CN112579061A (en) * | 2020-12-17 | 2021-03-30 | 青岛以萨数据技术有限公司 | Method, device, system and storage medium for data transmission between android components |
| CN115563187A (en) * | 2022-10-17 | 2023-01-03 | 中航信移动科技有限公司 | 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 (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040230900A1 (en) * | 2003-05-16 | 2004-11-18 | Microsoft Corporation | Declarative mechanism for defining a hierarchy of objects |
| 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 |
-
2020
- 2020-04-17 CN CN202010309560.0A patent/CN111488151B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040230900A1 (en) * | 2003-05-16 | 2004-11-18 | Microsoft Corporation | Declarative mechanism for defining a hierarchy of objects |
| 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页面跳转和参数传递" * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111966939A (en) * | 2020-09-18 | 2020-11-20 | 北京百度网讯科技有限公司 | Page skipping method and device |
| CN112579061A (en) * | 2020-12-17 | 2021-03-30 | 青岛以萨数据技术有限公司 | Method, device, system and storage medium for data transmission between android components |
| CN115563187A (en) * | 2022-10-17 | 2023-01-03 | 中航信移动科技有限公司 | Data conversion method, storage medium and electronic equipment |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111488151B (en) | 2023-09-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111488151B (en) | Page interaction method and device among Android modules | |
| WO2022170801A1 (en) | Ios application program construction method and apparatus, electronic device, and storage medium | |
| US8756407B2 (en) | Configuration rule prototyping tool | |
| US10817284B2 (en) | Melding of mediation flow service component architecture (SCA) components | |
| CN110351325B (en) | Data processing method and related equipment | |
| US20200174917A1 (en) | Rapid Automation First-pass Testing Framework | |
| CN104615462B (en) | Cross-platform Mobile solution generation service end and system | |
| CN109597604B (en) | iOS platform based APP modularization development method, device and equipment | |
| WO2019085290A1 (en) | Test preparation method and apparatus, terminal device, and storage medium | |
| CN111026634A (en) | Interface automation test system, method, device and storage medium | |
| CN110825430A (en) | API document generation method, device, equipment and storage medium | |
| WO2019029451A1 (en) | Method for publishing mobile applications and electronic apparatus | |
| CN111159099A (en) | Online data generation method and device, electronic equipment and storage medium | |
| CN108810164A (en) | Device supporting SaaS application flow customization and operation as required | |
| CN113687858A (en) | Configuration file checking method and device, electronic equipment and storage medium | |
| CN111596951A (en) | Method and device for configuring engineering file | |
| CN110109671B (en) | Webpack label size and style conversion method and device | |
| CN112068879B (en) | Method and device for constructing client application program development framework based on configuration | |
| CN108833482B (en) | Method, system, computer equipment and storage medium for automatically downloading MDL (management data language) file | |
| CN107239265B (en) | Binding method and device of Java function and C function | |
| CN116301951B (en) | Micro-service application installation upgrading method and device based on kubernetes | |
| CN111679828A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN110825622A (en) | Software testing method, device, equipment and computer readable medium | |
| CN113448689A (en) | Dubbo protocol conversion device and method in operation period | |
| CN111125149B (en) | Hive-based data acquisition method, hive-based data acquisition device 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 |