development/news/3.2M7/sourceediting.xml

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="../new_and_noteworthy.xsl"?>
<release
	name="3.2 M7"
	root="../../.."
>
	<!--
		<component name="component name, such as Web Services Tools">
		<item title="item title can go here">
			<title>item title can also go here</title>
			<description>description of this new feature, preferably with cropped .pngs of the UI</description>
		</item>
		</component>
	<component name="XML">
	</component>

	<component name="HTML">
	</component>

	<component name="JSP">
	</component>

	<component name="CSS">
		<item title="">
			<description>
			</description>
		</item>
	</component>

	-->
	<component name="JSDT">
		<item title="Quick Access to Breakpoint Properties">
			<description>
				<p>
					Breakpoint properties are now quickly accessible via the context menu in the Breakpoints View (to better match
					JDT breakpoint support).
				</p>
				<img src="jsdtdebug/bp_menu_props.png" alt="Breakpoint Properties Quick Access"></img>
			</description>
		</item>
		<item title="Breakpoint Condition Content Assist">
			<description>
				<p>
					Content Assist is now available in the breakpoint condition editor.
				</p>
				<img src="jsdtdebug/bp_content_assist.png" alt="Breakpoint Condition Content Assist"></img>
			</description>
		</item>
		<item title="Rhino Console">
			<description>
				<p>
					When wanting to test Rhino, or work from a command line interface, we have provided the Rhino debug console.
					Our Rhino console allows access to all of the Mozilla Rhino shell tools as described 
					<a href="http://www.mozilla.org/rhino/shell.html">here</a>. Our shell replacement can be run using the 
					<code>org.eclipse.wst.jsdt.debug.rhino.debugger.shell.DebugShell</code> class from the 
					<code>org.eclipse.wst.jsdt.debug.rhino.debugger</code> project.
				</p>
				<img src="jsdtdebug/rhino_console.png" alt="Rhino Console"></img>
			</description>
		</item>
		<item title="Show All Scripts">
			<description>
				<p>
					In the Debug View you can view all of the scripts currently loaded in the the running debug target.
				</p>
				<img src="jsdtdebug/all_loaded_scripts.png" alt="Show All Scripts"></img>
			</description>
		</item>
		<item title="Open Source (Ctrl + 3)">
			<description>
				<p>
					When showing all scripts you can also load the source for any scripts that has been loaded at any given time. 
					To do so we have provided the Open Source command available in the Debug View (Ctrl + 3).
				</p>
				<img src="jsdtdebug/open_source.png" alt="Open Source"></img>
			</description>
		</item>
		<item title="Step Into Script Load">
			<description>
			<p>
				With our existing support to suspend execution when a (or any) script loads it was not clear to the user what could 
				happen next. We have added support to be able to step into the first executable line of the the loaded script (as well as
				resume execution like before). Also the suspended message on the thread now gives a very clear message why you are suspended. 
			</p>
			<img src="jsdtdebug/step_into_script.png" alt="Step Into Script Load"></img>
			</description>
		</item>
	</component>
<!--
	<component name="XML Schema">
	</component>
-->
</release>