CN115617420B - Application program generation method, device, equipment and storage medium - Google Patents
Application program generation method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN115617420B CN115617420B CN202211381717.6A CN202211381717A CN115617420B CN 115617420 B CN115617420 B CN 115617420B CN 202211381717 A CN202211381717 A CN 202211381717A CN 115617420 B CN115617420 B CN 115617420B
- Authority
- CN
- China
- Prior art keywords
- module
- engineering
- file
- sub
- configuration file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 60
- 238000003860 storage Methods 0.000 title claims abstract description 20
- 238000004806 packaging method and process Methods 0.000 claims abstract description 27
- 230000006870 function Effects 0.000 claims description 84
- 238000012856 packing Methods 0.000 claims description 14
- 238000004891 communication Methods 0.000 description 11
- 238000004590 computer program Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 8
- 238000007726 management method Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 238000011161 development Methods 0.000 description 5
- 230000010354 integration Effects 0.000 description 5
- 230000008676 import Effects 0.000 description 4
- 239000000463 material Substances 0.000 description 4
- 238000005457 optimization Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000009877 rendering Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
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
- G06F8/44—Encoding
- G06F8/447—Target code generation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- 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/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The disclosure provides a method, a device, equipment and a storage medium for generating an application program, relates to the technical field of computers, and particularly relates to the technical field of software development and the technical field of micro front ends. The specific implementation scheme is as follows: acquiring software engineering data, wherein the software engineering data comprises a first configuration file and a first starting file; adding a main engineering module and at least one sub engineering module in a first configuration file; adding a view layer mounting operation code of the main engineering module in the first starting file; and packaging the added software engineering data to obtain the target application program.
Description
Technical Field
The present disclosure relates to the field of computer technology, and in particular, to the field of software development technology and the field of micro front-end technology.
Background
In recent years, saaS (Software-as-a-Service) has grown in application as a Software Service. Many software service providers package developed software services into brands for sale to users. However, many users have own personalized customization demands on software services, and a large number of customization demands lead to the need of large manpower input for customizing and developing software service providers.
Disclosure of Invention
The present disclosure provides a method, apparatus, device, storage medium, and program product for generating an application program.
According to an aspect of the present disclosure, there is provided a method for generating an application program, including: acquiring software engineering data, wherein the software engineering data comprises a first configuration file and a first starting file; adding a main engineering module and at least one sub engineering module in the first configuration file; adding a view layer mounting operation code of the main engineering module in the first starting file; and packaging the added software engineering data to obtain a target application program.
According to another aspect of the present disclosure, there is provided an apparatus for generating an application program, including: the system comprises a first acquisition module, a second acquisition module and a first control module, wherein the first acquisition module is used for acquiring software engineering data, and the software engineering data comprises a first configuration file and a first starting file; the first introducing module is used for adding a main engineering module and at least one sub-engineering module into the first configuration file; the second introducing module is used for adding a view layer mounting operation code of the main engineering module in the first starting file; and the first packing module is used for packing the added software engineering data to obtain a target application program.
Another aspect of the present disclosure provides an electronic device, comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the methods shown in the embodiments of the present disclosure.
According to another aspect of the disclosed embodiments, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the methods shown in the disclosed embodiments.
According to another aspect of the disclosed embodiments, there is provided a computer program product comprising a computer program/instruction, characterized in that the computer program/instruction, when executed by a processor, implements the steps of the method shown in the disclosed embodiments.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
Drawings
The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is a schematic view of an application scenario of an application program generation method, apparatus, electronic device and storage medium according to an embodiment of the disclosure;
FIG. 2 schematically illustrates a flow chart of a method of generating an application according to an embodiment of the disclosure;
FIG. 3 schematically illustrates a flow chart of a method of generating an application according to another embodiment of the disclosure;
FIG. 4 schematically illustrates a flow chart of a method of packaging main project data to yield a main project module, according to an embodiment of the disclosure;
FIG. 5 schematically illustrates a flow chart of a method of packaging sub-engineering data to obtain a sub-engineering module, according to an embodiment of the disclosure;
FIG. 6 schematically illustrates a schematic diagram of a method of generating an application according to an embodiment of the disclosure;
FIG. 7 is a block diagram of a generating device for an application to implement an embodiment of the present disclosure; and
FIG. 8 schematically illustrates a block diagram of an example electronic device that may be used to implement embodiments of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
An application scenario of the method and apparatus for generating an application program provided in the present disclosure will be described below with reference to fig. 1.
Fig. 1 is an application scenario schematic diagram of an application program generating method, an apparatus, an electronic device, and a storage medium according to an embodiment of the present disclosure. It should be noted that fig. 1 illustrates only an example of an application scenario in 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, but it 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, an application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the terminal devices 101, 102, 103.
The terminal devices 101, 102, 103 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites or applications used by users browsing with the terminal devices 101, 102, 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that, the method for generating an application program provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the generating device of the application program provided in the embodiment of the present disclosure may be generally disposed in the server 105. The method for generating an application provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the generating device of the application program provided by the embodiment of the present disclosure may also be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.
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 the technical scheme of the disclosure, the related processes of collecting, storing, using, processing, transmitting, providing, disclosing, applying and the like of the personal information of the user all conform to the regulations of related laws and regulations, necessary security measures are adopted, and the public order harmony is not violated.
In the technical scheme of the disclosure, the authorization or consent of the user is obtained before the personal information of the user is obtained or acquired.
The method of generating an application provided by the present disclosure will be described below with reference to fig. 2.
Fig. 2 schematically illustrates a flowchart of a method of generating an application according to an embodiment of the present disclosure.
As shown in fig. 2, the method 200 of generating an application program includes acquiring software engineering data in operation S210.
According to an embodiment of the present disclosure, the software engineering data includes a configuration file (config) and a boot file (bootstrap), wherein the configuration file may include configuration information required when packaging the software engineering data. The startup file may be used to launch an application. For convenience of description, the configuration file in the software engineering data is hereinafter referred to as a first configuration file, and the start file in the software engineering data is hereinafter referred to as a first start file.
It is to be appreciated that the software engineering data may include other data, such as application page data, resource data, etc., in addition to the first configuration file and the first startup file, which is not specifically limited by the present disclosure.
Then, in operation S220, a main engineering module and at least one sub engineering module are added in the first profile.
According to an embodiment of the present disclosure, a main engineering module and at least one sub engineering module may be added in the first configuration file to introduce the main engineering module and the at least one sub engineering module so that the target application may call the main engineering module and the at least one sub engineering module. In addition, on the basis of adding the main engineering module and at least one sub engineering module in the first configuration file, data files corresponding to the main engineering module and the at least one sub engineering module can be added into the software engineering data. The data files may include, among other things, configuration files, startup files, application page data, resource data, and the like. Alternatively, the data files may be stored in other locations than the software engineering data, where the data files may be obtained by introducing code during the running of the application.
According to embodiments of the present disclosure, the main engineering module and the sub engineering module may be packaged applications, respectively. The main engineering module may have infrastructure functions. The sub-engineering modules may have other extended functions beyond infrastructure functions. The sub-engineering module can be introduced into the main engineering module to obtain a new sub-engineering module, and the new sub-engineering module has the infrastructure function of the main engineering module and other expansion functions of the atomic engineering module.
The infrastructure functions may include a business bottom function required by each sub-engineering module to access the main engineering module, for example, a user information management function, a message center function, a material management function, and the like. The user information management function may be used to synchronize information such as user status and operations related to user information between the sub-engineering module and the main engineering module. The message center function can be used for controlling the sub-engineering module and the main engineering module to call the same channel to receive the message, and can also have the functions of synchronously caching the message, synchronously sending the roles and the like between the sub-engineering module and the main engineering module. The material management function may be used to synchronize information such as material states and operations related to the material between the sub-engineering module and the main engineering module.
Other extended functions may include business functions that want to access the main engineering module in addition to infrastructure functions, for example, may include rich text editing functions, image editing functions, and so forth. Wherein the rich text editing function can be used for editing rich text. The image editing function may be used to edit an image.
In operation S230, a view layer mount operation code of the main engineering module is added to the first start file.
According to the embodiment of the disclosure, the view layer mounting operation code of the main engineering module can be added in the first starting file to introduce the view layer mounting operation code of the main engineering module, so that the view layer mounting operation code can be called when the first starting file is executed.
According to embodiments of the present disclosure, view layer mount operation code of a main engineering module may be used to render a view layer of the main engineering module and add the view layer to a corresponding page.
Operations S220 and S230 may be performed in any order, according to an embodiment of the present disclosure, which is not particularly limited.
In operation S240, the added software engineering data is packaged to obtain the target application.
According to the embodiment of the disclosure, the target application program can be obtained by packing the software engineering data by using a packing tool. Illustratively, in this embodiment, the packaging tool may include, for example, weback.
In the related art, the process of customizing development software is complicated.
According to embodiments of the present disclosure, a main engineering module may have an infrastructure function, and a sub engineering module may have a customized extension function. And adding a view layer mounting operation code of the main engineering module in a first starting file by adding the main engineering module and at least one sub engineering module in a first configuration file. And then the software engineering data is packaged, so that a target application program with an infrastructure function and an extension function can be obtained, and the process of customizing and developing the software can be simplified.
According to embodiments of the present disclosure, a module federation plug-in, hereinafter referred to as a first module federation plug-in, may be added, for example, in a first configuration file. Wherein the module federation plug-in can be used to group multiple independently built applications into one application. And then adding the main engineering module and at least one sub-engineering module into the first configuration file by using the first module federation plugin.
For example, a first module federation plug-in may be added to the first configuration file. And then setting the introduction parameters of the first module federal plug-in according to the address of the main engineering module and the address of at least one sub engineering module so as to add the main engineering module and the at least one sub engineering module in the first configuration file. The import parameters may be used to import other engineering modules other than the software engineering data into the software engineering data, that is, the other engineering modules are configured into a state that can be called by the target application program, that is, the state can be called. Illustratively, in this embodiment, the introducing parameter may be used to configure the main engineering module and the at least one sub engineering module into a callable state. The address of the main engineering module indicates the storage address of the main engineering module, and the address of the sub engineering module indicates the storage address of the sub engineering module. Or, the introduction parameters of the first module federal plug-in may be set according to the acquisition code of the main engineering module and the acquisition code of the at least one sub engineering module, so as to add the main engineering module and the at least one sub engineering module in the first configuration file. The acquiring code of the main engineering module can be used for acquiring the data file of the main engineering module, and the acquiring code of the sub engineering module can be used for acquiring the data file of the sub engineering module.
The module federal plug-in this embodiment may include Module Federation Plugin in weback 5, for example. Based on this, for example, the plugins attribute may be set in the first configuration file, and an instance of Module Federation Plugin is passed into the plugins attribute, thereby adding the first module federation plugin to the first configuration file. In addition, module Federation Plugin may have a remote parameter into which the address of the main engineering module and the address of the at least one sub engineering module may be transferred, or into which the acquisition code of the main engineering module and the acquisition code of the at least one sub engineering module may be transferred to be introduced into the main engineering module and the sub engineering modules.
If the applications are combined and packaged together to obtain an integrated application, then after integration, the respective page optimization measures for each application will fail.
According to the embodiment of the disclosure, by using the module federal plug-in, the main engineering module and the sub engineering module can be introduced into the application program, so that the application program can have the functions of the main engineering module and the sub engineering module, and the original page optimization measures of the main engineering module and the sub engineering module can be reserved according to the needs, wherein the optimization measures can comprise, for example, on-demand loading, route lazy loading, resource preloading and the like. In addition, the main engineering module and the sub engineering module are introduced by adopting a mode of a module federal plug-in, and better performance can be obtained without excessive optimization.
According to the embodiment of the disclosure, for example, the view layer mounting operation code of the main engineering module can be added at the tail part of the first starting file. By adding the view layer mounting operation code of the main engineering module at the tail part of the first starting file, the view layer mounting operation of the main engineering module can be executed in the final stage of starting. Since various code logic required by the view layer mounting at the last stage of starting is loaded, the view layer can be mounted normally, so that the error in the mounting process caused by incomplete loading of the code logic required by the view layer mounting can be avoided.
According to the embodiment of the disclosure, after the target application program is started, the entry files of the main engineering module and the entry files of all the sub engineering modules can be called according to the introduction parameters of the module federation plugins so as to load various code logics, but not mount the view layer. And then, according to the tail lead-in information of the first starting file, a view layer mounting operation code exposed by the main engineering module is led in, and the view layer mounting operation of the main engineering module is started, so that the view layer can be normally mounted, and the error in the mounting process caused by incomplete loading of code logic required by the view layer mounting is avoided.
Fig. 3 schematically illustrates a flowchart of a method of generating an application according to another embodiment of the present disclosure.
As shown in fig. 3, the method 300 for generating an application program may include packaging main engineering data to obtain a main engineering module in operation S350.
In operation S360, the sub-engineering data is packaged to obtain a sub-engineering module.
In operation S310, software engineering data is acquired.
Then, in operation S320, a main engineering module and at least one sub engineering module are added in the first profile.
In operation S330, a view layer mount operation code of the main engineering module is added to the first start file.
In operation S340, the software engineering data is packaged to obtain the target application.
According to embodiments of the present disclosure, the main engineering data may include, for example, infrastructure function code, which may be used to provide infrastructure functions. Based on this, the main engineering module may have an infrastructure function. Based on this, the sub-engineering data may be used, for example, to provide extended functions beyond the infrastructure functions, the sub-engineering module may have other extended functions beyond the infrastructure functions. In addition, the sub-engineering module may be introduced into the main engineering module, thereby acquiring the infrastructure function of the main engineering module.
Operations S310 to S340 may refer to the above, and are not described herein.
Operations S350 and S360 may be performed in any order, according to an embodiment of the present disclosure, which is not particularly limited by the present disclosure.
According to the embodiment of the disclosure, the main engineering module and the sub engineering module are obtained by respectively packaging the main engineering data and the sub engineering data, so that a developer can conveniently and freely combine the main engineering module and the sub engineering module to obtain a target application program, and in addition, the labor cost and the time cost in the development process can be reduced. For example, the functional requirements of different users may be different, based on which, for each user's functional requirements, a developer may select a sub-engineering module that matches the functional requirements, and then generate a customized application that meets the user's functional requirements based on the sub-engineering modules and the main engineering module, without having to develop an entire application for each user separately, thereby simplifying the process of customizing development software.
The method for packaging the main engineering data to obtain the main engineering module provided by the present disclosure will be described below with reference to fig. 4.
FIG. 4 schematically illustrates a flow chart of a method of packaging main project data to yield a main project module, according to an embodiment of the disclosure.
As shown in fig. 4, the method 450 of packaging the main engineering data to obtain the main engineering module includes acquiring the main engineering data in operation S451.
According to an embodiment of the present disclosure, the main engineering data may include a configuration file, a start-up file, an entry file, a core code module, and at least one infrastructure function code module. For convenience of description, the configuration file in the main engineering data is hereinafter referred to as a second configuration file, the start file in the main engineering data is referred to as a second start file, and the entry file in the main engineering data is referred to as a first entry file. Wherein the second configuration file may include configuration information required when packaging the main engineering data. The second boot file may be used to boot the main engineering module. The first portal file may be used as a portal at the start-up of the main engineering module.
In operation S452, a second module federation plug-in is added to the second configuration file.
According to an embodiment of the present disclosure, a module federation plug-in, i.e., a second module federation plug-in, may be added to the second configuration file. The operation of adding the module federation plugin to the second configuration file may refer to, for example, adding the module federation plugin to the first configuration file, which is not described herein.
In operation S453, the first entry file is set to an exposed state in the second configuration file by the second module federation plugin.
According to the embodiment of the disclosure, by setting the first entry file to the exposed state, other applications outside the main engineering module can access the first entry file.
At least one infrastructure function code is set to a shared state in a second configuration file by a second module federation plug-in operation S454.
According to the embodiment of the present disclosure, by setting the infrastructure function codes to the shared state, it is possible to allow other applications other than the main engineering module to call the infrastructure function codes.
According to embodiments of the present disclosure, the infrastructure function code may be used to invoke the infrastructure function provided by the main engineering module, for example, may include an API (application program interface) that invokes the infrastructure function provided by the main engineering module. The infrastructure function code may be in the form of a package (code module), for example npm-package.
According to an embodiment of the present disclosure, the sharing parameters of the first module federal plug-in are set, for example, according to the identity of the at least one infrastructure function code, and the identity of the at least one infrastructure function code is set to be globally unique.
According to the embodiment of the disclosure, the basic setting function code is obtained by splitting the infrastructure function provided by the main engineering module into packages and API (application programming interface), and then the basic setting function code is exposed to other applications. The sub-functional module can call various functions exposed by the main engineering module across the technical stack, so that the development process of an access party can be simplified.
According to the embodiment of the disclosure, the identification of the infrastructure function code is set to be globally unique, so that global dependence is in the form of a single instance, and the problem of dependence conflict is avoided. In addition, in this embodiment, status information may be transferred between the main engineering module and the sub engineering module, and status information may also be transferred between the plurality of sub functional modules, where the status information may include, for example, a login status and the like. The state management among multiple modules can be unified well through a single-instance mechanism.
In operation S455, the first portal file and the view layer mount operation code of the main engineering module are added to the second start file.
According to embodiments of the present disclosure, view layer mount operation code of a main engineering module may be used to render a view layer of the main engineering module and add the view layer to a corresponding page.
According to the embodiment of the disclosure, by adding the first entry file and the view layer mounting operation code of the main engineering module in the second starting file, the first entry file and the view layer mounting operation code of the main engineering module can be introduced, so that when the main engineering module is started, corresponding calling code logic can be loaded according to the first entry file. And then rendering the view layer according to the view layer mounting operation code, and adding the view layer into the page.
Operations S452 to S454 and S455 may be performed in any order according to an embodiment of the present disclosure, which is not particularly limited by the present disclosure.
In operation S456, the added main engineering data is packaged to obtain a main engineering module.
According to the embodiment of the disclosure, the main engineering module can be obtained by packing the main engineering data by using a packing tool. Illustratively, in this embodiment, the packaging tool may include, for example, weback.
The module federal plug-in this embodiment may include Module Federation Plugin in weback 5, for example. Based on this, for example, the exposure parameter of Module Federation Plugin may be set in the second configuration file, and the storage path of the first entry file may be transferred into the exposure parameter to set the first entry file in the exposed state. For example, a shared parameter of Module Federation Plugin may be set in the second configuration file, and a package identifier corresponding to the at least one infrastructure function code is transferred into the shared parameter, so as to set the at least one infrastructure function code to a shared state. In addition, a single parameter may be set for each package, thereby constraining each package to be globally unique.
The method for packaging sub-engineering data to obtain a sub-engineering module provided by the present disclosure will be described below with reference to fig. 5.
FIG. 5 schematically illustrates a flow chart of a method of packaging sub-engineering data to obtain a sub-engineering module, according to an embodiment of the disclosure.
As shown in fig. 5, the method 560 of packing the sub-engineering data to obtain the main engineering module includes acquiring the sub-engineering data in operation S561.
According to embodiments of the present disclosure, the sub-engineering data may include a configuration file, a start-up file, and an entry file. For convenience of description, the configuration file in the sub-engineering data is hereinafter referred to as a third configuration file, the start file in the sub-engineering data is referred to as a third start file, and the entry file in the sub-engineering data is referred to as a second entry file. Wherein the third configuration file may include configuration information required when packaging the sub-engineering data. The third start-up file may be for a promoter engineering module. The second portal file may be used as a portal at the start-up of the sub-engineering module.
In operation S562, a third module federation plug-in is added to the third configuration file.
According to an embodiment of the present disclosure, a module federation plug-in, i.e., a third module federation plug-in, may be added to the third configuration file. The operation of adding the module federation plugin to the third configuration file may refer to, for example, adding the module federation plugin to the first configuration file, which is not described herein.
In operation S563, a first entry file of the exposed state is added to the third configuration file through the third module federation plug-in.
According to the embodiment of the disclosure, the first entry file of the exposure state is added in the third configuration file, so that the sub-engineering module can access the first entry file.
In operation S564, the infrastructure function code of the shared state is added to the third configuration file through the third module federation plugin.
According to embodiments of the present disclosure, by configuring the infrastructure function codes of the shared state in the third configuration file, the sub-engineering module may be enabled to call the infrastructure function codes.
In operation S565, a second entry file and a view layer mount operation code of the sub engineering module are added to the third start file.
According to embodiments of the present disclosure, view layer mount operation code of a sub-engineering module may be used to render a view layer of the sub-engineering module and add the view layer to a corresponding page.
According to the embodiment of the disclosure, by introducing the second entry file and the view layer mounting operation code of the sub engineering module into the third starting file, corresponding calling code logic can be loaded according to the second entry file when the sub engineering module is started. And then rendering the view layer according to the view layer mounting operation code, and adding the view layer into the page.
Operations S562 to S564 and S565 may be performed in any order according to an embodiment of the present disclosure, which is not particularly limited in this disclosure.
In operation S566, the added sub engineering data is packaged to obtain a sub engineering module.
According to the embodiment of the disclosure, the sub-engineering data can be packaged by utilizing a packaging tool to obtain the sub-engineering module. Illustratively, in this embodiment, the packaging tool may include, for example, weback.
The method of generating the application program shown above is further described with reference to fig. 6 in connection with a specific embodiment. Those skilled in the art will appreciate that the following example embodiments are merely for the understanding of the present disclosure, and the present disclosure is not limited thereto.
Fig. 6 schematically illustrates a schematic diagram of a method of generating an application according to an embodiment of the present disclosure.
In fig. 6, it is shown that at the main engineering module code layer, the project code repository of the main engineering module can be converted into a form of a plurality of projects, for example, a mono-repo form. The core module may be used as a project body, hereinafter referred to as a core, and splits the infrastructure functions from the core to obtain at least one package, for example, package1, package2, etc., where each infrastructure function corresponds to one package, and is uniformly managed in a mono-repo. Therefore, unified dependency version inside the main engineering module can be ensured.
Illustratively, in this embodiment, at the build layer, the dependency of the main engineering module may be set to weback 5. The main engineering data can be edited by using an editor, and then the main engineering module is obtained by packing by using weback 5. Wherein the editor may comprise typescript, babel, esbuild, for example.
For example, for a production environment, an editor may be utilized to add Module Federation Plugin (module federal plug-in) to the weback profile of the main engineering module. Wherein Module Federation Plugin has exposes, shared parameters. The core's entry file may then be exposed through the expose parameter. The portal file does not include an operation of view layer mounting, and the operation of view layer mounting is responsible for a specific package. And uniformly providing the packages corresponding to the infrastructure functions for each access party through shared parameters, and restricting global uniqueness of each package by using single. In addition, core dependencies may also be constrained to be globally unique in shared parameters. Core dependencies may include, for example, exact, vue, etc.
For development (development) environment, an editor may be used to create a bootstrap file for the main engineering module, add the import code of the entry file in the bootstrap file and add the view layer mount operation code. Then, the entry attribute of the weback can be set as the bootstrap file, so that the local normal starting of the project can be ensured.
And then the edited main engineering data can be packaged by utilizing the weback 5 to obtain a main engineering module. In addition, static resources in the main engineering data can be deployed to the CDN (content delivery network). Subsequently, the host engineering module may also be provided to the user as a standard application.
In accordance with embodiments of the present disclosure, at the sub-engineering module code layer, the sub-engineering module may include, for example, guest1, guest2. At the build level, the dependency of the sub-engineering module may be set to weback 5. The sub-engineering data can be edited by using an editor, and then packaged by using weback 5 to obtain the sub-engineering module. Wherein the editor may comprise typescript, babel, esbuild, for example.
For example, an editor may be utilized to add Module Federation Plugin to the configuration file of the sub-engineering module, and the core of the main engineering module may be added by configuring Module Federation Plugin the remote parameter, such as the main function module entry file address in the deployment CDN. And a bootstrap file can be created, and codes of the view layer mounted with the sub engineering module are moved into the bootstrap file. And then asynchronously introducing a bootstrap file into the sub-engineering module entry file.
For the production environment, the editor can be used for introducing the bootstrap file header of the sub-engineering module into the core file exposed by the main engineering module through module-creation. And the operation codes can be mounted on the view layer exposed by the main engineering module by leading the package into the tail part of the bootstrap file of the sub engineering module.
For the development environment, the editor can be used for introducing the bootstrap file header of the sub-engineering module into the core file exposed by the main engineering module through module-creation. The bootstrap file tail of the sub engineering module can be introduced through a package, and the view layer mounting operation exposed by the main engineering module can be started. When the sub engineering module is started, the project of the main engineering module is started locally, and if the main engineering module exposes other infrastructure functions, the sub engineering module can be called. Therefore, the sub engineering module can be directly subjected to joint debugging with the main engineering module project locally.
Then, the editor may be used to expose the entry file of the sub-engineering module through the exposure parameter of Module Federation Plugin, introduce the package of each main engineering module to be called through the shared parameter, and restrict each package globally unique by using single.
And then the sub-engineering modules can be packaged to obtain the sub-engineering modules. For example, the guide 1 is packed as the sub-engineering module 1, and the guide 2 is packed as the sub-engineering module 2.
At the integration layer, the main engineering module and each sub engineering module may be added by remote parameter of Module Federation Plugin in the configuration file of the integration project (i.e. the project integrating the main engineering module and each sub engineering module). And introducing codes for starting the view layer mounting operation exposed by the main engineering module into the tail part of the bootstrap file of the integration project through the package. And then the integrated project can be packaged and deployed, so that all infrastructure functions and extended functions can be seen to complete integration in the form of a micro front end. And if no new sub-engineering module is accessed, the integrated project does not need to be deployed again, and the function module can independently update the static resource to complete project update.
For example, the main engineering module and the sub engineering module 1 may be integrated to obtain the customized application 1. And integrating the main engineering module and the sub engineering module 2 to obtain the customized application 2.
According to embodiments of the present disclosure, a packaged application may be launched. After the packaged application is started, the entry files of the main engineering module and each sub engineering module can be called first according to the remote parameter of Module Federation Plugin, and code logic is loaded, but the view layer is not mounted. And then, according to the package introduction information at the tail of the bootstrap file, introducing a package corresponding to the view layer mounting operation exposed by the main engineering module, and starting the view layer mounting operation of the main engineering module according to the package.
The generation apparatus of the application program provided by the present disclosure will be described below with reference to fig. 7.
Fig. 7 schematically shows a block diagram of a generating apparatus of an application according to an embodiment of the present disclosure.
As shown in fig. 7, the application generating apparatus 700 includes an acquisition module 710, a first introduction module 720, a second introduction module 730, and a first packing module 740.
The first obtaining module 710 is configured to obtain software engineering data, where the software engineering data includes a first configuration file and a first start file.
The first introduction module 720 is configured to add the main engineering module and at least one sub-engineering module to the first configuration file.
And the second import module 730 is configured to add the view layer mounting operation code of the main engineering module in the first start file.
And the first packing module 740 is configured to pack the added software engineering data to obtain the target application program.
According to an embodiment of the present disclosure, the first introduction module may include: the first adding sub-module is used for adding a first module federation plugin into the first configuration file; and the first setting sub-module is used for setting the introduction parameters of the first module federal plugin according to the address of the main engineering module and the address of at least one sub-engineering module so as to add the main engineering module and the at least one sub-engineering module in the first configuration file.
According to an embodiment of the present disclosure, the first introduction module may include: the second adding sub-module is used for adding the first module federation plugin into the first configuration file; and the second setting sub-module is used for setting the introduction parameters of the first module federal plugin according to the acquisition code of the main engineering module and the acquisition code of at least one sub-engineering module so as to add the main engineering module and the at least one sub-engineering module in the first configuration file.
According to an embodiment of the present disclosure, the generating device of the application program may further include: the second acquisition module is used for acquiring main engineering data, wherein the main engineering data comprises a second configuration file, a second starting file, a first entry file, a core code module and at least one infrastructure function code module; the third adding module is used for adding a second module federation plugin in the second configuration file; the exposure state setting module is used for setting the first entry file to be in an exposure state in the second configuration file through the second module federation plugin; the shared state setting module is used for setting at least one infrastructure function code to be in a shared state in a second configuration file through a second module federation plugin; the third introducing module is used for adding a first inlet file and a view layer mounting operation code of the main engineering module in the second starting file; and the second packaging module is used for packaging the added main engineering data to obtain the main engineering module.
According to an embodiment of the present disclosure, the sharing state setting module may include: and the third setting submodule is used for setting sharing parameters of the first module federal plugin according to the identification of the at least one infrastructure function code and setting the identification of the at least one infrastructure function code to be globally unique, wherein the sharing parameters are used for configuring the at least one infrastructure function code to be in a sharing state.
According to an embodiment of the present disclosure, the generating device of the application program may further include: the third acquisition module is used for acquiring sub-engineering data, wherein the sub-engineering data comprises a third configuration file, a third starting file and a second entry file; the fourth adding module is used for adding a third module federation plugin into the third configuration file; the fourth introducing module is used for adding the first entry file in the exposure state into the third configuration file through the third module federation plugin; a fifth introducing module, configured to add, through a third module federation plugin, an infrastructure function code of a shared state in a third configuration file; the sixth introducing module is used for configuring a second entry file and a view layer mounting operation code of the sub engineering module in the third starting file; and the third packing module is used for packing the added sub-engineering data to obtain the sub-engineering module.
According to an embodiment of the present disclosure, the second introduction module may include: and the sixth introducing sub-module is used for adding the view layer mounting operation code of the main engineering module at the tail part of the first starting file.
According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.
Fig. 8 schematically illustrates a block diagram of an example electronic device 800 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 8, the apparatus 800 includes a computing unit 801 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 802 or a computer program loaded from a storage unit 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the device 800 can also be stored. The computing unit 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to the bus 804.
Various components in device 800 are connected to I/O interface 805, including: an input unit 806 such as a keyboard, mouse, etc.; an output unit 807 such as various types of displays, speakers, and the like; a storage unit 808, such as a magnetic disk, optical disk, etc.; and a communication unit 809, such as a network card, modem, wireless communication transceiver, or the like. The communication unit 809 allows the device 800 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The computing unit 801 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 801 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the respective methods and processes described above, for example, the generation method of the application program. For example, in some embodiments, the method of generating an application program may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as the storage unit 808. In some embodiments, part or all of the computer program may be loaded and/or installed onto device 800 via ROM 802 and/or communication unit 809. When a computer program is loaded into RAM 803 and executed by computing unit 801, one or more steps of the method of generating an application program described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform the method of generating the application program in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above can be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, 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), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service ("Virtual Private Server" or simply "VPS") are overcome. The server may also be a server of a distributed system or a server that incorporates a blockchain.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel or sequentially or in a different order, provided that the desired results of the technical solutions of the present disclosure are achieved, and are not limited herein.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.
Claims (14)
1. A method of generating an application program, comprising:
acquiring software engineering data, wherein the software engineering data comprises a first configuration file and a first starting file;
adding a main engineering module and at least one sub engineering module in the first configuration file;
adding a view layer mounting operation code of the main engineering module in the first starting file; and
packaging the added software engineering data to obtain a target application program;
The method further comprises the steps of: obtaining main engineering data, wherein the main engineering data comprises a second configuration file, a second starting file, a first entry file, a core code module and at least one infrastructure function code module;
adding a second module federation plugin to the second configuration file;
setting, by the second module federation plug-in, the first entry file to an exposed state in the second configuration file;
setting, by the second module federation plug-in, the at least one infrastructure function code to a shared state in the second configuration file;
adding the first entry file and a view layer mounting operation code of the main engineering module in the second starting file; and
and packaging the added main engineering data to obtain the main engineering module.
2. The method of claim 1, wherein the adding a main engineering module and at least one sub-engineering module in the first configuration file comprises:
adding a first module federation plugin to the first configuration file; and
setting the introduction parameters of the first module federation plugin according to the address of the main engineering module and the address of the at least one sub engineering module so as to add the main engineering module and the at least one sub engineering module in the first configuration file.
3. The method of claim 1, wherein the adding a main engineering module and at least one sub-engineering module in the first configuration file comprises:
adding a first module federation plugin to the first configuration file; and
setting the introduction parameters of the first module federation plugin according to the acquisition codes of the main engineering module and the at least one sub engineering module so as to add the main engineering module and the at least one sub engineering module in the first configuration file.
4. A method according to claim 2 or 3, wherein said setting, by said second module federation plug-in, said at least one infrastructure function code to a shared state in said second configuration file comprises:
setting sharing parameters of the first module federation plugin according to the identification of at least one infrastructure function code, and setting the identification of the at least one infrastructure function code to be globally unique, wherein the sharing parameters are used for configuring the at least one infrastructure function code to be in a sharing state.
5. The method of claim 1, further comprising:
sub-engineering data are obtained, wherein the sub-engineering data comprise a third configuration file, a third starting file and a second entry file;
Adding a third module federation plugin to the third configuration file;
adding a first entry file in an exposed state into the third configuration file through the third module federation plugin;
adding infrastructure function codes of a sharing state in the third configuration file through the third module federation plugin;
adding the second entry file and a view layer mounting operation code of the sub engineering module in the third starting file; and
and packaging the added sub-engineering data to obtain the sub-engineering module.
6. The method of claim 1, wherein the adding view layer mount operation code of the main engineering module in the first boot file comprises:
and adding a view layer mounting operation code of the main engineering module at the tail part of the first starting file.
7. An application program generation apparatus, comprising:
the system comprises a first acquisition module, a second acquisition module and a first control module, wherein the first acquisition module is used for acquiring software engineering data, and the software engineering data comprises a first configuration file and a first starting file;
the first introducing module is used for adding a main engineering module and at least one sub-engineering module into the first configuration file;
The second introducing module is used for adding a view layer mounting operation code of the main engineering module in the first starting file; and
the first packing module is used for packing the added software engineering data to obtain a target application program;
the apparatus further comprises:
the second acquisition module is used for acquiring main engineering data, wherein the main engineering data comprises a second configuration file, a second starting file, a first entry file, a core code module and at least one infrastructure function code module;
the third adding module is used for adding a second module federation plugin in the second configuration file;
the exposure state setting module is used for setting the first entry file to be in an exposure state in the second configuration file through the second module federation plugin;
a shared state setting module configured to set, by the second module federation plug-in, the at least one infrastructure function code to a shared state in the second configuration file;
the third introducing module is used for adding the first inlet file and the view layer mounting operation code of the main engineering module in the second starting file;
And the second packaging module is used for packaging the added main engineering data to obtain the main engineering module.
8. The apparatus of claim 7, wherein the first introduction module comprises:
the first adding submodule is used for adding a first module federation plugin into the first configuration file; and
and the first setting sub-module is used for setting the introduction parameters of the first module federal plug-in according to the address of the main engineering module and the address of the at least one sub-engineering module so as to add the main engineering module and the at least one sub-engineering module in the first configuration file.
9. The apparatus of claim 7, wherein the first introduction module comprises:
the second adding sub-module is used for adding the first module federation plugin into the first configuration file; and
and the second setting sub-module is used for setting the introduction parameters of the first module federal plug-in according to the acquisition codes of the main engineering module and the at least one sub-engineering module so as to add the main engineering module and the at least one sub-engineering module in the first configuration file.
10. The apparatus of claim 8 or 9, wherein the shared state setting module comprises:
and the third setting sub-module is used for setting the sharing parameter of the first module federal plug-in according to the identification of at least one infrastructure function code and setting the identification of the at least one infrastructure function code as global unique, wherein the sharing parameter is used for configuring the at least one infrastructure function code into a sharing state.
11. The apparatus of claim 7, further comprising:
the third acquisition module is used for acquiring sub-engineering data, wherein the sub-engineering data comprises a third configuration file, a third starting file and a second inlet file;
the fourth adding module is used for adding a third module federation plugin into the third configuration file;
the fourth introducing module is used for adding a first entry file in an exposed state into the third configuration file through the third module federation plugin;
a fifth introducing module, configured to add, through the third module federation plugin, an infrastructure function code of a shared state in the third configuration file;
the sixth introducing module is used for configuring the second inlet file and the view layer mounting operation code of the sub-engineering module in the third starting file; and
And the third packaging module is used for packaging the added sub-engineering data to obtain the sub-engineering module.
12. The apparatus of claim 7, wherein the second introduction module comprises:
and a sixth introduction sub-module, configured to add a view layer mounting operation code of the main engineering module at the tail of the first start file.
13. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.
14. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211381717.6A CN115617420B (en) | 2022-11-03 | 2022-11-03 | Application program generation method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211381717.6A CN115617420B (en) | 2022-11-03 | 2022-11-03 | Application program generation method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115617420A CN115617420A (en) | 2023-01-17 |
| CN115617420B true CN115617420B (en) | 2024-03-01 |
Family
ID=84878985
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211381717.6A Active CN115617420B (en) | 2022-11-03 | 2022-11-03 | Application program generation method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115617420B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116069325B (en) * | 2023-01-28 | 2023-08-04 | 深圳市明源云采购科技有限公司 | Front-end project construction method, device, equipment and computer readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107291458A (en) * | 2017-06-06 | 2017-10-24 | 北京知道创宇信息技术有限公司 | A kind of plug-in unit construction method, system and the server of Web applications |
| CN110442327A (en) * | 2018-05-03 | 2019-11-12 | 阿里巴巴集团控股有限公司 | A kind of application builds method, apparatus, server |
| CN113157345A (en) * | 2021-04-30 | 2021-07-23 | 中国工商银行股份有限公司 | Automatic starting method and device for front-end engineering |
| CN113220367A (en) * | 2021-05-12 | 2021-08-06 | 北京百度网讯科技有限公司 | Applet running method and device, electronic equipment and storage medium |
-
2022
- 2022-11-03 CN CN202211381717.6A patent/CN115617420B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107291458A (en) * | 2017-06-06 | 2017-10-24 | 北京知道创宇信息技术有限公司 | A kind of plug-in unit construction method, system and the server of Web applications |
| CN110442327A (en) * | 2018-05-03 | 2019-11-12 | 阿里巴巴集团控股有限公司 | A kind of application builds method, apparatus, server |
| CN113157345A (en) * | 2021-04-30 | 2021-07-23 | 中国工商银行股份有限公司 | Automatic starting method and device for front-end engineering |
| CN113220367A (en) * | 2021-05-12 | 2021-08-06 | 北京百度网讯科技有限公司 | Applet running method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115617420A (en) | 2023-01-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110795195B (en) | Webpage rendering method and device, electronic equipment and storage medium | |
| CN113010827B (en) | Page rendering method and device, electronic equipment and storage medium | |
| CN109062563B (en) | Method and device for generating page | |
| CN111090423B (en) | Webhook framework system and method for realizing active calling and event triggering | |
| CN111338623B (en) | Method, device, medium and electronic equipment for developing user interface | |
| CN112947965B (en) | Containerized service updating method and device | |
| CN110007936B (en) | Data processing method and device | |
| CN115617420B (en) | Application program generation method, device, equipment and storage medium | |
| CN113760324A (en) | Method and device for constructing micro front-end application | |
| CN113050940A (en) | Method for previewing small program, related device and computer program product | |
| CN115509522A (en) | Interface arranging method and system for low-code scene and electronic equipment | |
| CN113468067B (en) | Application program debugging method and device, electronic equipment and computer readable medium | |
| CN113138768B (en) | Application package generation method and device, electronic equipment and readable storage medium | |
| CN112214250A (en) | Application program assembly loading method and device | |
| CN110807162A (en) | Method and device for loading occupation bitmap | |
| CN110795328A (en) | Interface testing method and device | |
| CN117234582A (en) | Project code processing method and device, electronic equipment and storage medium | |
| CN112596854A (en) | Method and device for continuously integrating running of assembly line | |
| WO2023169193A1 (en) | Method and device for generating smart contract | |
| CN111382953A (en) | Dynamic process generation method and device | |
| CN111414154A (en) | Method and device for front-end development, electronic equipment and storage medium | |
| CN113612643B (en) | Network configuration method, device and equipment of cloud mobile phone and storage medium | |
| CN111142972B (en) | Method, apparatus, system, and medium for extending functions of application program | |
| CN114398035A (en) | Method, apparatus, device and computer readable medium for providing service using component | |
| US8990271B2 (en) | Specifying data in a standards style pattern of service-oriented architecture (SOA) environments |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |