CN111949312B - Packaging method and device for data module, computer equipment and storage medium - Google Patents
Packaging method and device for data module, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111949312B CN111949312B CN202010816367.6A CN202010816367A CN111949312B CN 111949312 B CN111949312 B CN 111949312B CN 202010816367 A CN202010816367 A CN 202010816367A CN 111949312 B CN111949312 B CN 111949312B
- Authority
- CN
- China
- Prior art keywords
- data
- size
- data module
- module
- modules
- 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 72
- 238000004806 packaging method and process Methods 0.000 title claims abstract description 70
- 238000007781 pre-processing Methods 0.000 claims description 76
- 238000004458 analytical method Methods 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 13
- 230000006870 function Effects 0.000 claims description 12
- 238000010586 diagram Methods 0.000 description 16
- 238000012856 packing Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 10
- 238000005457 optimization Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 3
- 230000001419 dependent effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000004883 computer application Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 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/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The embodiment of the disclosure relates to a packaging method, a packaging device, computer equipment and a storage medium of a data module. According to the method, the dependency relationship between a plurality of data modules corresponding to the front-end project and each data module is obtained, then each data module is split or combined according to attribute information of each data module and the dependency relationship between each data module, each target data module and the dependency relationship between each target data module are obtained, and finally the target data modules are packaged according to the dependency relationship between each target data module. The size and/or the number of the target data modules are the optimal size and/or the number required by later packaging, and the output efficiency of the packaged file when being output to the front-end browser is improved.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of computer application, in particular to a packaging method and device of a data module, computer equipment and a storage medium.
Background
With the increasing complexity of the functions carried by the web application, the front-end project of the web application is also becoming larger and larger, so that the front-end project is usually divided into a plurality of data modules in order to facilitate development and maintenance of the front-end project, so as to improve the development efficiency of the front-end project. However, the data modules cannot be directly output to the front-end browser of the web application, after compiling of each data module corresponding to the front-end project is completed, each data module needs to be packaged, a packaged file which can be output to the front-end browser is obtained, and finally the front-end browser displays the front-end project page based on the packaged file.
Currently, when each data module is packaged, an existing packaging tool is generally adopted to directly package each data module based on the acquired data module. However, if the front-end items are huge, and the dependency relationship between the corresponding data modules is complex, the problem that the number of the packaged files is too large or the number of the packaged files generated by packaging is too large due to multiple times of packaging in the process of packaging the data modules by using the packaging tool can occur, so that the output efficiency is extremely low when the packaged files are output to the front-end browser.
Disclosure of Invention
The embodiment of the disclosure provides a packaging method, a packaging device, computer equipment and a storage medium for a data module, which can be used for improving the output efficiency of a front-end item of a web application when the front-end item is output to a front-end browser.
In a first aspect, an embodiment of the present disclosure provides a method for packaging a data module, where the method includes:
acquiring a plurality of data modules corresponding to the front-end project and a dependency relationship among the data modules;
preprocessing each data module according to attribute information of each data module and the dependency relationship among each data module to obtain each target data module and the dependency relationship among each target data module; preprocessing comprises splitting or merging each data module; the attribute information of the data modules comprises the size and/or the number of the data modules; the size represents the data size of the data module;
and packaging the target data modules according to the dependency relationship among the target data modules.
In one embodiment, the attribute information includes a size of the data module, and preprocessing each data module according to the attribute information of each data module and the dependency relationship between each data module includes:
Comparing the size of the data module with a preset size threshold;
if the size of the data module is larger than the preset size threshold, determining that the size type of the data module is a large-size data module, and preprocessing each large-size data module according to the dependency relationship among the data modules;
if the size of the data module is smaller than or equal to the preset size threshold, determining that the size type of the data module is a small-size data module, and preprocessing each small-size data module according to the dependency relationship among the small-size data modules.
In the above embodiment, the preprocessing is implemented on each data module by determining the size type of each data module, so that the size of the preprocessed data module is the optimal size, and it can be avoided that the number of package files obtained by packaging the data module in the later stage is too large due to the oversized size of the data module, or the number of package files obtained by packaging the data modules in the later stage is too large due to the undersize size of the data module. Therefore, the method can ensure that the size and the number of the packaged files after the module data are packaged by the computer equipment at a later stage are optimal.
In one embodiment, preprocessing each data module according to the size type of each data module and the dependency relationship between each data module includes:
According to the dependency relationship among the small-size data modules, determining a plurality of candidate small-size data modules with primary dependency relationship from all the small-size data modules;
and merging the plurality of candidate small-size data modules.
In this embodiment, since a plurality of candidate small-size data modules are combined, the number of data modules is greatly reduced, and thus, the optimization of the number of data modules and the optimization of the number of package files after the package according to the data modules in the later stage are realized. Meanwhile, because the dependency relationship among the plurality of candidate small-size data modules is a first-level dependency relationship, the dependency relationship among module codes in the combined data modules is simplified, so that the number of times of packaging the combined data modules in the later period is reduced, and the packaging efficiency is improved.
In one embodiment, preprocessing each large-size data module according to a dependency relationship between the data modules includes:
determining the number of data modules with dependency relations with the large-size data modules according to the dependency relations among the data modules;
and preprocessing each large-size data module according to the number.
In one embodiment, preprocessing each large-size data module according to the number includes:
if the number is smaller than the preset number threshold, splitting the large-size data module.
In the process of splitting the large-size data modules, the large-size data modules corresponding to the number smaller than the preset number threshold are split, so that the dependency relationship among the split data modules is simpler, and the dependency relationship among all the preprocessed data modules is simplified.
In one embodiment, preprocessing each data module according to attribute information of each data module and dependency relationship between each data module includes:
determining whether a single dependency exists between every two data modules according to the dependency relationship between the data modules; a singleness dependency indicates that one data module in every two data modules refers to the other data module, and the other data module does not refer to the other data module;
every two data modules with a single dependency are merged.
In the process of merging every two data modules with the uniqueness dependency, one data module does not refer to any other data module in every two data modules with the uniqueness dependency, and the two data modules are in a single reference relationship, so that the dependency relationship among all module codes in the merged data module is relatively simple, the dependency relationship between the merged data module and other data modules is relatively simple, and the dependency relationship among all data modules after preprocessing is greatly simplified.
In one embodiment, after merging each two data modules having a singleness dependency, the method further comprises:
judging whether the data module groups obtained after combination contain the same data module or not;
if the same data module is contained, determining whether the same data module references other data modules according to the dependency relationship among the data modules;
if the same data module does not reference other data modules, the same data module is split from the data module group.
In the above embodiment, since the computer device directly splits the same data module from the data module group, there is no dependency between the split data module and other data modules, and the dependency between the preprocessed data modules is simplified.
In one embodiment, after obtaining the dependency relationships between the plurality of data modules corresponding to the front-end item and the plurality of data modules, the method further includes:
generating drawing data according to the data modules and the dependency relationship between the data modules; the drawing data comprises connection relations among nodes corresponding to the data modules;
drawing and displaying a relation chart according to drawing data; the relationship graph is used to represent the dependency relationship between the data modules.
In the embodiment, since the dependency relationship among the data modules can be clearly shown by the relationship graph, the end user can view the page displaying the relationship graph through the browser, so that the dependency relationship among the plurality of data modules corresponding to the front-end project can be intuitively known, and the accuracy of analyzing the dependency relationship among the data modules by the front-end developer is improved.
In a second aspect, an embodiment of the present disclosure provides a packaging apparatus for a data module, the apparatus including:
the acquisition module is used for acquiring a plurality of data modules corresponding to the front-end project and the dependency relationship among the data modules;
the preprocessing module is used for preprocessing each data module according to the attribute information of each data module and the dependency relationship among the data modules to obtain each target data module and the dependency relationship among the target data modules; the preprocessing comprises splitting or merging the data modules; the attribute information of the data modules comprises the size and/or the number of the data modules; the dimension represents a data size of the data module;
and the packaging module is used for packaging the target data modules according to the dependency relationship among the target data modules.
In a third aspect, an embodiment of the disclosure provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the method of the first aspect when the processor executes the computer program.
In a fourth aspect, embodiments of the present disclosure provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements the method of the first aspect.
According to the packaging method, the packaging device, the computer equipment and the storage medium for the data modules, the data modules are split or combined according to the attribute information of the data modules and the dependency relationship among the data modules by acquiring the dependency relationship among the data modules corresponding to the front-end items, the target data modules and the dependency relationship among the target data modules are obtained, and finally the target data modules are packaged according to the dependency relationship among the target data modules. The target data module is a data module obtained by preprocessing the first acquired data module by the computer equipment, the computer equipment is used for preprocessing the original data module by combining the size and/or the number of the data modules and the dependency relationship among the data modules, so that the size and/or the number of the target data module obtained after preprocessing is the optimal size and/or the number required by later packaging, the size and the number of the packaging file obtained after later packaging of each target data module are also optimal, the output efficiency of the packaging file when the packaging file is output to the front-end browser is improved, and the resource request efficiency when a user accesses the front-end browser is also improved. In addition, the computer equipment pre-processes the original data modules by analyzing the dependency relationship among the data modules, so that the dependency relationship among the target data modules obtained after the pre-processing is simplified, and when the target data modules with the simplified dependency relationship are packed in the later period, the packing times of the data modules with the complex dependency relationship are reduced, and the packing efficiency of the computer equipment on the data modules is further improved.
Drawings
FIG. 1 is an internal block diagram of a computer device in one embodiment;
FIG. 2 is a flow diagram of a method of packaging data modules in one embodiment;
FIG. 3 is a flow chart of one implementation of S102 in the embodiment of FIG. 2;
FIG. 4 is a flow chart of one implementation of S102 in the embodiment of FIG. 2;
FIG. 5 is a flow chart of one implementation of S202 in the embodiment of FIG. 3;
FIG. 6 is a flow chart of another implementation of S202 in the embodiment of FIG. 3;
FIG. 7 is a flow chart of another implementation of S102 in the embodiment of FIG. 2;
FIG. 8 is a flow diagram of a method of packaging data modules in one embodiment;
FIG. 9 is a flow diagram of a method of packaging data modules in one embodiment;
FIG. 10 is a flow diagram of a method of packaging data modules in one embodiment;
FIG. 11 is a block diagram of a data module packaging apparatus in one embodiment;
FIG. 12 is a block diagram of a data module packaging apparatus in one embodiment;
FIG. 13 is a block diagram of a data module packaging apparatus in one embodiment;
FIG. 14 is a block diagram of a data module packaging apparatus in one embodiment;
FIG. 15 is a block diagram of a data module packaging apparatus in one embodiment;
FIG. 16 is a block diagram of a data module packaging apparatus in one embodiment;
FIG. 17 is a block diagram of a data module packaging apparatus in one embodiment;
fig. 18 is a block diagram showing the structure of a packing apparatus for data modules in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present disclosure more apparent, the embodiments of the present disclosure will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the disclosed embodiments and are not intended to limit the disclosed embodiments.
The method for packaging the data module can be applied to computer equipment shown in fig. 1, wherein the computer equipment can be a server, the computer equipment can also be a terminal, and the internal structure diagram of the computer equipment can be shown in fig. 1. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of packaging data modules. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in fig. 1 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, as shown in fig. 2, a method for packaging a data module is provided, and the method is applied to the computer device in fig. 1 for illustration, and includes the following steps:
s101, acquiring a plurality of data modules corresponding to the front-end project and the dependency relationship among the data modules.
The data module is source code corresponding to the development front-end project. There are references or referenced dependencies between the data modules. Specifically, the computer device may obtain a plurality of data modules corresponding to the front-end project according to an editing instruction input by the front-end project developer, for example, the front-end project developer edits source code related to the front-end project on the computer device, where the source code may be divided into a plurality of code blocks having respective functions, where the plurality of code blocks respectively correspond to the plurality of data modules. Optionally, the computer device may also obtain a plurality of data modules corresponding to the front-end item through a downloading manner, and the method for obtaining the data modules is not limited in this embodiment. When the computer equipment acquires a plurality of data modules corresponding to the front-end project, the computer equipment can analyze the dependency relationship among the data modules by adopting the existing dependency analysis tool or the existing dependency analysis function to obtain the dependency relationship among the data modules; optionally, the front-end developer analyzes the relationship between the data modules to obtain an analysis result, and then the computer device may also obtain the dependency relationship between the data modules according to the analysis result.
S102, preprocessing each data module according to attribute information of each data module and the dependency relationship among each data module to obtain each target data module and the dependency relationship among each target data module; preprocessing comprises splitting or merging each data module; the attribute information of the data modules comprises the size and/or the number of the data modules; the size represents the data size of the data module.
The target data module is a data module obtained by preprocessing a data module obtained by the computer equipment, namely an updated data module. Specifically, when the computer device obtains the dependency relationships between the plurality of data modules corresponding to the front-end project and each data module based on the foregoing steps, the attribute information of each data module may be further obtained, and the data modules may be preprocessed by comprehensively analyzing the attribute information of each data module and the dependency relationships between each data module, where specific analysis and processing methods include, but are not limited to, the following ways:
firstly, the computer equipment analyzes the sizes of all the data modules, determines a plurality of data modules with the sizes meeting the preset size requirement, further analyzes the dependency relationship among the data modules, and finally merges or splits the data modules according to the analysis result. Wherein the preset size requirement can be determined by the computer device in advance according to the optimal size requirement of the data module.
Secondly, the computer equipment analyzes the number of each data module, determines a plurality of data modules with the number meeting the preset number requirement, further analyzes the dependency relationship among the data modules, and finally merges or splits the data modules according to the analysis result. The preset number of requirements can be determined by the computer device in advance according to the optimal size requirements and/or the optimal number of requirements of the data module.
Thirdly, the computer equipment analyzes the size of each data module, determines a plurality of data modules with the size meeting the preset size requirement, further analyzes the number of the data modules meeting the preset size requirement, determines a plurality of data modules with the number meeting the preset number requirement, further analyzes the dependency relationship among the data modules with the number meeting the preset number requirement, and finally merges or splits the data modules according to the analysis result.
Fourth, the computer device analyzes the number of each data module, determines a plurality of data modules with the number meeting the preset number requirement, further analyzes the sizes of the data modules with the number meeting the preset number requirement, determines a plurality of data modules with the sizes meeting the preset size requirement, further analyzes the dependency relationship among the data modules with the sizes meeting the preset size requirement, and finally merges or splits the data modules according to the analysis result.
In this embodiment, after the computer device performs preprocessing on each data module by using the foregoing several preprocessing methods, a preprocessed target data module may be obtained, and then a corresponding dependency analysis tool or a dependency analysis function method may be used to analyze the dependency relationship between each target data module, so as to obtain the dependency relationship between each target data module.
S103, packaging the target data modules according to the dependency relationship among the target data modules.
Specifically, when the computer device obtains the dependency relationship between the target data modules and each target data module, the existing data module packager (for example, weback module packager) or other packaging methods may be used to package the multiple target data modules according to the dependency relationship between each target data module, so as to obtain a packaged package file.
In the above method for packaging data modules, the computer device obtains the dependency relationships between the plurality of data modules corresponding to the front-end project and each data module, then splits or merges each data module according to the attribute information of each data module and the dependency relationship between each data module to obtain each target data module and the dependency relationship between each target data module, and finally packages the target data module according to the dependency relationship between each target data module. The target data module is a data module obtained by preprocessing the acquired data module by the computer equipment, the computer equipment is used for preprocessing the original data module by combining the size and/or the number of the data modules and the dependency relationship among the data modules, so that the size and/or the number of the target data module obtained after preprocessing is the optimal size and/or the number required by later packaging, the size and the number of the packaging file obtained after later packaging of each target data module are also optimal, the output efficiency of the packaging file when the packaging file is output to the front-end browser is improved, and the resource request efficiency when a user accesses the front-end browser is also improved. In addition, the computer equipment pre-processes the original data modules by analyzing the dependency relationship among the data modules, so that the dependency relationship among the target data modules obtained after the pre-processing is simplified, and when the target data modules with the simplified dependency relationship are packed in the later period, the packing times of the data modules with the complex dependency relationship are reduced, and the packing efficiency of the computer equipment on the data modules is further improved.
In one embodiment, when the attribute information of the data module includes the size of the data module, as shown in fig. 3, the step S102 includes:
s201, determining the size type of each data module according to the size of each data module.
The size type of the data module comprises a large-size data module and a small-size data module. The large-size data module is a data module with large data volume, and the small-size data module is a data module with small data volume. Specifically, when the computer device obtains a plurality of data modules, the size of each data module may be further determined according to the size of the data volume contained in each data module, and then whether each data module belongs to a large-size data module or a small-size data module is determined according to the size of each data module.
S202, preprocessing each data module according to the size type of each data module and the dependency relationship among each data module.
When the size type of each data module is determined by the computer device, the data modules belonging to the same size type may be further screened (for example, data modules of a large size type or data modules of a small size type), then the dependency relationship between each screened data module is analyzed, or the dependency relationship between each screened data module and other data modules is analyzed, and the data modules belonging to the same size type are preprocessed (for example, combined) by adopting a corresponding preprocessing method, or the data modules belonging to the same size type are preprocessed (for example, split) respectively.
In one embodiment, based on the foregoing embodiment, the application provides an implementation manner of the foregoing S102, as shown in fig. 4, where the foregoing S102 "preprocesses each data module according to attribute information of each data module and a dependency relationship between each data module" includes:
s301, comparing the size of the data module with a preset size threshold, if the size of the data module is larger than the preset size threshold, executing step S302, and if the size of the data module is smaller than or equal to the preset size threshold, executing step S303.
The preset size threshold value can be determined by the computer equipment in advance according to the requirement of the actual optimized data module. Specifically, the present embodiment relates to a process in which a computer device determines a size type of a data module, that is, after the size of each data module is obtained, the size of each data module is compared with a preset size threshold, and if the size of the data module is greater than the preset size threshold, it is indicated that the data module contains a larger amount of data, the data module is defined as a large-size data module; if the size of the data module is smaller than or equal to the preset size threshold, the data module is defined as a small-size data module if the data module is indicated to contain smaller data quantity.
S302, determining that the size type of the data module is a large-size data module, and preprocessing each large-size data module according to the dependency relationship among the data modules.
The present embodiment relates to a case where the computer apparatus determines that the size of the data module is larger than a preset size threshold, in which case the computer apparatus determines the size type of the data module as a large-size data module.
S303, determining the size type of the data module as a small-size data module, and preprocessing each small-size data module according to the dependency relationship among the small-size data modules.
The present embodiment relates to a case where the computer device determines that the size of the data module is smaller than or equal to a preset size threshold, in which case the computer device determines the size type of the data module as a small-size data module.
According to the embodiment, the size type of each data module is determined, so that the data modules are preprocessed, the size of the preprocessed data modules is the optimal size, and the situation that the package files after the data modules are packaged in the later period due to the overlarge size of the data modules or the package files after the data modules are packaged in the later period due to the undersize of the data modules are avoided. Therefore, the method can ensure that the size and the number of the packaged files after the module data are packaged by the computer equipment at a later stage are optimal.
In practical application, when the determined size type of the data module is a small-size data module, the implementation manner of the foregoing S202, that is, the implementation manner of preprocessing the small-size data module, as shown in fig. 5, the foregoing S303 "preprocessing each small-size data module according to the dependency relationship between each small-size data module" includes:
s401, determining a plurality of candidate small-size data modules with a first-level dependency relationship from all small-size data modules according to the dependency relationship among the small-size data modules.
The first-level dependency relationship refers to a direct reference relationship, for example, the data module a refers to the data module B, the data module B refers to the data module C, and then the data module a and the data module B have a first-level dependency relationship therebetween, and the data module B and the data module C have a first-level dependency relationship therebetween. Specifically, when the computer device screens out at least two small-size data modules from the plurality of data modules, the dependency relationship between the small-size data modules can be analyzed to see whether the small-size data modules with the first-order dependency relationship exist in the at least two small-size data modules, and if so, the small-size data modules with the first-order dependency relationship are screened out from the plurality of small-size data modules to be used as candidate small-size data modules.
And S402, merging the plurality of candidate small-size data modules.
When the computer device screens out a plurality of candidate small-size data modules from a plurality of small-size data modules, the plurality of candidate small-size data modules can be combined. After the candidate small-size data modules are combined, the number of the data modules is greatly reduced, and further, the optimization of the number of the data modules and the optimization of the number of the packed files packed according to the data modules in the later period are realized. Meanwhile, because the dependency relationship among the plurality of candidate small-size data modules is a first-level dependency relationship, the dependency relationship among module codes in the combined data modules is simplified, so that the number of times of packaging the combined data modules in the later period is reduced, and the packaging efficiency is improved.
In practical application, when the determined size type of the data module is a large-size data module, the implementation manner of the step S202 is provided correspondingly, that is, the implementation manner of preprocessing the large-size data module, as shown in fig. 6, the step S202 "preprocessing each large-size data module according to the dependency relationship between each data module" includes:
S501, determining the number of data modules with dependency relations with the large-size data modules according to the dependency relations among the data modules.
Specifically, when the computer device screens out the large-size data modules from the plurality of data modules, the number of data modules having a dependency relationship with each large-size data module can be further determined by checking the dependency relationship between each data module. For example, if the data module a is a large-sized data module, the computer device may look at the number of data modules that the data module a references other modules and determine the number as the number of data modules that have a dependency relationship with the data module a, or the computer device may also look at the number of other data modules that reference the data module a and determine the number as the number of data modules that have a dependency relationship with the data module a, or the computer device may simultaneously determine the number of other data modules that reference the data module a and the number of data modules that the data module a references other data modules together as the number of data modules that have a dependency relationship with the data module a.
S502, preprocessing each large-size data module according to the number.
After the computer equipment determines the number of the data modules with the dependency relationship with each large-size data module based on the steps, large-size data modules with the number meeting the preset number requirement can be screened from a plurality of large-size data modules according to the number, and then preprocessing is carried out on the screened large-size data modules.
Further, the step S502 "preprocessing each large-size data module according to the number" may specifically include: if the number is smaller than the preset number threshold, splitting the large-size data module.
The preset number threshold value can be determined by the computer equipment in advance according to the size requirement of the optimization module data or the number requirement of the optimization module data. The embodiment relates to a specific implementation manner of preprocessing each large-size data module by computer equipment according to the number, namely, the computer equipment compares the number of the data modules with the dependency relationship with the large-size data modules with a preset number threshold, and if the number is smaller than the preset number threshold, the large-size data modules corresponding to the number are correspondingly split to obtain the data modules with proper sizes. In the process of splitting the large-size data modules, the large-size data modules corresponding to the number smaller than the preset number threshold are split, so that the dependency relationship among the split data modules is simpler, and the dependency relationship among all the preprocessed data modules is simplified.
In an application scenario, there is a case where the number of data modules having a dependency relationship with a large-size data module is smaller than a preset number threshold, and in this scenario, there is a complex dependency relationship between the large-size data module and other data modules, so that splitting is inconvenient, the computer device may not perform any processing on the large-size data module, and may directly package the large-size data module in a later period.
In an application, when there are a plurality of data modules with singleness in the plurality of data modules acquired by the computer device, the application correspondingly provides an implementation manner of S102, that is, an implementation manner of preprocessing the data modules with singleness, as shown in fig. 7, where S102 "preprocessing each data module according to attribute information of each data module and a dependency relationship between each data module", includes:
s601, determining whether a single dependency exists between every two data modules according to the dependency relationship among the data modules; a singleness dependency indicates that one of every two data modules references the other data module, and the other data module does not reference the other data module.
Specifically, when the computer device obtains a plurality of data modules and the dependency relationship between the plurality of data modules, it may be determined whether each two data modules have a monotonically dependent relationship by analyzing the dependency relationship between the data modules, for example, if there are data module a and data module B, the data module a refers to the data module B, and the data module B does not refer to any other data module, it is determined that the data module a and the data module B have a monotonically dependent relationship.
S602, merging every two data modules with the single dependency.
When the computer device determines each two data modules with the single dependency based on the steps, the two data modules with the single dependency can be directly combined. In the process of merging every two data modules with the uniqueness dependency, one data module does not refer to any other data module in every two data modules with the uniqueness dependency, and the two data modules are in a single reference relationship, so that the dependency relationship among all module codes in the merged data module is relatively simple, the dependency relationship between the merged data module and other data modules is relatively simple, and the dependency relationship among all data modules after preprocessing is greatly simplified.
On the basis of the method described in the embodiment of fig. 7, the present application further provides a method for splitting and merging the obtained data module group, as shown in fig. 8, where the method is performed after S602, and the method includes:
s701, judging whether the data module group obtained after combination contains the same data module.
After the computer device obtains the combined data module groups based on the method in the embodiment of fig. 7, the computer device may further perform preprocessing on each data module group, specifically, the computer device may look at the data modules included in each data module group, determine whether each data module group includes the same data module, if so, indicate that there is a repeated data module, and correspondingly split the data module group by adopting a corresponding processing method, if not, indicate that there is no repeated data module, and at this time, do not split the data module group. For example, the data module group O1 includes a data module a and a data module B, and the data module group O2 includes a data module C and a data module B, so that the data module B is the same data module.
S702, if the same data module is included, determining whether the same data module references other data modules according to the dependency relationship among the data modules.
The embodiment relates to a scene that the computer equipment determines that the data module group obtained after the combination contains the same data module, under the application scene, the computer equipment determines whether the same data module refers to other data modules by analyzing the dependency relationship between the same data module and other data modules in the data module group, if the same data module refers to other data modules, the computer equipment indicates that complex dependency relationship exists between the data module group containing the same data module and other data modules, and the data module group cannot be split; if the same data module does not refer to other data modules, the dependency relationship between the data module group containing the same data module and other data modules is very simple, or the data module group is relatively independent and does not have the dependency relationship with other data modules, so that the data module group can be split.
S703, if the same data module does not reference other data modules, splitting the same data module from the data module group.
The embodiment relates to an application scene that the same data module does not refer to other data modules, and in the application scene, the computer equipment directly splits the same data module from a data module group, so that no dependency relationship exists between the split data module and other data modules, and the dependency relationship among all the data modules after preprocessing is simplified. For example, the data module group O1 includes a data module a and a data module B, and the data module a refers to the data module B, the data module group O2 includes a data module C and a data module B, and the same data module B does not refer to not only the data module a and the data module C but also to any other data module. Then the data module B can be split from the data module group O1 and the data module group O2, respectively.
In practical applications, after the computer device obtains the dependency relationship between the data modules, the method for packaging the data modules provided in the present application further provides a method for generating and displaying a correspondence graph according to the dependency relationship between the data modules, for example, after the computer device executes the step S101 in the embodiment of fig. 2, as shown in fig. 9, the method in the embodiment of fig. 2 further includes the following steps:
s801, drawing data is generated according to the data modules and the dependency relationship among the data modules; the drawing data includes connection relations between nodes corresponding to the data modules.
When the computer device obtains the dependency relationships between the plurality of data modules corresponding to the front-end items and the data modules based on the step S101 in the embodiment of fig. 2, the dependency relationships between the data modules may be further presented by adopting a relationship diagram. Specifically, the computer device may select an existing graphic generating tool to generate drawing data according to each data module and the dependency relationship between each data module, and the tool for generating and drawing the drawing data is not limited herein.
S802, drawing and displaying a relation chart according to drawing data; the relationship graph is used to represent the dependency relationship between the data modules.
Wherein the relationship graph may include different types of illustrations such as binary graphs, node graphs, tree graphs, and the like, without limitation. After the computer equipment generates drawing data by using a corresponding graph generating tool, a corresponding drawing tool (for example, a visual library echartis tool) can be used for drawing and displaying a relation graph in a front-end page according to the drawing data, the relation graph can clearly show the dependency relationship among the data modules, and an end user can view the page with the relation graph through a browser, so that the dependency relationship among a plurality of data modules corresponding to a front-end project is intuitively known, and the accuracy of analyzing the dependency relationship among the data modules by a front-end developer is improved.
In one embodiment, a specific implementation manner of the embodiment S101 of fig. 2 is provided, for example, the step S101 "obtaining the dependency relationship between the plurality of data modules corresponding to the front-end item and each data module" specifically includes: and analyzing the plurality of data modules corresponding to the front-end projects by using a module dependency analysis function of the module packer to obtain the dependency relationship among the data modules.
The module packer is a tool for packing each module data to generate a packed file. The module dependency analysis function is used for analyzing each module data to obtain a dependency relationship between each data module, for example, if the weback packer is used for packing each module data, the emit hook function of the compiler in the weback can be used for analyzing and processing a plurality of module data to obtain the dependency relationship between each module data. Because the Webpack packer is an existing relatively mature module packing tool, when the module packing tool is used for packing each data module in the later period, the method is simple and convenient, and the popularization and the application of the packing method of the data module are improved.
In all the above embodiments, the present application further provides a method for packaging a data module, as shown in fig. 10, where the method includes:
s901, acquiring a plurality of data modules corresponding to front-end items.
S902, analyzing a plurality of data modules corresponding to the front-end projects by using a module dependency analysis function of a module packer to obtain dependency relations among the data modules.
S903, drawing data is generated from each data module and the dependency relationship between each data module.
S904, drawing and displaying a relation chart according to the drawing data.
S905, comparing the size of the data module with a preset size threshold, if the size of the data module is larger than the preset size threshold, determining that the size type of the data module is a large-size data module, executing step S906, if the size of the data module is smaller than or equal to the preset size threshold, determining that the size type of the data module is a small-size data module, and executing steps S910-S911.
S906, determining the number of data modules with the dependency relationship with each large-size data module according to the dependency relationship among each data module.
S907, comparing the number with a preset number threshold, if the number is smaller than the preset number threshold, executing step S908, and if the number is larger than or equal to the preset number threshold, executing step S909.
S908, splitting the large-size data module.
S909, no operation is performed.
S910, according to the dependency relationship among the small-size data modules, determining a plurality of candidate small-size data modules with primary dependency relationship from all the small-size data modules.
And S911, merging the plurality of candidate small-size data modules.
S912, determining whether a single dependency exists between every two data modules according to the dependency relationship between the data modules; a singleness dependency indicates that one of every two data modules references the other data module, and the other data module does not reference the other data module.
And S913, combining every two data modules with the uniqueness dependence to obtain a plurality of data module groups.
S914, judging whether the same data module is contained in different data module groups, if so, executing step S915, and if not, executing step S917.
S915, according to the dependency relationship among the data modules, determining whether the same data module refers to other data modules, if the same data module does not refer to other data modules, executing step S916, and if the same data module refers to other data modules, executing step S917.
S916, splitting the same data module from the data module group.
S917, no operation is performed.
S918, preprocessing each data module according to the method described in the above S905-S917 to obtain a plurality of target data modules.
S919, analyzing the plurality of target data modules by using a module dependency analysis function of the module packer to obtain the dependency relationship among the target data modules.
S920, packaging the target data modules according to the dependency relationship among the target data modules.
For a detailed description of each step in this embodiment, please refer to the description of the foregoing embodiment, and the detailed description is not repeated here. It should be noted that, the steps S912-S917 may be performed before the computer device performs the step S905, or may be performed after the computer device performs the step S905-S911 and obtains the combined and/or split data module, that is, the computer device may perform the preprocessing on each data module according to the method described in S905-S911, then perform the preprocessing on each data module according to the method described in S912-S917, and finally obtain the dependency relationship between each target data module and each target data module after the preprocessing. Optionally, the computer device may pre-process each data module according to the method described in S912-S917, then pre-process each data module after pre-processing according to the method described in S905-S911, and finally obtain the dependency relationship between the plurality of target data modules after pre-processing and each target data module.
It should be understood that, although the steps in the flowcharts of fig. 2-10 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in FIGS. 2-10 may include multiple steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor do the order in which the steps or stages are performed necessarily performed in sequence, but may be performed alternately or alternately with at least a portion of the steps or stages in other steps or other steps.
In one embodiment, as shown in fig. 11, there is provided a packaging apparatus of a data module, including: an acquisition module 11, a preprocessing module 12 and a packaging module 13, wherein:
the acquiring module 11 is configured to acquire a plurality of data modules corresponding to the front-end item and a dependency relationship between each of the data modules.
A preprocessing module 12, configured to preprocess each data module according to attribute information of each data module and a dependency relationship between each data module, so as to obtain each target data module and a dependency relationship between each target data module; the preprocessing comprises splitting or merging the data modules; the attribute information of the data modules comprises the size and/or the number of the data modules; the dimension represents a data size of the data module.
And the packaging module 13 is used for packaging the target data modules according to the dependency relationship among the target data modules.
In one embodiment, the attribute information includes the size of the data module, and as shown in fig. 12, the preprocessing module 12 includes:
a first determining unit 121, configured to determine a size type of each data module according to a size of each data module;
the preprocessing unit 122 is configured to preprocess each of the data modules according to the size type of each of the data modules and the dependency relationship between each of the data modules.
In one embodiment, as shown in fig. 13, the first determining unit 121 includes:
a comparing subunit 1211, configured to compare the size of the data module with a preset size threshold;
a first determining subunit 1212, configured to determine that the size type of the data module is a large-size data module when the size of the data module is greater than the preset size threshold;
a second determining subunit 1213, configured to determine that the size type of the data module is a small-size data module when the size of the data module is less than or equal to the preset size threshold.
In one embodiment, as shown in fig. 14, the preprocessing unit 122 includes:
a third determining subunit 1221 configured to determine, from among all the small-size data modules, a plurality of candidate small-size data modules having a first-order dependency relationship according to the dependency relationship between the small-size data modules;
a merging subunit 1222 configured to merge a plurality of the candidate small-size data modules.
In one embodiment, as shown in fig. 15, the preprocessing unit 122 includes:
a fourth determining subunit 1223 configured to determine, according to the dependency relationship between each of the data modules, the number of data modules having a dependency relationship with each of the large-size data modules;
a processing subunit 1224, configured to preprocess each of the large-size data modules according to the number.
In one embodiment, the processing subunit 1224 is specifically configured to split the large-size data module when the number is smaller than a preset number threshold.
In one embodiment, as shown in fig. 16, the preprocessing module 12 includes:
a second determining unit 123, configured to determine whether a single dependency exists between every two data modules according to the dependency relationship between the data modules; the singleness dependency indicates that one data module in every two data modules references another data module, and the other data module does not reference other data modules;
And a merging unit 124, configured to merge each two data modules having the singleness dependency.
In one embodiment, as shown in fig. 17, after the preprocessing module 12, the apparatus further includes:
a judging and processing unit 125, configured to judge whether the data module group obtained after the merging contains the same data module; if the same data module is contained, determining whether the same data module references other data modules according to the dependency relationship among the data modules; and if the same data module does not refer to other data modules, splitting the same data module from the data module group.
In one embodiment, as shown in fig. 18, after the obtaining module 11, the apparatus further includes:
a generating module 14, configured to generate drawing data according to each of the data modules and the dependency relationship between each of the data modules; the drawing data comprise connection relations among nodes corresponding to the data modules;
a drawing module 15, configured to draw and display a relationship graph according to the drawing data; the relationship graph is used for representing the dependency relationship among the data modules.
In one embodiment, the obtaining module 11 is specifically configured to analyze the plurality of data modules corresponding to the front-end item by using a module dependency analysis function of a module packer, so as to obtain a dependency relationship between the data modules.
For specific limitations of the packaging device of the data module, reference may be made to the above limitation of the packaging method of the data module, which is not repeated here. The above-mentioned individual modules in the packaging device of the data modules may be implemented in whole or in part by software, hardware or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the electronic device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of:
acquiring a plurality of data modules corresponding to a front-end project and a dependency relationship between each data module;
preprocessing each data module according to attribute information of each data module and the dependency relationship between each data module to obtain each target data module and the dependency relationship between each target data module; the preprocessing comprises splitting or merging the data modules; the attribute information of the data modules comprises the size and/or the number of the data modules; the dimension represents a data size of the data module;
And packaging the target data modules according to the dependency relationship among the target data modules.
The computer device provided in the foregoing embodiments has similar implementation principles and technical effects to those of the foregoing method embodiments, and will not be described herein in detail.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring a plurality of data modules corresponding to a front-end project and a dependency relationship between each data module;
preprocessing each data module according to attribute information of each data module and the dependency relationship between each data module to obtain each target data module and the dependency relationship between each target data module; the preprocessing comprises splitting or merging the data modules; the attribute information of the data modules comprises the size and/or the number of the data modules; the dimension represents a data size of the data module;
and packaging the target data modules according to the dependency relationship among the target data modules.
The foregoing embodiment provides a computer readable storage medium, which has similar principles and technical effects to those of the foregoing method embodiment, and will not be described herein.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, or the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples merely represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (10)
1. A method of packaging data modules, the method comprising:
acquiring a plurality of data modules corresponding to front-end projects, and analyzing the dependency relationship among the data modules by adopting a dependency analysis tool or a dependency analysis function to obtain the dependency relationship among the data modules;
preprocessing each data module according to attribute information of each data module and the dependency relationship between each data module to obtain each target data module and the dependency relationship between each target data module; the preprocessing comprises splitting large-size data modules with a dependency relationship in each data module or merging small-size data modules with a first-level dependency relationship in each data module; the attribute information of the data modules comprises the size and/or the number of the data modules; the dimension represents a data size of the data module; the first-level dependency relationship is a direct reference relationship;
Packaging the target data modules according to the dependency relationship among the target data modules;
the splitting the large-size data module with the dependency relationship in each data module comprises the following steps:
determining the number of data modules with dependency relations with the large-size data modules according to the dependency relations among the data modules;
and if the number is smaller than a preset number threshold, splitting the large-size data module.
2. The method of claim 1, wherein the attribute information includes a size of the data module, and wherein preprocessing each data module based on the attribute information of each data module and the dependency relationship between each data module includes:
comparing the size of the data module with a preset size threshold;
if the size of the data module is larger than the preset size threshold, determining that the size type of the data module is a large-size data module, and preprocessing each large-size data module according to the dependency relationship among the data modules;
if the size of the data module is smaller than or equal to the preset size threshold, determining that the size type of the data module is a small-size data module, and preprocessing each small-size data module according to the dependency relationship among the small-size data modules.
3. The method of claim 2, wherein preprocessing each of the small-sized data modules according to the dependency relationship between each of the small-sized data modules comprises:
determining a plurality of candidate small-size data modules with primary dependency relations from all small-size data modules according to the dependency relations among the small-size data modules;
and merging a plurality of candidate small-size data modules.
4. The method according to claim 1, wherein preprocessing each of the data modules according to the attribute information of each of the data modules and the dependency relationship between each of the data modules comprises:
determining whether a singleness dependency exists between every two data modules according to the dependency relationship between the data modules; the singleness dependency indicates that one data module in every two data modules references another data module, and the other data module does not reference other data modules;
every two data modules with the singleness dependency are merged.
5. The method of claim 4, wherein after merging each two data modules having the singleness dependency, the method further comprises:
Judging whether the data module groups obtained after combination contain the same data module or not;
if the same data module is contained, determining whether the same data module references other data modules according to the dependency relationship among the data modules;
and if the same data module does not refer to other data modules, splitting the same data module from the data module group.
6. The method according to claim 1, wherein after the obtaining the dependency relationship between the plurality of data modules corresponding to the front-end item and the plurality of data modules, the method further comprises:
generating drawing data according to the data modules and the dependency relationship between the data modules; the drawing data comprise connection relations among nodes corresponding to the data modules;
drawing and displaying a relation chart according to the drawing data; the relationship graph is used for representing the dependency relationship among the data modules.
7. A packaging apparatus for data modules, the apparatus comprising:
the acquisition module is used for acquiring a plurality of data modules corresponding to the front-end project, and analyzing the dependency relationship among the data modules by adopting a dependency analysis tool or a dependency analysis function to obtain the dependency relationship among the data modules;
The preprocessing module is used for preprocessing each data module according to the attribute information of each data module and the dependency relationship among the data modules to obtain each target data module and the dependency relationship among the target data modules; the preprocessing comprises splitting large-size data modules with a dependency relationship in each data module or merging small-size data modules with a first-level dependency relationship in each data module; the attribute information of the data modules comprises the size and/or the number of the data modules; the dimension represents a data size of the data module; the first-level dependency relationship is a direct reference relationship;
the packaging module is used for packaging the target data modules according to the dependency relationship among the target data modules;
the preprocessing module is used for determining the number of data modules with the dependency relationship with the large-size data modules according to the dependency relationship among the data modules; and splitting the large-size data module under the condition that the number is smaller than a preset number threshold value.
8. The apparatus of claim 7, wherein the preprocessing module comprises:
A comparing subunit, configured to compare the size of the data module with a preset size threshold;
a first determining subunit, configured to determine that a size type of the data module is a large-size data module when the size of the data module is greater than the preset size threshold;
and the second determining subunit is used for determining that the size type of the data module is a small-size data module when the size of the data module is smaller than or equal to the preset size threshold value.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.
10. A storage medium having stored thereon a computer program, which when executed by a processor, implements the steps of the method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010816367.6A CN111949312B (en) | 2020-08-14 | 2020-08-14 | Packaging method and device for data module, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010816367.6A CN111949312B (en) | 2020-08-14 | 2020-08-14 | Packaging method and device for data module, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111949312A CN111949312A (en) | 2020-11-17 |
| CN111949312B true CN111949312B (en) | 2024-02-09 |
Family
ID=73342199
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010816367.6A Active CN111949312B (en) | 2020-08-14 | 2020-08-14 | Packaging method and device for data module, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111949312B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112822514B (en) * | 2020-12-30 | 2022-06-28 | 北京大学 | Video stream packet transmission method, system, terminal and medium based on dependency relationship |
| CN117369865B (en) * | 2023-12-07 | 2024-04-05 | 麒麟软件有限公司 | GNU linux universal application program packaging method and graphical application packer |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH10222353A (en) * | 1997-01-31 | 1998-08-21 | Hitachi Ltd | Method for generating program |
| JP2015135535A (en) * | 2014-01-16 | 2015-07-27 | 株式会社 日立産業制御ソリューションズ | File processor and file processing method |
| CN106874394A (en) * | 2017-01-13 | 2017-06-20 | 百度在线网络技术（北京）有限公司 | A kind of method and apparatus of file packing pretreatment |
| CN106959997A (en) * | 2017-02-04 | 2017-07-18 | 深圳市中博科创信息技术有限公司 | Document handling method and device based on cluster file system |
| CN107679177A (en) * | 2017-09-29 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of small documents storage optimization method based on HDFS, device, equipment |
| CN109145236A (en) * | 2017-06-28 | 2019-01-04 | 艺龙网信息技术（北京）有限公司 | Page file processing method, apparatus and system |
| CN109816527A (en) * | 2019-01-25 | 2019-05-28 | 网联清算有限公司 | Reconciliation document handling method, device, computer equipment and storage medium |
| CN109857385A (en) * | 2018-12-24 | 2019-06-07 | 四川长虹电器股份有限公司 | Application file packaging method, installation method and starting method |
| CN110636111A (en) * | 2019-08-22 | 2019-12-31 | 北京达佳互联信息技术有限公司 | Resource packaging method and device, electronic equipment and storage medium |
| CN110795143A (en) * | 2019-10-22 | 2020-02-14 | 中国工商银行股份有限公司 | Method, apparatus, computing device, and medium for processing functional module |
| CN110908697A (en) * | 2019-11-28 | 2020-03-24 | 米哈游科技（上海）有限公司 | Resource packaging method, device, server and storage medium |
| CN110908707A (en) * | 2019-11-28 | 2020-03-24 | 米哈游科技（上海）有限公司 | Resource packaging method, device, server and storage medium |
| CN111399863A (en) * | 2020-03-13 | 2020-07-10 | 深圳前海微众银行股份有限公司 | Dependent file packaging method, device, equipment and computer readable storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150363195A1 (en) * | 2014-06-16 | 2015-12-17 | npm, Inc. | Software package management |
| US9367425B1 (en) * | 2015-09-30 | 2016-06-14 | Semmle Limited | Disjoint-or trees for caching aggregated dependencies |
-
2020
- 2020-08-14 CN CN202010816367.6A patent/CN111949312B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH10222353A (en) * | 1997-01-31 | 1998-08-21 | Hitachi Ltd | Method for generating program |
| JP2015135535A (en) * | 2014-01-16 | 2015-07-27 | 株式会社 日立産業制御ソリューションズ | File processor and file processing method |
| CN106874394A (en) * | 2017-01-13 | 2017-06-20 | 百度在线网络技术（北京）有限公司 | A kind of method and apparatus of file packing pretreatment |
| CN106959997A (en) * | 2017-02-04 | 2017-07-18 | 深圳市中博科创信息技术有限公司 | Document handling method and device based on cluster file system |
| CN109145236A (en) * | 2017-06-28 | 2019-01-04 | 艺龙网信息技术（北京）有限公司 | Page file processing method, apparatus and system |
| CN107679177A (en) * | 2017-09-29 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of small documents storage optimization method based on HDFS, device, equipment |
| CN109857385A (en) * | 2018-12-24 | 2019-06-07 | 四川长虹电器股份有限公司 | Application file packaging method, installation method and starting method |
| CN109816527A (en) * | 2019-01-25 | 2019-05-28 | 网联清算有限公司 | Reconciliation document handling method, device, computer equipment and storage medium |
| CN110636111A (en) * | 2019-08-22 | 2019-12-31 | 北京达佳互联信息技术有限公司 | Resource packaging method and device, electronic equipment and storage medium |
| CN110795143A (en) * | 2019-10-22 | 2020-02-14 | 中国工商银行股份有限公司 | Method, apparatus, computing device, and medium for processing functional module |
| CN110908697A (en) * | 2019-11-28 | 2020-03-24 | 米哈游科技（上海）有限公司 | Resource packaging method, device, server and storage medium |
| CN110908707A (en) * | 2019-11-28 | 2020-03-24 | 米哈游科技（上海）有限公司 | Resource packaging method, device, server and storage medium |
| CN111399863A (en) * | 2020-03-13 | 2020-07-10 | 深圳前海微众银行股份有限公司 | Dependent file packaging method, device, equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111949312A (en) | 2020-11-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109634598B (en) | Page display method, device, equipment and storage medium | |
| US8997065B2 (en) | Automatic modularization of source code | |
| US11106437B2 (en) | Lookup table optimization for programming languages that target synchronous digital circuits | |
| US9875090B2 (en) | Program analysis based on program descriptors | |
| US7844898B2 (en) | Exporting a document in multiple formats | |
| CN111949312B (en) | Packaging method and device for data module, computer equipment and storage medium | |
| CN111176717B (en) | Method and device for generating installation package and electronic equipment | |
| CN114153459A (en) | Interface document generation method and device | |
| US11366704B2 (en) | Configurable analytics for microservices performance analysis | |
| CN109634611B (en) | Mobile terminal three-dimensional model ply file analysis and display method based on OpenGL | |
| CN113495728A (en) | Dependency relationship determination method, dependency relationship determination device, electronic equipment and medium | |
| Ledur et al. | A high-level dsl for geospatial visualizations with multi-core parallelism support | |
| CN112889026A (en) | User interface resource file optimization | |
| CN115982491A (en) | Page updating method and device, electronic equipment and computer readable storage medium | |
| US9811448B2 (en) | Event-driven software testing | |
| CN115048083A (en) | Visualization method and device for assembly, storage medium and electronic equipment | |
| CN114077575A (en) | Format conversion method, equipment and system for memory snapshot file | |
| CN116755714B (en) | Method, device, equipment and storage medium for operating deep neural network model | |
| JP7073431B2 (en) | Source code analysis system and source code analysis method | |
| CN108182362B (en) | Multi-dex file analysis method and system | |
| CN114281317A (en) | Code visualization method and system, electronic device and storage medium | |
| CN115658797A (en) | Data processing method, device and storage medium | |
| CN117453223A (en) | Image file generation method and device of operating system, computer equipment and medium | |
| CN114138379A (en) | Task execution method, device and computer readable storage medium | |
| Jackson II | Peephole pretty printing |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20211011 Address after: Building 36, yard 8, Dongbeiwang West Road, Haidian District, Beijing 100089 Applicant after: Dawning Information Industry (Beijing) Co.,Ltd. Applicant after: Zhongke Shuguang International Information Industry Co.,Ltd. Applicant after: ZHONGKE SUGON INFORMATION INDUSTRY CHENGDU Co.,Ltd. Address before: Building 36, yard 8, Dongbeiwang West Road, Haidian District, Beijing 100089 Applicant before: Dawning Information Industry (Beijing) Co.,Ltd. Applicant before: Zhongke Shuguang International Information Industry Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |