[rkward-cvs] SF.net SVN: rkward:[3272] branches/jss_dec_10/FINAL_JSS_TEX

tfry at users.sourceforge.net tfry at users.sourceforge.net
Mon Dec 20 07:41:08 UTC 2010

Revision: 3272
Author:   tfry
Date:     2010-12-20 07:41:08 +0000 (Mon, 20 Dec 2010)

Log Message:
Fix a couple of references

Modified Paths:

Modified: branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex
--- branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex	2010-12-20 01:59:34 UTC (rev 3271)
+++ branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex	2010-12-20 07:41:08 UTC (rev 3272)
@@ -1,4 +1,4 @@
-\section{User Interface Elements of the Main RKWard Window}
+\section{Main elements of the user interface}
 The default layout of the main application window is divided into five
 parts, as depicted in figure \ref{seq:refFigure1}. While many aspects
@@ -40,7 +40,7 @@
 The remainder of the central area is a single row TDI (Tab document
 interface) for different documents. Currently, the supported types of
 documents are results output (Section~\ref{sec:results_output}), spreadsheet-like data editors
-(Section~\ref{sec:}), help pages (Section~\ref{sec:help_system}), script editors (Section~\ref{sec:code_editor}), object summaries (Section XXX), and also
+(Section~\ref{sec:spreadsheet}), help pages (Section~\ref{sec:help_system}), script editors (Section~\ref{sec:code_editor}), object summaries (Section XXX), and also
 \proglang{R} onscreen graphics devices (Section~\ref{sec:technical_graphics}). Early uses of TDIs date back to 1988 and are
 widely applied nowadays \citep{Hopkins2005, MDN2010,
 KimLutteroth2010}. The order of tabs can be conveniently re-arranged
@@ -72,7 +72,7 @@
 of data manipulation and analysis features from the GUI using
 Settings/Configure RKWard/Plugins.
-\subsection{Using the \proglang{R} Console}
+\subsection{Using the R Console}
 For users with knowledge of \proglang{R}, RKWard provides direct access to the
 embedded \proglang{R} engine in the

Modified: branches/jss_dec_10/FINAL_JSS_TEX/RKWard_paper.tex
--- branches/jss_dec_10/FINAL_JSS_TEX/RKWard_paper.tex	2010-12-20 01:59:34 UTC (rev 3271)
+++ branches/jss_dec_10/FINAL_JSS_TEX/RKWard_paper.tex	2010-12-20 07:41:08 UTC (rev 3272)
@@ -4,7 +4,7 @@
 %% almost as usual
-\author{Stefan R\"odiger\\L.U.A.S. & Charit\'e
+\author{Stefan R\"odiger\\L.U.A.S. \& Charit\'e
 	\And Prasenjit Kapat\\Plus Affiliation
 	\And Meik Michalke\\Plus Affiliation
 	\And Thomas Friedrichsmeier\\Ruhr-University Bochum}
@@ -89,7 +89,6 @@
 %% end of declarations %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 %% include your article here, just as usual
@@ -98,12 +97,11 @@
 %% For the time being, each main chapter is in a separate file, so we can
 %% work in parallel, easier

Modified: branches/jss_dec_10/FINAL_JSS_TEX/background.tex
--- branches/jss_dec_10/FINAL_JSS_TEX/background.tex	2010-12-20 01:59:34 UTC (rev 3271)
+++ branches/jss_dec_10/FINAL_JSS_TEX/background.tex	2010-12-20 07:41:08 UTC (rev 3272)
@@ -33,7 +33,7 @@
 or by allowing to implement routinely performed tasks as a GUI element. In
 addition, many features, such as the integrated data editor, or the plot preview
 feature will be useful to \proglang{R} novices and \proglang{R} experts alike in their everyday work
-(see section \ref{sec:usage}).
+(see section \ref{sec:results_output}).
 %% TODO: TF: I have edited this section (and the following) a bit more. Please take a look.
 RKWard provides a high level of transparency about the steps that are needed to
@@ -56,7 +56,7 @@
 artificial limitations on how users can work with the application. For example,
 the user is not limited to using only one \code{data.frame} or one model at a
 time, in RKWard. RKWard is designed to allow users to create custom GUI dialogs
-easily (see sections \ref{sec:technical_plugins} and \ref{sec:example_plugins}).
+easily (see sections \ref{sec:technical_plugins} and \ref{sec:example_plugin}).
 %% TODO: TF: I've removed the reference to ``Beta''-status. It's just an arbitrary estimate without a real definition, anyway.
 %% Please take a look at the wording I have added, instead.

Modified: branches/jss_dec_10/FINAL_JSS_TEX/technical.tex
--- branches/jss_dec_10/FINAL_JSS_TEX/technical.tex	2010-12-20 01:59:34 UTC (rev 3271)
+++ branches/jss_dec_10/FINAL_JSS_TEX/technical.tex	2010-12-20 07:41:08 UTC (rev 3272)
@@ -13,7 +13,7 @@
 time-consuming analyses. For instance while waiting for the estimation of a
 complex model to complete, the user should be able to continue to use the GUI to
 prepare the next analysis. Asynchronous command execution is also a prerequisite
-for a implementation of the plot-preview feature (see Section~\ref{sec:usage_plotpreview}). Commands
+for a implementation of the plot-preview feature (see Section~\ref{sec:plot_previews}). Commands
 generated from plugins or user actions are placed in queue and are evaluated in
 a separate thread in the order they were submitted\footnote{
     It is possible, and in some cases necessary to enforce a different order of command execution in
@@ -27,7 +27,7 @@
 A further implication is that RKWard avoids quering information about the
 existence and properties of objects in \proglang{R}, interactively. Rather
 RKWard keeps a representation of \proglang{R} objects and their basic properties
-(e.g. class and dimensions), which is used for the workspace browser (Section~\ref{sec:usage_browser}),
+(e.g. class and dimensions), which is used for the workspace browser (Section~\ref{sec:workspace_browser_object_viewer}),
 object name completion, function argument hinting and
 other occasions. The object representation includes objects in all environments
 on the search path, and any objects contained within these environments in a
@@ -62,7 +62,7 @@
 workspace browser, object selection lists, and object views. Beyond that,
 detecting any changes is particularly important with respect to objects which
 are currently opened for editing in the data editor (which provides an illusion
-of in-place editing, see Section~\ref{sec:usage_dataeditor}). Here, it is necessary to synchronize
+of in-place editing, see Section~\ref{sec:spreadsheet}). Here, it is necessary to synchronize
 the data between \proglang{R} and the GUI in both directions.
 For simplicity and performance, object modification detection is only
@@ -183,7 +183,7 @@
 The actual plotting calls are tracked using appropriate \code{sys.call()} commands in
 the hooks. These call strings are displayed as a drop-down menu on the toolbar
-for non-sequential browsing (see Figure~\ref{fig:plot_history}) providing a very intuitive browsing
+for non-sequential browsing (see Figure~\ref{fig:refFigure5}) providing a very intuitive browsing
 interface unlike the implementation for windows or quartz devices.
 \subsection{Plugin infrastructure}

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

More information about the rkward-tracker mailing list