Jump to: navigation, search

Difference between revisions of "JSDT/Debug"

(Bundles)
Line 45: Line 45:
  
 
The JSDI is used to provide a common way for our models and UI to communicate with a variety of debugger back-ends - write one UI + model and provide additional debuggers. The complete specification for the [[/JavaScript_Debug_Interface|JSDI]] can be found [[/JavaScript_Debug_Interface|here]].
 
The JSDI is used to provide a common way for our models and UI to communicate with a variety of debugger back-ends - write one UI + model and provide additional debuggers. The complete specification for the [[/JavaScript_Debug_Interface|JSDI]] can be found [[/JavaScript_Debug_Interface|here]].
 
== Testing ==
 
 
[[/Testing|Smoke Tests]], scenarios, example scripts and more to aid testing.
 
  
 
[[Category:JSDT]]
 
[[Category:JSDT]]

Revision as of 20:46, 14 January 2011

JSDT Debug
Website
Download
Community
Mailing ListForumsIRC
Bugzilla
Open
Help Wanted
Bug Day
Contribute
Browse SourceProject Set File

The JSDT debug project brings a variety of JavaScript debugging support to the JSDT using a common UI and communicating using a common protocol - JavaScript Debug Interface (JSDI). The common interface for the debugger emulates that of the platform and JDT debugger to allow a smooth transition and ease of use for the JSDT debugger.

Currently we have debugging support for Rhino and an incubation version of Crossfire / Firebug support.

Bundles

The entire JSDT debugger is comprised of several bundles:

All of the bundles required for development of the JSDT debugger can be acquired using the team project set file here.

Planning

JSDT Debug follows directly the project plan for JSDT.

HOWTO

Using the Crossfire Debugger

An alternative debugger that interacts with Firebug using Crossfire is under development. This page describes how to try and get the experimental version of the debugger up and running.

Using the Google Chrome Debugger

Another alternative debugger that can be tested is using v8 for Google Chrome. This page describes how to try and get the experimental version up and running.

Development

JavaScript Debug Interface (JSDI)

The JSDI is used to provide a common way for our models and UI to communicate with a variety of debugger back-ends - write one UI + model and provide additional debuggers. The complete specification for the JSDI can be found here.