Introduction to JavaScript Debugger _javascript tips

But only from the point of view of debugging, the functions of these debuggers are fully adequate. What I really need is not a JavaScript IDE, but a JavaScript refactoring tool that allows me to quickly refactor JavaScript components, which is much more efficient and more secure than the original method of finding/replacing using UltraEdit. In fact, any language without refactoring tool development efficiency is no way and Java such language (with Eclipse, idea, etc. powerful refactoring tools) compared to. It is true that Communism has not yet come true, but it does not mean that we must wait and there is no way to do our job in the present conditions. The main reason why you must use JavaScript is not because it is the most advanced language (as opposed to Python, Ruby, etc). But from the language itself, I don't think JavaScript is the language of the function/object oneness that is backward, Python It is the same language), has a powerful development tool, but because it has Broadest range of support(All modern browsers are supported) and cheap(because it is a WEB standard, there are a lot of people, the cost of learning and using is very low). In fact, HTML based WEB development, to avoid javascirpt is almost impossible. From the perspective of improving the user interaction experience, rather than thinking from a purely technical perspective, there is no need to deliberately avoid JavaScript.

The original JavaScript debugger is a script debugger with Windows. In Windows 2000, open Add/Remove Programs-> Add/Remove Windows components, and then you can see a script debugger. This script debugger can be used to debug JavaScript and can be used to debug any ActiveX-based scripting language (VBScript, ASP, etc.). Although this tool has most commonly used 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 that you used to use.
It's better to use the Script Debugger with Office 2003. More powerful and stable than Visual InterDev. The Script Debugger is hidden deep and needs to be carefully found in the installation directory.

Above is the m$ series JS debugging tool. Visual Studio and Office 2003 are all paid for. If you don't want to spend money, there is a good choice is that Mozilla Venkman,venkman is a JavaScript debugger developed by the Mozilla organization, the function is already perfect. If you install the Mozilla kit, which already includes Venkman, just select it when you install it. If the kit is in Chinese, the Venkman interface is all Chinese.
Users who use Firefox need to install another:
http://www.hacksrus.com/~ginda/venkman/
Select the latest version of the installation, such as the direct click in Firefox
Http://www.hacksrus.com/~ginda/venkman/venkman-0.9.85.xpi
You can complete the installation. Of course, you can download it, then use Firefox to open this file directly to complete the installation.

After installation, a "Javascirpt Debugger" will appear in the Firefox Tools menu, and you can open the Venkman debugger after clicking it.
The resources associated with 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
Direct Search Venkman can also search for a number of related resources.

Firefox + Venkman is a good combination of developing Ajax apps.