[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[cdt-patch] Usability feedback; please add new file
|
As discussed on cdt-test-dev, I have some CDT usability feedback from a
fellow Hatter that I'm adding as a supplement to the test plan. Please
add this as a new file under
/home/tools/cdt-home/developer/usability_feedback.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>CDT Informal Usability Study</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<LINK rel="stylesheet"
HREF="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt-home/cdt.css?cvsroot=Tools_Project"
type="text/css">
</head>
<body>
<!-- Document Header -->
<TABLE cellPadding=2 width="100%" border=0>
<TBODY>
<TR>
<TD align=left width="72%">
<FONT class=indextop>CDT Informal Usability Study</FONT><BR>
<FONT class=indexsub>Study results</FONT>
</TD>
<TD width="28%"><IMG height=86
src="http://dev.eclipse.org/images/Idea.jpg" width=120 alt=""></TD>
</TR>
</TBODY>
</TABLE>
<table>
<tbody>
<tr><td>Author</td><td> : <a
href="mailto:blee@xxxxxxxxxx">Bertina Lee</a>, compiled by <a
href="mailto:handcock@xxxxxxxxxx">Jeremy Handcock</td></tr>
<tr><td>Revision Date</td><td> : 08/27/2003 - Version: 0.1.0</td></tr>
<tr><td>Change History</td><td> : 0.1.0 - Document Creation</td></tr>
</tbody>
</table>
<br>
<!-- End of Document Header -->
<!-- Table of Contents -->
<div class=section>Table of Contents</div>
<br>
<div class=indent><a href="#intro">1. Introduction</a>
</div>
<div class=indent><a href="#results">2. Results</a>
<div class=indent><a href="#high">2.1 High Points</a></div>
<div class=indent><a href="#pitfalls">2.2 Pitfalls</a></div>
</div>
<br><br>
<!-- End of Table of Contents -->
<!-- Introduction -->
<div class=section><a name="intro"> 1. Introduction</a></div>
<p>
This document is the result of feedback obtained from an application
developer's experiences in using CDT 1.1. Bertina Lee used the CDT to
develop a non-trivial C++ application in which MIDI files are parsed and
converted to sheet music format. Her feedback on CDT usability is
offered as an informal study of both the major high points and the
pitfalls of using the CDT for application development within the Eclipse
framework.
</p>
<p>
It should be noted that this study was done using CDT 1.1. Some of the
points below have been addressed as of the most recent development
version, and comments of that nature have been added for clarification.</p>
<!-- End of Introduction -->
<div class=section><a name="results"> 2. Results</a></div>
<p>
<div class=subsection><a name="high"> 2.1 High Points</a></div>
<p>
<table width="100%" border="1" cellpadding="5">
<tr align="left">
<th>Area/Functionality</th>
<th>Comments</th>
</tr>
<tr>
<td>Build on Save</td>
<td>Option to build on save and ability to turn this functionality
on/off is nice.</td>
</tr>
<tr>
<td>Perspective concept</td>
<td>The CDT takes good advantage of the "perspective" concept that
Eclipse uses. Toggling between perspectives while coding allows one to
quickly switch between a set of editing-related windows/views to a
different set of debugging-related windows/views. Also, the ability to
customize and save perspectives is extremely useful.
</tr>
<tr>
<td>Debugger</td>
<td>The debug perspective is very intuitive and extremely easy for a new
user to work with.</td>
</tr>
<tr>
<td>Outline View</td>
<td>A very useful tool. "Search for references" functionality is
particularly useful when changing function parameters and doing
refactoring.</td>
</tr>
<tr>
<td>Import/Export Wizards</td>
<td>Intuitive and easy to pick up.</td>
</tr>
<tr>
<td>Non-default Build Command</td>
<td>Being able to specify a non-default build command is nice. However,
there are some limitations - see pitfalls below for details.
</tr>
</table>
</p>
<div class=subsection><a name="pitfalls"> 2.2 Pitfalls</a></div>
<p>
<table width="100%" border="1" cellpadding="5">
<tr align="left">
<th>Area/Functionality</th>
<th>Comments</th>
<th>Related Defects</th>
</tr>
<tr>
<td>Task Tags</td>
<td>No support for automatic TODO or FIXME task tags as in the JDT.</td>
<td></td>
</tr>
<tr>
<td>Build Abortion</td>
<td>There isn't currently a functioning method of aborting a build once
it has been started.</td>
<td>[<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=41752">41752</a>]</td>
</tr>
<tr>
<td>Search/Replace</td>
<td>Search/Replace functionality currently does not support a tab
delimiter.</td>
<td></td>
</tr>
<tr>
<td>Makefile Reliance</td>
<td>CDT 1.1: Unlike some other IDEs, the CDT component of Eclipse
requires a Makefile in order to build a project. No standard Makefile
templates are given, so you have to learn how to write a Makefile in
order to use the CDT. Additionally, with the exception of editing it by
hand, there is no way to update an existing Makefile within the CDT.
<p><b>NOTE: </b>This is currently being addressed in development
versions of the CDT with the Managed Make Builder.</td>
<td></td>
</tr>
<tr>
<td>Code Completion</td>
<td>CDT 1.1: No support for automatic code completion as in the JDT.
<p><b>NOTE: </b>Code completion functionality is currently in
development.</td>
<td></td>
</tr>
<tr>
<td>Non-default Build Commands</td>
<td>Non-default build commands are not handled well. Non-default build
commands are assumed to be targeted build tools with 'clean' and 'all'
targets.</td>
<td>[<a
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=25979">25979</a>]</td>
</tr>
<tr>
<td>Refactoring</td>
<td>Currently no formal refactoring support as in the JDT.</td>
<td></td>
</tr>
<tr>
<td>Icons</td>
<td>No reference for the toolbar icons, etc. is available. Perhaps a
reference key should be available for users in the documentation with a
clear explanation of the icon's meaning.</td>
<td></td>
</tr>
</table>
</p>
<p>
<!-- Footer -->
<p>
<table BORDER=0 CELLPADDING=2 WIDTH="100%">
<tr>
<td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0">
</td>
</tr>
</table>
<center><I>
Last Modified on Wednesday, August 27, 2003
</I></center>
</body>
</html>