CN112860231A - Front-end framework conversion method and device - Google Patents
Front-end framework conversion method and device Download PDFInfo
- Publication number
- CN112860231A CN112860231A CN202110264786.8A CN202110264786A CN112860231A CN 112860231 A CN112860231 A CN 112860231A CN 202110264786 A CN202110264786 A CN 202110264786A CN 112860231 A CN112860231 A CN 112860231A
- Authority
- CN
- China
- Prior art keywords
- project
- end frame
- function
- layer
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000006243 chemical reaction Methods 0.000 title claims abstract description 22
- 230000006870 function Effects 0.000 claims abstract description 67
- 230000007704 transition Effects 0.000 claims abstract description 9
- 230000007246 mechanism Effects 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 13
- 230000018109 developmental process Effects 0.000 description 13
- 238000011161 development Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 7
- 230000008859 change Effects 0.000 description 6
- 238000004519 manufacturing process Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 239000000243 solution Substances 0.000 description 3
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 238000002347 injection Methods 0.000 description 1
- 239000007924 injection Substances 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 230000009191 jumping Effects 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
- 238000012827 research and development Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a front-end frame conversion method and a front-end frame conversion device, wherein the method comprises the following steps: building a blank project by utilizing a first front-end frame corresponding to a first system; storing a js file of a second front-end frame corresponding to a second system under a public directory of a root directory of the project, wherein the public directory is at the same level as a node _ modules folder; after a first system sends a call request to a second system, loading the second system in the project of the first system according to the js file; rewriting the loaded function codes of the second system layer by layer in the project of the first system until the functions of the second system are all realized in the project of the first system; and removing the corresponding second front end frame of the second system. The invention can convert the front-end framework and realize the smooth transition of system upgrading.
Description
Technical Field
The invention relates to the technical field of research and development frameworks, in particular to a front-end framework conversion method and device.
Background
The front-end development of a software system can select one or more universal frames to help development, the frames are continuously updated with time, some frames are always alive, others are gradually not fallen, new frames continuously emerge, and the superior wins. For some old projects which start earlier, the front-end framework selected previously may have fallen and no longer updated, and the outdated system cannot meet the current business or performance requirements, and it is urgent to switch to an excellent new front-end framework. However, different frames often have gullies, which are not compatible with each other and are difficult to be switched smoothly.
Old systems are usually abandoned directly in the prior art, and new systems are developed from the beginning. In the process, although the new system can accept the new requirements or the requirement changes of the original system, the original functions are not completely realized, the new framework cannot be put into use, the new requirements or the requirement changes cannot be converted into usable system functions, and the business goal is realized. On the other hand, the old system will reject the new requirement or the requirement change as much as possible because of being abandoned, otherwise, the code writing work caused by the new requirement will be performed on the old system once and on the new system once again, the labor is repeated, and the efficiency is reduced. Any change in demand is unacceptable throughout the process of rewriting the system.
Therefore, there is a need for a front-end framework conversion scheme that can overcome the above-mentioned problems.
Disclosure of Invention
The embodiment of the invention provides a front-end frame conversion method, which is used for converting a front-end frame and realizing smooth transition of system upgrading and comprises the following steps:
building a blank project by utilizing a first front-end frame corresponding to a first system;
storing a js file of a second front-end frame corresponding to a second system in a public directory of the root directory of the item, wherein the public directory is at the same level as a node _ modules folder;
after the first system sends a call request to the second system, loading the second system in the project of the first system according to the js file;
rewriting the loaded function codes of the second system layer by layer in the project of the first system until the functions of the second system are all realized in the project of the first system;
and removing the corresponding second front end frame of the second system.
The embodiment of the invention provides a front-end frame conversion device, which is used for converting a front-end frame and realizing smooth transition of system upgrading, and comprises the following components:
the project building module is used for building blank projects by utilizing a first front-end framework corresponding to the first system;
the file storage module is used for storing js files of a second front-end frame corresponding to a second system under a public directory of the root directory of the item, wherein the public directory is at the same level as the node _ modules folder;
the system loading module is used for loading the second system in the project of the first system according to the js file after the first system sends a call request to the second system;
the function rewriting module is used for rewriting the loaded function codes of the second system layer by layer in the project of the first system until the functions of the second system are all realized in the project of the first system;
and the frame removing module is used for removing the second front end frame corresponding to the second system.
The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the front-end framework conversion method when executing the computer program.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program for executing the foregoing front-end framework conversion method is stored in the computer-readable storage medium.
The embodiment of the invention builds a blank project by utilizing a first front-end frame corresponding to a first system; storing a js file of a second front-end frame corresponding to a second system in a public directory of the root directory of the item, wherein the public directory is at the same level as a node _ modules folder; after the first system sends a call request to the second system, loading the second system in the project of the first system according to the js file; rewriting the loaded function codes of the second system layer by layer in the project of the first system until the functions of the second system are all realized in the project of the first system; and removing the corresponding second front end frame of the second system. According to the embodiment of the invention, the js file of the second front-end frame corresponding to the second system is stored in the root directory public directory of the project, the second system is loaded in the project of the first system according to the js file after the first system sends the calling request to the second system, coexistence of the two frames is realized in one system, once a new requirement or a requirement change enters along with updating, the requirement is realized by the new frame, and once the requirement is realized, a production process can be immediately entered. Therefore, in the whole upgrading process, new requirement input can be received at any time and converted into user value, the front-end framework is effectively converted, and smooth transition of system upgrading is realized.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts. In the drawings:
FIG. 1 is a schematic diagram of a front-end framework conversion method according to an embodiment of the present invention;
fig. 2 is a structural diagram of a front end frame conversion device in an embodiment of the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention.
First, terms referred to in the embodiments of the present application are described:
front end: an interface facing users in the use of software, such as a web page browsed on the internet at ordinary times, is a front end.
Front-end development: the software developer completes the front-end functions of a set of system by writing codes.
A frame: the software development uses an existing set of codes which define the infrastructure of the project, and all development work is carried out within the framework. Meanwhile, the framework also provides a series of convenient measures, and repeated labor in development work is reduced. A set of frames cannot be used directly by a system user itself. A set of frames will typically be used for a number of different systems, providing a consistent infrastructure for them.
A front end frame: the framework for assisting the front-end development is composed of codes, defines development specifications of a component mechanism, a template mechanism, a communication mechanism, a routing mechanism, a form mechanism, dependency injection and the like during development, and provides corresponding bottom codes for calling project codes.
The system comprises the following steps: the system comprises a set of code set consisting of a framework and function codes written based on the framework. The system is released to the production environment as an application that the user can use.
Routing: the url address used when accessing the front end can be understood as a character string in the address bar of the browser. In system development, it also refers to a set of mechanisms for implementing the above-mentioned routing concept.
The method comprises the following steps: a description of the functionality that the software system needs to implement. It is generally proposed by the business side, i.e. the system delivery object.
And (3) requirement change: for the original requirement, some changes are proposed.
In order to convert a front-end framework and implement smooth transition of system upgrade, an embodiment of the present invention provides a front-end framework conversion method, which, as shown in fig. 1, may include:
103, after the first system sends a call request to the second system, loading the second system in the project of the first system according to the js file;
and 105, removing the second front end frame corresponding to the second system.
As shown in fig. 1, in the embodiment of the present invention, a blank project is created by using a first front-end framework corresponding to a first system; storing a js file of a second front-end frame corresponding to a second system in a public directory of the root directory of the item, wherein the public directory is at the same level as a node _ modules folder; after the first system sends a call request to the second system, loading the second system in the project of the first system according to the js file; rewriting the loaded function codes of the second system layer by layer in the project of the first system until the functions of the second system are all realized in the project of the first system; and removing the corresponding second front end frame of the second system. According to the embodiment of the invention, the js file of the second front-end frame corresponding to the second system is stored in the root directory public directory of the project, the second system is loaded in the project of the first system according to the js file after the first system sends the calling request to the second system, coexistence of the two frames is realized in one system, once a new requirement or a requirement change enters along with updating, the requirement is realized by the new frame, and once the requirement is realized, a production process can be immediately entered. Therefore, in the whole upgrading process, new requirement input can be received at any time and converted into user value, the front-end framework is effectively converted, and smooth transition of system upgrading is realized.
In the embodiment, a blank item is built by utilizing a first front-end framework corresponding to a first system; and storing a js file of a second front-end frame corresponding to a second system in a public directory of the root directory of the item, wherein the public directory is at the same level as the node _ modules folder.
In practice, a modern front-end project generally has a node _ modules folder under the project root directory, where the files required by the framework are stored. The functions therein are accessible through canonical calls to these modules. However, the old front-end framework is only a few common js files, and the developer can freely specify the placement position. However, since these common js files do not meet the specifications of modern modular development, they cannot be accessed in the code of the software front-end developer if they are placed in the node _ modules folder; if the code file is put together with the code file developed by the developer, the code file cannot be accessed because the routing cannot be configured for the code file, and the code file originally does not meet the module development requirements of the new framework. Therefore, in the embodiment of the invention, the js file is placed in the public directory at the same level as the node _ modules folder, so that the js file can be accessed as a public resource by the development code.
In this embodiment, rewriting the loaded function code of the second system in the project of the first system layer by layer includes:
if the function code of the second system is a function code of a common function or a common mechanism of the transecting items, the common function or the common mechanism is realized again when the common function or the common mechanism is involved for the first time in the first system.
In this embodiment, rewriting the loaded function code of the second system in the project of the first system layer by layer includes:
and if the turning point needing to jump from the second system to the first system exists, the browser is required to be switched to a routing address corresponding to the corresponding function of the first system.
In this embodiment, the first front end frame is vue front end frame, and the second front end frame is kissy front end frame.
In the embodiment, after a first system sends a call request to a second system, the second system is loaded in a project of the first system according to the js file; rewriting the loaded function codes of the second system layer by layer in the project of the first system until the functions of the second system are all realized in the project of the first system; and removing the corresponding second front end frame of the second system.
In particular, a loading component for an old system is defined in a new system (a first system), and the component has only one role: the old system (second system) is loaded. Meanwhile, an entry file for accepting a new system call is defined in an old system, and the component has only one role: and receiving and calling, and loading the corresponding old module according to the received parameters. And (3) rewriting the functions of the original system layer by layer inwards in the project, and removing the codes replacing the original system after finishing a replaceable function: in the specific implementation of this step, differentiation is encountered, that is, a certain module (parent module) of the old system calls another plurality of modules (child modules), when the parent module is replaced, the number of new and old butted entries becomes multiple, and when the new parent module calls different old child modules, the new parent module needs to butt joint the loading child modules through the two interface files mentioned in the above paragraph, and the design needs to be made here to avoid conflict. For the turning point needing to jump from the old system to the new system, the browser is directly required to be switched to the routing address corresponding to the corresponding function of the new system: this step is relatively easy to implement functionally, and it is critical that this method be taken, otherwise the calling of the new system by the old system would be particularly difficult.
The key point of the invention is that the coexistence of two sets of front-end frames has the basis of coexistence, and the old frame can be replaced by the new frame gradually. And only one starting entry of a set of system is needed, and when the upgrade is started, the starting entry is necessarily based on the old framework. The method comprises the steps of firstly replacing an entrance with a new frame, which actually requires that the frame at the outermost layer of the whole system is the new frame, extending the new frame to the starting entrance point of the system, calling the starting entrance of the old frame from the point, and restarting the user-facing interface system inside the old frame. And gradually advancing inwards from the intersection points of the new and old frameworks, and replacing and rewriting the front-end code of the original system based on the old frameworks in a layered and batch mode. The new system contains the old system for the first period of time, but when this transition has progressed to a certain stage, there may be circumstances in which it is necessary to invoke the new system module in the old system. At this time, an environment of a new system cannot be built in an old system, two sets of identical and nested complete frames cannot exist in the system, and the problem is solved by a method of directly jumping out of the old system and directly switching into the new system through a route. When the process advances to a system where no development code based on the old system is available, the old framework is completely removed, and the updating of the front-end framework is completed.
Based on the same inventive concept, the embodiment of the present invention further provides a front end frame conversion apparatus, as described in the following embodiments. Since the principles of solving these problems are similar to the front-end framework conversion method, the implementation of the apparatus can be referred to the implementation of the method, and the repeated details are not repeated.
Fig. 2 is a structural view of a front end frame switching apparatus according to an embodiment of the present invention, and as shown in fig. 2, the apparatus includes:
the project building module 201 is used for building a blank project by using a first front-end framework corresponding to a first system;
a file storing module 202, configured to store a js file of a second front-end frame corresponding to a second system in a public directory of a root directory of the item, where the public directory is at the same level as the node _ modules folder;
the system loading module 203 is configured to load the second system in the project of the first system according to the js file after the first system sends a call request to the second system;
the function rewriting module 204 is configured to rewrite, layer by layer, the loaded function codes of the second system in the project of the first system until all functions of the second system are implemented in the project of the first system;
and a frame removing module 205, configured to remove a second front end frame corresponding to the second system.
In one embodiment, the function rewriting module 204 is further configured to:
if the function code of the second system is a function code of a common function or a common mechanism of the transecting items, the common function or the common mechanism is realized again when the common function or the common mechanism is involved for the first time in the first system.
In one embodiment, the function rewriting module 204 is further configured to:
and if the turning point needing to jump from the second system to the first system exists, the browser is required to be switched to a routing address corresponding to the corresponding function of the first system.
In one embodiment, the first front end frame is an vue front end frame and the second front end frame is a kissy front end frame.
In summary, in the embodiment of the present invention, a blank item is built by using the first front-end framework corresponding to the first system; storing a js file of a second front-end frame corresponding to a second system in a public directory of the root directory of the item, wherein the public directory is at the same level as a node _ modules folder; after the first system sends a call request to the second system, loading the second system in the project of the first system according to the js file; rewriting the loaded function codes of the second system layer by layer in the project of the first system until the functions of the second system are all realized in the project of the first system; and removing the corresponding second front end frame of the second system. According to the embodiment of the invention, the js file of the second front-end frame corresponding to the second system is stored in the root directory public directory of the project, the second system is loaded in the project of the first system according to the js file after the first system sends the calling request to the second system, coexistence of the two frames is realized in one system, once a new requirement or a requirement change enters along with updating, the requirement is realized by the new frame, and once the requirement is realized, a production process can be immediately entered. Therefore, in the whole upgrading process, new requirement input can be received at any time and converted into user value, the front-end framework is effectively converted, and smooth transition of system upgrading is realized.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. A front-end framework conversion method, comprising:
building a blank project by utilizing a first front-end frame corresponding to a first system;
storing a js file of a second front-end frame corresponding to a second system in a public directory of the root directory of the item, wherein the public directory is at the same level as a node _ modules folder;
after the first system sends a call request to the second system, loading the second system in the project of the first system according to the js file;
rewriting the loaded function codes of the second system layer by layer in the project of the first system until the functions of the second system are all realized in the project of the first system;
and removing the corresponding second front end frame of the second system.
2. The front-end framework conversion method of claim 1, wherein rewriting loaded function code of the second system in a project of the first system layer by layer comprises:
if the function code of the second system is a function code of a common function or a common mechanism of the transecting items, the common function or the common mechanism is realized again when the common function or the common mechanism is involved for the first time in the first system.
3. The front-end framework conversion method of claim 1, wherein rewriting loaded function code of the second system in a project of the first system layer by layer comprises:
and if the turning point needing to jump from the second system to the first system exists, the browser is required to be switched to a routing address corresponding to the corresponding function of the first system.
4. The front-end framework conversion method of claim 1, wherein said first front-end framework is an vue front-end framework and said second front-end framework is a kissy front-end framework.
5. A front end frame transition apparatus, comprising:
the project building module is used for building blank projects by utilizing a first front-end framework corresponding to the first system;
the file storage module is used for storing js files of a second front-end frame corresponding to a second system under a public directory of the root directory of the item, wherein the public directory is at the same level as the node _ modules folder;
the system loading module is used for loading the second system in the project of the first system according to the js file after the first system sends a call request to the second system;
the function rewriting module is used for rewriting the loaded function codes of the second system layer by layer in the project of the first system until the functions of the second system are all realized in the project of the first system;
and the frame removing module is used for removing the second front end frame corresponding to the second system.
6. The front-end frame conversion apparatus of claim 5, wherein the functionality rewrite module is further to:
if the function code of the second system is a function code of a common function or a common mechanism of the transecting items, the common function or the common mechanism is realized again when the common function or the common mechanism is involved for the first time in the first system.
7. The front-end frame conversion apparatus of claim 5, wherein the functionality rewrite module is further to:
and if the turning point needing to jump from the second system to the first system exists, the browser is required to be switched to a routing address corresponding to the corresponding function of the first system.
8. The front end frame conversion device of claim 5, wherein said first front end frame is an vue front end frame and said second front end frame is a kissy front end frame.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 4 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing the method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110264786.8A CN112860231A (en) | 2021-03-11 | 2021-03-11 | Front-end framework conversion method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110264786.8A CN112860231A (en) | 2021-03-11 | 2021-03-11 | Front-end framework conversion method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112860231A true CN112860231A (en) | 2021-05-28 |
Family
ID=75994044
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110264786.8A Pending CN112860231A (en) | 2021-03-11 | 2021-03-11 | Front-end framework conversion method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112860231A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113448559A (en) * | 2021-07-13 | 2021-09-28 | 壹药网科技(上海)股份有限公司 | Development system and method of global wide area network front end aiming at multiple development projects |
| CN113741947A (en) * | 2021-08-27 | 2021-12-03 | 厦门华厦学院 | Method and system for solving island problem |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108491206A (en) * | 2018-04-12 | 2018-09-04 | 江南大学 | A kind of SPA single-pages realization method and system |
| CN110489119A (en) * | 2019-06-26 | 2019-11-22 | 中电万维信息技术有限责任公司 | The method, apparatus and storage medium of query result are shown based on chart database |
| CN111651703A (en) * | 2020-04-14 | 2020-09-11 | 北京奇艺世纪科技有限公司 | Page jump method and device, electronic equipment and readable storage medium |
| CN112306533A (en) * | 2020-11-27 | 2021-02-02 | 平安普惠企业管理有限公司 | Front-end framework automatic conversion method and device, computer equipment and storage medium |
| CN112306474A (en) * | 2020-10-28 | 2021-02-02 | 科大国创云网科技有限公司 | VUE project smooth upgrading method based on modular template |
-
2021
- 2021-03-11 CN CN202110264786.8A patent/CN112860231A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108491206A (en) * | 2018-04-12 | 2018-09-04 | 江南大学 | A kind of SPA single-pages realization method and system |
| CN110489119A (en) * | 2019-06-26 | 2019-11-22 | 中电万维信息技术有限责任公司 | The method, apparatus and storage medium of query result are shown based on chart database |
| CN111651703A (en) * | 2020-04-14 | 2020-09-11 | 北京奇艺世纪科技有限公司 | Page jump method and device, electronic equipment and readable storage medium |
| CN112306474A (en) * | 2020-10-28 | 2021-02-02 | 科大国创云网科技有限公司 | VUE project smooth upgrading method based on modular template |
| CN112306533A (en) * | 2020-11-27 | 2021-02-02 | 平安普惠企业管理有限公司 | Front-end framework automatic conversion method and device, computer equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| FANNIEGIRL: "vue引用外部JS的两种方案", pages 1 - 2, Retrieved from the Internet <URL:https://www.cnblogs.com/ifannie/p/12222192.html> * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113448559A (en) * | 2021-07-13 | 2021-09-28 | 壹药网科技(上海)股份有限公司 | Development system and method of global wide area network front end aiming at multiple development projects |
| CN113741947A (en) * | 2021-08-27 | 2021-12-03 | 厦门华厦学院 | Method and system for solving island problem |
| CN113741947B (en) * | 2021-08-27 | 2023-11-14 | 厦门华厦学院 | Method and system for solving island problem |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109684057B (en) | Task processing method and device and storage medium | |
| CN104182255A (en) | Method and terminal for upgrading library files of system application | |
| CN106547527B (en) | JavaScript file construction method and device | |
| CN112860231A (en) | Front-end framework conversion method and device | |
| CN102508669A (en) | Automatic program code generating method | |
| CN104468226A (en) | Nginx configuration method and device | |
| CN108694564A (en) | A kind of task status control method and device | |
| US9772865B2 (en) | On-demand loading of dynamic scripting language code for reduced memory usage | |
| CN103995696B (en) | The program bag custom-built system and method for customizing of mobile terminal | |
| CN109558159A (en) | The update method and device of user interface in game | |
| US20150242205A1 (en) | Non-Transitory Computer-Readable Recording Medium Storing Application Development Support Program and Application Development Support System That Automatically Support Platform Version | |
| CN116954685B (en) | Gray scale rolling upgrading method, system, equipment and medium for low-code application system | |
| CN114416311A (en) | Method and device for managing message queue based on Go language | |
| CN103714814A (en) | Voice introducing method of voice recognition engine | |
| CN111580938A (en) | Transaction processing method, device, equipment and medium for work unit | |
| CN115953017A (en) | Flow changing method and device, electronic equipment and computer readable storage medium | |
| CN108241671B (en) | Service processing method and system and storage medium | |
| CN109241071A (en) | A kind of Android database upgrade method, apparatus and terminal | |
| CN109857380B (en) | Workflow file compiling method and device | |
| CN111061568A (en) | Method and device for deleting load balancer | |
| CN107479864B (en) | Platform transplanting method and device for MapReduce computing framework | |
| JP5317182B2 (en) | POS terminal, module update method and module update program | |
| JP2016071725A (en) | Workflow control program, workflow control method and information processing unit | |
| CN113703778B (en) | Engineering file conflict processing method and device based on mobile communication equipment | |
| CN104408619A (en) | Method and device for configuring IC (integrated circuit) card payment terminal transaction flow, method and device for implementing IC card payment terminal transaction flow and business system |
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 |