Debug JS using Aptana + firefox3 + plug-in

This is the original Aptana debug JavaScript tutorial of $ ('Demo'), a member of the blog. Due to the publishing of images, $ ('Demo') is handed over to me for release, I have modified some text in this article. Thank you $ ('Demo ')!

Preliminary work 1. You must install the Firefox browser; 2. Download and install aptanadebugger and firebug from the http://support.aptana.com/asap/browse/STU-1769; both are Firefox plug-ins; so we can debug the script. Let's use a small example today to talk about Aptana debug Javascript. Click to download this example 1. When the Aptana default panel is activated, that is, the Aptana icon in the upper right corner, In the left-side panel project, create a project [Right-click to create] A. Create a project css88. Note: do not contain Chinese characters in the folder/file path of the new project, or you will not be able to debug the project. For example, do not place the file on the desktop (in the Chinese version system) B. Right-click the css88 project and create a css88.js file. 2. Now debug the newly created css88.js. Click the debug icon in the upper right corner. Next, debug the Aptana debug functions. If the function panel cannot be found on the debug interface, add it to show view under the window menu. Step 1: Add a breakpoint. Double-click the row number and double-click Delete] Step 2: Click the debug icon to run firefox   If the interface appears in Firefox, You can debug it, Take a closer look at the icon aptanadebugger and firebug icons in the lower right corner of Firefox, And the webpage status Return to Aptana and you can see Step 3: analyze the functions of each panel on the right. 3. My experience in using Aptana. If you have any good skills, share them with me! If you encounter a problem when using Aptana, leave a message to solve the problem together, or join the Javascript discussion QQ group (7617538 ).

 

 

 

From: http://www.css88.com/archives/685

 

 

 

 

 

 

Note:

According to the plug-in mentioned above, after downloading and using the plug-in, it is very convenient to debug JS, but it is a little bad. During each debugging, you must first jump to a third-party page, as shown in:

 

If the network is not fast enough, it will stay on this page and cannot enter the real debugging page.

 

 

 

 

Finally, I found a tip:

 

That is, when the page stays on a third-party page,Select the address bar and press Enter.In this way, the debugging page can be accelerated.