Jump to: navigation, search

Difference between revisions of "JSDT/Debug"

(Development)
(Bundles)
Line 13: Line 13:
 
*'''org.eclipse.wst.jsdt.debug.core''' - contains the JSDI specification and debug model elements.
 
*'''org.eclipse.wst.jsdt.debug.core''' - contains the JSDI specification and debug model elements.
 
*'''org.eclipse.wst.jsdt.debug.crossfire''' (incubation) - contains a Crossfire implementation of the debugger.
 
*'''org.eclipse.wst.jsdt.debug.crossfire''' (incubation) - contains a Crossfire implementation of the debugger.
 +
*'''org.eclipse.wst.jsdt.debug.chrome''' (incubation) - contains a Google Chrome implementation of the debugger.
 +
*'''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.
 
*'''org.eclipse.wst.jsdt.debug.rhino''' - contains a Rhino implementation of the debugger.
 
*'''org.eclipse.wst.jsdt.debug.rhino''' - contains a Rhino implementation of the debugger.
 
*'''org.eclipse.wst.jsdt.debug.rhino.debugger''' - contains the Rhino debug hooks to connect to the Rhino interpreter.
 
*'''org.eclipse.wst.jsdt.debug.rhino.debugger''' - contains the Rhino debug hooks to connect to the Rhino interpreter.

Revision as of 17:13, 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:

  • org.eclipse.wst.jsdt.debug.core - contains the JSDI specification and debug model elements.
  • org.eclipse.wst.jsdt.debug.crossfire (incubation) - contains a Crossfire implementation of the debugger.
  • org.eclipse.wst.jsdt.debug.chrome (incubation) - contains a Google Chrome implementation of the debugger.
  • 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.
  • org.eclipse.wst.jsdt.debug.rhino - contains a Rhino implementation of the debugger.
  • org.eclipse.wst.jsdt.debug.rhino.debugger - contains the Rhino debug hooks to connect to the Rhino interpreter.
  • org.eclipse.wst.jsdt.debug.ui - contains the shared UI presentation for the debugger implementations.
  • org.eclipse.wst.jsdt.debug.core.tests - contains related test cases for the debug core.
  • org.eclipse.wst.jsdt.debug.rhino.tests - contains Rhino specific tests.

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

Embedding the Rhino Debugger

To use the Rhino debug support it must be linked to a running Rhino interpreter. This page describes how to do this.

Using the Rhino Debug Console

Launching the Rhino debugger with the Rhino console available is a very powerful tool that allows developers to perform many operations, one notable operation is loading scripts on demand. This page describes how to launch with the Rhino console and some common usage scenarios.

Using Local Rhino Launching

New support added in 1.3 allows you to launch Rhino locally with a single click. More information on how to do so is found here.

The related New and Noteworthy entry is here.

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.

Testing

Smoke Tests, scenarios, example scripts and more to aid testing.