Jump to: navigation, search

Difference between revisions of "JSDT/Debug"

Line 29: Line 29:
  
 
JSDT Debug follows directly the project plan for JSDT.
 
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.  [[/Using_Crossfire_Debugger|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. [[/Using_Google_Chrome_Debugger|This page]] describes how to try and get the experimental version up and running.
 
  
 
== Development ==
 
== Development ==

Revision as of 20:47, 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.

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.