CN114911509A - Configuration method, equipment and storage medium of patch package - Google Patents

Abstract

The application belongs to the technical field of computers, and provides a configuration method, equipment and a storage medium of a patch package, which can effectively solve the problem that different application programs cannot be embedded as required in the process of multiplexing functional component codes in the traditional technology. The method comprises the following steps: acquiring a template patch package, replacing the templated parameters in the template patch package with instantiation parameters adapted to the second application program, and generating a target patch package; the target patch package is applied to a second application.

Description

Configuration method, equipment and storage medium of patch package

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, and a storage medium for configuring a patch package.

Background

At present, applications in electronic devices are generally developed based on an existing development framework, and functional modules for implementing different functions are generally included in the respective applications.

Based on a unified development framework, after an electronic device develops a certain functional module in an application a, when an application B also needs to develop the functional module, a general method is to rely a functional component code corresponding to the functional module in the application a on the application B in a patch package manner, so that the application B has the functional module at the same time. However, all the functions corresponding to the functional module in the application a are not all necessary for the application B, and therefore, when the electronic device applies the electronic device to the application B, the functional component codes in the system a need to be re-carded to obtain the functional component codes adapted to the system B. It can be seen that the functional modules developed by application a and application B cannot implement quick reuse and embed components as needed.

Disclosure of Invention

In view of this, embodiments of the present application provide a method, a device, and a storage medium for configuring a patch package, so as to solve the problem that different application programs cannot be embedded as needed in the process of multiplexing functional component codes in the prior art.

A first aspect of an embodiment of the present application provides a method for configuring a patch package, including: acquiring a template patch package; replacing the templated parameters in the template patch package with instantiation parameters adapted to a second application program to generate a target patch package; and applying the target patch package to the second application program.

It should be understood that the target patch package is the second patch package mentioned in the embodiments.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the template patch package is generated according to a first patch package of a target function module in a first application program; wherein the first application and the second application are developed based on the same development framework.

With reference to the first aspect, in a second possible implementation manner of the first aspect, before the obtaining the template patch package, the method further includes: creating the first patch package, wherein the first patch package is created according to the change record of the functional component code corresponding to the target functional module in the first application program; and performing templating processing on the first patch package to generate a template patch package.

With reference to the first aspect, in a third possible implementation manner of the first aspect, before the creating the first patch package, the method further includes: generating initial engineering code of the first application program based on the development framework; creating a code management tool of the first application program, and submitting the initial engineering code to the code management tool; and abstracting and reconstructing the functional component code corresponding to the target functional module, and submitting the change record generated in the process of abstracting and reconstructing the functional component code to the code management tool.

With reference to the first aspect, in a fourth possible implementation manner of the first aspect, the refining and reconstructing the functional component code corresponding to the target functional module includes: transplanting the source code of the functional component code corresponding to the target functional module into the initial engineering code; and refining and reconstructing the source code of the functional component code.

With reference to the first aspect, in a fifth possible implementation manner of the first aspect, the refining and reconstructing the functional component code corresponding to the target functional module includes: transplanting the source code of the functional component code corresponding to the target functional module into the engineering code of another development framework adapted to the target functional module; refining and restructuring the functional component code in engineering code of another development framework; and migrating the abstracted and reconstructed functional component codes to the initial engineering codes in a code calling mode.

With reference to the first aspect, in a sixth possible implementation manner of the first aspect, the first patch package is created according to a change record submitted in the code management tool of the first application program, where the change record includes all changes in the first application program, which are generated from an initial engineering code to a refined and reconstructed function component code.

With reference to the first aspect, in a seventh possible implementation manner of the first aspect, the performing templating processing on the first patch package to generate a template patch package includes: and parameterizing data which is changed according to different application programs and exists in the first patch package to generate a generalized template patch package.

A second aspect of embodiments of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the method according to any one of the first aspect when executing the computer program.

A third aspect of embodiments of the present application provides a computer-readable storage medium, in which a computer program is stored, which, when executed by a processor, implements the steps of the method according to any one of the first aspects.

Compared with the prior art, the embodiment of the application has the advantages that: in order to implement the function component code multiplexing of different application programs based on the same development framework, the embodiment provides a method, a device and a storage medium for configuring a patch package, wherein a template patch package is used as a basis, and a templating parameter in the template patch package is replaced to obtain an instantiation parameter adapted to a second application program, so as to generate a target patch package, and then the target patch package is applied to the second application program. The configuration method in the embodiment realizes rapid sharing and application of the component functions, and meanwhile, the realization codes of the components can be maintained in a unified project, so that the reusability and maintainability of the components are improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is a schematic diagram illustrating a creation flow of a first application and its functional components according to an embodiment of the present application;

fig. 2 is a flowchart of a method for generating a template patch package according to an embodiment of the present disclosure;

FIG. 3 is a flowchart of a method for configuring a template patch package according to an embodiment of the present disclosure;

fig. 4 is a schematic diagram of an electronic device provided in an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

The technical solutions provided in the present application are explained in detail below with reference to specific examples.

The electronic equipment can be used for developing various application programs based on the existing development framework, and different functional modules are built in each application program. Wherein the development framework is created based on the functions to be implemented by different applications. In the present embodiment, an application program may also be referred to as an application (App).

Based on a unified development framework, after a developer develops a certain functional module 1 in an application program a, when an application program B also needs to develop the functional module 1, a manner is usually adopted in which a functional component code corresponding to the functional module 1 in the application program a is dependent on the application program B in a copy and paste manner. In the process of dependence, since the functional module 1 in the application a may merge some functions that are not needed by the application B, the functional component code in the application a needs to be modified and re-combed to obtain the functional component code adapted to the application B. Therefore, the functional module developed by the application program A and the application program B cannot realize quick reuse, and the components can not be embedded according to requirements, so that the aims of quick sharing of the components and unified maintenance and management of the components cannot be realized.

Furthermore, when the electronic device applies the functional component codes corresponding to the functional module 1 in the application a to the applications B and C in the above manner, if a test finds that there is a problem in the functional component codes in the application a, the functional component codes in all the applications (including the applications B and C) to which the functional module 1 is applied need to be modified, which increases the management and maintenance cost of the system.

In addition, based on a unified development framework, after the electronic device develops a certain functional module 1 in the application program a, when the application program B also needs to develop the functional module, the electronic device can also use a mode of redevelopment in the application program B, which wastes manpower and material resources and affects the development efficiency of the functional module, and is not suitable for the actual operation process.

Based on the above problem, an embodiment of the present application provides a method for configuring a patch package, where the patch package is a template patch package containing parameter variables, and when the patch package is applied to an application program, the parameter variables in the template patch package may be modified according to parameter characteristics of a target application program, so as to obtain a patch package adapted to the target application program.

In this embodiment, the electronic device may be a smart phone, a tablet computer, a computer running an operating system, or a smart hardware device, and the like, which is not particularly limited in this embodiment.

The method for generating and configuring the patch package provided in the embodiment mainly relates to three parts, and specifically includes a process of creating a first application program and a functional component thereof, generating a template patch package, and configuring the template patch package.

Fig. 1 shows a schematic diagram of a creation flow of a first application and its functional components, and as shown in fig. 1, the creation flow includes the following steps S11-S14.

And S11, the electronic equipment generates initial engineering codes of the first application program based on the development framework.

In this embodiment, the development framework may be any template framework having an application development function, such as a Spring Web MVC framework (Spring MVC for short), an open source framework, and the like.

In some embodiments, the electronic device can generate initial engineering code for the first application based on the development framework. The initial engineering code is empty engineering code required for creating the first application. It should be understood that all the applications (for example, application a, application B, or application C) are created based on the empty initial engineering code and generated based on a unified development framework, thereby ensuring the starting point uniformity of all the applications, so that when the functional component code corresponding to the functional module in application a is applied to application B, the functional module can be reasonably adapted in application B.

S12, the electronic device creates a code management tool of the first application program and submits the initial engineering code of the first application program to the code management tool.

Each application corresponds to a code management tool, and in this embodiment, the code management tool is mainly used for recording a change record of the engineering code. The code management tool may be an svn (subversion) code manager, or a distributed version control system Git repository.

In some embodiments, the electronic device creates a Git repository of the first application in the development framework and then submits the initial engineering code of the first application into the Git repository.

It should be understood that in the present embodiment, the Git warehouse is used to record each change to the engineering code. For example, for a first application, the Git repository initialization is completed, i.e., after the initial engineering code for the first application is submitted to the Git repository. And if the electronic equipment modifies the initial engineering code in the first application program in the subsequent use process and creates a functional component code belonging to the first application program, submitting the modified engineering code to the Git warehouse. When other applications need to use the functional component code of the first application, they can be called directly from the Git repository of the first application. Illustratively, when the second application needs to use the functional component code in the first application, the corresponding functional component submitted by the first application is pulled from the Git repository of the first application, and then automatically relied on the local engineering code of the second application after the pulling, so that the functional component codes in the first application and the second application are consistent.

In other embodiments, if the first application has been created based on the unified development framework, the electronic device does not need to perform the above steps S11-S12, and directly performs the step S13.

And S13, the electronic equipment configures the target function module for the first application program.

The electronic device can configure different target function modules for the first device according to user requirements. In this embodiment, the target function module refers to a module having a specific function in the application, and the specific function may be a payment function, a search function, a voice recognition function, or the like.

The target function module may be developed in a development framework of the first application program, or may be developed from another development framework and then dependent on the first application program.

In the configuration process, the electronic equipment refines and reconstructs the functional component codes corresponding to the target functional module so as to enable the functional component codes to be adapted to the initial engineering codes of the first application program. The functional component code refers to a component code required by an application program to realize the specific function. For example, for a voice search function, when the electronic device needs to provide the voice search function to a first application program in the form of a component for use, the functional component code corresponding to the voice search function is uploaded to the component market of the first application program, and before the uploading, the functional component code needs to be refined and reconstructed.

If the target function module is developed in the development framework of the first application program, the electronic equipment transplants the source code of the functional component code corresponding to the target function module into the initial engineering code of the first application program. Then, the source code of the functional component code is abstracted according to the actual requirement in the first application program, the necessary functional code in the first application program is reserved, and the unnecessary functional code is deleted. Alternatively, when there are some technical problems with the source code of the functional component code, the source code is reconstructed to adapt the functional component code to the original engineering code.

If the target function module is developed from another development framework and then depends on the development framework of the first application program, when the electronic equipment applies the target function module to the first application program, the electronic equipment transplants the source code of the function component code corresponding to the target function module into the engineering code of the other development framework adapted to the target function module. The engineering code of the other development framework may be any engineering code that is capable of adapting to the target functional module. And the electronic equipment places the functional component code corresponding to the target functional module in the engineering code for adaptation, and transplants the functional component code adapted by the engineering code into the initial engineering code of the development framework in a code calling mode for use after the adaptation is completed. That is, when applied in the initial engineering code, the applied functional component code does not include the source code, but the code defined by the above engineering code.

In the embodiment, the function component codes are firstly adapted to the initial engineering codes, and are refined and reconstructed according to the use requirements of the initial engineering codes, so that the good maintainability and expandability of the function code components are improved.

And S14, the electronic equipment submits the change records generated in the process of abstracting and reconstructing the functional component code corresponding to the target functional module to the code management tool.

In this embodiment, the electronic device further needs to perform component function testing on the refined and reconstructed functional component code to determine that the functional component code can be adapted to the first application. And submitting the change records generated in the process of abstracting and reconstructing the functional component codes to a code management tool.

The above is the creation flow of the first application program and its functional components, and the following explains the generation method of the second patch package in detail.

Fig. 2 shows a flowchart of a method for generating a template patch package, which includes the following steps S21-S23, as shown in fig. 2.

And S21, the electronic equipment creates a first patch package according to the function component code change record of the target function module in the code management tool of the first application program.

In some embodiments, the first patch package is created from a change record submitted in the code management tool of the first application, the change record including all changes in the first application resulting from the initial engineering code to the refined and restructured functional component code.

No matter how the electronic device introduces the functional component code into the initial engineering code, the functional component code finally adapted to the initial engineering code will be changed. The electronic equipment stores the change record by adopting a code management tool, and generates a first patch package of the functional component based on the change record. And when the second application program calls the functional component code based on the first patch package, all change records of the functional component code in the process of extraction and reconstruction can be clearly identified, and then the functional component code is adapted to the engineering code of the second application program according to the change records.

And S22, the electronic equipment performs templating processing on the first patch package to generate a template patch package, wherein the template patch package is used for configuring the function corresponding to the target function module in the second application program.

It should be understood that the same patch package exists in different applications, and there is data that varies from application to application, such as the package name, class name, application name, etc. of the patch package. Therefore, in this embodiment, data that changes according to different application programs and exists in the first patch package needs to be parameterized to form a generalized template patch package.

Illustratively, the electronic device performs templating on the first patch package, modifies the package name, the class name, and the application name in the first patch package into parameter variables, and generates a template patch package containing the parameter variables. And when the electronic equipment applies the template patch package to the second application program, modifying the parameter variables into the package name, the class name and the application name which are adaptive to the second application program to obtain a second patch package adaptive to the second application program.

It should be noted that, when the second application program and the first application program are generated based on the unified development framework, the starting points of the empty development projects based on the two application programs are consistent, so that the generated patch can be applied to the second application program only after the same starting point.

And S23, the electronic equipment uploads the template patch package to a component market of the development framework.

The component market is built in a development framework and is used for storing different functional components and providing technical support for different application programs during technical development.

The electronic device uploads the template patch package with the parameter variables to a component market of the development framework, so that the template patch package becomes a universal component patch package. Because the template patch package carries parameter variables and is not instantiated, the template patch package is uploaded to a component market, so that other application programs can be called as required.

The embodiment also provides a method for configuring the patch package, which is used for specifically configuring the template patch package in the configuration process of the second application program after the patch package is generated. As shown in FIG. 3, the configuration process includes the following steps S31-S35.

S31, the electronic equipment acquires the template patch package.

In some embodiments, when the electronic device needs to configure the target function module for the second application, the required functional component may be obtained in a component market of the development framework. Illustratively, when the second application needs to use the template patch package, the template patch package may be found from the component marketplace and downloaded. In this embodiment, the second application program may download the corresponding template patch package from the component market according to its own requirements, so that the flexibility is better in the component reuse process.

And S32, the electronic device replaces the templated parameters in the template patch package with the instantiated parameters in the second application program to generate a second patch package adapted to the second application program.

Since the template patch package is generated according to the functional component code specific to the first application, the parameter variable in the template patch package needs to be replaced by a component patch package specific to the second application, for example, the parameter variable package name, the class name, and the application name in the template patch package are replaced by a package name, a class name, and an application name specific to the second application, and a second patch package which is adapted to the second application and contains instantiation parameters is generated, so that instantiation of the template patch package in the second application is realized.

And S33, the electronic device applies the second patch package to the second application program.

In some embodiments, the second patch package is a patch package after replacing the templated parameters, and when the second patch package is applied to the second application, the second patch package can be directly applied to the engineering code of the second application through a command function in the code management tool.

In other embodiments, the electronic device applies the second patch package to the second application program, and the second patch package may be transplanted into the development tool IDEA through a commonly used development tool IDEA, and the development tool IDEA may display the function component code change record in the patch package in a visual page. After the development tool IDEA confirms the run, the functional component code is automatically applied to the second application project.

And S34, the electronic equipment carries out secondary development on the second patch package according to the application requirements of the target function module in the second application program.

In the second application program, the electronic device may modify the second patch package according to a specific application requirement of the second application program, or perform secondary development, so that the target function module can develop a function component more suitable for the second application program.

In an embodiment, if the functional component in the second application needs to be changed, the electronic device may also perform secondary development in the engineering code of the second application, so as to meet the customized requirement.

And S35, the electronic equipment tests the functional components in the second application program.

And after the second patch package is applied to the second application program, the electronic equipment verifies whether the function of the target function module can normally run, meets the requirement and the like through component testing.

And if the electronic equipment has the problem of unsuccessful function verification during component testing, revising the first patch package after the templating processing or re-executing the generation process of the first patch package, and then re-generating the template patch package.

The method for generating and configuring the patch package provided in the embodiment can realize rapid sharing and application of the functional component codes, and meanwhile, the functional component codes can be maintained in a unified development framework, so that the reusability and maintainability of the components are improved. The application program can select the templated components from the component market according to the self requirements, and the flexibility is better. In addition, the application program can perform secondary development on the functional component codes according to the needs of the application program, so that the customized requirements are met.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Fig. 4 is a schematic view of an electronic device provided in an embodiment of the present application. As shown in fig. 4, the electronic apparatus 4 of this embodiment includes: a processor 40, a memory 41 and a computer program 42, such as a patch generation program, stored in said memory 41 and executable on said processor 40. The processor 40 implements the steps in the various patch package configuration method embodiments described above when executing the computer program 42. Alternatively, the processor 40 implements the functions of the modules/units in the above-described device embodiments when executing the computer program 42.

Illustratively, the computer program 42 may be partitioned into one or more modules/units that are stored in the memory 41 and executed by the processor 40 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing certain functions, which are used to describe the execution of the computer program 42 in the electronic device 4.

The electronic device 4 may be a tablet computer, a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The electronic device may include, but is not limited to, a processor 40, a memory 41. Those skilled in the art will appreciate that fig. 4 is merely an example of an electronic device 4 and does not constitute a limitation of the electronic device 4 and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the electronic device may also include input-output devices, network access devices, buses, etc.

The Processor 40 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 41 may be an internal storage unit of the electronic device 4, such as a hard disk or a memory of the electronic device 4. The memory 41 may also be an external storage device of the electronic device 4, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the electronic device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the electronic device 4. The memory 41 is used for storing the computer program and other programs and data required by the electronic device. The memory 41 may also be used to temporarily store data that has been output or is to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated module/unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by hardware related to instructions of a computer program, which can be stored in a computer readable storage medium, and when the computer program is executed by a processor, the steps of the methods described above can be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain other components which may be suitably increased or decreased as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media which may not include electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims (10)

1. A method for configuring a patch package, comprising:

acquiring a template patch package;

replacing the templated parameters in the template patch package with instantiation parameters adapted to a second application program to generate a target patch package;

and applying the target patch package to the second application program.

2. The method of claim 1, wherein the template patch package is generated from a first patch package of a target function module in a first application; wherein the first application and the second application are developed based on the same development framework.

3. The method according to claim 1 or 2, wherein before obtaining the template patch package, the method further comprises:

creating the first patch package, wherein the first patch package is created according to the change record of the functional component code corresponding to the target functional module in the first application program;

and performing templating processing on the first patch package to generate a template patch package.

4. The method as recited in claim 3, wherein prior to the creating the first patch package, the method further comprises:

generating initial engineering code of the first application program based on the development framework;

creating a code management tool of the first application program, and submitting the initial engineering code to the code management tool;

and extracting and reconstructing the functional component code corresponding to the target functional module, and submitting change records generated in the process of extracting and reconstructing the functional component code to the code management tool.

5. The method according to claim 3, wherein the refining and reconstructing the functional component code corresponding to the target functional module comprises:

transplanting the source code of the functional component code corresponding to the target functional module into the initial engineering code;

and refining and reconstructing the source code of the functional component code.

6. The method according to claim 3, wherein the refining and reconstructing the functional component code corresponding to the target functional module comprises:

transplanting the source code of the functional component code corresponding to the target functional module into the engineering code of another development framework adapted to the target functional module;

refining and restructuring the functional component code in engineering code of another development framework;

and migrating the abstracted and reconstructed functional component codes to the initial engineering codes in a code calling mode.

7. The method of claim 2, wherein the first patch package is created from a change record submitted in the code management tool of the first application, the change record including all changes in the first application resulting from the initial engineering code to the refined and rebuilt functional component code.

8. The method of claim 3, wherein the templating the first patch package to generate a template patch package comprises:

and parameterizing data which is changed according to different application programs and exists in the first patch package to generate a generalized template patch package.

9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the steps of the method according to any of claims 1 to 8 are implemented when the computer program is executed by the processor.

10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 8.

Images