search
HomeWeb Front-endJS TutorialJS front-end framework's failure experience sharing on refactoring_javascript skills

Okay, let’s get started
Refactoring is actually not a big move. The main function to be achieved is to re-divide the existing JS code and decouple the existing modules. Then I plan to divide the existing program into modules and repackage it into a namespace to implement use or something similar to Java's Package. Then I only need to load a use js file and call the use function of this file. By setting certain parameters, I can dynamically load the required modules. This was the most perfect idea (I was stupid and naive at the time). OK, the nightmare begins.
Premise, I underestimated myself 3 months ago. //Okay, uncivilized terms may appear below~~

First of all, on the first day of the plan, my intention is to separate the most decoupled part of this program, the self-made control part. Speaking of which, people have also tried to write some form controls such as Panel.js, Button.js and other controls. There are a lot of js files in them. Although I have divided the folders, but when I see the index page That series of <script> tags is so annoying. So the nightmare entered the second stage, I wanted to load a JS file, and this JS file can dynamically load all control JS. If you want to know more about "Dynamic Loading JS", please go to Du Niang G Niang and ask for clarification. I think you should be able to find a lot of 3 asynchronous 1 Ajax implementations. Okay, this is all nonsense. I referred to the book "High Performance JavaScript" and generated the following code: <BR><div class="codetitle"><span><a style="CURSOR: pointer" data="2608" class="copybut" id="copybut2608" onclick="doCopy('code2608')"><U>Copy the code The code is as follows :<div class="codebody" id="code2608"> <BR>function loadScript (url, callback){ <BR>var script = document.createElement("script"); <BR>script.type = "text/javascript"; <BR>if (script.readyState){ //IE <BR>script.onreadystatechange = function(){ <BR>if(script.readyState == "loaded" || script.readState == "complete"){ <BR>script. onreadystatechange = null; <BR>callback(); <BR>} <BR>} <BR>}else{ <BR>script.onload = function(){ <BR>callback(); <BR>} <BR> } <BR>script.src = url; <BR>document.getElementsByTagName("head")[0].appendChild(script); <BR>} <BR> <BR>Good tragedy begins slowly, First of all, my controls are all based on JQuery, so I must loadScript(jqueryURL, function(){//Load my controls s}). OK, I will interrupt here and continue below. <BR>Then I suddenly wanted to implement the namespace function. I did a lot of research on object-oriented, prototype chains and other miscellaneous things. Then I found that this function of managing references is very abstract, so I gave it to the book "Javascript Design Patterns". "The book is so deceptive. In the end, after understanding the prototype mode, it was still a mystery. Okay, I think I need to rethink this issue. I actually just want to create a control. Then I just need to bind my control to a global object as a property of an object. So I used my English name Gssl as an object and got the following structure: <BR><div class="codetitle"><span><a style="CURSOR: pointer" data="94322" class="copybut" id="copybut94322" onclick="doCopy('code94322')"><U>Copy code The code is as follows: <div class="codebody" id="code94322"> <BR>var Gssl = {} <BR> <BR>Okay, back to where I interrupted above, my idea is to construct my global object and bind it to the space when dynamically loading JS Named Gssl, the specific implementation is as follows: <BR><div class="codetitle"><span><a style="CURSOR: pointer" data="72296" class="copybut" id="copybut72296" onclick="doCopy('code72296')"><U>Copy code The code is as follows: <div class="codebody" id="code72296"> <BR>loadScript(jqueryURL , function(){ <BR>//Load my controls <BR>loadScript(controlURL, function(){ <BR>//Bind control <BR>Gssl.control = control; <BR>}); <BR>}); <BR><BR>As I write this, the test has been adjusted. I was a little happy last night, but I know from the programmer’s intuition that the nightmare is not over yet. <BR>I went back this morning and referenced this dynamically loaded JS JS file to my page. As a result, due to the asynchronous nature, the following code started executing before the Gssl object was generated (I go, this is unreasonable) ). Then I thought about it and wanted to make a ready flag on the last loaded control to mark whether Gssl has been loaded. But you find that each component has its own callback function, and you don't know which one is loaded last. Although the code execution is in order, the parallelism of this transmission makes you not sure which one is last. one. Okay, I was completely crushed, so I thought of a very 2B method. I simply wrote a function to jam the program for 2 seconds. Two seconds will definitely be enough~. Then he discovered that setTimeout TM cannot block codes, and his good friend setIXXXXX cannot block codes either. Okay, I got angry and wrote an infinite loop to determine the ready bit. OK, the browser quits. <br><br>Back to the starting point, I began to consider trying recursive loading, that is, loading the next control only during the Callback, so that I can know when the control has been loaded. But when I think about it carefully, I guess, if I want to load it like this, then I have to dynamically load it. Doesn’t this not improve the efficiency at all? Then I looked at the implementation of the ready method of various frameworks. Well, the one with single file is IMBA. Then there is only one way in front of me, which is to write all controls on a JS. This is simply avoiding the important and choosing the light. <br><br>Then I spent a nightmare day proposing solutions and then complaining about myself. It's almost time to get off work, and I'm still thinking about whether there is a solution to this problem. Then the third voice in my head started, Zhiwei~ (haha, this is my name~), is it really necessary? Okay, I have to admit that every time I escape from nightmares, I have to rely on him. Then I opened the folder of the entire project at each location and then returned it, and then I thought, okay, this is not writing a novel, so I won’t describe these little actions when thinking (I will tell you that when I think about a problem, it will be like Are mentally ill people just as stupid?) In the end, I found that even if I separated all these modules, I would still have to make certain modifications to other projects. Although there are interfaces, the interfaces are connected to the backend, and the interfaces between my modules have not been done yet. This kind of separation will be accompanied by a lot of additional payments (estimated, but based on experience these are inevitable~), and the new JS framework is not compatible with the overall framework (when I was off work, I found that some resources were not accessible. problem), although I didn’t give up, I still gave up (the progress of all evil, Ciao). This version of the code has not been saved, and SVN has not been updated~. There was no backup on my USB hard drive, but all the source codes were deleted in anger. I only keep this diary as a souvenir. <br><br>The lesson is that if I had a front-end modular idea from the beginning, I would not be where I am today. I can definitely do it with my ability, but now it’s hard to come back~ It’s still those evil milk powder advertisements, let the baby have a good start, then my goal is to give the code a good start~ Forgive me for being a failed daddy ~~ (T_T)<br><br>Also, I know that the Blog Forum is a magical place. If anyone has encountered the same problem and solved it, can you share it? There will always be a reply!</script>

Statement
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
From Websites to Apps: The Diverse Applications of JavaScriptFrom Websites to Apps: The Diverse Applications of JavaScriptApr 22, 2025 am 12:02 AM

JavaScript is widely used in websites, mobile applications, desktop applications and server-side programming. 1) In website development, JavaScript operates DOM together with HTML and CSS to achieve dynamic effects and supports frameworks such as jQuery and React. 2) Through ReactNative and Ionic, JavaScript is used to develop cross-platform mobile applications. 3) The Electron framework enables JavaScript to build desktop applications. 4) Node.js allows JavaScript to run on the server side and supports high concurrent requests.

Python vs. JavaScript: Use Cases and Applications ComparedPython vs. JavaScript: Use Cases and Applications ComparedApr 21, 2025 am 12:01 AM

Python is more suitable for data science and automation, while JavaScript is more suitable for front-end and full-stack development. 1. Python performs well in data science and machine learning, using libraries such as NumPy and Pandas for data processing and modeling. 2. Python is concise and efficient in automation and scripting. 3. JavaScript is indispensable in front-end development and is used to build dynamic web pages and single-page applications. 4. JavaScript plays a role in back-end development through Node.js and supports full-stack development.

The Role of C/C   in JavaScript Interpreters and CompilersThe Role of C/C in JavaScript Interpreters and CompilersApr 20, 2025 am 12:01 AM

C and C play a vital role in the JavaScript engine, mainly used to implement interpreters and JIT compilers. 1) C is used to parse JavaScript source code and generate an abstract syntax tree. 2) C is responsible for generating and executing bytecode. 3) C implements the JIT compiler, optimizes and compiles hot-spot code at runtime, and significantly improves the execution efficiency of JavaScript.

JavaScript in Action: Real-World Examples and ProjectsJavaScript in Action: Real-World Examples and ProjectsApr 19, 2025 am 12:13 AM

JavaScript's application in the real world includes front-end and back-end development. 1) Display front-end applications by building a TODO list application, involving DOM operations and event processing. 2) Build RESTfulAPI through Node.js and Express to demonstrate back-end applications.

JavaScript and the Web: Core Functionality and Use CasesJavaScript and the Web: Core Functionality and Use CasesApr 18, 2025 am 12:19 AM

The main uses of JavaScript in web development include client interaction, form verification and asynchronous communication. 1) Dynamic content update and user interaction through DOM operations; 2) Client verification is carried out before the user submits data to improve the user experience; 3) Refreshless communication with the server is achieved through AJAX technology.

Understanding the JavaScript Engine: Implementation DetailsUnderstanding the JavaScript Engine: Implementation DetailsApr 17, 2025 am 12:05 AM

Understanding how JavaScript engine works internally is important to developers because it helps write more efficient code and understand performance bottlenecks and optimization strategies. 1) The engine's workflow includes three stages: parsing, compiling and execution; 2) During the execution process, the engine will perform dynamic optimization, such as inline cache and hidden classes; 3) Best practices include avoiding global variables, optimizing loops, using const and lets, and avoiding excessive use of closures.

Python vs. JavaScript: The Learning Curve and Ease of UsePython vs. JavaScript: The Learning Curve and Ease of UseApr 16, 2025 am 12:12 AM

Python is more suitable for beginners, with a smooth learning curve and concise syntax; JavaScript is suitable for front-end development, with a steep learning curve and flexible syntax. 1. Python syntax is intuitive and suitable for data science and back-end development. 2. JavaScript is flexible and widely used in front-end and server-side programming.

Python vs. JavaScript: Community, Libraries, and ResourcesPython vs. JavaScript: Community, Libraries, and ResourcesApr 15, 2025 am 12:16 AM

Python and JavaScript have their own advantages and disadvantages in terms of community, libraries and resources. 1) The Python community is friendly and suitable for beginners, but the front-end development resources are not as rich as JavaScript. 2) Python is powerful in data science and machine learning libraries, while JavaScript is better in front-end development libraries and frameworks. 3) Both have rich learning resources, but Python is suitable for starting with official documents, while JavaScript is better with MDNWebDocs. The choice should be based on project needs and personal interests.

See all articles

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

SecLists

SecLists

SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

WebStorm Mac version

WebStorm Mac version

Useful JavaScript development tools

Atom editor mac version download

Atom editor mac version download

The most popular open source editor

EditPlus Chinese cracked version

EditPlus Chinese cracked version

Small size, syntax highlighting, does not support code prompt function

DVWA

DVWA

Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software