CN108021389B - Method and device for introducing ARouter into Android - Google Patents
Method and device for introducing ARouter into Android Download PDFInfo
- Publication number
- CN108021389B CN108021389B CN201711130180.5A CN201711130180A CN108021389B CN 108021389 B CN108021389 B CN 108021389B CN 201711130180 A CN201711130180 A CN 201711130180A CN 108021389 B CN108021389 B CN 108021389B
- Authority
- CN
- China
- Prior art keywords
- arouter
- version number
- configuration file
- component
- variable
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a method and a device for introducing an ARouter into Android, wherein the method comprises the following steps: s1, creating a first configuration file, defining an aggregate variable in the first configuration file, wherein the aggregate variable is a global variable, and defining a first version number of an ARouter core function and a second version number of an ARouter resolver in the aggregate variable; s2, generating version information for introducing the ARouter according to the first version number and the second version number; s3, when the component is created, injecting the version information in the second configuration file of the component. On one hand, the invention realizes the unified upgrade and management of the version numbers of the Arouter introduced by all the components, and is convenient for maintenance; on the other hand, the automatic configuration of the ARouter version number is realized when the component is created, and the development efficiency and the configuration accuracy are improved.
Description
Technical Field
The invention belongs to the field of application development, and particularly relates to a method and a device for introducing an ARouter into Android.
Background
In the Android componentization development process, in order to facilitate communication among the components, a third-party open source communication framework ARouter is generally required to be introduced.
Each time a new component is added, in order to enable the new component to communicate with other components, the information related to ARouter needs to be configured in the new component, so that the introduction of ARouter is realized. When a component needs to introduce ARouter, the related information of ARouter needs to be configured in the build script build. The traditional method directly introduces relevant information of the ARouter, such as compound "com. alibaba: ARouter-api:2.2.2", compound "com. alibaba: ARouter-compiler:1.2.2", wherein 2.2.2 is the version number of the ARouter core function, and 1.2.2 is the version number of the ARouter resolver.
Since configuring the character string of ARouter is cumbersome, configuring a new component manually is error-prone and time-consuming and labor-intensive. When the version number of ARouter changes, it is necessary to change the version number of ARouter in the compilation script of all components introduced into ARouter, which consumes a lot of time.
Disclosure of Invention
In order to overcome the problems that ARouter is easily mistaken, time-consuming, labor-consuming and inconvenient to change when manually introduced into a component or at least partially solve the problems, the invention provides a method and a device for introducing ARouter into Android.
According to a first aspect of the invention, a method for introducing ARouter in Android is provided, which comprises the following steps:
s1, creating a first configuration file, defining an aggregate variable in the first configuration file, wherein the aggregate variable is a global variable, and defining a first version number of an ARouter core function and a second version number of an ARouter resolver in the aggregate variable;
s2, generating version information for introducing the ARouter according to the first version number and the second version number;
s3, when the component is created, injecting the version information in the second configuration file of the component.
Specifically, the step S2 specifically includes:
and respectively adding a $ symbol before the variable of the first version number and the variable of the second version number to generate version information for introducing the ARouter.
Specifically, the step S3 specifically includes:
s31, registering the listener by using a register function;
s32, when the listener is used for monitoring that the component is created, calling back the component creating method;
s33, injecting the version information in a second configuration file of the component using the component creation method.
Specifically, the step S33 specifically includes:
s331, acquiring a second configuration file of the component, and sequentially reading data of each row in the second configuration file until a 'dependencies' character string is read;
s332, inserting the version information into the next line of the line where the character string of the dependencies is located.
Specifically, the step S331 specifically includes:
s3311, opening the second configuration File by using an open method in the File class, and returning a File object of the second configuration File;
s3312, calling the readLine method of the file object to read each line data in the second configuration file until the character string of 'dependencies' is read.
Specifically, the step S3312 specifically includes:
s33121, calling the readLine method of the file object to read the data in the current line in the second configuration file;
s33122, if there is no "dependencies" character string in the current line, moving the file cursor to the beginning of the next line;
s33123, iteratively executing steps S33121 to S33123 with the next line as the current line until a "dependencies" character string is read.
Specifically, the step S332 includes:
using the seek method to move the file cursor to the next line of the line where the character string of the dependencies is located;
writing the version information into the second configuration file using a write method;
and refreshing the second configuration file by using a flush method.
Specifically, the step S3 is followed by:
and changing the value of the first version number and/or the value of the second version number in the set variable.
According to a second aspect of the invention, a device for introducing ARouter in Android is provided, which comprises:
the system comprises a creating unit, a setting unit and a processing unit, wherein the creating unit is used for creating a first configuration file, defining an aggregate variable in the first configuration file, the aggregate variable is a global variable, and a first version number of an ARouter core function and a second version number of an ARouter resolver are defined in the aggregate variable;
the generating unit is used for generating the version information of the ARouter according to the first version number and the second version number;
an injection unit, configured to inject the version information in a second configuration file of the component when the component is created.
According to a third aspect of the invention, there is provided a non-transitory computer readable storage medium storing a computer program of the method as described above.
The invention provides a method and a device for introducing ARouter into Android, on one hand, a first version number of a core function of the ARouter and a second version number of an analyzer are placed in a global set variable to avoid renaming, when the version number of the ARouter is changed, the set variable is only changed to realize the uniform upgrade and management of the version numbers of the ARouter introduced into all components, the maintenance is convenient, on the other hand, the version information of the ARouter is introduced according to the set variable, when the components are created, the version information is automatically injected into a second configuration file of the components, the automatic configuration of the ARouter version number is realized when the components are created, and the development efficiency and the configuration accuracy are improved.
Drawings
Fig. 1 is a schematic overall flow chart of a method for introducing ARouter into Android provided by an embodiment of the present invention;
fig. 2 is a schematic view of an overall structure of a device for introducing ARouter in Android according to an embodiment of the present invention;
fig. 3 is a schematic view of an overall structure of a device introducing ARouter in Android provided by the embodiment of the present invention.
Detailed Description
The following detailed description of embodiments of the present invention is provided in connection with the accompanying drawings and examples. The following examples are intended to illustrate the invention but are not intended to limit the scope of the invention.
In an embodiment of the present invention, a method for introducing ARouter into Android is provided, and fig. 1 is an overall flowchart schematic diagram of the method for introducing ARouter into Android provided in the embodiment of the present invention, where the method includes: s1, creating a first configuration file, defining an aggregate variable in the first configuration file, wherein the aggregate variable is a global variable, and defining a first version number of an ARouter core function and a second version number of an ARouter resolver in the aggregate variable; s2, generating version information for introducing the ARouter according to the first version number and the second version number; s3, when the component is created, injecting the version information in the second configuration file of the component.
Specifically, in S1, the version number of ARouter is required at the time of introduction of ARouter. In order to facilitate later-stage identical update of the version information of Arouter in the configuration files of all the components, the version number of Arouter is defined in an independent global variable, so that the version numbers of Arouter introduced by all the components are the same, and the uniform upgrade and management of the version numbers of Arouter introduced by all the components in later stage are facilitated. The version number of Arouter includes a first version number of the Arouter's core functionality and a second version number of the Arouter's parser. The first configuration file is a config. Adding code defining the set variables in the first configuration file, such as:
where ext is a defined set variable, and then a first version number of the ARouter's core function and a second version number of the parser are defined in the ext set variable. ARouterAPi is a variable of the first version number, 2.2.2 is a value of the first version number, ArouterProcess is a variable of the second version number, and 1.2.2 is a value of the first version number. The first version number of ARouter is defined by ARouter's core function library and the second version number is defined by the parser library. Configuring ARouter by configuring the first version number and the second version number. In S2, after defining a global ARouter version number, generating version information that introduces the ARouter according to the first version number and the second version number, where the version information is a configuration statement that includes the first version number and the second version number. In S3, when a component is created, the version information is injected in a second configuration file of the component. The second configuration file is a build. Thereby realizing automatic injection of ARouter version number in the newly-built component.
In this embodiment, on one hand, a first version number of a core function of the ARouter and a second version number of the parser are placed in a global set variable to avoid duplication of names, when the version number of the ARouter is changed, only the set variable is changed, so that the version numbers of the ARouter introduced by all components are uniformly upgraded and managed, maintenance is facilitated, on the other hand, version information introduced into the ARouter is generated according to the set variable, when the components are created, the version information is automatically injected into a second configuration file of the components, so that the version number of the ARouter is automatically configured when the components are created, and development efficiency and configuration accuracy are improved.
On the basis of the foregoing embodiment, step S2 in this embodiment specifically includes: and respectively adding a $ symbol before the variable of the first version number and the variable of the second version number to generate version information for introducing the ARouter.
Specifically, after a first version number and a second version number of ARouter are defined, $ symbols are respectively added before a variable of the first version number and a variable of the second version number, and version information introducing the ARouter is generated, such as:
compile"com.alibaba:arouter-api:${ext.ARouterAPi}"，
compile"com.alibaba:arouter-compiler:${ext.ARouterProcess}"；
comparing the prior art, it can be found that, in the embodiment, the value of the first version number and the value of the second version number of ARouter in the prior art are replaced by $ { ext.
On the basis of the foregoing embodiments, in this embodiment, the step S3 specifically includes: s31, registering the listener by using a register function; s32, when the listener is used for monitoring that the component is created, calling back the component creating method; s33, injecting the version information in a second configuration file of the component using the component creation method.
Specifically, in order to realize automatic introduction of the version number of Arouter, a listener is registered by using a register (onModelCreated) function, the listener is used for monitoring the creation of a component, and the onModelCreated is a component creation method. After registering using the registrar function, the component creation method onModelCreated is called back when it is monitored that a component has been created. And automatically injecting the generated version information into a second configuration file of the component in the component creation method onModelCreated, wherein the second configuration file is a build.
On the basis of the foregoing embodiment, step S33 in this embodiment specifically includes: s331, acquiring a second configuration file of the component, and sequentially reading data of each row in the second configuration file until a 'dependencies' character string is read; s332, inserting the version information into the next line of the line where the character string of the dependencies is located.
Specifically, a second configuration file of the newly created component is acquired, data is sequentially read line by line from a first line of data in the second configuration file, and when a "dependencies" character string is read, reading of the second configuration file is stopped. Inserting the generated version information in the next line of the line where the character string of the dependencies is located, such as inserting the component "com" aiiba: $ (ext. Arouter. api } "and the component" com "aiiba $: $ (ext. Arouter. process }" in the built. gradl script file of the newly created component, thereby introducing the version information of the Arouter.
On the basis of the foregoing embodiment, the step S331 in this embodiment specifically includes: s3311, opening the second configuration File by using an open method in the File class, and returning a File object of the second configuration File; s3312, calling the readLine method of the file object to read each line data in the second configuration file until the character string of 'dependencies' is read.
Specifically, the second configuration File is opened by using an open method in a File class, a File object File of the second configuration File is returned, a readLine method in the File object File is called to read data of each line in the second configuration File line by line according to the sequence, and reading is stopped after a 'dependencies' character string is read.
On the basis of the foregoing embodiment, the step S3312 in this embodiment specifically includes: s33121, calling the readLine method of the file object to read the data in the current line in the second configuration file; s33122, if the fact that the characters of the dependencies do not exist in the current line is known by using the dependencies method, moving the cursor of the file to the beginning of the next line; s33123, iteratively executing steps S33121 to S33123 with the next line as the current line until a "dependencies" character string is read.
In the above embodiment, the step S332 includes: using the seek method to move the file cursor to the next line of the line where the character string of the dependencies is located; writing the version information into the second configuration file using a write method; and refreshing the second configuration file by using a flush method.
On the basis of the foregoing embodiment, the step S3 in this embodiment further includes: and changing the value of the first version number and/or the value of the second version number in the set variable.
Specifically, the version information of ARouter in the second configuration file of a component is all dependent on the first version number and the second version number of ARouter in the defined set variable. When Arouter needs to be upgraded, only the first version number and/or the second version number of Arouter in the set variable need to be changed, so that the ARouter versions introduced by all the components are upgraded in a unified mode, and time is saved.
In another embodiment of the present invention, a device for introducing ARouter into Android is provided, and fig. 2 is a schematic diagram of an overall structure of the device for introducing ARouter into Android provided in the embodiment of the present invention, where the device includes a creating unit 1, a generating unit 2, and an injecting unit 3, where:
the creating unit 1 is configured to create a first configuration file, define an aggregate variable in the first configuration file, where the aggregate variable is a global variable, and define a first version number of an ARouter core function and a second version number of an ARouter parser in the aggregate variable; the generating unit 2 is configured to generate version information into which the ARouter is introduced according to the first version number and the second version number; the injection unit 3 is configured to inject the version information in a second configuration file of the component when the component is created.
Specifically, the version number of ARouter is required at the time of introduction of ARouter. In order to facilitate later update of the version information of the Arouter in the configuration files of all the components, the creating unit 1 defines the version number of the Arouter in an independent global variable, so that the version numbers of the Arouter introduced by all the components are the same, and the later unified upgrade and management of the version numbers of the Arouter introduced by all the components are facilitated. The version number of Arouter includes a first version number of the Arouter's core functionality and a second version number of the Arouter's parser. The first configuration file is a config. The first version number of ARouter is defined by ARouter's core function library and the second version number is defined by the parser library. Configuring ARouter by configuring the first version number and the second version number. After defining the global ARouter version number, the generating unit 2 generates the version information of the ARouter according to the first version number and the second version number, where the version information is a configuration statement including the first version number and the second version number. When a component is captured to be created, the injection unit 3 injects the version information in a second configuration file of the component. The second configuration file is a build. Thereby realizing automatic injection of ARouter version number in the newly-built component.
In this embodiment, on one hand, a first version number of a core function of the ARouter and a second version number of the parser are placed in a global set variable to avoid duplication of names, when the version number of the ARouter is changed, only the set variable is changed, so that the version numbers of the ARouter introduced by all components are uniformly upgraded and managed, maintenance is facilitated, on the other hand, version information introduced into the ARouter is generated according to the set variable, when the components are created, the version information is automatically injected into a second configuration file of the components, so that the version number of the ARouter is automatically configured when the components are created, and development efficiency and configuration accuracy are improved.
On the basis of the foregoing embodiment, in this embodiment, the generating unit is specifically configured to add a $ symbol before the variable of the first version number and the variable of the second version number, respectively, and generate the version information into which the ARouter is introduced.
On the basis of the above embodiments, the injection unit in this embodiment includes: a registration subunit, configured to register the listener using a register function; a callback subunit, configured to, when it is monitored that a component is created using the listener, callback the component creation method; an injection subunit, configured to inject the version information in a second configuration file of the component using the component creation method.
On the basis of the above embodiments, the injection subunit in this embodiment includes: the reading subunit is used for acquiring a second configuration file of the component, and sequentially reading data of each row in the second configuration file until a 'dependencies' character string is read; and the inserting subunit is used for inserting the version information into the row next to the row of the 'dependencies' character string.
On the basis of the above embodiment, the reading subunit in this embodiment includes: an opening subunit, configured to open the second configuration File by using an open method in a File class, and return a File object of the second configuration File; and the calling subunit is used for calling a readLine method of the file object to read each line of data in the second configuration file until a character string of 'dependences' is read.
On the basis of the foregoing embodiment, the calling subunit in this embodiment is specifically configured to: calling a readLine method of the file object to read data in a current line in the second configuration file; if the 'dependences' character string does not exist in the current row, moving the file cursor to the beginning of the next row; and taking the next row as the current row to iteratively execute the steps of reading data, judging and moving to the next row until the character string of the dependencies is read.
On the basis of the above embodiment, the insertion subunit in this embodiment is specifically configured to: using the seek method to move the file cursor to the next line of the line where the character string of the dependencies is located; writing the version information into the second configuration file using a write method; and refreshing the second configuration file by using a flush method.
On the basis of the foregoing embodiment, the apparatus in this embodiment further includes an upgrading unit, configured to modify a value of the first version number and/or a value of the second version number in the set variable.
The embodiment provides a device for introducing ARouter in Android, and fig. 3 is a schematic view of an overall structure of the device for introducing ARouter in Android provided by the embodiment of the present invention, where the device includes: at least one processor 31, at least one memory 32, and a bus 33; wherein the content of the first and second substances,
the processor 31 and the memory 32 complete mutual communication through the bus 33;
the memory 32 stores program instructions executable by the processor 31, and the processor calls the program instructions to execute the methods provided by the method embodiments, for example, the method includes: s1, creating a first configuration file, defining an aggregate variable in the first configuration file, wherein the aggregate variable is a global variable, and defining a first version number of an ARouter core function and a second version number of an ARouter resolver in the aggregate variable; s2, generating version information for introducing the ARouter according to the first version number and the second version number; s3, when the component is created, injecting the version information in the second configuration file of the component.
The present embodiments provide a non-transitory computer-readable storage medium storing computer instructions that cause the computer to perform the methods provided by the above method embodiments, for example, including: s1, creating a first configuration file, defining an aggregate variable in the first configuration file, wherein the aggregate variable is a global variable, and defining a first version number of an ARouter core function and a second version number of an ARouter resolver in the aggregate variable; s2, generating version information for introducing the ARouter according to the first version number and the second version number; s3, when the component is created, injecting the version information in the second configuration file of the component.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
The above-described embodiment of the device for introducing ARouter in Android is only schematic, where the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may also be distributed on multiple 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 described in the embodiments or some parts of the embodiments.
Finally, the method of the present application is only a preferred embodiment and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (9)
1. A method for introducing ARouter in Android is characterized by comprising the following steps:
s1, creating a first configuration file, defining an aggregate variable in the first configuration file, wherein the aggregate variable is a global variable, and defining a first version number of an ARouter core function and a second version number of an ARouter resolver in the aggregate variable;
s2, generating version information for introducing the ARouter according to the first version number and the second version number;
s3, when the component is created, injecting the version information in a second configuration file of the component;
wherein, the step S3 specifically includes:
s31, registering the listener by using a register function;
s32, when the listener is used for monitoring that the component is created, calling back the component creating method;
s33, injecting the version information in a second configuration file of the component using the component creation method.
2. The method according to claim 1, wherein the step S2 specifically includes:
and respectively adding a $ symbol before the variable of the first version number and the variable of the second version number to generate version information for introducing the ARouter.
3. The method according to claim 1, wherein the step S33 specifically includes:
s331, acquiring a second configuration file of the component, and sequentially reading data of each row in the second configuration file until a 'dependencies' character string is read;
s332, inserting the version information into the next line of the line where the character string of the dependencies is located.
4. The method according to claim 3, wherein the step S331 specifically includes:
s3311, opening the second configuration File by using an open method in the File class, and returning a File object of the second configuration File;
s3312, calling the readLine method of the file object to read each line data in the second configuration file until the character string of 'dependencies' is read.
5. The method according to claim 4, wherein the step S3312 specifically comprises:
s33121, calling the readLine method of the file object to read the data in the current line in the second configuration file;
s33122, if there is no "dependencies" character string in the current line, moving the file cursor to the beginning of the next line;
s33123, iteratively executing steps S33121 to S33123 with the next line as the current line until a "dependencies" character string is read.
6. The method according to claim 3, wherein the step S332 comprises:
using the seek method to move the file cursor to the next line of the line where the character string of the dependencies is located;
writing the version information into the second configuration file using a write method;
and refreshing the second configuration file by using a flush method.
7. The method according to any one of claims 1 to 6, wherein the step S3 is further followed by:
and changing the value of the first version number and/or the value of the second version number in the set variable.
8. An ARouter introducing device in Android, which is characterized by comprising:
the system comprises a creating unit, a setting unit and a processing unit, wherein the creating unit is used for creating a first configuration file, defining an aggregate variable in the first configuration file, the aggregate variable is a global variable, and a first version number of an ARouter core function and a second version number of an ARouter resolver are defined in the aggregate variable;
the generating unit is used for generating the version information of the ARouter according to the first version number and the second version number;
an injection unit, configured to inject the version information in a second configuration file of a component when the component is created;
wherein the injection unit includes:
a registration subunit, configured to register the listener using a register function;
a callback subunit, configured to, when it is monitored that a component is created using the listener, callback the component creation method;
an injection subunit, configured to inject the version information in a second configuration file of the component using the component creation method.
9. A non-transitory computer-readable storage medium storing computer instructions that cause a computer to perform the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711130180.5A CN108021389B (en) | 2017-11-15 | 2017-11-15 | Method and device for introducing ARouter into Android |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711130180.5A CN108021389B (en) | 2017-11-15 | 2017-11-15 | Method and device for introducing ARouter into Android |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108021389A CN108021389A (en) | 2018-05-11 |
| CN108021389B true CN108021389B (en) | 2021-01-01 |
Family
ID=62080631
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711130180.5A Active CN108021389B (en) | 2017-11-15 | 2017-11-15 | Method and device for introducing ARouter into Android |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108021389B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109189490A (en) * | 2018-07-03 | 2019-01-11 | 武汉斗鱼网络科技有限公司 | A kind of configuration method and relevant device of module |
| CN112256324B (en) * | 2020-12-08 | 2021-03-19 | 智道网联科技(北京)有限公司 | Method and device for processing files in android application program construction process |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102880456A (en) * | 2012-07-31 | 2013-01-16 | 北京奇虎科技有限公司 | Method and device for creating plug-in |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW201224814A (en) * | 2010-12-07 | 2012-06-16 | Hon Hai Prec Ind Co Ltd | System and method for updating software on android |
| CN105988995B (en) * | 2015-01-27 | 2019-05-24 | 杭州海康威视数字技术股份有限公司 | A method of based on HFile batch load data |
-
2017
- 2017-11-15 CN CN201711130180.5A patent/CN108021389B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102880456A (en) * | 2012-07-31 | 2013-01-16 | 北京奇虎科技有限公司 | Method and device for creating plug-in |
Non-Patent Citations (1)
| Title |
|---|
| 浅谈android组件化之ARouter简单使用;繁华落尽666;《脚本之家 https://www.jb51.net/article/123776.htm 》;20170915;第1-10页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108021389A (en) | 2018-05-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102622241B (en) | A kind of method for upgrading software and device | |
| US8910113B2 (en) | Methods and systems for visual code refactoring | |
| US9342538B2 (en) | Electronic device and database accessing method | |
| US20240045850A1 (en) | Systems and methods for database orientation transformation | |
| CN104932973B (en) | A kind of edition compatibility test method and device | |
| US10437574B2 (en) | System and method for providing code completion features for code modules | |
| CN107844313B (en) | Method and device for upgrading SDK version in Android | |
| US10203943B2 (en) | Static analysis and reconstruction of deep link handling in compiled applications | |
| CN105446775A (en) | Configurative generation method and device for game installation package | |
| CN108021389B (en) | Method and device for introducing ARouter into Android | |
| CN108694049B (en) | Method and equipment for updating software | |
| CN108279905B (en) | Method and device for introducing library file into assembly | |
| CN112631644A (en) | Method and device for modifying initial formula of Flutter constructor | |
| CN117215558A (en) | Visual software development method, device, equipment and medium for android | |
| Rahman et al. | A DSL for importing models in a requirements management system | |
| CN115951916A (en) | Component processing method and device, electronic equipment and storage medium | |
| CN116048609A (en) | Configuration file updating method, device, computer equipment and storage medium | |
| CN106648441A (en) | Method and device for transferring equipment partition information | |
| CN112748905B (en) | Method and device for initializing and calling basic library, electronic equipment and storage medium | |
| US11429383B2 (en) | Method, device, and program product for managing development job in development environment | |
| US10838716B1 (en) | Automated dependency detection and response | |
| CN114138815A (en) | Multi-database compatibility implementation method, device and medium for application program | |
| CN111427581B (en) | Method, device, equipment and medium for realizing type multi-inheritance | |
| US11144287B2 (en) | Compile time validation of programming code | |
| CN106778301A (en) | Reliable cross-platform data storage method and system based on cocos2d x |
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 |