You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: progNav Paper/progNav Paper.tex
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ \section{Introduction}
82
82
We will refer to these two concepts together as \textit{program flow}.
83
83
84
84
To realize their ideal program flow navigation strategies, developers rely on navigation tools that expose the links between sometimes distant locations in the source code.
85
-
Many existing tools do so by displaying call graph visualizations or adding views to the the screen.
85
+
Many existing tools do so by displaying call graph visualizations or adding views to the screen.
86
86
In general, evaluations have demonstrated the effectiveness of such tools ~\cite{Reacher,Whyline,Relo,Stacksplorer}.
87
87
88
88
However, these tools rely on cumbersome user interface widgets that new users might struggle to understand and occupy valuable screen real estate.
@@ -163,7 +163,7 @@ \section{Design Principles}
163
163
\section{Related Work}
164
164
%Summary of related work, including a table evaluating existing %tools on various design principles.
165
165
%Spoiler alert, none of the tools satisfy all of the principles.
166
-
Here we discuss some of the existing tools that help developers navigate code. We also relate the exiting tools back to Design Principles Described in Section \ref{DesignPrinciples}.
166
+
Here we discuss some of the existing tools that help developers navigate code. We also relate the existing tools back to Design Principles Described in Section \ref{DesignPrinciples}.
167
167
168
168
Many modern IDEs provide tools that help developers navigate source code.
169
169
For example, Eclipse~\cite{Eclipse} includes \emph{Call Hierarchy} and \emph{Find References}.
@@ -238,7 +238,7 @@ \section{Flower}
238
238
239
239
When active, Flower makes two modifications to Eclipse's user interface.
240
240
First, it highlights on-screen references to selected variables.
241
-
Secondly, when references to the selected variable appear off-screen -- either elsewhere in the current method or in other methods -- Flower adds links to those locations above and bellow the code view as well as to the code itself.
241
+
Secondly, when references to the selected variable appear off-screen -- either elsewhere in the current method or in other methods -- Flower adds links to those locations above and below the code view as well as to the code itself.
242
242
Figure \ref{fig:tool} depicts Flower invoked on a variable participants were asked to inspect as part of our evaluation. We also provide a video demonstrating Flower online.\footnote{Screen cast of Flower in action: \url{tinyurl.com/FlowerDemo}} To visualize how a programmer would interact with Flower, consider the following scenario:
243
243
244
244
Suppose you are a programmer and you notice that by tampering with the value of the \texttt{fileName} variable, malicious users could gain access to sensitive information in the database.
0 commit comments