Implement JSDT integration

[GoogleCodeExporter]

JavaScript Development Environment is a set of JS tools from eclipse.org (it is 
currently a part of WTP).

I believe Chrome Dev Tools users would benefit from integrated experience when 
they 
could use rich editing capabilities of the JSDT together with ChDT JS debugger.

We implemented similar functionality in our IDE 
(http://developer.symbian.org/main/source/packages/package/index.php?pk=263) 
and the 
source code is available under EPL. We would be glad to cooperate with Chrome 
Developer Tools project.

What we have:
1. Launch configuration type - will run Chrome and set the debugging session 
(i.e. add 
the breakpoint)
2. ChDT will work with JSDT editors - i.e. breakpoints can be set in JSDT 
editor (and 
stored between user sessions), stepping through the code will happen in JSDT 
editor, 
etc, stack view shows workspace resource names (instead of URLs), etc.

What is not in our code:
Our code relies on our requirements - i.e. it will expect HTML page with 
specific name 
in the project, Chrome is ran with lowered security, etc.

I would like to suggest discussing the requirements for "generic" JSDT 
integration. We 
will be glad to provide our code and help adopting it to new requirements.

Original issue reported on code.google.com by eostrouk...@gmail.com on 20 Jan 2010 at 5:14

[GoogleCodeExporter]

JSDT included in Eclipse 3.6 includes debugging support with their own 
IDebugTarget implementation and VM connections. It would be interesting to see 
how much could be leveraged from the org.eclipse.wst.jsdt.debug.core interfaces 
and implementation. See 
http://www.eclipse.org/webtools/releases/3.2.0/NewAndNoteworthy/sourceediting.ph
p

Original comment by the.john...@gmail.com on 3 Jul 2010 at 12:32

[GoogleCodeExporter]

Dance,

thank you for the link. I think we should look into this. Meanwhile 0.1.6 
version has been released. You may find interesting to take a look at its new 
features list here http://code.google.com/p/chromedevtools/wiki/Release_0_1_6

Peter

Original comment by peter.ry...@gmail.com on 10 Aug 2010 at 8:56

• Changed state: Accepted

[GoogleCodeExporter]

Is anybody working on JSDT connector already? Would you accept external 
contribution for this part?

Original comment by eostrouk...@gmail.com on 18 Aug 2010 at 5:52

[GoogleCodeExporter]

To some extent the integration is delivered in 0.2.0 release. It allows 
creating breakpoints from JSDT editor.

Original comment by peter.ry...@gmail.com on 22 Jan 2011 at 12:08

• Changed state: Fixed

[GoogleCodeExporter]

I'm running org.chromium.debug.feature.group Chromium JavaScript Remote 
Debugger    0.2.2.201102182139 with the latest JSDT 1.1.2 and I can't figure how 
to set breakpoints in Eclipse at all. The usual technique from Java of clicking 
in the margin does nothing at all in the editors on my local project files, 
even after setting up a source mapper. 

So far I just installed Chrome Dev tools, and not the Chromium Javascript 
Debugger bridge because I get the error...
 Missing requirement: Chromium JavaScript Debugger Bridge to JSDT 0.2.2.201102182139 (org.chromium.debug.jsdtbridge 0.2.2.201102182139) requires 'bundle org.eclipse.wst.jsdt.core 1.1.0' but it could not be found

In the absence of a comprehensive walkthrough, (including the use of Eclipse 
debugging in Chrome), I'm still wasting time trying to get debugging within an 
editor using Chrome Dev tools, whilst Aptana with Firefox at least works. About 
12 months and counting now.

Someone has invested time in detailing some information at 
http://code.google.com/p/chromedevtools/wiki/FeatureDebugOnRealFiles but this 
is essentially useless without telling us how to use debugging and editing. 

Do we try to set breakpoints on the files from our local filesystem project 
(can't) on the Chromium files (maybe, but then the editable file isn't shown, 
whilst the uneditable Chromium project file appears when breakpoints are hit), 
through the Chrome dev tools (in principle, yes, since there is an option to 
coalesce local and remote breakpoints, but in practice no, since the Scripts 
tab disappears the moment you launch Chromium with a remote debug session).

If it's important to make this available to developers, could someone try and 
set it up and document the installation and use of the feature? 

In the meantime, can anyone give me guidance how I can satisfy the requirements 
of Chrome Dev tools to give me BOTH breakpoints AND editing on the same files.

Original comment by c...@cefn.com on 10 Jun 2011 at 6:14

[GoogleCodeExporter]

Breakpoints:
1. set up source look-up and connect to chrome.
2. open properties of your source file (probably Alt+Enter).
3. if source look-up is correct, under "V8 JavaScript Script" section you will 
see "Workspace file is currently linked to scripts in debug launches" with 
non-empy pop-up list below. If source look-up is incorrect, the list will be 
disabled.
4. in editor, set the breakpoint:
  a. menu "Run | Breakpoint Types | Chrome/V8 breakpoints" (once per session)
  b. menu "Run | Toggle Breakpoint"

the breakpoint should be set.

Original comment by peter.ry...@gmail.com on 10 Jun 2011 at 8:04