new/0.1/new.html - gerrit/www.eclipse.org/linuxtools - Git at Google

 <html>
 <body bgcolor="FFFFFF">

 <table border="1" style="border-collapse: collapse" width="100%" id="table128" cellpadding="4" bordercolor="#FFFFFF">
 	<tr>
 		<td bgcolor="#595791" width="8%" align="center"><b>
 		<font color="#FFFFFF" size="1">Release</font></b></td>
 		<td bgcolor="#595791" width="5%" align="center"><b>
 		<font color="#FFFFFF" size="1">Resolved
 		</font></b></td>
 		<td bgcolor="#595791" width="*" align="center"><b>
 		<font color="#FFFFFF" size="1">Community Contributions</font></b></td>
 	</tr>

 	<tr>
 		<td bgcolor="#FAF7FB"><font size="1">0.1<br>
 		<i>11 Feb. 2009</i></font></td>
 		<td bgcolor="#FAF7FB" align="center">
 		<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Linux+Tools&target_milestone=0.1&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
 		12 bugs</a></td>
 		<td bgcolor="#FAF7FB"><font size="1">Alphonse van Assche contributed
 		many fixes for our RPM specfile editor as well as integration of
 		<a href="http://rpmlint.zarb.org">rpmlint</a> error and warning
 		parsing.  Phil Muldoon contributed his <a href="http://systemtap.org">Systemtap</a>
 		editor and helped
 		with ChangeLog bug fixes.  Kent Sebastian picked up Keith Seitz's work
 		on <a href="http://oprofile.sourceforge.net">OProfile</a>
 		and worked with Elliott Baron to create a framework for profiling tools.
 		Elliott contributed his work on integrating the <a href="http://valgrind.org">Valgrind</a>
 		suite of tools
 		into the IDE.  Alexander Kurtakov contributed many fixes to our RPM
 		specfile editor as well as making the initial RPM Stubby work usable.
 		Nick Boldt helped us immensely as we got our release engineering
 		processes straightened out.  Jeff Johnston contributed his work on
 		integrating the GNU Autotools with the CDT.  Jeff also contributed
 		his work on bridging the gap between API documentation and the CDT's
 		hover help with his libhover work.
 		</font></td>
 	</tr>
 	<tr>
 		<td bgcolor="#FAF7FB"><font size="1">pre-0.1</font></td>
 		<td bgcolor="#FAF7FB" align="center">
 		<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Linux+Tools&target_milestone=---&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
 		69 bugs</a></td>
 		<td bgcolor="#FAF7FB"><font size="1">Prior to our 0.1 release, Remy Chi
 		Jian Suen helped us out with proper execution environments for our
 		plugins among other things.  Phil Muldoon contributed his ChangeLog
 		plugin.  Kyu Lee then contributed an editor for ChangeLog files.  Keith
 		Seitz contributed his OProfile integration plugins.  Igor Foox helped
 		out a great deal getting our RPM specfile editor started.
 		</font></td>
 	</tr>
 </table>

 <hr>

 <p><span style="font-weight: 700; background-color: #E0D0E6">New in Linux Tools 0.1</span> </p>
 <ul>
 	<li><a href="#autotools">GNU Autotools Support (3)</a></li>
 	<li><a href="#changelog">ChangeLog Tools (3)</a></li>
 	<li><a href="#libhover">API Documentation Hover Help (1)</a></li>
 	<li><a href="#oprofile">OProfile Profiling (3)</a></li>
 	<li><a href="#rpmstubby">RPM Stubby (1)</a></li>
 	<li><a href="#specfileeditor">RPM <tt>.spec</tt> Editor (5)</a></li>
 	<li><a href="#systemtap">Systemtap Editor (3)</a></li>
 	<li><a href="#valgrind">Valgrind Profiling (3)</a></li>
 </ul>

 <h2><a name="autotools">GNU Autotools Support</a></h2>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Configuration</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">The Autotools integration plugins add support for a configuration step prior to running the Makefile of existing projects that use a configure or autogen.sh script.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/autotools-configuration.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Maintenance</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">The Autotools plugins add colourized editors for configure scripts including hover help and completion for macros.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/autotools-editor.png"><br><br>
 			<img border="0" src="images/0.1/autotools-editor-2.png">
 			</td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Tools Access</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Invoking autotools can be done directly from within the IDE.  Support is provided for running aclocal, automake, and autoconf.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/autotools-tools.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <h2><a name="changelog">ChangeLog Tools</a></h2>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Source code parsing</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">The ChangeLog tools assist in generating ChangeLog entries.  Pressing the key combination Ctrl-Alt-c will parse the current file and add a ChangeLog entry in the appropriate ChangeLog file.  C, C++, and Java source files are parsed to fill out the method/function.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/changelog-generation-3.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Repository integration</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">The ChangeLog tools can generate a ChangeLog entry for projects that use a source code repository.  Support is provided for standard org.eclipse.team providers and has been tested with both CVS and SVN repositories.  A ChangeLog entry can be generated for all changes between the local copy and the repository by pressing Ctrl+Alt+p.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/changelog-generation.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Formatting extensibility</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">The ChangeLog plugin allows extending the ChangeLog format as exemplified by the RPM specfile editor which adds specfile <tt>%changelog</tt> section formatting invoked via Ctrl-Alt-c.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/changelog-format.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <h2><a name="libhover">API Documentation Hover Help</a></h2>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Standards</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">The Libhover plugin adds C library hover help and completion support for various C libraries including glibc and newlib.  The plugin provides an extension and a documentation format for adding new C libraries in the future.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/libhover-sample.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <h2><a name="oprofile">OProfile Profiling</a></h2>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>New View</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">The OProfile view is all new as well as much of the backend supplying the data. Events are top level elements allowing multiple events to be shown simultaneously. Double-clicking on a line number node brings up an editor with the source file at the appropriate line (if available). Double-clicking on the default session (named "current") allows it to be saved for future viewing.
 			</p>
 			<p>
 			<img border="0" alt="New OProfile View UI" src="images/0.1/oprofile-newui.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>One Click Launch</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Profiling is as easy as a single click. Right-clicking on a CDT binary, project or editor of a source file will launch the associated project's binary under OProfile with no configuration needed. Configuration is set to appropriate defaults for the user's processor (an event based on execution time) and this configuration is left for the user to customize later. If multiple binaries exist in the project, a dialog will allow the user to select the appropriate one.
 			</p>
 			<p>
 			<img border="0" alt="Launch Shortcut" src="images/0.1/oprofile-launchshortcut.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>New Event Config Tab UI</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Allows users of all experience levels with OProfile to take advantage of its powerful profiling capabilities. Default event configuration option. Multiple hardware counters appear as tabs. All unit masks properly displayed with appropriate defaults. Caching of event check results allowing for faster validation. Scrollable composite for events with many unit masks.
 			</p>
 			<p>
 			<img border="0" alt="Event Config Tab" src="images/0.1/oprofile-eventconfigtab.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <h2><a name="rpmstubby">RPM Stubby</a></h2>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Generation</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">The RPM Stubby plugin assists in generating an RPM specfile for an Eclipse feature by using the data in its feature.xml.
 			The plugin uses the latest best practices for packaging an Eclipse feature as an RPM.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/rpmstubby-sample.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <h2><a name="specfileeditor">RPM <tt>.spec</tt> Editor</a></h2>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Auto-completion</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Completion proposals for RPM Group tags has been added based on the system-installed <tt>GROUPS</tt> file.
 			</p>
 			<img border="0" src="images/0.1/specfileeditor-completion.png">
 			<p align="left">Autocompletion for patches has been fixed to appear only in the %prep section.</p>
 			<img border="0" src="images/0.1/specfileeditor-completion-patch.png">
 			</td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>
 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Task tags</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Task tags support is added with custom defined tags.
 			</p>
 			<img border="0" src="images/0.1/specfileeditor-tasks.png">
 			</td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Templates</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Templates for common actions are available.  In the example shown here, RPM <tt>Requires</tt> completions
 			are shown.
 			</p>
 			<img border="0" src="images/0.1/specfileeditor-completion-requires.png">
 			</td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Hover help</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Both system- and file-defined variable definitions are displayed when hovering over their usage.
 			</p>
 			<img border="0" src="images/0.1/specfileeditor-hover.png">
 			</td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Quick fixes</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Quick fixes for the following rpmlint warnings have been added:
 			<ul>
 				<li>HardcodedPackagerTag</li>
 				<li>HardcodedPrefixTag</li>
 				<li>NoCleanSection</li>
 				<li>NoInstallSection</li>
 				<li>NoPrepSection</li>
 			</ul>
 			</td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <h2><a name="systemtap">Systemtap Editor</a></h2>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Probe completion</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">The Systemtap script editor provides probe completion
 			suggestions for Systemtap scripts.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/systemtap-completion.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Syntax highlighting</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">While editing Systemtap scripts, syntax highlighting showing
 			script conformance is shown.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/systemtap-highlighting.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Code folding</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Logical sections of Systemtap scripts can be
 			collapsed to increase readability.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/systemtap-folding.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <h2><a name="valgrind">Valgrind Profiling</a></h2>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Launching</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Profiling with Valgrind is done through the launch framework
 			and can be accessed via the "Profile As" menu item in the Run and context menus.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/valgrind-profile-as.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Memcheck</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Support for Memcheck, the memory error-checking tool, includes
 			a tree view of errors and their corresponding stack trace. Stack frames can be
 			double-clicked to show the given line in an editor. Markers annotate the corresponding
 			source code.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/valgrind-memcheck.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 <table cellpadding="10" cellspacing="0">
 		<tr>
 			<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
 			<p align="right"><b>Massif</b></p>
 			</td>
 			<td valign="top" width="70%">
 			<p align="left">Massif integration consists of three different forms of output.
 			A table view lists each heap snapshot taken. Of these snapshots, some have more
 			detailed information available, including a call trace of the functions performing heap
 			allocations in each snapshot. This extended information is available in a tree view
 			accessible either by double clicking on a snapshot with the "tree" icon, or by clicking
 			the similar icon in the Valgrind view's toolbar. Within the tree view, allocation functions
 			found in source files can be viewed in an editor by double clicking on the element in the tree.
 			Finally, there is a heap chart displayed in an editor that graphically outlines the information
 			provided in the snapshots. Clicking on a point in the chart selects the snapshot in the
 			table.
 			</p>
 			<p>
 			<img border="0" src="images/0.1/valgrind-massif.png"></td>
 		</tr>
 		<tr>
 			<td colspan="2">
 			<hr>
 			</td>
 		</tr>
 </table>

 </body>
 </html>
	<html>
	<body bgcolor="FFFFFF">

	<table border="1" style="border-collapse: collapse" width="100%" id="table128" cellpadding="4" bordercolor="#FFFFFF">
	<tr>
	<td bgcolor="#595791" width="8%" align="center"><b>
	<font color="#FFFFFF" size="1">Release</font></b></td>
	<td bgcolor="#595791" width="5%" align="center"><b>
	<font color="#FFFFFF" size="1">Resolved
	</font></b></td>
	<td bgcolor="#595791" width="*" align="center"><b>
	<font color="#FFFFFF" size="1">Community Contributions</font></b></td>
	</tr>

	<tr>
	<td bgcolor="#FAF7FB"><font size="1">0.1<br>
	<i>11 Feb. 2009</i></font></td>
	<td bgcolor="#FAF7FB" align="center">
	<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Linux+Tools&target_milestone=0.1&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
	12 bugs</a></td>
	<td bgcolor="#FAF7FB"><font size="1">Alphonse van Assche contributed
	many fixes for our RPM specfile editor as well as integration of
	<a href="http://rpmlint.zarb.org">rpmlint</a> error and warning
	parsing. Phil Muldoon contributed his <a href="http://systemtap.org">Systemtap</a>
	editor and helped
	with ChangeLog bug fixes. Kent Sebastian picked up Keith Seitz's work
	on <a href="http://oprofile.sourceforge.net">OProfile</a>
	and worked with Elliott Baron to create a framework for profiling tools.
	Elliott contributed his work on integrating the <a href="http://valgrind.org">Valgrind</a>
	suite of tools
	into the IDE. Alexander Kurtakov contributed many fixes to our RPM
	specfile editor as well as making the initial RPM Stubby work usable.
	Nick Boldt helped us immensely as we got our release engineering
	processes straightened out. Jeff Johnston contributed his work on
	integrating the GNU Autotools with the CDT. Jeff also contributed
	his work on bridging the gap between API documentation and the CDT's
	hover help with his libhover work.
	</font></td>
	</tr>
	<tr>
	<td bgcolor="#FAF7FB"><font size="1">pre-0.1</font></td>
	<td bgcolor="#FAF7FB" align="center">
	<a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Linux+Tools&target_milestone=---&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=">
	69 bugs</a></td>
	<td bgcolor="#FAF7FB"><font size="1">Prior to our 0.1 release, Remy Chi
	Jian Suen helped us out with proper execution environments for our
	plugins among other things. Phil Muldoon contributed his ChangeLog
	plugin. Kyu Lee then contributed an editor for ChangeLog files. Keith
	Seitz contributed his OProfile integration plugins. Igor Foox helped
	out a great deal getting our RPM specfile editor started.
	</font></td>
	</tr>
	</table>

	<hr>

	<p><span style="font-weight: 700; background-color: #E0D0E6">New in Linux Tools 0.1</span> </p>
	<ul>
	<li><a href="#autotools">GNU Autotools Support (3)</a></li>
	<li><a href="#changelog">ChangeLog Tools (3)</a></li>
	<li><a href="#libhover">API Documentation Hover Help (1)</a></li>
	<li><a href="#oprofile">OProfile Profiling (3)</a></li>
	<li><a href="#rpmstubby">RPM Stubby (1)</a></li>
	<li><a href="#specfileeditor">RPM <tt>.spec</tt> Editor (5)</a></li>
	<li><a href="#systemtap">Systemtap Editor (3)</a></li>
	<li><a href="#valgrind">Valgrind Profiling (3)</a></li>
	</ul>

	<h2><a name="autotools">GNU Autotools Support</a></h2>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Configuration</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">The Autotools integration plugins add support for a configuration step prior to running the Makefile of existing projects that use a configure or autogen.sh script.
	</p>
	<p>
	<img border="0" src="images/0.1/autotools-configuration.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Maintenance</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">The Autotools plugins add colourized editors for configure scripts including hover help and completion for macros.
	</p>
	<p>
	<img border="0" src="images/0.1/autotools-editor.png"><br><br>
	<img border="0" src="images/0.1/autotools-editor-2.png">
	</td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Tools Access</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Invoking autotools can be done directly from within the IDE. Support is provided for running aclocal, automake, and autoconf.
	</p>
	<p>
	<img border="0" src="images/0.1/autotools-tools.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<h2><a name="changelog">ChangeLog Tools</a></h2>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Source code parsing</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">The ChangeLog tools assist in generating ChangeLog entries. Pressing the key combination Ctrl-Alt-c will parse the current file and add a ChangeLog entry in the appropriate ChangeLog file. C, C++, and Java source files are parsed to fill out the method/function.
	</p>
	<p>
	<img border="0" src="images/0.1/changelog-generation-3.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Repository integration</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">The ChangeLog tools can generate a ChangeLog entry for projects that use a source code repository. Support is provided for standard org.eclipse.team providers and has been tested with both CVS and SVN repositories. A ChangeLog entry can be generated for all changes between the local copy and the repository by pressing Ctrl+Alt+p.
	</p>
	<p>
	<img border="0" src="images/0.1/changelog-generation.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Formatting extensibility</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">The ChangeLog plugin allows extending the ChangeLog format as exemplified by the RPM specfile editor which adds specfile <tt>%changelog</tt> section formatting invoked via Ctrl-Alt-c.
	</p>
	<p>
	<img border="0" src="images/0.1/changelog-format.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<h2><a name="libhover">API Documentation Hover Help</a></h2>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Standards</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">The Libhover plugin adds C library hover help and completion support for various C libraries including glibc and newlib. The plugin provides an extension and a documentation format for adding new C libraries in the future.
	</p>
	<p>
	<img border="0" src="images/0.1/libhover-sample.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<h2><a name="oprofile">OProfile Profiling</a></h2>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>New View</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">The OProfile view is all new as well as much of the backend supplying the data. Events are top level elements allowing multiple events to be shown simultaneously. Double-clicking on a line number node brings up an editor with the source file at the appropriate line (if available). Double-clicking on the default session (named "current") allows it to be saved for future viewing.
	</p>
	<p>
	<img border="0" alt="New OProfile View UI" src="images/0.1/oprofile-newui.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>One Click Launch</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Profiling is as easy as a single click. Right-clicking on a CDT binary, project or editor of a source file will launch the associated project's binary under OProfile with no configuration needed. Configuration is set to appropriate defaults for the user's processor (an event based on execution time) and this configuration is left for the user to customize later. If multiple binaries exist in the project, a dialog will allow the user to select the appropriate one.
	</p>
	<p>
	<img border="0" alt="Launch Shortcut" src="images/0.1/oprofile-launchshortcut.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>New Event Config Tab UI</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Allows users of all experience levels with OProfile to take advantage of its powerful profiling capabilities. Default event configuration option. Multiple hardware counters appear as tabs. All unit masks properly displayed with appropriate defaults. Caching of event check results allowing for faster validation. Scrollable composite for events with many unit masks.
	</p>
	<p>
	<img border="0" alt="Event Config Tab" src="images/0.1/oprofile-eventconfigtab.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<h2><a name="rpmstubby">RPM Stubby</a></h2>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Generation</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">The RPM Stubby plugin assists in generating an RPM specfile for an Eclipse feature by using the data in its feature.xml.
	The plugin uses the latest best practices for packaging an Eclipse feature as an RPM.
	</p>
	<p>
	<img border="0" src="images/0.1/rpmstubby-sample.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<h2><a name="specfileeditor">RPM <tt>.spec</tt> Editor</a></h2>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Auto-completion</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Completion proposals for RPM Group tags has been added based on the system-installed <tt>GROUPS</tt> file.
	</p>
	<img border="0" src="images/0.1/specfileeditor-completion.png">
	<p align="left">Autocompletion for patches has been fixed to appear only in the %prep section.</p>
	<img border="0" src="images/0.1/specfileeditor-completion-patch.png">
	</td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>
	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Task tags</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Task tags support is added with custom defined tags.
	</p>
	<img border="0" src="images/0.1/specfileeditor-tasks.png">
	</td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Templates</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Templates for common actions are available. In the example shown here, RPM <tt>Requires</tt> completions
	are shown.
	</p>
	<img border="0" src="images/0.1/specfileeditor-completion-requires.png">
	</td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Hover help</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Both system- and file-defined variable definitions are displayed when hovering over their usage.
	</p>
	<img border="0" src="images/0.1/specfileeditor-hover.png">
	</td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Quick fixes</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Quick fixes for the following rpmlint warnings have been added:
	<ul>
	<li>HardcodedPackagerTag</li>
	<li>HardcodedPrefixTag</li>
	<li>NoCleanSection</li>
	<li>NoInstallSection</li>
	<li>NoPrepSection</li>
	</ul>
	</td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<h2><a name="systemtap">Systemtap Editor</a></h2>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Probe completion</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">The Systemtap script editor provides probe completion
	suggestions for Systemtap scripts.
	</p>
	<p>
	<img border="0" src="images/0.1/systemtap-completion.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Syntax highlighting</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">While editing Systemtap scripts, syntax highlighting showing
	script conformance is shown.
	</p>
	<p>
	<img border="0" src="images/0.1/systemtap-highlighting.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Code folding</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Logical sections of Systemtap scripts can be
	collapsed to increase readability.
	</p>
	<p>
	<img border="0" src="images/0.1/systemtap-folding.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<h2><a name="valgrind">Valgrind Profiling</a></h2>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Launching</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Profiling with Valgrind is done through the launch framework
	and can be accessed via the "Profile As" menu item in the Run and context menus.
	</p>
	<p>
	<img border="0" src="images/0.1/valgrind-profile-as.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Memcheck</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Support for Memcheck, the memory error-checking tool, includes
	a tree view of errors and their corresponding stack trace. Stack frames can be
	double-clicked to show the given line in an editor. Markers annotate the corresponding
	source code.
	</p>
	<p>
	<img border="0" src="images/0.1/valgrind-memcheck.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	<table cellpadding="10" cellspacing="0">
	<tr>
	<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
	<p align="right"><b>Massif</b></p>
	</td>
	<td valign="top" width="70%">
	<p align="left">Massif integration consists of three different forms of output.
	A table view lists each heap snapshot taken. Of these snapshots, some have more
	detailed information available, including a call trace of the functions performing heap
	allocations in each snapshot. This extended information is available in a tree view
	accessible either by double clicking on a snapshot with the "tree" icon, or by clicking
	the similar icon in the Valgrind view's toolbar. Within the tree view, allocation functions
	found in source files can be viewed in an editor by double clicking on the element in the tree.
	Finally, there is a heap chart displayed in an editor that graphically outlines the information
	provided in the snapshots. Clicking on a point in the chart selects the snapshot in the
	table.
	</p>
	<p>
	<img border="0" src="images/0.1/valgrind-massif.png"></td>
	</tr>
	<tr>
	<td colspan="2">
	<hr>
	</td>
	</tr>
	</table>

	</body>
	</html>