https://sourceforge.net/p/chromedevtools/wiki/VirtualProject/Recent changes to VirtualProjectenSat, 25 Apr 2015 13:43:53 -0000https://sourceforge.net/p/chromedevtools/wiki/VirtualProject/<div class="markdown_content"><h2 id="what-is-it">What is it?</h2> <p>A "virtual project" is an Eclipse project created by the <a class="" href="/p/chromedevtools/wiki/EclipseDebugger">Debugger</a> for every debug session (<a class="" href="../LaunchElement">launch</a>) and deleted once the debug session is over. Virtual projects can be found among other regular projects. Since <a class="" href="/p/chromedevtools/wiki/Release_0_2_0">release 0.2.0</a>, the virtual project icon is decorated by a small <a class="" href="http://www.chromium.org" rel="nofollow">Chromium</a> logo. A virtual project serves as a container for JavaScript scripts downloaded from a remote VM. Those scripts are never saved on disk and are forgotten when the virtual project is deleted. </p> <h2 id="why-do-we-need-it">Why do we need it?</h2> <p>For languages like C++ or Java, all source files reside in a developer's working directory. The JavaScript case is quite different: the entire source scripts collection (which includes scripts generated on the fly) can be found only inside a running JavaScript virtual machine (VM). That's why a JavaScript debugger has to download the scripts from a VM into Eclipse first. A virtual project is the way the Debugger presents them. </p> <h2 id="virtual-project-vs-workspace-local-files">Virtual project vs. Workspace local files</h2> <p>A virtual project is useful because it contains all up-to-date sources, so you don't have to care about getting them from elsewhere. It also contains sources that are generated on the fly, and is irreplaceable in this aspect. </p> <p>Unfortunately, a virtual project is not very useful for a JavaScript developer who may want to <em>edit</em> files, not only debug them. (Actually, scripts from virtual projects <em>are</em> editable, which is used for the <em>live editing</em> feature, but all changes are lost once the VM stops). In a more common setting, a developer will link a debug session to the workspace source files -- see <a class="" href="/p/chromedevtools/wiki/FeatureDebugOnRealFiles">feature description</a>. </p> <p>Note that a virtual project exists for any debug session, regardless of whether it has the workspace source files configured or not. </p></div>AnonymousSat, 25 Apr 2015 13:43:53 -0000https://sourceforge.net9e490e593fded1c496dc545f3d2880aee61f23df