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

Fri May 20 10:21:30 UTC 2011

Revision: 3585
          http://rkward.svn.sourceforge.net/rkward/?rev=3585&view=rev
Author:   tfry
Date:     2011-05-20 10:21:30 +0000 (Fri, 20 May 2011)

Log Message:
-----------
Fix / remove references to sections / figures of the main article

Modified Paths:
--------------
    branches/jss_dec_10/FINAL_JSS_TEX/FINAL_splitted/example_plugin.tex
    branches/jss_dec_10/FINAL_JSS_TEX/FINAL_splitted/technical.tex

Modified: branches/jss_dec_10/FINAL_JSS_TEX/FINAL_splitted/example_plugin.tex
===================================================================

--- branches/jss_dec_10/FINAL_JSS_TEX/FINAL_splitted/example_plugin.tex	2011-05-20 08:59:43 UTC (rev 3584)
+++ branches/jss_dec_10/FINAL_JSS_TEX/FINAL_splitted/example_plugin.tex	2011-05-20 10:21:30 UTC (rev 3585)
@@ -56,7 +56,9 @@
 In this example, the ``Assume equal variances'' checkbox is only enabled for paired sample tests.
 Optionally, GUI behavior can also be scripted in \proglang{ECMAScript}.
 
-The XML file defines the t-test plugin (\code{<!DOCTYPE rkplugin>}) to be organized in two tabs (Figure~\ref{fig:t_test}A).
+The XML file defines the t-test plugin (\code{<!DOCTYPE rkplugin>}) to be organized in two tabs\footnote{
+  A screenshot of the resulting dialog can be found the in the main article.
+}.
 On the first tab, two variables can be selected (\code{<varslot .../>}). These are set to be ``required'', i.\,e.,
 the ``Submit'' button will remain disabled until the user has made a valid selection for both. The second tab includes some
 additional settings like the confidence level (default 0.95).
@@ -110,9 +112,7 @@
 
 \subsection[Generating R code from GUI settings]{Generating \proglang{R} code from GUI settings}
 \label{sec:generating_r_code_from_ui_settings}
-A simple \proglang{ECMAScript} script is used to generate \proglang{R} code from GUI settings (using \code{echo()} commands)\footnote{
-  See Figure~\ref{fig:t_test}A) for code generated in this example.
-}. Generated code for each plugin is divided into three sections: ``Preprocess'', ``Calculate'', and ``Printout'', although each
+A simple \proglang{ECMAScript} script is used to generate \proglang{R} code from GUI settings (using \code{echo()} commands). Generated code for each plugin is divided into three sections: ``Preprocess'', ``Calculate'', and ``Printout'', although each
 may be empty.
 
 \begin{footnotesize}

Modified: branches/jss_dec_10/FINAL_JSS_TEX/FINAL_splitted/technical.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/FINAL_splitted/technical.tex	2011-05-20 08:59:43 UTC (rev 3584)
+++ branches/jss_dec_10/FINAL_JSS_TEX/FINAL_splitted/technical.tex	2011-05-20 10:21:30 UTC (rev 3585)
@@ -14,7 +14,8 @@
 time-consuming analysis. 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 an implementation of the plot-preview feature (see Section~\ref{sec:plot_previews}). Commands
+for an implementation of the plot-preview feature (see the section no graphics windows
+in the main article). 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
@@ -28,7 +29,7 @@
 A further implication is that \pkg{RKWard} avoids querying information about the
 existence and properties of objects in \proglang{R} interactively. Rather,
 \pkg{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:workspace_browser_object_viewer}),
+(e.\,g., class and dimensions), which is used for the workspace browser,
 object name completion, function argument hinting, and
 other places. The object representation includes objects in all environments
 in the search path, and any objects contained within these environments in a
@@ -69,7 +70,8 @@
 workspace browser, object selection lists, and object views. Beyond that,
 detecting any changes is particularly important with respect to objects which
 are currently being edited in the data editor (which provides an illusion
-of in-place editing, see Section~\ref{sec:spreadsheet}). Here, it is necessary to synchronize
+of in-place editing, see the section on the spreadsheet-like data editor in the
+main article). 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
@@ -179,7 +181,8 @@
 and behaves independently when recording a new plot or deleting an existing
 one.
 
-The \pkg{lattice} system \citep[see also][]{Sarkar2008} is implemented by inserting a hook in the \code{print.lattice()}
+Plot history support for the
+\pkg{lattice} system \citep[see also][]{Sarkar2008} is implemented by inserting a hook in the \code{print.lattice()}
 function. This hook retrieves and stores the \code{lattice.status} object from the
 \code{lattice:::.LatticeEnv} environment, thereby making \code{update()} calls on trellis
 objects transparent to the user. Any recorded trellis object is then replayed
@@ -191,7 +194,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 the section on graphics windows in the main article) providing a very intuitive browsing
 interface unlike the native implementations in \code{windows()} and \code{quartz()} devices.
 
 \subsection{Plugin infrastructure}
@@ -308,7 +311,7 @@
 \code{HTML()} function of the \pkg{R2HTML} package \citep{Lecoutre2003} in the current
 implementation. The use of custom formatting with HTML is possible, but
 discouraged. Standard elements such as a horizontal separator, and the ``Run again''
-link (see Section~\ref{sec:results_output}) are inserted automatically, without the need to define
+link (see the section on the results output in the main article) are inserted automatically, without the need to define
 them for each plugin.
 
 Regarding the style of the generated \proglang{R} code, enforcing consistency is harder,
@@ -346,7 +349,7 @@
 plugins which depend on a certain package simply include an appropriate call to
 \code{require()} in the pre-processing section of the generated \proglang{R} code. The \code{require()}
 function is overloaded in \pkg{RKWard}, in order to bring up the package-installation
-dialog (see Section~\ref{sec:package_management}) whenever needed. Packages invoked by \code{require()} remain loaded
+dialog whenever needed. Packages invoked by \code{require()} remain loaded
 in the active \pkg{RKWard} session unless unloaded manually (from the workspace browser, or using the
 \proglang{R} function \code{detach()}).
 


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


