Application management method, device, electronic device and storage medium

Abstract

This application proposes an application management method, apparatus, electronic device, and storage medium, which can conveniently obtain applications with specified functions, thereby improving development efficiency. The application management method includes: receiving an input packaging instruction, the packaging instruction carrying a first packaging mechanism identifier or a second packaging mechanism identifier; determining the target packaging mechanism corresponding to the target packaging mechanism identifier based on the correspondence between the packaging mechanism identifier and the packaging mechanism, wherein the target packaging mechanism identifier is either the first packaging mechanism identifier or the second packaging mechanism identifier, and the target packaging mechanism is either the first packaging mechanism or the second packaging mechanism; and packaging multiple functional modules developed based on a component-based model into a target application using the target packaging mechanism.

Description

[Technical field]

[0001] The embodiments of the present application relate to the field of software development technology, and in particular to a method, device, electronic device and storage medium for managing an application. [Background technology]

[0002] As the application of in-vehicle intelligent systems becomes more and more widespread, the project cycle of in-vehicle application development is generally long. During the development cycle, the update and iteration of application functions on the market are also changing rapidly. Multiple applications planned in the early stage may need to be merged into one application due to some changes in the middle, or a large application planned in the early stage may need to be split into multiple small applications.

[0003] In the prior art, when encountering the above situation, the application needs to be decoupled into single functional modules before merging or splitting can be completed. The decoupling process inevitably involves some additional development work, resulting in low development efficiency for obtaining a large application or multiple small applications. [Summary of the invention]

[0004] The embodiments of the present application provide an application management method, device, electronic device and storage medium, which can more conveniently obtain applications with specified functions, thereby improving development efficiency.

[0005] In a first aspect, an embodiment of the present application provides a method for managing an application, the method comprising:

[0006] Receive an input packaging instruction, wherein the packaging instruction carries a first packaging mechanism identifier or a second packaging mechanism identifier, wherein the first packaging mechanism identifier is an identifier of a first packaging mechanism, and the first packaging mechanism is used to indicate that a single functional module is packaged into a single application program, and the second packaging mechanism identifier is an identifier of a second packaging mechanism, and the second packaging mechanism is used to indicate that at least two functional modules are packaged together into a single application program;

[0007] Determine, based on the correspondence between the packaging mechanism identifier and the packaging mechanism, a target packaging mechanism corresponding to the target packaging mechanism identifier, wherein the target packaging mechanism identifier is the first packaging mechanism identifier or the second packaging mechanism identifier, and the target packaging mechanism is the first packaging mechanism or the second packaging mechanism;

[0008] The target packaging mechanism is used to package multiple functional modules developed based on the componentization mode into a target application.

[0009] In the embodiment of the present application, the multiple functional modules that have been developed are developed based on a componentized mode, that is, it can be considered that the coupling degree between the above-mentioned multiple functional modules is low and there is no need for artificial decoupling. Therefore, according to actual needs, the above-mentioned multiple functional modules can be conveniently packaged into a single application, or each of the above-mentioned multiple functional modules can be independently packaged into a corresponding application, thereby improving development efficiency.

[0010] Optionally, the target packaging mechanism identifier is the first packaging mechanism identifier, and based on the correspondence between the packaging mechanism identifier and the packaging mechanism, determining the target packaging mechanism corresponding to the target packaging mechanism identifier includes:

[0011] Based on the correspondence between the packaging mechanism identifier and the packaging mechanism, determining that the target packaging mechanism corresponding to the first packaging mechanism identifier is the first packaging mechanism;

[0012] Packaging multiple functional modules developed based on the componentization mode into a target application using the target packaging mechanism includes:

[0013] Each of the multiple functional modules is packaged into a corresponding target application program using the first packaging mechanism through an application construction open source tool, and the application construction open source tool and the multiple functional modules are in the same engineering project.

[0014] In an embodiment of the present application, when the target packaging mechanism identifier is the first packaging mechanism identifier, it indicates that the target packaging mechanism executed by the user is to package a single functional module into a single application. At this time, an open source tool can be built through an application that is located in the same engineering project as multiple functional modules developed based on a componentized model, so that a single functional module can be packaged into a corresponding single application more conveniently.

[0015] Optionally, packaging each of the multiple functional modules into a corresponding target application program by using the first packaging mechanism through an application construction open source tool includes:

[0016] Based on the pre-configured target application entry address of each functional module in the plurality of functional modules, searching for the corresponding target application entry, the target application entry being the entry of the target application, and the target application entry address being the address of the target application entry;

[0017] Initializing each of the functional modules at the target application entry;

[0018] The application construction open source tool packages each of the initialized functional modules into a corresponding target application program using the first packaging mechanism.

[0019] In the embodiment of the present application, if each of the multiple function modules is to be packaged into the corresponding target application, it is necessary to pass through the target application entry, so each function module can be considered to be configured with a corresponding target program entry. During the packaging process, the target program entry corresponding to each function module can be found based on the address of the target application entry. After entering the target application entry, the target application entry initializes the function module. After the function module is initialized, the initialized function module can be packaged into the corresponding target application more conveniently through the application construction open source tool.

[0020] Optionally, packaging the initialized functional modules into corresponding target application programs by using the first packaging mechanism through the application construction open source tool includes:

[0021] The initialized functional modules and pre-configured preset name variables are packaged by using the application construction open source tool using the first packaging mechanism to obtain the target application program marked with the preset name variables.

[0022] In an embodiment of the present application, an open source tool can be applied to build an open source tool and a first packaging mechanism can be used to package the initialized functional modules together with the preset name variables into corresponding target applications, so that each target application has a unique identifier, so that users can quickly distinguish between the target applications.

[0023] Optionally, the target packaging mechanism identifier is the second packaging mechanism identifier, and based on the correspondence between the packaging mechanism identifier and the packaging mechanism, determining the target packaging mechanism corresponding to the target packaging mechanism identifier includes:

[0024] Based on the correspondence between the packaging mechanism identifier and the packaging mechanism, determining that the target packaging mechanism corresponding to the second packaging mechanism identifier is the second packaging mechanism;

[0025] Packaging multiple functional modules developed based on the componentization mode into a target application based on the target packaging mechanism includes:

[0026] The plurality of functional modules are packaged into a target application program by using an open source application construction tool using the second packaging mechanism. The open source application construction tool and the plurality of functional modules are in the same engineering project.

[0027] In an embodiment of the present application, when the target packaging mechanism identifier is the second packaging mechanism identifier, it indicates that the target packaging mechanism executed by the user is to package at least two functional modules together into a single application. At this time, an open source tool can be built through an application that is located in the same engineering project as multiple functional modules developed based on a componentized model, so that multiple functional modules can be packaged into a target application more conveniently.

[0028] Optionally, packaging the plurality of functional modules into a target application program by using the second packaging mechanism through an application construction open source tool includes:

[0029] Based on the pre-configured common target application entry address of the plurality of functional modules, searching for a corresponding target application entry, the target application entry being the entry of the target application, and the target application entry address being the address of the target application entry;

[0030] Initializing the multiple functional modules at the target application entry;

[0031] The application construction open source tool is used to package the initialized multiple functional modules into one target application program using the second packaging mechanism.

[0032] In the embodiment of the present application, if multiple functional modules are to be packaged into a target application, they need to pass through the target application entry, so the multiple functional modules can be considered to be configured with a common target program entry. During the packaging process, the target program entry common to the multiple functional modules can be found based on the address of the target application entry, and after entering the target application entry, the target application entry initializes the multiple functional modules. After the multiple functional modules are initialized, the multiple functional modules can be packaged into a target application more conveniently through the application construction open source tool.

[0033] Optionally, packaging the initialized multiple functional modules into one target application program by using the second packaging mechanism through the application construction open source tool includes:

[0034] The initialized multiple functional modules and the pre-configured preset name variables are packaged by the application construction open source tool using the second packaging mechanism to obtain a target application program marked with the preset name variable.

[0035] In an embodiment of the present application, an open source tool can be applied to build an open source tool and a second packaging mechanism can be used to package multiple initialized functional modules together with preset name variables into a target application, so that the target application has a unique identifier, so that the user can quickly determine whether the multiple functional modules are packaged successfully.

[0036] In a second aspect, an embodiment of the present application provides a device for managing an application, the device comprising:

[0037] A receiving unit, configured to receive an input packaging instruction, wherein the packaging instruction carries a first packaging mechanism identifier or a second packaging mechanism identifier, wherein the first packaging mechanism identifier is an identifier of a first packaging mechanism, and the first packaging mechanism is used to indicate that a single functional module is packaged into a single application program, and the second packaging mechanism identifier is an identifier of a second packaging mechanism, and the second packaging mechanism is used to indicate that at least two functional modules are packaged together into a single application program;

[0038] a determining unit, configured to determine a target packaging mechanism corresponding to a target packaging mechanism identifier based on a correspondence between a packaging mechanism identifier and a packaging mechanism, wherein the target packaging mechanism identifier is the first packaging mechanism identifier or the second packaging mechanism identifier, and the target packaging mechanism is the first packaging mechanism or the second packaging mechanism;

[0039] The packaging unit is used to package multiple functional modules developed based on the componentization mode into a target application using the target packaging mechanism.

[0040] Optionally, the target packaging mechanism identifier is the first packaging mechanism identifier, and the determining unit is specifically configured to:

[0041] Based on the correspondence between the packaging mechanism identifier and the packaging mechanism, determining that the target packaging mechanism corresponding to the first packaging mechanism identifier is the first packaging mechanism;

[0042] The packaging unit comprises:

[0043] The first packaging mechanism packaging unit is used to package each of the multiple functional modules into a corresponding target application program using the first packaging mechanism through an application construction open source tool, and the application construction open source tool and the multiple functional modules are in the same engineering project.

[0044] Optionally, the first packaging mechanism packaging unit includes:

[0045] A search subunit, configured to search for a corresponding target application entry based on a pre-configured target application entry address of each functional module in the plurality of functional modules, wherein the target application entry is an entry of the target application, and the target application entry address is an address of the target application entry;

[0046] An initialization subunit, used for initializing each of the functional modules at the target application entry;

[0047] The first packaging mechanism packaging subunit is used to package each of the initialized functional modules into a corresponding target application program by using the first packaging mechanism through the application construction open source tool.

[0048] Optionally, the first packaging mechanism packaging subunit is specifically used for:

[0049] The initialized functional modules and pre-configured preset name variables are packaged by using the application construction open source tool using the first packaging mechanism to obtain the target application program marked with the preset name variables.

[0050] Optionally, the target packaging mechanism identifier is the second packaging mechanism identifier, and the determining unit is specifically configured to:

[0051] Based on the correspondence between the packaging mechanism identifier and the packaging mechanism, determining that the target packaging mechanism corresponding to the second packaging mechanism identifier is the second packaging mechanism;

[0052] The packaging unit comprises:

[0053] The second packaging mechanism packaging unit is used to package the multiple functional modules into a target application program by using the second packaging mechanism through an application construction open source tool, and the application construction open source tool and the multiple functional modules are in the same engineering project.

[0054] Optionally, the second packaging mechanism packaging unit includes:

[0055] A search subunit, configured to search for a corresponding target application entry based on a pre-configured target application entry address common to the plurality of functional modules, wherein the target application entry is an entry of the target application, and the target application entry address is an address of the target application entry;

[0056] The initialization subunit packages the initialized multiple functional modules into a corresponding target application program through the application construction open source tool.

[0057] The second packaging mechanism packaging sub-unit is used to use the application construction open source tool to package the initialized multiple functional modules into one target application program by using the second packaging mechanism.

[0058] Optionally, the second packaging mechanism packaging subunit is specifically used for:

[0059] The initialized multiple functional modules and the pre-configured preset name variables are packaged by the application construction open source tool using the second packaging mechanism to obtain a target application program marked with the preset name variable.

[0060] In a third aspect, an embodiment of the present application provides an electronic device, comprising a processor and a memory, wherein the processor is configured to implement the steps of the method described in any embodiment of the first aspect when executing a computer program stored in the memory.

[0061] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the method described in any embodiment of the first aspect are implemented.

[0062] It should be understood that the second to third aspects of the embodiments of the present application are consistent with the technical solutions of the first aspect of the embodiments of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here.

Brief Description of the Drawings

[0063] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0064] Figure 1 A flowchart of a method for managing an application program provided in an embodiment of the present application;

[0065] Figure 2 A corresponding relationship diagram between functional modules and application programs in the first packaging mechanism provided in an embodiment of the present application;

[0066] Figure 3 A corresponding relationship diagram between functional modules and application programs in the second packaging mechanism provided in an embodiment of the present application;

[0067] Figure 4 A schematic diagram of the structure of an application management device provided in an embodiment of the present application;

[0068] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. [Specific implementation method]

[0069] In order to better understand the technical solution of this specification, the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0070] It should be clear that the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0071] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit this specification. The singular forms of "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.

[0072] The inventors of this application have discovered through research that in the related art, when it is necessary to merge multiple applications into a large application, or split a large application into multiple small applications, it often involves a process of decoupling the application into single functional modules. The decoupling process inevitably involves some additional development work, resulting in low development efficiency for obtaining a large application or multiple small applications.

[0073] In view of this, an embodiment of the present application provides an application management method, in which multiple functional modules are developed based on a componentized mode, that is, it can be considered that the coupling degree between the above-mentioned multiple functional modules is low, and there is no need for artificial decoupling. Then, according to actual needs, the above-mentioned multiple functional modules can be more conveniently packaged into a single application, or each of the above-mentioned multiple functional modules can be independently packaged into a corresponding application, thereby improving development efficiency.

[0074] The technical solution provided by the embodiment of the present application is introduced below in conjunction with the accompanying drawings. Figure 1 The embodiment of the present application provides a method for managing an application program. The method is applied to an electronic device, which may be a laptop computer, a desktop computer, a server, etc., and is not particularly limited here. The method flow is described as follows:

[0075] Step 101: Receive an input packaging instruction.

[0076] In the embodiment of the present application, the developer develops multiple functional modules based on the componentized mode, and sets two types of packaging mechanisms: the first packaging mechanism is to package a single functional module into a single application; the second packaging mechanism is to package at least two functional modules into one application. On this basis, the developer can choose any of the above packaging mechanisms to conveniently form the final application according to his actual development needs. Before this, the developer needs to inform the electronic device of his actual development needs.

[0077] As a possible implementation method, the developer can input a packaging instruction to the electronic device. When the developer wants to package the above-mentioned multiple functional modules based on the first packaging mechanism, the input packaging instruction can be considered to carry the first packaging mechanism identifier, and the first packaging mechanism identifier can be considered to be the identifier of the first packaging mechanism; when the developer wants to package the above-mentioned multiple functional modules based on the second packaging mechanism, the input packaging instruction can be considered to carry the second packaging mechanism identifier, and the second packaging mechanism identifier can be considered to be the identifier of the second packaging mechanism.

[0078] Step 102: Based on the correspondence between the packaging mechanism identifier and the packaging mechanism, determine the target packaging mechanism corresponding to the target packaging mechanism identifier.

[0079] In the embodiment of the present application, after receiving the input packaging instruction, the electronic device can identify the actual packaging requirements of the developer according to the packaging instruction, and then perform the packaging action according to the actual packaging requirements of the developer.

[0080] As a possible approach, the electronic device can be considered to have pre-stored a correspondence between a packing mechanism identifier and a packing mechanism, and then the corresponding target packing mechanism can be determined based on the target packing mechanism identifier carried in the packing instruction and the above-mentioned correspondence. It should be understood that the target packing mechanism identifier here is the first packing mechanism identifier or the second packing mechanism identifier, and the target packing mechanism is the first packing mechanism or the second packing mechanism.

[0081] Step 103: Package multiple functional modules developed based on the componentization mode into a target application using a target packaging mechanism.

[0082] In the embodiment of the present application, after determining the target packaging mechanism, the electronic device can package the developed multiple functional modules into a target application based on the target packaging mechanism. The following describes in detail how to package under the two packaging mechanisms.

[0083] Packaging method 1: Packaging based on the first packaging mechanism.

[0084] In the embodiment of the present application, when the target packaging mechanism identifier is the first packaging mechanism identifier, based on the correspondence between the packaging mechanism identifier and the packaging mechanism, it can be determined that the target packaging mechanism corresponding to the first packaging mechanism identifier is the first packaging mechanism.

[0085] After determining to use the first packaging mechanism, each of the multiple functional modules can be packaged into a corresponding target application using the first packaging mechanism through an application construction open source tool in the same engineering project as the multiple functional modules. For example, the application construction open source tool in the same engineering project is gradle.

[0086] Specifically, considering that each functional module needs to be packaged into the corresponding target application, it needs to pass through the target application entry, that is, the entry of the target application, so each functional module can be considered to be configured with a corresponding target program entry address, that is, the address of the target program entry. In the formal packaging process, the electronic device can find the corresponding target application entry based on the target application entry address pre-configured for each functional module in multiple functional modules. Then initialize the corresponding functional module at each target application entry. Finally, use the application to build an open source tool to package each initialized functional module into a corresponding target application using the first packaging mechanism.

[0087] For example, Figure 2 As shown, in the formal packaging process, there are n function modules that need to be packaged, n is a natural number not less than 1, and these n function modules are function module 1, function module 2, ..., function module n. Taking function module 1 as an example, based on the pre-configured target program entry address of function module 1, the corresponding target application entry is found. Exemplarily, it can be considered that function module 1 matches entry address 1, and function module 1 finds the corresponding target application entry 1 (not shown in the figure) according to entry address 1, and then the application entry 1 initializes function module 1, and then the initialized function module 1 is packaged into the corresponding target application using the first packaging mechanism through the application construction open source tool.

[0088] Taking into account that multiple independent applications will be formed when packaging is performed based on the first packaging mechanism, in an embodiment of the present application, corresponding unique identifiers can be added to the ultimately formed applications so that developers can quickly distinguish between the various target applications.

[0089] As a possible implementation, the electronic device can assume that the application formed after packaging each functional module is configured with a corresponding preset name variable. During the formal packaging process, the initialized functional modules and the pre-configured preset name variables can be packaged using the first packaging mechanism to obtain a target application identified with a preset name variable.

[0090] For example, see Figure 2 Taking function module 1 as an example, after function module 1 is initialized, it will be packaged with the pre-configured preset name variable A using the first packaging mechanism. The name of the application obtained after packaging is the preset name A, and the preset name A is the unique identifier of the final application.

[0091] Packaging method 2: Packaging based on the second packaging mechanism.

[0092] In an embodiment of the present application, when the target packaging mechanism identifier is the second packaging mechanism identifier, based on the correspondence between the packaging mechanism identifier and the packaging mechanism, it can be determined that the target packaging mechanism corresponding to the second packaging mechanism identifier is the second packaging mechanism.

[0093] After the second packaging mechanism is determined, multiple functional modules can be packaged into the same target application using the second packaging mechanism through an application construction open source tool in the same engineering project as the multiple functional modules. For example, the application construction open source tool in the same engineering project is gradle.

[0094] Specifically, considering that all functional modules in the same project must be packaged into a target application and must pass through the target application entry, that is, the target application entry, all functional modules in the same project can be considered to match the pre-configured target application entry address, that is, the address of the target program entry. In the formal packaging process, the electronic device can find the target application entry based on the pre-configured target application entry addresses of multiple functional modules. Then, all functional modules in the same project are initialized at the target application entry. Finally, the multiple functional modules after initialization are packaged into the same target application using a second packaging mechanism by applying an open source tool.

[0095] For example, Figure 3 As shown, in the formal packaging process, there are m function modules in the same project that need to be packaged into a target application, where m is a natural number not less than 1, and these m function modules are function module 1, function module 2, ..., function module m. All function modules find out the target application entry s based on the pre-configured target program entry address s (not shown in the figure), and it can be considered that function module 1, function module 2, ..., function module m all match the entry address s, and function module 1, function module 2, ... function module m will find the corresponding target application entry s according to the entry address s, and then initialize the application entry s, and then use the application to build the open source tool to package the initialized function module 1, function module 2, ... function module m into the same target application using the second packaging mechanism.

[0096] Taking into account that only one independent application is formed when packaging is performed based on the second packaging mechanism, therefore, in an embodiment of the present application, a corresponding unique identifier can be added to the finally formed application.

[0097] As a possible implementation, the electronic device can assume that the application formed after packaging each functional module is configured with a corresponding preset name variable. During the formal packaging process, the initialized functional modules and the pre-configured preset name variables can be packaged using a second packaging mechanism to obtain a target application identified with a preset name variable.

[0098] For example, see Figure 3 After being initialized, function module 1, function module 2, ..., function module m will be packaged with the pre-configured preset name variable Z using the second packaging mechanism. The name of the application obtained after packaging is the preset name Z, and the preset name Z is the unique identifier of the final application.

[0099] See also Figure 4 Based on the same inventive concept, the embodiment of the present application further provides a management device for an application program, the device comprising:

[0100] The receiving unit 201 is used to receive an input packaging instruction, where the packaging instruction carries a first packaging mechanism identifier or a second packaging mechanism identifier, where the first packaging mechanism identifier is an identifier of a first packaging mechanism, and the first packaging mechanism is used to indicate that a single functional module is packaged into a single application program, and the second packaging mechanism identifier is an identifier of a second packaging mechanism, and the second packaging mechanism is used to indicate that at least two functional modules are packaged together into a single application program;

[0101] The determining unit 202 is used to determine the target packaging mechanism corresponding to the target packaging mechanism identifier based on the correspondence between the packaging mechanism identifier and the packaging mechanism, the target packaging mechanism identifier is the first packaging mechanism identifier or the second packaging mechanism identifier, and the target packaging mechanism is the first packaging mechanism or the second packaging mechanism;

[0102] A packaging unit 203 is used to package multiple functional modules developed based on the componentization mode into a target application using a target packaging mechanism;

[0103] Optionally, the target packaging mechanism identifier is the first packaging mechanism identifier, and the determining unit 202 is specifically configured to:

[0104] Based on the correspondence between the packaging mechanism identifier and the packaging mechanism, determining that the target packaging mechanism corresponding to the first packaging mechanism identifier is the first packaging mechanism;

[0105] The packaging unit 203 includes:

[0106] The first packaging mechanism packaging unit is used to package each of the multiple functional modules into a corresponding target application program using the first packaging mechanism by applying an open source construction tool, and the application construction open source tool and the multiple functional modules are in the same engineering project.

[0107] Optionally, the first packaging mechanism packaging unit includes:

[0108] A search subunit, used to search for a corresponding target application entry based on a target application entry address of each functional module in a plurality of pre-configured functional modules, wherein the target application entry is an entry of the target application, and the target application entry address is an address of the target application entry;

[0109] An initialization subunit is used to initialize each functional module at the target application entry;

[0110] The first packaging mechanism packaging sub-unit is used to package each initialized functional module into a corresponding target application program by using the first packaging mechanism through the application construction open source tool.

[0111] Optionally, the first packaging mechanism packaging subunit is specifically used for:

[0112] The initialized functional modules and pre-configured preset name variables are packaged by using an open source application construction tool using a first packaging mechanism to obtain a target application program marked with the preset name variables.

[0113] Optionally, the target packaging mechanism identifier is a second packaging mechanism identifier, and the determining unit 202 is specifically configured to:

[0114] Based on the correspondence between the packaging mechanism identifier and the packaging mechanism, determining that the target packaging mechanism corresponding to the second packaging mechanism identifier is the second packaging mechanism;

[0115] The packaging unit 203 includes:

[0116] The second packaging mechanism packaging unit is used to package multiple functional modules into a target application program by using the second packaging mechanism through an application construction open source tool, and the application construction open source tool and the multiple functional modules are in the same engineering project.

[0117] Optionally, the second packaging mechanism packaging unit includes:

[0118] A search subunit, used to search for a corresponding target application entry based on a target application entry address common to a plurality of pre-configured functional modules, wherein the target application entry is an entry of the target application, and the target application entry address is an address of the target application entry;

[0119] The initialization subunit packages the initialized multiple functional modules into a corresponding target application program by applying the open source construction tool.

[0120] The second packaging mechanism packaging sub-unit is used to package the initialized multiple functional modules into a target application program by using the second packaging mechanism through the application construction open source tool.

[0121] Optionally, the second packaging mechanism packaging subunit is specifically used for:

[0122] The initialized multiple functional modules and the pre-configured preset name variables are packaged by using an open source application construction tool using a second packaging mechanism to obtain a target application program marked with the preset name variable.

[0123] See also Figure 5 Based on the same inventive concept, an embodiment of the present application provides an electronic device, the electronic device includes at least one processor 301, the processor 301 is used to execute a computer program stored in a memory, and implement the embodiment of the present application as provided in Figure 1 The steps of the application management method are shown.

[0124] Optionally, the processor 301 may specifically be a central processing unit, a specific ASIC, or one or more integrated circuits for controlling program execution.

[0125] Optionally, the electronic device may further include a memory 302 connected to the at least one processor 301, and the memory 302 may include a ROM, a RAM, and a disk memory. The memory 302 is used to store data required by the processor 301 when it is running, that is, it stores instructions that can be executed by the at least one processor 301. The at least one processor 301 executes the instructions stored in the memory 302 to execute the following steps: Figure 1 The method shown. The number of the memory 302 is one or more. The memory 302 is Figure 5 However, it should be noted that the memory 302 is not a mandatory functional module, so Figure 5 Shown by dotted lines.

[0126] The physical devices corresponding to the receiving unit 201, the determining unit 202 and the packaging unit 203 can all be the aforementioned processor 301. The electronic device can be used to execute Figure 1 Therefore, for the functions that can be realized by each functional module in the electronic device, please refer to Figure 1 The corresponding description in the illustrated embodiment will not be repeated here.

[0127] The present application also provides a computer storage medium, wherein the computer storage medium stores computer instructions, and when the computer instructions are executed on a computer, the computer executes Figure 1 The method described.

[0128] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A method for managing an application program, It is characterized in that The method comprises: Receive an input packaging instruction, wherein the packaging instruction carries a first packaging mechanism identifier or a second packaging mechanism identifier, wherein the first packaging mechanism identifier is an identifier of a first packaging mechanism, and the first packaging mechanism is used to indicate that a single functional module is packaged into a single application program, and the second packaging mechanism identifier is an identifier of a second packaging mechanism, and the second packaging mechanism is used to indicate that at least two functional modules are packaged together into a single application program; Determine, based on the correspondence between the packaging mechanism identifier and the packaging mechanism, a target packaging mechanism corresponding to the target packaging mechanism identifier, wherein the target packaging mechanism identifier is the first packaging mechanism identifier or the second packaging mechanism identifier, and the target packaging mechanism is the first packaging mechanism or the second packaging mechanism; Packing multiple functional modules developed based on the componentization mode into a target application using the target packaging mechanism; Among them, the functional modules are included by applying open source tools, including: When the target packaging mechanism is the first packaging mechanism, based on the pre-configured target application entry address of each functional module, the target application entry of each functional module is searched, a single functional module is initialized at the target application entry, and each of the initialized functional modules is packaged into a corresponding target application using the first packaging mechanism through the application construction open source tool; When the target packaging mechanism is the second packaging mechanism, based on the common target application entry address of the pre-configured multiple functional modules, the corresponding target application entry is found, and the multiple functional modules are initialized at the target application entry; the multiple functional modules after initialization are packaged into one target application using the second packaging mechanism through the application construction open source tool.

2. The method according to claim 1, It is characterized in that Packaging the initialized functional modules into corresponding target application programs by using the first packaging mechanism through the application construction open source tool includes: The initialized functional modules and pre-configured preset name variables are packaged by using the application construction open source tool using the first packaging mechanism to obtain the target application program marked with the preset name variables.

3. The method according to claim 1, It is characterized in that Using the application construction open source tool to package the initialized multiple functional modules into one target application using the second packaging mechanism includes: The initialized multiple functional modules and the pre-configured preset name variables are packaged by the application construction open source tool using the second packaging mechanism to obtain a target application program marked with the preset name variable.

4. A device for managing an application program, It is characterized in that The device comprises: A receiving unit receives an input packaging instruction, wherein the packaging instruction carries a first packaging mechanism identifier representing packaging a single functional module into a single application, or carries a second packaging mechanism identifier representing packaging at least two functional modules into a single application; a determining unit, which determines a target packaging mechanism corresponding to the target packaging mechanism identifier based on a correspondence between the packaging mechanism identifier and the packaging mechanism, wherein the target packaging mechanism identifier is the first packaging mechanism identifier or the second packaging mechanism identifier; A packaging unit, which packages a plurality of functional modules developed based on the componentization mode into a target application based on the target packaging mechanism; Among them, the functional modules are included by applying open source tools, including: When the target packaging mechanism is the first packaging mechanism, based on the pre-configured target application entry address of each functional module, the target application entry of each functional module is searched, a single functional module is initialized at the target application entry, and each of the initialized functional modules is packaged into a corresponding target application using the first packaging mechanism through the application construction open source tool; When the target packaging mechanism is the second packaging mechanism, based on the common target application entry address of the pre-configured multiple functional modules, the corresponding target application entry is found, and the multiple functional modules are initialized at the target application entry; the multiple functional modules after initialization are packaged into one target application using the second packaging mechanism through the application construction open source tool.

5. An electronic device, It is characterized in that The electronic device comprises at least one processor and a memory connected to the at least one processor, and the at least one processor is configured to implement the steps of the method according to any one of claims 1 to 3 when executing a computer program stored in the memory.

6. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 3 are implemented.

Images