CN109375921B - Page file quick compiling method and device, storage device and computer device - Google Patents
Page file quick compiling method and device, storage device and computer device Download PDFInfo
- Publication number
- CN109375921B CN109375921B CN201810931286.3A CN201810931286A CN109375921B CN 109375921 B CN109375921 B CN 109375921B CN 201810931286 A CN201810931286 A CN 201810931286A CN 109375921 B CN109375921 B CN 109375921B
- Authority
- CN
- China
- Prior art keywords
- module
- compiled
- path information
- storage path
- associated storage
- 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 50
- 230000015654 memory Effects 0.000 claims description 35
- 238000004806 packaging method and process Methods 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 7
- 238000011161 development Methods 0.000 abstract description 19
- 230000006870 function Effects 0.000 description 12
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000012790 confirmation Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 239000012634 fragment Substances 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012827 research and development Methods 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
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Devices For Executing Special Programs (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method and a device for quickly compiling a page file, storage equipment and computer equipment, wherein the method comprises the following steps: confirming that the triggering operation aiming at the page file and used for triggering a user to compile a module is received; acquiring associated storage path information of the module to be compiled; the associated storage path information is path information of codes to be compiled of the modules to be compiled; writing the associated storage path information into a configuration file of a front-end resource module packer; and the front-end resource module packer acquires the code to be compiled according to the associated storage path information in the configuration file, and executes compiling on the code to be compiled. The method calls the recompilation of the front-end resource module packer to enable the new configuration file to take effect immediately, thereby simplifying the development and compiling process and improving the development efficiency of the page file.
Description
Technical Field
The invention relates to the technical field of file code compiling, in particular to a method and a device for quickly compiling a page file, storage equipment and computer equipment.
Background
Web pages are generally classified into single page applications and multi-page applications. The single page application is an application with only one web page, is a rich client loaded from a web server, and is commonly used for websites such as PC end official networks and shopping. Applications where multiple web pages exist for multiple pages, commonly used for apps or clients, etc. In the web site development process, whether it is a multi-page application or a single-page application, the files are typically manually configured by a developer.
Particularly, when a page application is modified, such as adding a new functional module, a code of the new module needs to be recompiled, and at this time, a developer needs to manually modify a configuration file, and then a compiling service is restarted. This manual mode of operation is not only cumbersome but also inefficient and manual modification is prone to error.
Disclosure of Invention
The invention provides a method and a device for quickly compiling a page file, storage equipment and computer equipment, which are used for simplifying the development and compiling process and improving the development efficiency of the page file.
The invention provides the following scheme:
A method for quickly compiling a page file, comprising: confirming that a triggering operation aiming at the page file and used for triggering a module to be compiled is received; acquiring associated storage path information of the module to be compiled; the associated storage path information is path information of codes to be compiled of the modules to be compiled; writing the associated storage path information into a configuration file of a front-end resource module packer; and the front-end resource module packer acquires the code to be compiled according to the associated storage path information in the configuration file, and executes compiling on the code to be compiled.
In one embodiment, the associated path information of the module to be compiled includes storage path information of the module to be compiled and storage path information of a sub-module of the module to be compiled; the obtaining the associated storage path information of the module to be compiled, writing the associated storage path information into a configuration file of a front-end resource module packer, includes: and acquiring the storage path information of the module to be compiled and the storage path information of the sub-module of the module to be compiled in a recursive traversal mode, and writing the storage path information of the module to be compiled and the storage path information of the sub-module of the module to be compiled into a configuration file of a front-end resource module packer.
In one embodiment, the front-end resource module packer obtains the code to be compiled according to the associated storage path information in the configuration file, and further includes: the front-end resource module packer detects whether the associated storage path information is written in the configuration file; if yes, the front-end resource module packer acquires the code to be compiled according to the associated storage path information in the configuration file; if not, the front-end resource module packer returns the prompt information of the failure of acquiring the code to be compiled to the page, and guides the user to trigger the module to be compiled again.
In one embodiment, the obtaining the associated storage path information of the module to be compiled, writing the associated storage path information into a configuration file of a front-end resource module packer, includes: and acquiring the storage path information of the module to be compiled and the storage path information of the module on which the module to be compiled depends, and writing the storage path information of the module to be compiled and the storage path information of the module on which the module to be compiled depends into a configuration file of a front-end resource module packer.
In one embodiment, after the confirmation receives the triggering operation for triggering the module to be compiled for the page file, before the obtaining the associated storage path information of the module to be compiled, the method further includes: identifying a type of the triggering operation; the obtaining the associated storage path information of the module to be compiled includes: and acquiring the associated storage path information of the module to be compiled according to the type of the triggering operation.
In one embodiment, the type of the trigger operation includes a select operation and a cancel operation; the obtaining the associated storage path information of the module to be compiled according to the type of the triggering operation includes: and determining the type of the triggering operation as a selecting operation, and acquiring the associated storage path information of the module to be compiled.
In one embodiment, after the writing of the associated storage path information into the configuration file of the front-end resource module packaging machine, before the front-end resource module packaging machine obtains the code to be compiled according to the associated storage path information in the configuration file, the method further includes: confirming that the cancel operation of the user to the compiling module in the page file is received; removing the associated storage path information from the configuration file of the front-end resource module baling press; and the front-end resource module packer determines that the associated storage path information is not written in the configuration file and prompts the user to trigger the module to be compiled.
A rapid compiling device for page files, comprising: the confirming module is used for confirming that the triggering operation aiming at the page file and used for triggering the module to be compiled is received; the acquisition module is used for acquiring the associated storage path information of the module to be compiled; the associated storage path information is path information of codes to be compiled of the modules to be compiled; the writing module is used for writing the associated storage path information into a configuration file of the front-end resource module packer; and the compiling module is used for acquiring the code to be compiled according to the associated storage path information in the configuration file by the front-end resource module packer and executing compiling on the code to be compiled.
A storage device having a computer program stored thereon; the computer program is adapted to be loaded by a processor and to perform the method for fast compiling a pagefile according to any one of the embodiments described above.
A computer apparatus, comprising: one or more processors; a memory; one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications configured to perform the pagefile rapid compilation method according to any of the embodiments described above.
According to the method for quickly compiling the page file, after the triggering operation of the to-be-compiled module by the user in the page file is received, the associated storage path information of the to-be-compiled module is written into the configuration file of the front-end resource module packer, and the front-end resource module packer acquires the to-be-compiled code of the to-be-compiled module according to the associated storage path information and executes compiling of the to-be-compiled code. Therefore, the front-end resource module packer is called to recompile, so that the new configuration file is immediately effective, the development and compiling process is simplified, and the development efficiency of the page file is improved.
Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
The foregoing and/or additional aspects and advantages of the invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
FIG. 1 is a flow chart of a method for fast compiling a pagefile according to an embodiment of the present invention;
FIG. 2 is a flowchart of a method according to an embodiment of step S400;
FIG. 3 is a flow chart of a method in another embodiment of a method for quickly compiling a pagefile according to the present invention;
FIG. 4 is a flow chart of a method for a fast compiling method for a pagefile according to another embodiment of the present invention;
FIG. 5 is a schematic view of an application scenario of a method for quickly compiling a page file according to the present invention;
FIG. 6 is a block diagram illustrating an exemplary embodiment of a fast compiling apparatus for a pagefile according to the present invention;
Fig. 7 is a schematic diagram of an embodiment of a computer device structure according to the present invention.
Detailed Description
Embodiments of the present invention are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are illustrative only and are not to be construed as limiting the invention.
It will be understood by those within the art that, unless expressly stated otherwise, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, and that "first," "second," and "the" are used herein merely to distinguish one and the same technical feature and do not limit the order, quantity, etc. of that technical feature. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It will be understood by those skilled in the art that all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs unless defined otherwise. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The invention provides a quick compiling method of a page file, which is used for automatically modifying a configuration file to compile a self-starting code when a module code is recompiled in the page development process. In one embodiment, as shown in FIG. 1, the method for rapidly compiling a pagefile includes the following steps:
And S100, confirming that the triggering operation aiming at the page file and used for triggering the module to be compiled is received.
In the page development process, a developer needs to compile the module code of the module after finishing writing the function code of the new module aiming at the new module development of a specific function so as to detect the running condition of the module code. The traditional mode of compiling new module codes is that a developer manually modifies a configuration file and restarts compiling services, and the manual mode is not only tedious but also low in efficiency.
In the actual operation process, after the developer completes writing of the new module function code, the system forms a corresponding module file to be compiled in the architecture catalog. The system catalog comprises a plurality of module files, and each module file corresponds to one function of the realization page. In this embodiment, the system interface displays all modules in the current system to a user (here, the user is generally referred to as a developer) in a directory manner, where the system interface includes each functional module file for page development, and when the user needs to compile a module file to be compiled, the user selects the module to be compiled, and the system confirms that the triggering operation of the module to be compiled by the user in the page file is received. The triggering operation of the user to-be-compiled module comprises clicking the to-be-compiled module, double clicking the to-be-compiled module or hooking the to-be-compiled module in the page. Here, the pagefile according to the present invention is a pagefile developed for a single-page application.
S200, acquiring associated storage path information of the module to be compiled; the associated storage path information is path information of codes to be compiled of the modules to be compiled.
In the directory files of all modules in the system, each module file is associated with storage path information of a storage space storing a corresponding code. The system can acquire codes corresponding to each module through the storage path information corresponding to the module in the page file. In this embodiment, after the system confirms that the triggering operation of the module to be compiled is received from the user in the page file, the associated storage path information of the module to be compiled is further obtained. Here, the system may obtain the stored code to be compiled according to the associated storage path of the module to be compiled. The associated storage path information of the module to be compiled may include storage path information of the module to be compiled and storage path information of a sub-module of the module to be compiled.
And S300, writing the associated storage path information into a configuration file of the front-end resource module packer.
In this implementation, the system utilizes a front-end resource module packer to compile the code of the module to be compiled. The front end resource module baler of the present invention is also referred to as webpack. For the front-end resource module baler, the main core idea is that the module, just as the JS file can be considered as a "module", all other things (including CSS, pictures, HTML, etc.) can be considered as modules, loaded by request. The module loader will eventually package all modules to generate a huge "bundle. Js" file and will always load continuously. The front-end resource module wrapper breaks the code through a number of features, generates multiple "bundle" fragments, and asynchronously loads different portions of the item. The configuration file of the front-end resource module packer has no fixed naming and no fixed path requirement, and if the front-end resource module packer is directly used for compiling, the front-end resource module packer defaults to read the front-end resource module packer under the current directory. In this embodiment, the associated storage path information of the module to be compiled is written into the configuration file of the front-end resource module packaging machine, and when the front-end resource module packaging machine executes compiling, the associated storage path information of the module to be compiled in the configuration file is read, so that the corresponding code to be compiled is read in the associated storage path.
In an embodiment, the associated path information of the module to be compiled includes storage path information of the module to be compiled and storage path information of a sub-module of the module to be compiled. Step S200 and step S300 include: and acquiring the storage path information of the module to be compiled and the storage path information of the sub-module of the module to be compiled in a recursive traversal mode, and writing the storage path information of the module to be compiled and the storage path information of the sub-module of the module to be compiled into a configuration file of a front-end resource module packer. Specifically, after the system receives the triggering operation of the module to be compiled, the background reads the storage path information of the module to be compiled and the storage path information of the sub-module thereof in the directory file in a recursion traversal mode.
S400, the front-end resource module packer acquires the code to be compiled according to the associated storage path information in the configuration file, and executes compiling on the code to be compiled.
In this embodiment, after the system writes the associated storage path information of the module to be compiled into the configuration file of the front-end resource module packer, the system triggers automated compiling of the front-end resource module packer. And the front-end resource module packer acquires codes to be compiled of the modules to be compiled according to the associated storage path information, and compiles the codes to be compiled. Specifically, when a developer selects a module (to-be-compiled module), the web tool of the system automatically writes the associated storage path information of the module into the configuration file, and simultaneously, the front-end resource module packer automatically compiles. The configuration file is written into and compiled automatically, and the configuration file and the automatic compiling are the same trigger behavior.
In an embodiment, step S400 further includes: and acquiring the storage path information of the module to be compiled and the storage path information of the module on which the module to be compiled depends, and writing the storage path information of the module to be compiled and the storage path information of the module on which the module to be compiled depends into a configuration file of a front-end resource module packer. Specifically, in the page development process, each functional module does not implement its function independently, and according to its dependency relationship, it needs to be referred to other functional modules. Therefore, in the implementation code corresponding to the module to be compiled, the dependency module relationship of the module to be compiled is generally written. When code compiling is performed, the front-end resource module packer needs to acquire codes of modules on which modules to be compiled depend. In this embodiment, the system acquires storage path information of a module to be compiled and storage path information of a module on which the module to be compiled depends, and writes the two storage path information into a configuration file of the front-end resource module packer, so that when the front-end resource module packer executes compilation, corresponding codes to be compiled are acquired according to the two storage path information to execute compilation.
According to the method for quickly compiling the page file, after the triggering operation of the to-be-compiled module by the user in the page file is received, the associated storage path information of the to-be-compiled module is written into the configuration file of the front-end resource module packer, and the front-end resource module packer acquires the to-be-compiled code of the to-be-compiled module according to the associated storage path information and executes compiling of the to-be-compiled code. Therefore, the front-end resource module packer is called to recompile, so that the new configuration file is immediately effective, the development and compiling process is simplified, and the development efficiency of the page file is improved.
In one embodiment, as shown in fig. 2, step S400 further includes the steps of:
S410, the front-end resource module packer detects whether the associated storage path information is written in the configuration file.
And S430, if so, the front-end resource module packer acquires codes to be compiled of the modules to be compiled according to the associated storage path information.
S450, if not, the front-end resource module packer returns the prompt information of the failure of acquiring the code to be compiled to the page, and guides the user to trigger the module to be compiled again.
In this embodiment, after the system writes the associated storage path information of the module to be compiled into the configuration file of the front-end resource module packaging machine, the front-end resource module packaging machine performs an operation of detecting whether the associated storage path information is written into the configuration file before the front-end resource module packaging machine performs compiling on the code to be compiled. If the associated storage path information is successfully written in the configuration file, the front-end resource module packer can acquire the code to be compiled according to the associated storage path information and execute subsequent code compiling operation. If the failure of writing the associated storage path information in the configuration file is detected, the front-end resource module packaging machine cannot acquire the code to be compiled, and at the moment, the front-end resource module packaging machine returns prompt information of failure of acquiring the code to be compiled to a current page of a user, prompts the user that the front-end resource module packaging machine cannot compile the code, and guides the user to trigger the code to be compiled again. For example, the system returns the user current page information "front end resource module baler code compilation failed, please again pick the module to be compiled.
In one embodiment, as shown in fig. 3, after step S100, before step S200, step S110 is further included: the type of the triggering operation is identified. At this time, step S200 includes step S210: and acquiring the associated storage path information of the module to be compiled according to the type of the triggering operation.
In this embodiment, the type of the trigger operation of the user to the compiling module includes a selecting operation and a cancelling operation. That is, the user may perform a selection or deselection operation of the module to be compiled. For example, when the user clicks on a module to be compiled, a selection operation is performed, i.e. the module to be compiled is checked. When the user double clicks the module to be compiled, the cancel operation is executed, namely the module to be compiled is deselected. In this embodiment, step S210 includes: and determining the type of the triggering operation as a selecting operation, and acquiring the associated storage path information of the module to be compiled. That is, when the system determines that the triggering operation of the user is to select the module to be compiled, the system acquires the associated storage path information of the module to be compiled. If the system identifies that the triggering operation of the user is to cancel the selection of the module to be compiled, the operation of acquiring the associated storage path information of the module to be compiled is not executed.
In a specific embodiment, as shown in fig. 4, after step S300, before step S400, the method further includes:
And S310, confirming that the cancel operation of the user to the compiling module in the page file is received.
And S330, removing the associated storage path information from the configuration file of the front-end resource module packaging machine.
S350, the front-end resource module packer determines that the associated storage path information is not written in the configuration file, and prompts the user to trigger the module to be compiled.
In this embodiment, when the system acquires the associated storage path information of the module to be compiled according to the triggering operation of the user and writes the associated storage path information into the configuration file of the front-end resource module packaging machine, the system identifies the cancel operation of the user on the module to be compiled, and removes the associated storage path information from the front-end resource module packaging machine configuration file. Therefore, the embodiment can solve the problem that the compiling error may be caused by the misoperation when the user selects the module to compile. Meanwhile, after the system removes the associated storage path information from the configuration file of the front-end resource module packaging machine, the front-end resource module packaging machine detects that the configuration file has no associated storage path information, and prompts a user to pick up the module to be compiled, which needs to be compiled, again.
The following details of the overall application environment based on the above-mentioned page file quick compiling method are specifically shown in fig. 5:
In the page file of the front-end interface, the system displays each functional module developed by a single page for a research and development personnel, and particularly can display the functional modules in a directory structure mode. As shown, the page file may include an A module, a B module, a module to be compiled, and a C module. In the background storage system, codes of each module are stored corresponding to each module. Such as a module code, B module code, module code to be compiled, and C module code. And the module file displayed at the front end is associated with the module code stored in the background by the storage path information. The code corresponding to each module can be obtained through the storage path information of the module. When a user triggers a module to be compiled in a front-end page file, the system instantly writes all associated storage path information of the module to be compiled into a configuration file of a front-end resource module packer, and at the moment, the front-end resource module packer acquires all associated codes of the module to be compiled from a background system according to all associated storage path information and executes compiling on all associated codes. Therefore, the method for quickly compiling the page file simplifies the development and compiling process and improves the development efficiency of the page file.
The invention also provides a device for quickly compiling the page file. In one embodiment, as shown in fig. 6, the pagefile rapid compiling apparatus includes a confirmation module 100, an acquisition module 200, a writing module 300, and a compiling module 400.
The confirmation module 100 is configured to confirm that a triggering operation for the page file and for triggering the module to be compiled is received. In the page development process, a developer needs to compile the module code of the module after finishing writing the function code of the new module aiming at the new module development of a specific function so as to detect the running condition of the module code. The traditional mode of compiling new module codes is that a developer manually modifies a configuration file and restarts compiling services, and the manual mode is not only tedious but also low in efficiency.
In the actual operation process, after the developer completes writing of the new module function code, the system forms a corresponding module file to be compiled in the architecture catalog. The system catalog comprises a plurality of module files, and each module file corresponds to one function of the realization page. In this embodiment, the system interface displays all modules in the current system to a user (here, the user is generally referred to as a developer) in a directory manner, where the system interface includes each functional module file for page development, and when the user needs to compile a module file to be compiled, the user selects the module to be compiled, and the system confirms that the triggering operation of the module to be compiled by the user in the page file is received. The triggering operation of the user to-be-compiled module comprises clicking the to-be-compiled module, double clicking the to-be-compiled module or hooking the to-be-compiled module in the page. Here, the pagefile according to the present invention is a pagefile developed for a single-page application.
The obtaining module 200 is configured to obtain associated storage path information of the module to be compiled; the associated storage path information is path information of codes to be compiled of the modules to be compiled. In the directory files of all modules in the system, each module file is associated with storage path information of a storage space storing a corresponding code. The system can acquire codes corresponding to each module through the storage path information corresponding to the module in the page file. In this embodiment, after the system confirms that the triggering operation of the module to be compiled is received from the user in the page file, the associated storage path information of the module to be compiled is further obtained. Here, the system may obtain the stored code to be compiled according to the associated storage path of the module to be compiled. The associated storage path information of the module to be compiled may include storage path information of the module to be compiled and storage path information of a sub-module of the module to be compiled.
The writing module 300 is configured to write the associated storage path information into a configuration file of the front-end resource module baling machine. In this implementation, the system utilizes a front-end resource module packer to compile the code of the module to be compiled. For the front-end resource module baler, the main core idea is that the module, just as the JS file can be considered as a "module", all other things (including CSS, pictures, HTML, etc.) can be considered as modules, loaded by request. The module loader will eventually package all modules to generate a huge "bundle. Js" file and will always load continuously. The front-end resource module wrapper breaks the code through a number of features, generates multiple "bundle" fragments, and asynchronously loads different portions of the item. The configuration file of the front-end resource module packer has no fixed naming and no fixed path requirement, and if the front-end resource module packer is directly used for compiling, the front-end resource module packer defaults to read the front-end resource module packer under the current directory. In this embodiment, the associated storage path information of the module to be compiled is written into the configuration file of the front-end resource module packaging machine, and when the front-end resource module packaging machine executes compiling, the associated storage path information of the module to be compiled in the configuration file is read, so that the corresponding code to be compiled is read in the associated storage path.
The compiling module 400 is configured to obtain the code to be compiled according to the associated storage path information in the configuration file by using the front-end resource module packer, and perform compiling on the code to be compiled. In this embodiment, after the system writes the associated storage path information of the module to be compiled into the configuration file of the front-end resource module packer, the system triggers automated compiling of the front-end resource module packer. And the front-end resource module packer acquires codes to be compiled of the modules to be compiled according to the associated storage path information, and compiles the codes to be compiled. Specifically, when a developer selects a module (to-be-compiled module), the web tool of the system automatically writes the associated storage path information of the module into the configuration file, and simultaneously, the front-end resource module packer automatically compiles. The configuration file is written into and compiled automatically, and the configuration file and the automatic compiling are the same trigger behavior.
In other embodiments, each module in the device for quickly compiling a pagefile provided by the present invention is further configured to execute operations corresponding to each step in the method for quickly compiling a pagefile according to the present invention, which are not described in detail herein.
The invention also provides a storage medium. The storage medium has a computer program stored thereon; the computer program, when executed by a processor, implements the method for quickly compiling a pagefile according to any one of the embodiments described above. The storage medium may be a memory. Such as internal memory or external memory, or both. The internal memory may include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), flash memory, or random access memory. The external memory may include a hard disk, floppy disk, ZIP disk, U-disk, tape, etc. The storage media disclosed herein include, but are not limited to, these types of memory. The memory disclosed herein is by way of example only and not by way of limitation.
The invention also provides computer equipment. A computer device comprising: one or more processors; a memory; one or more applications. Wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications configured to perform the pagefile rapid compilation method of any of the embodiments described above.
Fig. 7 is a schematic structural diagram of a computer device according to an embodiment of the invention. The computer device in this embodiment may be a server, a personal computer, or a network device. As shown in fig. 7, the apparatus includes a processor 703, a memory 705, an input unit 707, a display unit 709, and the like. It will be appreciated by those skilled in the art that the device architecture shown in fig. 7 does not constitute a limitation of all devices, and may include more or fewer components than shown, or may combine certain components. The memory 705 may be used to store an application program 701 and various functional modules, and the processor 703 runs the application program 701 stored in the memory 705, thereby executing various functional applications of the device and data processing. The memory may be internal memory or external memory, or include both internal memory and external memory. The internal memory may include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), flash memory, or random access memory. The external memory may include a hard disk, floppy disk, ZIP disk, U-disk, tape, etc. The disclosed memory includes, but is not limited to, these types of memory. The memory disclosed herein is by way of example only and not by way of limitation.
The input unit 707 is used for receiving input of a signal and receiving keywords input by a user. The input unit 707 may include a touch panel and other input devices. The touch panel may collect touch operations on or near the user (e.g., the user's operation on or near the touch panel using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a preset program; other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., play control keys, switch keys, etc.), a trackball, mouse, joystick, etc. The display unit 709 may be used to display information input by a user or information provided to the user and various menus of the computer device. The display unit 709 may take the form of a liquid crystal display, an organic light emitting diode, or the like. The processor 703 is a control center of the computer device, connecting various parts of the overall computer using various interfaces and lines, performing various functions and processing data by running or executing software programs and/or modules stored in the memory 703, and invoking data stored in the memory.
In one embodiment, the device includes one or more processors 703, and one or more memories 705, one or more application programs 701. Wherein the one or more application programs 701 are stored in the memory 705 and configured to be executed by the one or more processors 703, the one or more application programs 701 are configured to perform the pagefile rapid compilation method described in the above embodiments.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.
Those of ordinary skill in the art will appreciate that all or a portion of the steps implementing the above embodiments may be implemented by hardware, or may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and the storage medium may include a memory, a magnetic disk, an optical disk, or the like.
The foregoing is only a partial embodiment of the present invention, and it should be noted that it will be apparent to those skilled in the art that modifications and adaptations can be made without departing from the principles of the present invention, and such modifications and adaptations are intended to be comprehended within the scope of the present invention.
It should be understood that each functional unit in the embodiments of the present invention may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules.
The foregoing is only a partial embodiment of the present invention, and it should be noted that it will be apparent to those skilled in the art that modifications and adaptations can be made without departing from the principles of the present invention, and such modifications and adaptations are intended to be comprehended within the scope of the present invention.
Claims (6)
1. A method for quickly compiling a page file, comprising:
each module of the page file is displayed in a directory mode, and the receiving of triggering operation aiming at the page file and used for triggering the module to be compiled is confirmed;
acquiring associated storage path information of the module to be compiled; the associated storage path information is path information of codes to be compiled of the modules to be compiled;
writing the associated storage path information into a configuration file of a front-end resource module packer;
The front-end resource module packer acquires the code to be compiled according to the associated storage path information in the configuration file, and executes compiling on the code to be compiled;
the obtaining the associated storage path information of the module to be compiled, writing the associated storage path information into a configuration file of a front-end resource module packer, includes:
Acquiring the storage path information of the module to be compiled and the storage path information of the sub-module of the module to be compiled in a recursion traversal mode, and writing the storage path information of the module to be compiled and the storage path information of the sub-module of the module to be compiled into a configuration file of a front-end resource module packer;
The obtaining the associated storage path information of the module to be compiled, writing the associated storage path information into a configuration file of a front-end resource module packer, includes:
Acquiring storage path information of the module to be compiled and storage path information of a module on which the module to be compiled depends, and writing the storage path information of the module to be compiled and the storage path information of the module on which the module to be compiled depends into a configuration file of a front-end resource module packer;
After receiving the triggering operation for triggering the module to be compiled for the page file, the method further comprises the following steps: identifying a type of the triggering operation; the type of the triggering operation comprises a selection operation;
the obtaining the associated storage path information of the module to be compiled includes: and determining the type of the triggering operation as a selecting operation, and acquiring the associated storage path information of the module to be compiled.
2. The method of claim 1, wherein the front-end resource module packager obtains the code to be compiled from associated storage path information in the configuration file, further comprising:
the front-end resource module packer detects whether the associated storage path information is written in the configuration file;
if yes, the front-end resource module packer acquires the code to be compiled according to the associated storage path information in the configuration file;
if not, the front-end resource module packer returns the prompt information of the failure of acquiring the code to be compiled to the page, and guides the user to trigger the module to be compiled again.
3. The method of claim 1, wherein the type of trigger operation comprises a cancel operation;
after the associated storage path information is written into the configuration file of the front-end resource module packaging machine, before the front-end resource module packaging machine obtains the code to be compiled according to the associated storage path information in the configuration file, the method further comprises:
confirming that the cancel operation of the user to the compiling module in the page file is received;
Removing the associated storage path information from the configuration file of the front-end resource module baling press;
and the front-end resource module packer determines that the associated storage path information is not written in the configuration file and prompts the user to trigger the module to be compiled.
4. A device for rapid compiling of a pagefile, comprising:
The confirming module is used for displaying each module of the page file in a directory mode, confirming that the triggering operation aiming at the page file and used for triggering the module to be compiled is received;
The acquisition module is used for acquiring the associated storage path information of the module to be compiled; the associated storage path information is path information of codes to be compiled of the modules to be compiled;
the writing module is used for writing the associated storage path information into a configuration file of the front-end resource module packer;
The compiling module is used for acquiring the code to be compiled according to the associated storage path information in the configuration file by the front-end resource module packer and executing compiling on the code to be compiled;
the obtaining module obtains the associated storage path information of the module to be compiled, and writes the associated storage path information into a configuration file of a front-end resource module packer, including:
Acquiring the storage path information of the module to be compiled and the storage path information of the sub-module of the module to be compiled in a recursion traversal mode, and writing the storage path information of the module to be compiled and the storage path information of the sub-module of the module to be compiled into a configuration file of a front-end resource module packer;
The obtaining module obtains the associated storage path information of the module to be compiled, writes the associated storage path information into a configuration file of a front-end resource module packer, and includes:
Acquiring storage path information of the module to be compiled and storage path information of a module on which the module to be compiled depends, and writing the storage path information of the module to be compiled and the storage path information of the module on which the module to be compiled depends into a configuration file of a front-end resource module packer;
After receiving the triggering operation for triggering the module to be compiled for the page file, the method further comprises the following steps: identifying a type of the triggering operation; the type of the triggering operation comprises a selection operation;
the obtaining the associated storage path information of the module to be compiled includes: and determining the type of the triggering operation as a selecting operation, and acquiring the associated storage path information of the module to be compiled.
5. A storage device having a computer program stored thereon; the computer program being adapted to be loaded by a processor and to perform the pagefile rapid compiling method of any one of the preceding claims 1 to 3.
6. A computer-readable medium comprising a computer program product, characterized in that it comprises:
One or more processors;
a memory;
One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications configured to perform the pagefile rapid compilation method according to any of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810931286.3A CN109375921B (en) | 2018-08-15 | 2018-08-15 | Page file quick compiling method and device, storage device and computer device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810931286.3A CN109375921B (en) | 2018-08-15 | 2018-08-15 | Page file quick compiling method and device, storage device and computer device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109375921A CN109375921A (en) | 2019-02-22 |
| CN109375921B true CN109375921B (en) | 2024-09-13 |
Family
ID=65404550
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810931286.3A Active CN109375921B (en) | 2018-08-15 | 2018-08-15 | Page file quick compiling method and device, storage device and computer device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109375921B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110543310B (en) * | 2019-08-08 | 2023-05-05 | 山东中创软件商用中间件股份有限公司 | JSP compiling method, device, equipment and storage medium |
| CN111145764A (en) * | 2019-12-26 | 2020-05-12 | 苏州思必驰信息科技有限公司 | Source code compiling method, device, equipment and medium |
| CN111443906B (en) * | 2020-03-25 | 2023-09-05 | 北京奇艺世纪科技有限公司 | Application access method and device |
| CN113760314A (en) * | 2020-07-17 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Page module control method and device, electronic equipment and storage medium |
| CN112596738B (en) * | 2020-12-28 | 2023-07-11 | 北京字跳网络技术有限公司 | Method and device for determining front-end page to be tested, storage medium and electronic equipment |
| CN115407977A (en) * | 2021-05-28 | 2022-11-29 | 腾讯科技（深圳）有限公司 | Information compiling method, device, equipment and computer readable storage medium |
| CN114020275A (en) * | 2021-10-29 | 2022-02-08 | 深圳壹账通创配科技有限公司 | Code compiling control method, device, medium and equipment for application program |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107885521A (en) * | 2017-12-11 | 2018-04-06 | 凌云天博光电科技股份有限公司 | Software engineering project automatically generates/update method, apparatus and system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7367023B2 (en) * | 2003-07-10 | 2008-04-29 | International Business Machines Corporation | Method and apparatus for generating computer programming code selectively optimized for execution performance and not optimized for serviceability |
| CN101771762B (en) * | 2009-01-06 | 2012-03-21 | 北京邮电大学 | Method and system for dynamically loading services in service system |
| US9442707B2 (en) * | 2014-06-25 | 2016-09-13 | Microsoft Technology Licensing, Llc | Incremental whole program compilation of code |
| CN107153536B (en) * | 2017-03-31 | 2021-05-07 | 北京三快在线科技有限公司 | Application processing method and device |
| CN107577469B (en) * | 2017-08-21 | 2019-12-17 | 厦门悦讯信息科技股份有限公司 | software packaging and publishing management method |
-
2018
- 2018-08-15 CN CN201810931286.3A patent/CN109375921B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107885521A (en) * | 2017-12-11 | 2018-04-06 | 凌云天博光电科技股份有限公司 | Software engineering project automatically generates/update method, apparatus and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109375921A (en) | 2019-02-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109375921B (en) | Page file quick compiling method and device, storage device and computer device | |
| CN108595329B (en) | Application testing method and device and computer storage medium | |
| US8261244B2 (en) | Arbitrary runtime function call tracing | |
| JP5933762B2 (en) | Code coverage rate determination method and system | |
| US7321988B2 (en) | Identifying a code library from the subset of base pointers that caused a failure generating instruction to be executed | |
| JP2023027785A (en) | Device and computer program | |
| CN103064720A (en) | Profile guided jit code generation | |
| CN101482845B (en) | Method and system for calling instant debugger | |
| CN106202100B (en) | Page loading method and device | |
| CN104346148A (en) | Method, device and system for acquiring program performance consumption information | |
| US11842188B2 (en) | Continuous integration and deployment pipeline selection based on dynamic mapping | |
| CN110955598B (en) | Breakpoint processing method and device for kernel mode program | |
| CN111679976A (en) | Method and device for searching page object | |
| CN112306501B (en) | Business data acquisition method and device, storage medium and computing equipment | |
| CN110663082B (en) | Data processing system and method | |
| US9405664B2 (en) | Automating software testing | |
| CN109753437B (en) | Test program generation method and device, storage medium and electronic equipment | |
| JP6336919B2 (en) | Source code review method and system | |
| US10872027B2 (en) | Run-time or compile-time error solutions for locating missing program elements in a programming environment | |
| US9841982B2 (en) | Locating import class files at alternate locations than specified in classpath information | |
| CN110955632A (en) | File index generation method and device | |
| CN107533544B (en) | Element identifier generation | |
| CN111857797B (en) | Mirror image construction method, system and related device | |
| US20220229673A1 (en) | Lazy loading of code containers based on invoked actions in applications | |
| CN110334031B (en) | Memory allocation code detection method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |