CN111427579A - Plug-in, application program implementing method and system, computer system and storage medium - Google Patents
Plug-in, application program implementing method and system, computer system and storage medium Download PDFInfo
- Publication number
- CN111427579A CN111427579A CN201910022287.0A CN201910022287A CN111427579A CN 111427579 A CN111427579 A CN 111427579A CN 201910022287 A CN201910022287 A CN 201910022287A CN 111427579 A CN111427579 A CN 111427579A
- Authority
- CN
- China
- Prior art keywords
- plug
- ins
- public
- service
- loading
- 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.)
- Pending
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
- G06F8/41—Compilation
-
- 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
-
- 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/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The present disclosure provides a plug-in implementation method, including: obtaining a source code of a public plug-in, wherein the public plug-in can be used by a plurality of business plug-ins in a public dependence manner, and at least two of the business plug-ins and the public plug-in can be used for realizing a target application program and can be loaded by a host program of the target application program when the target application program is realized; and compiling the source code and outputting the communal plug-in and a corresponding AAR package, wherein the AAR package is used for providing the dependency relationship between the service plug-ins and the communal plug-ins when compiling a plurality of service plug-ins. The present disclosure also discloses an application program implementation method, a plug-in implementation system, an application program implementation system, a computer system, and a computer-readable storage medium.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a plug-in, an application implementation method and system, a computer system, and a storage medium.
Background
The Android plug-in technology is mature at present, and a plug-in program (called plug-in for short) is dynamically loaded through a plug-in framework, so that the service logic of the application program can be decoupled, the number of methods and resource consumption of the application program are reduced, and the volume of the application program is reduced.
However, in implementing embodiments of the present disclosure, the inventors found that: in the existing application program using the Android plug-in technology, multiple plug-ins may depend on the same class, C library and resource in common, and the same class, C library and resource may be referred to repeatedly inside each plug-in, and in general, these classes, C libraries and resources that may be used in common or referred to repeatedly will be packaged in the common library part of the host program (also called host engineering) of the application program, but if some classes, C libraries and resources in the host program are not referred to by any plug-in of the application program at all, these classes, C libraries and resources are redundant to the host program.
Disclosure of Invention
In view of the above, the present disclosure provides a plug-in, an application implementation method and system, a computer system, and a storage medium.
One aspect of the present disclosure provides a plug-in implementation method, including: obtaining source code of a public plug-in, wherein the public plug-in can be used by a plurality of business plug-ins in public dependence, and at least two of the business plug-ins and the public plug-in can be used for realizing a target application program and can be loaded by a host program of the target application program when the target application program is realized; and compiling the source code and outputting the common plug-in and a corresponding AAR package, wherein the AAR package is used for providing the dependency relationship between the service plug-ins and the common plug-in when compiling the plurality of service plug-ins.
According to an embodiment of the present disclosure, the method further comprises: acquiring a corresponding source code for each of the plurality of service plug-ins; compiling the corresponding source code and outputting a corresponding service plug-in; and adding the dependency relationship in the configuration file of the corresponding service plug-in based on the AAR packet in the process of compiling the corresponding source code.
According to the embodiment of the disclosure, the public plug-in can also be reused by the interior of each service plug-in; the method further comprises the following steps: and aiming at the service plug-in needing to reuse the public plug-in the plug-in, adding the dependency relationship into the configuration file of the service plug-in based on the repeated reference times of the AAR package and the public plug-in the process of compiling the source code of the service plug-in.
One aspect of the present disclosure provides an application implementation method, including: obtaining a plurality of business plug-ins and a common plug-in for implementing the application, wherein the common plug-in can be used by at least two common dependencies of the plurality of business plug-ins or can be reused inside the plug-ins by at least one of the plurality of business plug-ins; acquiring a host program for realizing an application program; starting the plurality of service plug-ins by using the host program; and loading the public plug-in according to a preset loading logic in the process of starting the plurality of service plug-ins.
According to an embodiment of the present disclosure, the loading the common plug-in according to a predetermined loading logic in the process of starting the plurality of service plug-ins includes: for each service plug-in the plurality of service plug-ins, checking whether a dependency relationship exists between the corresponding service plug-in and the public plug-in the starting process; and if so, loading the common plug-in.
According to an embodiment of the present disclosure, the application includes a load object; the method further comprises the following steps: loading the loading object through a loader of the service plug-in; or loading the loading object through a loader of the public plug-in; or the loading object is loaded through a loader of the host program.
According to an embodiment of the present disclosure, the load object includes at least one of: class, C library, and resource.
Another aspect of the present disclosure provides a plug-in implementation system, including: the system comprises a first acquisition module, a first storage module and a second acquisition module, wherein the first acquisition module is used for acquiring a source code of a public plug-in, the public plug-in can be used by a plurality of business plug-ins in a public dependence, and at least two of the business plug-ins and the public plug-in can be used for realizing a target application program and can be loaded by a host program of the target application program when the target application program is realized; and a first compiling module, configured to compile the source code and output the common plug-in and a corresponding AAR package, where the AAR package is configured to provide a dependency relationship between the service plug-ins and the common plug-in when compiling the plurality of service plug-ins.
According to an embodiment of the present disclosure, the system further comprises: a second obtaining module, configured to obtain, for each of the plurality of service plug-ins, a corresponding source code; the second compiling module is used for compiling the corresponding source code and outputting a corresponding service plug-in; and a first adding module, configured to add the dependency relationship in the configuration file of the corresponding service plug-in based on the AAR package in the process of compiling the corresponding source code.
According to the embodiment of the disclosure, the public plug-in can also be reused by the interior of each service plug-in; the system further comprises: and the second adding module is used for adding the dependency relationship into the configuration file of the service plug-in based on the AAR package and the repeated reference times of the public plug-in the process of compiling the source code of the service plug-in aiming at the service plug-in needing to reuse the public plug-in inside the plug-in.
Another aspect of the present disclosure provides an application implementation system, including: a third obtaining module, configured to obtain a plurality of service plug-ins and a common plug-in for implementing the application, where the common plug-in may be used by at least two common dependencies of the plurality of service plug-ins or may be reused inside the plug-in by at least one of the plurality of service plug-ins; the fourth acquisition module is used for acquiring a host program for realizing the application program; the starting module is used for starting the plurality of service plug-ins by using the host program; and the first loading module is used for loading the public plug-in according to preset loading logic in the process of starting the plurality of service plug-ins.
According to an embodiment of the present disclosure, the first load module includes: the checking unit is used for checking whether the corresponding service plug-in and the public plug-in have a dependency relationship or not in the starting process aiming at each service plug-in; and the loading unit is used for loading the public plug-in under the condition that the dependency relationship exists.
According to an embodiment of the present disclosure, the application includes a load object; the system further comprises a second loading module for: loading the loading object through a loader of the service plug-in; or loading the loading object through a loader of the public plug-in; or the loading object is loaded through a loader of the host program.
According to an embodiment of the present disclosure, the load object includes at least one of: class, C library, and resource.
Another aspect of the present disclosure provides a computer system comprising: one or more processors; memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described above.
Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.
Another aspect of the disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.
According to the embodiment of the disclosure, because the class, the C library and the resource which can be used by a plurality of plug-ins in a public dependence mode are separated from the host program, are developed into independent public plug-ins, and the service plug-in of the application program is loaded when the public depends on some public plug-ins, otherwise, the technical means of loading is not carried out, therefore, the defects that the application program in the related art is not divided into business plug-ins and public plug-ins, only the plug-ins and the host program are divided, the class, the C library and the resources which are not used by any plug-in public dependence in the application program are not used at all, and the class, the C library and the resources are also packaged in the public library of the host program in advance, so that the application program is large in size, numerous in methods, serious in resource consumption and the like are overcome at least in part, and further, the technical effects of reducing the volume of the application program and reducing the number of methods and resource consumption of the application program are achieved.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:
FIG. 1 schematically illustrates an exemplary system architecture to which the plug-ins, application implementation methods and systems of the present disclosure may be applied;
FIG. 2 schematically illustrates a flow chart of a plug-in implementation method according to an embodiment of the present disclosure;
FIG. 3 schematically illustrates a plug-in implementation schematic in accordance with an embodiment of the present disclosure;
FIG. 4 schematically illustrates a plug-in implementation schematic diagram according to another embodiment of the present disclosure;
FIG. 5 schematically shows a flow chart of an application implementation method according to an embodiment of the present disclosure;
FIG. 6 schematically shows a flow diagram for running an application in accordance with an embodiment of the disclosure;
FIG. 7 schematically illustrates a block diagram of a plug-in implementation system according to an embodiment of the present disclosure;
FIG. 8 schematically illustrates a block diagram of an application implementation system in accordance with an embodiment of the present disclosure; and
FIG. 9 schematically illustrates a block diagram of a computer system suitable for implementing plug-ins and applications in accordance with an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
The embodiment of the disclosure provides a plug-in capable of reducing the volume of an application program, reducing the number of methods and resource consumption of the application program and decoupling the service logic of the application program, an application program implementation method, and a plug-in and application program implementation system capable of applying the method. The plug-in implementation method comprises the steps of obtaining a source code of a public plug-in, wherein the public plug-in can be used by a plurality of business plug-ins in a public dependence mode, and at least two of the business plug-ins and the public plug-in can be used for implementing a target application program and can be loaded by a host program of the target application program when the target application program is implemented; and compiling the source code and outputting the communal plug-in and a corresponding AAR package, wherein the AAR package is used for providing the dependency relationship between the service plug-ins and the communal plug-ins when compiling a plurality of service plug-ins.
FIG. 1 schematically illustrates an exemplary system architecture to which the plug-ins, application implementation methods, and systems of the present disclosure may be applied. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired and/or wireless communication links, and so forth.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have installed thereon various communication client applications, such as a shopping-like application, a web browser application, a search-like application, an instant messaging tool, a mailbox client, and/or social platform software, etc. (by way of example only).
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that the plug-in and application implementation provided by the embodiment of the present disclosure can be generally executed by the server 105. Accordingly, the plug-in, application system provided by the disclosed embodiments may be generally located in the server 105. The plug-in, application method provided by the embodiments of the present disclosure may also be performed by a server or server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the plug-in and application system provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Alternatively, the plug-in and the application method provided by the embodiment of the present disclosure may also be executed by the terminal device 101, 102, or 103, or may also be executed by another terminal device different from the terminal device 101, 102, or 103. Accordingly, the plug-in and application system provided by the embodiment of the present disclosure may also be provided in the terminal device 101, 102, or 103, or in another terminal device different from the terminal device 101, 102, or 103.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
In addition, the embodiment of the disclosure can be applied to an application program with the following characteristics: in this case, by using the technical solution provided by the embodiment of the present disclosure, the classes, the C libraries and the resources used by the common dependencies no longer need to be packaged in the host program of the application program in advance, but the classes, the C libraries and the resources can be developed into corresponding common plug-ins for use. Therefore, the application program can load and use the corresponding public plug-in only in the running stage, so that the method number and the resource consumption of the application program can be reduced, the volume of the application program is reduced, and the service logic of the application program is decoupled to a greater extent.
The embodiment of the disclosure mainly improves the host program part of the application program in the related art. Specifically, all classes, libraries C and resources used by the common dependence of the multiple plug-ins of the application program in the common library of the host program are separated from the host program, the original multiple plug-ins are used as multiple service plug-ins, the multiple common plug-ins are developed according to the common dependence of the multiple service plug-ins on the classes, libraries C and resources, the application program is loaded during running, the corresponding dependence is added into the configuration file of the service plug-ins when the service plug-ins are developed, and the corresponding common plug-ins are loaded when the service plug-ins are started by the host program.
It should be noted that, in the present disclosure, the implementation and use of each plug-in includes the following stages: the source code integration phase of the plug-in, the source code compilation phase of the plug-in, and the application execution phase use common plug-ins and business plug-ins.
Fig. 2 schematically shows a flow chart of a plug-in implementation method according to an embodiment of the present disclosure.
As shown in fig. 2, the method includes operations S210 to S220.
In operation S210, a source code of a common plug-in is obtained, wherein the common plug-in can be used by a plurality of business plug-ins in common dependence, and at least two of the plurality of business plug-ins and the common plug-in can be used for implementing a target application and can be loaded by a host program of the target application when the target application is implemented.
It should be noted that the common plug-in may be a class or C library or resource that can be depended on by the service plug-in common. For example, class 1, C library 1, resource 1 are often commonly relied upon by business plug-ins A, B, C, in which case one piece of source code for a common plug-in can be written for class 1, another piece of source code for a common plug-in can be written for C library 1, and another piece of source code for a common plug-in can be written for resource 1, each piece of source code being compiled to generate a common plug-in.
Based on the above example, for an application, it is assumed that service plug-ins A, B and D-G are included, where service plug-ins A, B depend on class 1, C library 1 and resource 1 in common, and service plug-ins D-G do not depend on any class, C library and resource in common, in this case, when implementing the application, not only service plug-ins A, B and D-G need to be loaded, but also a common plug-in corresponding to class 1, a common plug-in corresponding to C library 1 and a common plug-in corresponding to resource 1 need to be loaded according to the dependency relationship of service plug-ins A, B on class 1, C library 1 and resource 1.
In operation S220, the source code is compiled and the common plug-in and a corresponding AAR package are output, wherein the AAR package is used to provide a dependency relationship of the service plug-in and the common plug-in when compiling the plurality of service plug-ins.
In embodiments of the present disclosure, compiling the source code of a communal plug-in may produce two artifacts simultaneously, one being the corresponding communal plug-in and the other being the AAR package associated with the communal plug-in. The AAR package is essentially an android archive file, and is mainly used for providing the dependency relationship between the service plug-in and the public plug-in when compiling related service plug-ins. For example, assuming that in a certain application, service plug-in a needs to depend on public plug-in 1, and AAR package 1 is generated when public plug-in 1 is generated by compiling, in this case, in the process of generating service plug-in a by compiling the source code of service plug-in a, the dependency relationship between service plug-in a and public plug-in 1 may be added in the configuration file of service plug-in a based on AAR package 1.
In particular, the development of a common plug-in may be generally divided into two phases, namely a common plug-in source code integration phase and a common plug-in source code compilation phase.
In the embodiment of the present disclosure, the purpose of developing a common plug-in is to split a class, a C library, and a resource, which are only used in common dependence among a plurality of plug-ins, from a host program, and to develop and run as a plug-in alone.
According to the embodiment of the disclosure, in the compiling period of the public plug-in, two products, namely the public plug-in and the AAR packet associated with the public plug-in, are generated by compiling the source code, the public plug-in is provided for the host program to be loaded and used integrally, and the AAR packet is provided for other business plug-ins to be compiled and used, namely, the AAR packet is used for storing the dependency relationship with the corresponding public plug-in when the business plug-ins are compiled. Thus, the class, the C library and the resource of the public plug-in can be loaded and used through the dependency relationship during the operation period of the application program.
It can be seen that the embodiments of the present disclosure, because the class, C library and resource which may be used by a plurality of plug-ins in public dependence are separated from the host program, are developed into independent public plug-ins, and the service plug-in of the application program is loaded when the public depends on some public plug-ins, otherwise, the technical means of loading is not carried out, therefore, the defects that the application program in the related art is not divided into business plug-ins and public plug-ins, only the plug-ins and the host program are divided, the class, the C library and the resources which are not used by any plug-in public dependence in the application program are not used at all, and the class, the C library and the resources are also packaged in the public library of the host program in advance, so that the application program is large in size, numerous in methods, serious in resource consumption and the like are overcome at least in part, and further, the technical effects of reducing the volume of the application program and reducing the number of methods and resource consumption of the application program are achieved.
The method of fig. 2 is further described with reference to fig. 3 and 4 in conjunction with specific embodiments.
As an alternative embodiment, the method may further comprise: acquiring a corresponding source code for each of a plurality of service plug-ins; compiling a corresponding source code and outputting a corresponding service plug-in; and adding a dependency relationship in a configuration file of the corresponding service plug-in based on the AAR package in the process of compiling the corresponding source code.
Similar to the process for implementing the public plug-in, the implementation of the service plug-in is also divided into two stages, namely a service plug-in source code integration stage and a service plug-in source code compiling stage. Unlike the common plug-in source code compilation stage, compiling service plug-in source code produces only one product of service plug-in code. Moreover, if a service plug-in has a dependency relationship with one or several common plug-ins, when compiling the service plug-in, the service plug-in and the dependency relationship of the common plug-ins need to be added in the configuration file thereof based on the corresponding AAR package. Of course, if a service plug-in has no dependency relationship with any public plug-in, i.e. it does not need to depend on any public class, C library and resource, then when compiling the service plug-in, the source code is compiled directly to generate the service plug-in, and there is no need to add any dependency relationship in its configuration file.
Specifically, in the embodiment of the present disclosure, adding a dependency relationship with a common plug-in a configuration file may be implemented by adding a meta tag in android manifest. Of course, the dependency relationship may also be saved by a json file or other manners in the embodiments of the present disclosure.
Furthermore, in the disclosed embodiments, business plugins may be compiled via a plugins compilation tool. And different plug-in schemes can use different compiling tools, which are not limited herein.
In addition, it should be noted that, in the embodiment of the present disclosure, after directly compiling the public plug-in source code and generating the AAR package, the AAR package may be uploaded to the maven private server/repository for use in compiling the service plug-in. Of course, the storage mode of the AAR package includes, but is not limited to, the mode of uploading the maven private server/warehouse.
Through the embodiment of the disclosure, in order to facilitate loading in runtime, the dependency relationship between the service plug-in and the public plug-in can be added in the configuration file of the service plug-in.
Fig. 3 provides a plug-in implementation principle, that is, in one application, service plug-in 1 and service plug-in 2 depend on common plug-in 1 in common, and AAR packet 1 is an AAR packet generated when common plug-in 1 is compiled, then the implementation principle of service plug-in 1 and service plug-in 2 is shown in the figure.
As an alternative embodiment, the common plug-in may also be reused inside each service plug-in, and correspondingly, the method may further include: aiming at the service plug-in which the public plug-in is required to be reused inside the plug-in, in the process of compiling the source code of the service plug-in, the dependency relationship is added into the configuration file of the service plug-in based on the number of times that the AAR package and the public plug-in are repeatedly referenced.
In the embodiment of the present disclosure, the common plug-in may be a class, a C library and a resource that are used by common dependency among a plurality of service plug-ins, or may be a common class, a C library and a resource that are repeatedly referenced inside each service plug-in. Either the former or the latter can be split from the host program to reduce the size, number of methods and resource consumption of the application.
Fig. 4 provides another plug-in implementation principle, that is, in one application, service plug-in 1 refers to common plug-in 1 repeatedly twice, and AAR packet 1 is an AAR packet generated at the same time when common plug-in 1 is compiled, then service plug-in 1 implementation principle is shown in the figure.
By the embodiment of the disclosure, the classes, the C libraries and the resources repeatedly referenced in a single service plug-in can be split from the public library of the host program, developed into the public plug-in and loaded when the application program runs, so that the volume, the method number and the resource consumption of the application program can be reduced to a greater extent.
FIG. 5 schematically shows a flow chart of an application implementation method according to an embodiment of the present disclosure.
As shown in fig. 5, the method includes operations S510 to S540.
In operation S510, a plurality of service plugins and a common plug-in for implementing an application are obtained, wherein the common plug-in can be used by at least two common dependencies of the plurality of service plugins or can be reused inside the plug-in by at least one of the plurality of service plugins.
It should be noted that, both the service plug-in and the common plug-in mentioned in the embodiments of the present disclosure may be implemented by the solutions provided in the above embodiments, and are not described herein again.
In the embodiment of the present disclosure, for an application, it is assumed that service plug-ins A, B, C and D to G are included, where service plug-ins A, B all depend on class 1, C library 1, and resource 1 in a public way, service plug-in C refers to class 2, C library 2, and resource 2 in a repeated way, and service plug-ins D to G do not depend on any class, C library, and resource in a public way, and in this case, when implementing the application, it is necessary to load service plug-ins A, B, C and D to G, and also load a public plug-in corresponding to class 1, a public plug-in corresponding to C library 1, and a public plug-in corresponding to resource 1 according to the dependency relationship of service plug-ins A, B on class 1, C library 1, and resource 1, and load a public plug-in corresponding to class 2, C library 2, and resource 2 according to the dependency relationship of service plug-ins C on class 2, C library 2, and resource 2, And C, the public plug-in corresponding to the library 2 and the public plug-in corresponding to the resource 2.
In operation S520, a host program for implementing an application program is acquired.
The host program of the application program can load all service plug-ins of the application program and can also load all public plug-ins of the application program.
In operation S530, a plurality of service plug-ins are started using the host program.
In operation S540, in the process of starting the plurality of service plugins, the common plugin is loaded according to a predetermined loading logic.
How to load and use the public plug-in the running stage of the host program is the work of the plug-in framework, and the use mode of the public plug-in is explained by the process of searching a class with reference to fig. 6.
When a host program needs to start a service plug-in and load classes, if a class loader in the service plug-in can find the classes, the loading is successful, then the next class is continuously found until the end, and if the loading is failed, the next step is continuously carried out, namely whether a public plug-in exists is searched.
Specifically, when the class loader of the service plug-in cannot find the class, the service plug-in can be searched for whether the service plug-in depends on the public plug-in or not by analyzing android manifest.
Similarly, continuously searching whether the class exists through a class loader of the host program, if so, successfully loading, and continuously finding the next class until finishing; if not, the type loading is considered to be failed, and an exception is thrown.
Therefore, in the host program operation stage, the class, the C library and the resource of the public plug-in need to be loaded and used through the dependency relationship between the service plug-in and the public plug-in.
Furthermore, during the application running phase, the order of checking the classes/C libraries/resources includes, but is not limited to, the order shown in the above exemplary scheme, and the lookup logic can be adjusted accordingly according to the difference of the dependency relationship.
The embodiment of the disclosure provides an improved application program implementation scheme on the basis of public plug-ins and business plug-ins, and forms one or more public plug-ins by separating classes, C libraries and resources which are only used in public dependence among a plurality of business plug-ins and/or classes, C libraries and resources which are only repeatedly quoted in each business plug-in from a host program, and dynamically loads the public plug-ins, so that the business plug-ins can be prevented from respectively repeatedly quoting related classes, C libraries and resources, the method number and resource consumption of the host program can be further reduced, code redundancy is reduced, the size of the application program is reduced, and the installation and the starting of the application program are accelerated.
As an alternative embodiment, in the process of starting up a plurality of service plug-ins, loading a common plug-in according to a predetermined loading logic includes: for each of a plurality of service plug-ins, checking whether a dependency relationship exists between the corresponding service plug-in and a public plug-in the starting process; and if so, loading the common plug-in.
Specifically, when each service plug-in is started, whether the service plug-in depends on the public plug-in can be found by analyzing android xml of the service plug-in, if the service plug-in depends on the public plug-in, the public plug-in can be loaded first by using a plug-in framework, and if the service plug-in does not exist, the public plug-in does not need to be loaded.
By the embodiment of the disclosure, when the application program runs, only the public plug-in having the dependency relationship with the service plug-in of the application program is loaded, and the public plug-in having no dependency relationship is not loaded, so that the number of methods and resource consumption of the application program can be reduced, and the volume of the application program is reduced.
As an alternative embodiment, the application includes a load object; the method may further comprise: loading a loading object through a loader of a service plug-in; or loading the loading object through a loader of the public plug-in; or the load object is loaded by the loader of the host program.
As an alternative embodiment, loading the object includes at least one of: class, C library, and resource.
In the embodiment of the disclosure, if the loading object is depended by the service plug-in or referenced repeatedly, the loading object can be loaded by a loader of the service plug-in, otherwise, the loading object can be loaded by a loader of the service plug-in or the host program.
FIG. 7 schematically illustrates a block diagram of a plug-in implementation system according to an embodiment of the present disclosure.
As shown in fig. 7, the plug-in implementation system 700 includes a first obtaining module 710 and a first compiling module 720.
A first obtaining module 710, configured to obtain a source code of a common plug-in, where the common plug-in may be depended on by a plurality of business plug-ins, and at least two of the business plug-ins and the common plug-in may be used to implement a target application and may be loaded by a host program of the target application when the target application is implemented; and
a first compiling module 720, configured to compile the source code and output the common plug-in and a corresponding AAR package, where the AAR package is configured to provide a dependency relationship between the service plug-ins and the common plug-ins when compiling the plurality of service plug-ins.
By the embodiment of the disclosure, because the class, the C library and the resource which can be used by a plurality of plug-ins in a public dependence mode are separated from the host program, the plug-ins are developed into independent public plug-ins, and the service plug-in of the application program is loaded when the public depends on some public plug-ins, otherwise, the technical means of loading is not carried out, therefore, the defects that the application program in the related art is not divided into business plug-ins and public plug-ins, only the plug-ins and the host program are divided, the class, the C library and the resources which are not used by any plug-in public dependence in the application program are not used at all, and the class, the C library and the resources are also packaged in the public library of the host program in advance, so that the application program is large in size, numerous in methods, serious in resource consumption and the like are overcome at least in part, and further, the technical effects of reducing the volume of the application program and reducing the number of methods and resource consumption of the application program are achieved.
As an alternative embodiment, the system further comprises: the second acquisition module is used for acquiring a corresponding source code for each of the plurality of service plug-ins; the second compiling module is used for compiling the corresponding source code and outputting the corresponding service plug-in; and the first adding module is used for adding the dependency relationship in the configuration file of the corresponding service plug-in based on the AAR package in the process of compiling the corresponding source code.
Through the embodiment of the disclosure, in order to facilitate loading in runtime, the dependency relationship between the service plug-in and the public plug-in can be added in the configuration file of the service plug-in.
As an alternative embodiment, the common plug-in can also be reused inside each service plug-in; the system further comprises: and the second adding module is used for adding a dependency relationship into a configuration file of the service plug-in based on the AAR package and the repeated reference times of the public plug-in the process of compiling the source code of the service plug-in aiming at the service plug-in needing to reuse the public plug-in inside the plug-in.
By the embodiment of the disclosure, the classes, the C libraries and the resources repeatedly referenced in a single service plug-in can be split from the public library of the host program, developed into the public plug-in and loaded when the application program runs, so that the volume, the method number and the resource consumption of the application program can be reduced to a greater extent.
FIG. 8 schematically shows a block diagram of an application implementation system according to an embodiment of the present disclosure.
As shown in fig. 8, the application implementation system 800 includes a third obtaining module 810, a fourth obtaining module 820, a starting module 830, and a first loading module 840.
A third obtaining module 810, configured to obtain a plurality of service plugins and a common plugin for implementing an application, where the common plugin can be used by at least two common dependencies of the plurality of service plugins or can be reused inside the plugin by at least one of the plurality of service plugins;
a fourth obtaining module 820, configured to obtain a host program for implementing the application program;
a starting module 830, configured to start a plurality of service plug-ins by using a host program; and
the first loading module 840 is configured to load the common plug-in according to a predetermined loading logic in the process of starting the plurality of service plug-ins.
Through the embodiment of the disclosure, an improved application program implementation scheme is provided on the basis of a public plug-in and business plug-in implementation scheme. The classes, the C libraries and the resources which are only used in public dependence among the plurality of service plug-ins and/or the classes, the C libraries and the resources which are only repeatedly quoted in each service plug-in are separated from the host program to form one or more public plug-ins which are dynamically loaded, so that the classes, the C libraries and the resources which are respectively related to the repeated quote of the plurality of service plug-ins can be avoided, the method number and the resource consumption of the host program can be further reduced, the code redundancy is reduced, the size of the application program is reduced, and the installation and the starting of the application program are accelerated.
As an alternative embodiment, the first loading module includes: the checking unit is used for checking whether the corresponding service plug-in and the public plug-in have a dependency relationship in the starting process aiming at each of the plurality of service plug-ins; and the loading unit is used for loading the public plug-in under the condition that the dependency relationship exists.
By the embodiment of the disclosure, when the application program runs, only the public plug-in having the dependency relationship with the service plug-in of the application program is loaded, and the public plug-in having no dependency relationship is not loaded, so that the number of methods and resource consumption of the application program can be reduced, and the volume of the application program is reduced.
As an alternative embodiment, the application includes a load object; the system further comprises a second loading module for: loading a loading object through a loader of a service plug-in; or loading the loading object through a loader of the public plug-in; or the load object is loaded by the loader of the host program.
As an alternative embodiment, loading the object includes at least one of: class, C library, and resource.
Any one or more of the modules, units, or any other suitable combination thereof, in accordance with embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a programmable logic array (P L a), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or any other reasonable manner of integrating or packaging a circuit, such as a Field Programmable Gate Array (FPGA), a programmable logic array (P L a), a system on a chip, a system on a substrate, a system on a package, an ASIC, or any other reasonable manner of hardware or firmware, or any one or any combination thereof, or one or more of the modules, units, or any other suitable combination thereof, in accordance with embodiments of the present disclosure may be implemented at least in part as a computer program module that, when executed, may perform the corresponding functions.
For example, any number of the first obtaining module 710 and the first compiling module 720 may be combined into one module/unit/sub-unit, or any one of the modules/units/sub-units may be split into a plurality of modules/units/sub-units, or at least part of the functions of one or more of these modules/units/sub-units may be combined with at least part of the functions of the other modules/units/sub-units and implemented in one module/unit/sub-unit according to embodiments of the present disclosure, at least one of the first obtaining module 710 and the first compiling module 720 may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a programmable logic array (P L A), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or any other reasonable manner that may integrate or package the circuits, or be implemented in any one of three manners, or any suitable combination of the first obtaining module 710 and the first compiling module 720 may be implemented as a computer program when executed, at least part of the first obtaining module 710 and the first compiling module may be implemented as a computer program when executed by a computer.
It should be noted that, in the embodiments of the present disclosure, the system part implementation is the same as or similar to the method part implementation in the embodiments of the present disclosure, and for the description of the system part implementation, reference is specifically made to the description of the method part implementation, which is not described herein again.
FIG. 9 schematically illustrates a block diagram of a computer system suitable for implementing plug-ins and applications in accordance with an embodiment of the present disclosure. The computer system illustrated in FIG. 9 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the disclosure.
As shown in fig. 9, a computer system 900 according to an embodiment of the present disclosure includes a processor 901 which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. Processor 901 may comprise, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 901 may also include on-board memory for caching purposes. The processor 901 may comprise a single processing unit or a plurality of processing units for performing the different actions of the method flows according to embodiments of the present disclosure.
In the RAM 903, various programs and data necessary for the operation of the system 900 are stored. The processor 901, the ROM 902, and the RAM 903 are connected to each other through a bus 904. The processor 901 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 902 and/or the RAM 903. Note that the programs may also be stored in one or more memories other than the ROM 902 and the RAM 903. The processor 901 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.
The system 900 may further include AN input/output (I/O) interface 905, the input/output (I/O) interface 905 also being connected to the bus 904, the system 900 may further include one or more of AN input section 906 including a keyboard, a mouse, and the like, AN output section 907 including a device such as a Cathode Ray Tube (CRT), a liquid crystal display (L CD), and the like, and a speaker, a storage section 908 including a hard disk, and the like, and a communication section 909 including a network interface card such as a L AN card, a modem, and the like, the communication section 909 performs communication processing via a network such as the Internet, a drive 910 is also connected to the I/O interface 905 as necessary, a removable medium 911 such as a magnetic disk, AN optical disk, a magneto-optical disk, a semiconductor memory, and the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.
According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 909, and/or installed from the removable medium 911. The computer program, when executed by the processor 901, performs the above-described functions defined in the system of the embodiment of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 902 and/or the RAM 903 described above and/or one or more memories other than the ROM 902 and the RAM 903.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.
Claims (16)
1. A plug-in implementation method comprises the following steps:
obtaining source code of a public plug-in, wherein the public plug-in can be used by a plurality of business plug-ins in public dependence, and at least two of the business plug-ins and the public plug-in can be used for realizing a target application program and can be loaded by a host program of the target application program when the target application program is realized; and
compiling the source code and outputting the common plug-in and a corresponding AAR package, wherein the AAR package is used for providing the dependency relationship of the service plug-ins and the common plug-in when compiling the plurality of service plug-ins.
2. The method of claim 1, wherein the method further comprises:
acquiring a corresponding source code for each of the plurality of service plug-ins;
compiling the corresponding source code and outputting a corresponding service plug-in; and
and adding the dependency relationship in the configuration file of the corresponding service plug-in based on the AAR packet in the process of compiling the corresponding source code.
3. The method of claim 1 or 2, wherein:
the public plug-in can also be repeatedly used by each service plug-in;
the method further comprises the following steps:
and aiming at the service plug-in needing to reuse the public plug-in the plug-in, adding the dependency relationship into the configuration file of the service plug-in based on the repeated reference times of the AAR package and the public plug-in the process of compiling the source code of the service plug-in.
4. An application implementation method, comprising:
obtaining a plurality of business plug-ins and a common plug-in for implementing the application, wherein the common plug-in can be used by at least two common dependencies of the plurality of business plug-ins or can be reused inside the plug-ins by at least one of the plurality of business plug-ins;
acquiring a host program for realizing an application program;
starting the plurality of service plug-ins by using the host program; and
and in the process of starting the plurality of service plug-ins, loading the public plug-ins according to preset loading logic.
5. The method of claim 4, wherein loading the common plug-in according to a predetermined loading logic during the process of starting the plurality of service plug-ins comprises:
for each service plug-in the plurality of service plug-ins, checking whether a dependency relationship exists between the corresponding service plug-in and the public plug-in the starting process; and
if so, loading the public plug-in.
6. The method of claim 4, wherein:
the application program comprises a loading object;
the method further comprises the following steps:
loading the loading object through a loader of the service plug-in; or
Loading the loading object through a loader of the public plug-in; or
And loading the loading object through a loader of the host program.
7. The method of claim 4, wherein the load object comprises at least one of: class, C library, and resource.
8. A plug-in implementation system comprising:
the system comprises a first acquisition module, a first storage module and a second acquisition module, wherein the first acquisition module is used for acquiring a source code of a public plug-in, the public plug-in can be used by a plurality of business plug-ins in a public dependence, and at least two of the business plug-ins and the public plug-in can be used for realizing a target application program and can be loaded by a host program of the target application program when the target application program is realized; and
a first compiling module, configured to compile the source code and output the common plug-in and a corresponding AAR package, where the AAR package is configured to provide a dependency relationship between the service plug-ins and the common plug-in when compiling the plurality of service plug-ins.
9. The system of claim 8, wherein the system further comprises:
a second obtaining module, configured to obtain, for each of the plurality of service plug-ins, a corresponding source code;
the second compiling module is used for compiling the corresponding source code and outputting a corresponding service plug-in; and
a first adding module, configured to add the dependency relationship in a configuration file of the corresponding service plug-in based on the AAR package in a process of compiling the corresponding source code.
10. The system of claim 8 or 9, wherein:
the public plug-in can also be repeatedly used by each service plug-in;
the system further comprises:
and the second adding module is used for adding the dependency relationship into the configuration file of the service plug-in based on the AAR package and the repeated reference times of the public plug-in the process of compiling the source code of the service plug-in aiming at the service plug-in needing to reuse the public plug-in inside the plug-in.
11. An application implementation system, comprising:
a third obtaining module, configured to obtain a plurality of service plug-ins and a common plug-in for implementing the application, where the common plug-in may be used by at least two common dependencies of the plurality of service plug-ins or may be reused inside the plug-in by at least one of the plurality of service plug-ins;
the fourth acquisition module is used for acquiring a host program for realizing the application program;
the starting module is used for starting the plurality of service plug-ins by using the host program; and
and the first loading module is used for loading the public plug-in according to a preset loading logic in the process of starting the plurality of service plug-ins.
12. The system of claim 11, wherein the first load module comprises:
the checking unit is used for checking whether the corresponding service plug-in and the public plug-in have a dependency relationship or not in the starting process aiming at each service plug-in; and
and the loading unit is used for loading the public plug-in under the condition that the dependency relationship exists.
13. The system of claim 11, wherein:
the application program comprises a loading object;
the system further comprises a second loading module for:
loading the loading object through a loader of the service plug-in; or
Loading the loading object through a loader of the public plug-in; or
And loading the loading object through a loader of the host program.
14. The system of claim 11, wherein the load object comprises at least one of: class, C library, and resource.
15. A computer system, comprising:
one or more processors;
a memory for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-7.
16. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910022287.0A CN111427579A (en) | 2019-01-09 | 2019-01-09 | Plug-in, application program implementing method and system, computer system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910022287.0A CN111427579A (en) | 2019-01-09 | 2019-01-09 | Plug-in, application program implementing method and system, computer system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111427579A true CN111427579A (en) | 2020-07-17 |
Family
ID=71545990
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910022287.0A Pending CN111427579A (en) | 2019-01-09 | 2019-01-09 | Plug-in, application program implementing method and system, computer system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111427579A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111857689A (en) * | 2020-07-27 | 2020-10-30 | 深信服科技股份有限公司 | Framework, function configuration method of framework, terminal and storage medium |
| CN112416425A (en) * | 2020-11-20 | 2021-02-26 | 微医云(杭州)控股有限公司 | APP construction method and device, computer equipment and storage medium |
| CN112486512A (en) * | 2020-11-25 | 2021-03-12 | 湖南麒麟信安科技股份有限公司 | Linux general software adaptation method and system based on container and stacked file system |
| CN112540788A (en) * | 2020-12-03 | 2021-03-23 | 南方电网数字电网研究院有限公司 | Method compatible with multi-manufacturer unmanned aerial vehicle flight control application apps |
| CN113282347A (en) * | 2021-05-24 | 2021-08-20 | 挂号网（杭州）科技有限公司 | Plug-in operation method, device, equipment and storage medium |
| CN113407165A (en) * | 2021-06-29 | 2021-09-17 | 北京字节跳动网络技术有限公司 | SDK generation and self-upgrade method, device, readable medium and equipment |
-
2019
- 2019-01-09 CN CN201910022287.0A patent/CN111427579A/en active Pending
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111857689A (en) * | 2020-07-27 | 2020-10-30 | 深信服科技股份有限公司 | Framework, function configuration method of framework, terminal and storage medium |
| CN112416425A (en) * | 2020-11-20 | 2021-02-26 | 微医云(杭州)控股有限公司 | APP construction method and device, computer equipment and storage medium |
| CN112486512A (en) * | 2020-11-25 | 2021-03-12 | 湖南麒麟信安科技股份有限公司 | Linux general software adaptation method and system based on container and stacked file system |
| CN112540788A (en) * | 2020-12-03 | 2021-03-23 | 南方电网数字电网研究院有限公司 | Method compatible with multi-manufacturer unmanned aerial vehicle flight control application apps |
| CN113282347A (en) * | 2021-05-24 | 2021-08-20 | 挂号网（杭州）科技有限公司 | Plug-in operation method, device, equipment and storage medium |
| CN113407165A (en) * | 2021-06-29 | 2021-09-17 | 北京字节跳动网络技术有限公司 | SDK generation and self-upgrade method, device, readable medium and equipment |
| CN113407165B (en) * | 2021-06-29 | 2023-04-07 | 抖音视界有限公司 | SDK generation and self-upgrade method, device, readable medium and equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111427579A (en) | Plug-in, application program implementing method and system, computer system and storage medium | |
| US10528742B2 (en) | Method and apparatus for repairing kernel vulnerability | |
| CN111221521A (en) | Method and device for generating log code, computer system and readable storage medium | |
| US20150363195A1 (en) | Software package management | |
| CN110895471A (en) | Installation package generation method, device, medium and electronic equipment | |
| CN110865889A (en) | Method and apparatus for transferring events between components | |
| CN113127361A (en) | Application program development method and device, electronic equipment and storage medium | |
| CN115982491A (en) | Page updating method and device, electronic equipment and computer readable storage medium | |
| CN110457065B (en) | Method and apparatus for obtaining applications compatible with multi-version systems | |
| CN111142972B (en) | Method, apparatus, system, and medium for extending functions of application program | |
| US20180341475A1 (en) | Just In Time Deployment with Package Managers | |
| CN115248680A (en) | Software construction method, system, device, medium, and program product | |
| CN116431137A (en) | Cross-development-framework component conversion method, processing system and component conversion device | |
| CN112506781B (en) | Test monitoring method, device, electronic equipment, storage medium and program product | |
| CN116503005A (en) | Method, device, system and storage medium for dynamically modifying flow | |
| CN112068814A (en) | Method, device, system and medium for generating executable file | |
| CN114253599A (en) | Version deployment method, version deployment device, electronic device and storage medium | |
| CN111859403A (en) | Method and device for determining dependency vulnerability, electronic equipment and storage medium | |
| CN112882698A (en) | Development environment generation method and device, computer storage medium and electronic device | |
| CN113805878B (en) | Plug-in engineering method, device, computer system and medium | |
| CN116452208B (en) | Method, device, equipment and medium for determining change transaction code | |
| CN113515326B (en) | Data conversion method, device, electronic equipment and storage medium | |
| US20230259347A1 (en) | Container based generation of inputs for generic functions | |
| CN113051090A (en) | Interface processing method and device, interface calling method and device, system and medium | |
| CN116932032A (en) | Application program creation method and device, electronic equipment and readable 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 |