https://sourceforge.net/p/chromedevtools/wiki/ChromeDevToolsSdk/Recent changes to ChromeDevToolsSdkenSat, 25 Apr 2015 13:43:50 -0000https://sourceforge.net/p/chromedevtools/wiki/ChromeDevToolsSdk/<div class="markdown_content"><p>Originally posted by: fath...@gmail.com</p> <p>alert("") </p></div>AnonymousSat, 25 Apr 2015 13:43:50 -0000https://sourceforge.netbceda41393c53c571ab0a562b6a1d14c134cc443https://sourceforge.net/p/chromedevtools/wiki/ChromeDevToolsSdk/<div class="markdown_content"><p>Originally posted by: <a class="" href="http://code.google.com/u/117971710389242904661" rel="nofollow">shailesh...@gmail.com</a></p> <p>asdf </p></div>AnonymousSat, 25 Apr 2015 13:43:50 -0000https://sourceforge.net6500c725deda40d6b5d9365ea187d6fcc9b8725fhttps://sourceforge.net/p/chromedevtools/wiki/ChromeDevToolsSdk/<div class="markdown_content"><h1 id="overview">Overview</h1> <p>ChromeDevTools SDK is a library that enables developers to create <a class="" href="/p/chromedevtools/wiki/ChromeDevToolsProtocol">ChromeDevToolsProtocol</a>-aware applications (<a class="" href="/p/chromedevtools/wiki/EclipseDebugger">EclipseDebugger</a> is an example of such an application.) The library exposes an API and its default implementation for interaction with the Google Chrome (Chromium) browser. </p> <p>In addition SDK supports following protocols: </p> <ul> <li><a class="" href="http://code.google.com/p/v8/wiki/DebuggerProtocol" rel="nofollow">V8 debugger protocol</a> to attach to any V8-based applications, </li> <li><a class="" href="/p/chromedevtools/wiki/WIP">WebKit Remote Debugging Protocol</a> (starting from <a class="" href="/p/chromedevtools/wiki/Release_0_3_0">0.3.0 release</a>), subproject called 'WIP'. </li> </ul> <h2 id="documentation">Documentation</h2> <ul> <li><a class="" href="http://chromedevtools.googlecode.com/svn/trunk/plugins/org.chromium.sdk/javadocs/index.html" rel="nofollow">Javadocs</a> for the latest release. </li> <li><a class="" href="../SdkTutorial">SdkTutorial</a>. </li> </ul> <h2 id="wip-backends">WIP Backends</h2> <p>WebKit Remote Debugging Protocol support (WIP) is deployed in form of separate modules called backends. Each backend corresponds to a particular version of the protocol (see a table in <a class="" href="/p/chromedevtools/wiki/Release_0_3_0">release notes</a>). Note that all backends share the same class names, so you can put only one backend in the classpath at the same time. This is not a problem when using Eclipse plugin dynamic loading and you can do the same manipulations with the Java classloaders if needed. </p> <h1 id="binary">Binary</h1> <h2 id="standalone-library">Standalone library</h2> <p>The library is available as a set of .jar files from Downloads section ("ChromeDevTools SDK library as tar archive"). WIP backend jars are put in a separate directory. Note that backend jars cannot put simultaneously in one classpath. </p> <h2 id="in-eclipse">In Eclipse</h2> <p>From UI you can install "ChromeDevTools SDK" feature plus "ChromeDevTools SDK WIP Backends" feature. You also can manually get the following plugins: </p> <ul> <li>org.chromium.sdk </li> <li>org.chromium.sdk.wip.eclipse </li> <li>org.chromium.sdk.wipbackend.<code>*</code> -- backend plugins </li> </ul> <h1 id="sources">Sources</h1> <p>Sources could be found in project SVN under the path: </p> <div class="codehilite"><pre> trunk / plugins/org.chromium.sdk/src* trunk / plugins/org.chromium.sdk.wip.eclipse/src trunk / plugins/org.chromium.sdk.wipbackend.*/src* </pre></div> <p>(<code>trunk</code> can be replaced with <code>tags/...</code> for more stable code state. </p></div>AnonymousSat, 25 Apr 2015 13:43:50 -0000https://sourceforge.net402b258589b8fc232cd4d0131a4d66592a99cd2e