Introduction to the JavaScript debugger _ javascript skills

There are actually many JavaScript debuggers. Of course, these are just debuggers, and there is no way to compare them with the popular JavaIDE. However, from the perspective of debugging, the functions of these debuggers are sufficient. In fact, what I need is not a JavaScript IDE, but a JavaScript refactoring tool. This allows me to quickly refactor JavaScript components, it is much more efficient and safer than the original method that uses UltraEdit for search/replacement. In fact, the development efficiency of any language without reconstruction tools is not comparable to that of Java (such as Eclipse, IDEA, and other powerful reconstruction tools. Communism has not yet been realized. This is indeed a reality, but it does not mean that we have to wait, and there is no way to do our work well under the existing conditions. The main reason JavaScript must be used is not because it is the most advanced language (compared with Python, Ruby, etc. however, from the language itself, I do not think that the function/Object Integration Language of JavaScript is backward, and Python is also such a language), there is a powerful development tool, but because it has Most widely supported(All modern browsers support) and Cheap(Because it is a Web standard, there will be a lot of people, and the cost of learning and using is very low ). In fact, for HTML-based Web development, it is almost impossible to avoid using cirpt. From the perspective of improving the user interaction experience, rather than thinking about the problem from the perspective of pure technology, we do not have to deliberately avoid JavaScript.

The most primitive JavaScript debugger is the script debugger that comes with Windows. In Windows 2000, open the Add/delete program-> Add/delete Windows components, and then you can see a "script Debugger ". This script debugger can be used to debug JavaScript and debug any ActiveX-based scripting languages (VBScript, ASP, etc .). Although this tool has most common debugging functions, it is very inconvenient to use.
Advanced Visual InterDev, on the Visual Studio 6.0 installation CD. This is a common JavaScript debugging tool.
It is better to use the script Debugger in Office 2003. Enhanced and stable than Visual InterDev. This script debugger is very hidden and needs to be carefully located in the installation directory.

The above is the JS debugging tool of the M $ series. Visual Studio and Office 2003 both cost money. If you don't want to spend any money, Mozilla Venkman is another good choice. Venkman is a JavaScript debugger developed by Mozilla and has complete functions. If you have installed the Mozilla Suite, which includes Venkman, you only need to select it during installation. If the package is a Chinese version, the installed Venkman interface is also in Chinese.
Users who use Firefox need to install the following:
Http://www.hacksrus.com /~ Ginda/venkman/
Select the latest version for installation. For example, click
Http://www.hacksrus.com /~ Ginda/venkman/venkman-0.9.85.xpi
You can complete the installation. Of course, you can download the file and use Firefox to directly open the file for installation.

After the tool is installed, a "Export cirpt Debugger" will appear in the tool menu of Firefox. Click it to open the Venkman Debugger.
Resources related to the Venkman debugger include:
Venkman, the new JavaScript Debugger for Netscape 7.x:
Http://devedge-temp.mozilla.org/viewsource/2002/venkman/01/index_en.html
Venkman FAQ:
Http://www.hacksrus.com /~ Ginda/venkman/faq/venkman-faq.html
You can directly search For Venkman and find many related resources.

Firefox + Venkman is a good combination for developing Ajax applications.