Jump to: navigation, search

Difference between revisions of "JSDT/Debug"

(Bundles)
(Bundles)
 
(One intermediate revision by the same user not shown)
Line 14: Line 14:
 
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/development/org.eclipse.wst.jsdt.debug.crossfire/?root=WebTools_Project org.eclipse.wst.jsdt.debug.crossfire] (incubation) - contains a Crossfire implementation of the debugger.
 
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/development/org.eclipse.wst.jsdt.debug.crossfire/?root=WebTools_Project org.eclipse.wst.jsdt.debug.crossfire] (incubation) - contains a Crossfire implementation of the debugger.
 
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/development/org.eclipse.wst.jsdt.debug.chrome/?root=WebTools_Project org.eclipse.wst.jsdt.debug.chrome] (incubation) - contains a Google Chrome implementation of the debugger.
 
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/development/org.eclipse.wst.jsdt.debug.chrome/?root=WebTools_Project org.eclipse.wst.jsdt.debug.chrome] (incubation) - contains a Google Chrome implementation of the debugger.
 +
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/development/org.eclipse.wst.jsdt.debug.node/?root=WebTools_Project org.eclipse.wst.jsdt.debug.node] (incubation) - contains a Node.js implementation of the debugger.
 
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/development/org.eclipse.wst.jsdt.debug.opera/?root=WebTools_Project org.eclipse.wst.jsdt.debug.opera] (incubation) - contains an Opera implementation of the debugger.
 
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/development/org.eclipse.wst.jsdt.debug.opera/?root=WebTools_Project org.eclipse.wst.jsdt.debug.opera] (incubation) - contains an Opera implementation of the debugger.
*'''org.eclipse.wst.jsdt.debug.ie''' (incubation) - contains a Internet Explorer implementation of the debugger.
+
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/development/org.eclipse.wst.jsdt.debug.ie.debugger/?root=WebTools_Project org.eclipse.wst.jsdt.debug.ie.debugger] (incubation) - contains a Internet Explorer implementation of the debugger.
 
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/plugins/org.eclipse.wst.jsdt.debug.rhino/?root=WebTools_Project org.eclipse.wst.jsdt.debug.rhino] - contains a Rhino implementation of the debugger.
 
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/plugins/org.eclipse.wst.jsdt.debug.rhino/?root=WebTools_Project org.eclipse.wst.jsdt.debug.rhino] - contains a Rhino implementation of the debugger.
 
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/plugins/org.eclipse.wst.jsdt.debug.rhino.debugger/?root=WebTools_Project org.eclipse.wst.jsdt.debug.rhino.debugger] - contains the Rhino debug hooks to connect to the Rhino interpreter.
 
*[http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.jsdt/plugins/org.eclipse.wst.jsdt.debug.rhino.debugger/?root=WebTools_Project org.eclipse.wst.jsdt.debug.rhino.debugger] - contains the Rhino debug hooks to connect to the Rhino interpreter.

Latest revision as of 16:50, 31 March 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.