Note: I haven’t written for a long time. Today I copied an article I wrote on the company’s intranet to show off my face. I just switched to web development, so I started learning javascript!
Before the introduction of namespaces, a headache for developers was how to prevent function names/class names from conflicting with others. Within a company, project teams could make reservations through naming (such as adding prefixes, etc.) To solve this problem, but looking at the entire software development field, in today's era when collaborative development is quite popular, this problem still exists. When using multiple third-party frameworks or libraries, the only thing you can do is to pray that their naming does not conflict. If such a disaster really occurs, the only thing you can do is to abandon one of them (Note: Maybe I am ignorant) ,hehe). The introduction of namespaces has solved this problem to a considerable extent. Of course, if the namespace you use is unfortunately the same as that of other companies, and the other company is Microsoft, SUN, etc., then congratulations, haha@_@!
It is inevitable to be exposed to JavaScript when engaging in web development. The latest version of JavaScript still does not support namespaces, so the problem of naming conflicts is undoubtedly prominent. Imagine that you referenced two js files, but found that you had to give up due to naming problems. One of them, which leads to writing a lot of extra code, is undoubtedly very frustrating. Before the new version of JavaScript introduces the concept of namespaces, it is the basic obligation of our programmers to carry forward the spirit of self-reliance and creativity;-)
Prerequisite for implementation: Unlike languages such as Delphi and C#, classes in JavaScript are not objects Definition, in fact there is no real class in JavaScript, the class here is actually implemented using function simulation, and the function in JavaScript is actually an object, so in JavaScript: a class is an object. This is very different from the traditional concept. In JavaScript, creating an instance of a class is actually making a copy of the class (= object, remember). Seeing this, you should be able to see some concept of design patterns. In JavaScript, the class mechanism uses the prototype pattern.
Implementation principle: Now that the essence of the class is clearly seen, the problem is simple. If all the JS classes and functions of the GEA project team are placed as attributes in an object named GEA, and then the GEA object is Our purpose can be achieved by placing it in an object named Grandsoft. For example, Grandsoft.GEA.Person is actually the class Person (still an object) in the attribute GEA of the Grandsoft object (also an object).
The implementation is very simple. The implementation of the entire namespace mechanism does not exceed 20 lines of code. The analysis is as follows:
// Declare a global object Namespace to register the namespace