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

Tue Dec 21 08:56:49 UTC 2010

Revision: 3291
          http://rkward.svn.sourceforge.net/rkward/?rev=3291&view=rev
Author:   tfry
Date:     2010-12-21 08:56:49 +0000 (Tue, 21 Dec 2010)

Log Message:
-----------
Minor correctin of caption, and move R console section. Since R console shares many features with the script editor, I'm placing it directly after that section.

Modified Paths:
--------------
    branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex
    branches/jss_dec_10/FINAL_JSS_TEX/conclusion_summary_acknowledgments.tex

Modified: branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex
===================================================================

--- branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex	2010-12-21 08:37:25 UTC (rev 3290)
+++ branches/jss_dec_10/FINAL_JSS_TEX/GUI_elements.tex	2010-12-21 08:56:49 UTC (rev 3291)
@@ -90,29 +90,6 @@
 of data manipulation and analysis features from the GUI using
 ''Settings->Configure RKWard/Plugins``.
 
-\subsection{Using the R console}
-\label{sec:using_R_console}
-For users with knowledge of \proglang{R}, RKWard provides direct access to the
-embedded \proglang{R} engine in the
-\proglang{R} Console tool window. It is important to note that technically this is an
-emulation of \proglang{R} running in a console
-session, not a real \proglang{R} session. This leads to a few subtle
-differences, e.g. with respect to the command history-feature in
-\proglang{R}. For most purposes, the \proglang{R} Console in RKWard can be used exactly
-like \proglang{R} running in a terminal.
-
-The \proglang{R} Console in RKWard provides many of the
-features which are also available in the code editor (see Section~\ref{sec:code_editor}).
-Most prominently, it also supports syntax highlighting and code
-folding, function argument hinting, object-name completion, and pasting
-vector or matrix data directly from the clipboard.
-
-By default, any code that is submitted to the
-\proglang{R} engine from the code-editor or from help
-pages is sent through the \proglang{R} Console,
-however, it can also be configured to the submitted in the background,
-instead.
-
 \subsection{Workspace browser and object viewer}
 \label{sec:workspace_browser_object_viewer}
 
@@ -197,8 +174,8 @@
 \begin{figure}[htp]
  \centering
  \includegraphics{../figures/code_hinting.png}
- \caption{Code hinting features of the script editor. The script editor is able to hint A) \proglang{R} functions
-and B) arguments.}
+ \caption{Code hinting features of the script editor. The script editor is able to hint A) \proglang{R} object names
+and B) function arguments.}
  \label{fig:code_hinting}
 \end{figure}
 
@@ -222,6 +199,29 @@
 \code{file.edit()}, \code{file.show()} or \code{fix()}
 commands.
 
+\subsection{Using the R console}
+\label{sec:using_R_console}
+For users with knowledge of \proglang{R}, RKWard provides direct access to the
+embedded \proglang{R} engine in the
+\proglang{R} Console tool window. It is important to note that technically this is an
+emulation of \proglang{R} running in a console
+session, not a real \proglang{R} session. This leads to a few subtle
+differences, e.g. with respect to the command history-feature in
+\proglang{R}. For most purposes, the \proglang{R} Console in RKWard can be used exactly
+like \proglang{R} running in a terminal.
+
+The \proglang{R} Console in RKWard provides many of the
+features which are also available in the code editor (see Section~\ref{sec:code_editor}).
+Most prominently, it also supports syntax highlighting and code
+folding, function argument hinting, object-name completion, and pasting
+vector or matrix data directly from the clipboard.
+
+By default, any code that is submitted to the
+\proglang{R} engine from the code-editor or from help
+pages is sent through the \proglang{R} Console,
+however, it can also be configured to the submitted in the background,
+instead.
+
 \subsection{Spreadsheet-like data editor}
 \label{sec:spreadsheet}
 

Modified: branches/jss_dec_10/FINAL_JSS_TEX/conclusion_summary_acknowledgments.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/conclusion_summary_acknowledgments.tex	2010-12-21 08:37:25 UTC (rev 3290)
+++ branches/jss_dec_10/FINAL_JSS_TEX/conclusion_summary_acknowledgments.tex	2010-12-21 08:56:49 UTC (rev 3291)
@@ -3,14 +3,28 @@
 In this article we have introduced the RKWard GUI to \proglang{R}. RKWard provides features ranging
 from easy to use dialogs for common statistical procedures, targetted at \proglang{R} novices, to advanced
 IDE features targetted at \proglang{R} experts.
-The RKWard development 
-does not focus on \proglang{R} package development, except those internally 
-required for RKWard, but keeps it at the \proglang{R} community. This design brings the intrinsic 
-benefit of highly accurate results since calculations entirely rely on \proglang{R} code. 
-Comparison of the commonly used spreadsheet applications 
-regarding estimation, random number generation and statistical distributions revealed serious 
-limitations. \proglang{R} in contrast was found to be a reliable and accurate statistical 
-software package \citep{Almiron2009, Almiron2010}.
+
+RKWard tries to empower users of all knowledge levels to make more efficient use of the 
+\proglang{R} programming language, while carefully avoiding to lock in users to a specific
+GUI solution. In particular, RKWard
+\begin{itemize}
+ \item provides full transparency about the \proglang{R} code that is used to carry out tasks.
+ \item avoids introducing RKWard-specific \proglang{R} functions for central functionality (but uses some for output formatting).
+ \item avoids hard dependencies on third-party \proglang{R} packages.
+ \item uses standard \proglang{R} formats \citep[cf.][]{RDCT2010c} for data storage, and open standards (\proglang{HTML}, \proglang{PNG}, \proglang{SVG}) for storage of output.
+\end{itemize}
+
+%% TF: I don't think this comparison is entirely fair. Keep in mind that this is is a special issue about R GUIs.
+%% So all those GUIs will base their calculations on R. But some will do it more transparently than others.
+%The RKWard development 
+%does not focus on \proglang{R} package development, except those internally 
+%required for RKWard, but keeps it at the \proglang{R} community. This design brings the intrinsic 
+%benefit of highly accurate results since calculations entirely rely on \proglang{R} code. 
+%Comparison of the commonly used spreadsheet applications 
+%regarding estimation, random number generation and statistical distributions revealed serious 
+%limitations. \proglang{R} in contrast was found to be a reliable and accurate statistical 
+%software package \citep{Almiron2009, Almiron2010}.
+
 \proglang{R} scripts which are routinely in use or require complex steps can be programmed as GUI 
 elements in RKWard. Due to its plugin architecture RKWard provides the basis 
 for a highly customizable \proglang{R}-GUI. We show that the plugin development can take place 
@@ -18,10 +32,6 @@
 Current developments also targets plugin development via external canals like 
 GHNS (Get Hot New Stuff)\footnote{\url{http://ghns.freedesktop.org/}} independently of the 
 RKWard plugin development. 
-Basically all \proglang{R} functions can be provided with GUIs.
-The exclusive use of standard-complient formats (e.g. \proglang{HTML}, PNG) 
-and sole use of \proglang{R} formats (\proglang{R} Data Files \citep{RDCT2010c}) 
-guarantees cross-platform interoperability.
 Future versions of RKWard will continue to add value for both groups of users. Planned features include
 an enhanced interface for debugging \proglang{R} code, support for editing more types of data, and the
 ability to connect the RKWard GUI to a remote \proglang{R} engine. Perhaps most importantly, RKWard will


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


