https://sourceforge.net/p/chromedevtools/wiki/RelatedTools/Recent changes to RelatedToolsenSat, 25 Apr 2015 13:43:46 -0000https://sourceforge.net/p/chromedevtools/wiki/RelatedTools/<div class="markdown_content"><h1 id="related-tools">Related Tools</h1> <p>This project implements JavaScript <a class="" href="/p/chromedevtools/wiki/EclipseDebugger">debugger</a> for Eclipse platform. It relies on Eclipse ecosystem for other capabilities, in particular source file editor. While the standard Eclipse Platform configuration can be enough for virtually all <a class="" href="/p/chromedevtools/wiki/EclipseDebuggerFeatures">Debugger features</a> to work, additional third-party software could improve JavaScript developer experience. </p> <p>The following list mentions some software packages with notes about its compatibility with Debugger. </p> <h2 id="base-eclipse-configuration">Base Eclipse Configuration</h2> <p>Debugger requires "Eclipse Platform" configuration. In this configuration there are only abstract IDE capabilities, and no particular language/SDK is supported. </p> <p>Notes: </p> <ul> <li>A generic project with .js and .html source files can be created and successfully used with Debugger. </li> <li><code>Run | Debug Configuration</code> menu item is available from <code>Debug</code> perspective. </li> <li>A standard Text Editor should be manually chosen when opening .html file (<code>Open With | Text Editor</code> in context menu). </li> <li>The Text Editor doesn't create breakpoints, but a breakpoint can always be created from <code>Run | Toggle Breakpoint</code> menu. </li> </ul> <h2 id="possible-topics-to-be-done-later">Possible Topics (to be done later)</h2> <ul> <li>JSDT </li> <li>Aptana </li> <li>ZendStudio </li> <li>Spket IDE </li> <li>VJET </li> </ul></div>AnonymousSat, 25 Apr 2015 13:43:46 -0000https://sourceforge.net0f068cc136fc80c6e1db4c156e87f60ff0677eeb