-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathppig17.tex
79 lines (67 loc) · 3.36 KB
/
ppig17.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
\documentclass{ppig}
\usepackage{epsfig, graphicx} % support for image encoding and manipulation
\usepackage{ucs} % support for using UTF-8 as input encoding in LaTeX
\usepackage[utf8x]{inputenc} % required for UTF-8 support with ucs.sty
\usepackage{tabularx, multirow, booktabs} % support for high-quality tables
\usepackage{csquotes} % support for block quotes (using displayquote command)
\let\cite\shortcite % use short-form (first author et al.) for citations
% The titlebox defines how much vertical space is given for
% the authors' list. If you need extra space to show all the
% authors, uncomment the line below and increase the value. Please
% do not make the titlebox smaller than the original size of 5cm.
%\setlength\titlebox{5cm}
%\title{An Examination of IDE Design for Programming as Problem-Solving}
\title{Towards an IDE to Support Programming as Problem-Solving}
% List the authors like you would in a table.
% The \And command creates another author's column. Use it after the
% details of one author to separate them from the following author horizontally.
% The \AND command creates a new "row" of authors and it should be used
% when the authors don't fit on the same line. You may have to increase
% the titlebox so that the author's don't overlap with the abstract.
\author{Nicholas Nelson \\
EECS \\
Oregon State University \\
nelsonni@oregonstate.edu \\
\And
Anita Sarma \\
EECS\\
% Electrical Engineering \&\\ Computer Science \\
Oregon State University \\
anita.sarma@oregonstate.edu \\
\And
André van der Hoek \\
Department of Informatics \\
University of California, Irvine \\
andre@ics.uci.edu
}
\date{\today}
% Packages and macros for editorial purposes. Not required for submission.
\usepackage{color}
\definecolor{darkgreen}{rgb}{0.0, 0.5, 0.0}
\definecolor{ballblue}{rgb}{0.13, 0.67, 0.8}
\definecolor{aoblue}{rgb}{0.0, 0.0, 1.0}
\newcommand{\bold}[1]{\textit{\textbf{\color{aoblue}#1}}} % macro for boldifications
\newcommand{\todo}[1]{\textit{\textbf{\color{red}TODO: #1}}} % macro for TODO items
\newcommand{\discuss}[1]{\textit{\textbf{\color{darkgreen}#1}}} % macro for in-line discussions/questions
\newcommand{\nameUI}{\textit{<Insert Name>} UI} % macro placeholder for the name of the UI
\usepackage{enumitem}
\begin{document}
\maketitle
\thispagestyle{empty}
\begin{abstract}
Programming is inherently a problem-solving exercise: A programmer has to create an understanding of the situation, externalize and contextualize thoughts and ideas, develop strategies on how to proceed with the task, enact changes according to the most appropriate strategy, and reflect to learn from each problem.
Therefore, programming is clearly more than just code input, testing, and maintenance.
Current Integrated Development Environments (IDE), however, largely focus on the "writing code" parts of programming.
In this position paper, we revisit which activities and actions constitute programming, and highlight six challenges to supporting these activities.
We then briefly describe a new paradigm of interacting with the IDE on which we are working to more directly support each of the six activities.
\end{abstract}
\section{Programming as Problem-Solving}
\input{intro}
\section{Challenges}\label{challenges}
\input{challenges}
\input{figure_ide}
\section{Toward A New IDE}
\input{new_ide}
\bibliography{bibliography}
\bibliographystyle{apacite}
\end{document}